When Excel becomes the ERP: when custom software makes sense
Excel is flexible — until critical workflows, knowledge and decisions depend on individual files. Five signals that a dedicated system may be the better option.
In industrial companies, Excel is often not the problem. At first, it is the fastest solution to a real problem: immediately available, flexible and easy for domain teams to adapt.
It becomes risky when a pragmatic workaround slowly turns into a business-critical core system.
Five common warning signs
- Several versions of the same file circulate at the same time.
- Only a few people fully understand formulas, macros or exceptions.
- Data must regularly be copied from ERP, email or other systems.
- Status information is already outdated by the time a meeting starts.
- New requirements make the file slower and more fragile.
Do not replace Excel — understand the process
A useful software project does not start with “How do we rebuild this spreadsheet as a web app?”. The key question is which decision or workflow the spreadsheet represents.
That analysis often leads to clearer data models, roles, approvals and interfaces. A custom system can then consume information from existing sources, model the specialist workflow and return results to systems of record.
Custom software is not an end in itself
Not every spreadsheet deserves its own application. If a process is rare, stable and isolated, Excel may be completely sufficient. Custom software becomes relevant where errors, missing visibility, speed or dependency on individuals has a real operational cost.
That business case should be tested before the first development sprint.