Blog
Signs a spreadsheet should no longer run your operation.
In short. A spreadsheet stops being enough when several people depend on it at the same time, when nobody knows which version is right, or when operations stall if the one person who understands it is out. At that point there are three paths —clean up the sheet, adopt an off-the-shelf product, or build a custom platform— and the choice depends on how specific your process is.
The spreadsheet is not the problem
Spreadsheets are among the most useful tools there are for analyzing data, testing an idea, or getting a new process off the ground. Almost every system we have built started as a spreadsheet that worked well for years.
The problem starts when the sheet stops being one person’s tool and becomes, without anyone deciding it, the system the whole operation depends on.
The signs
If you recognize three or more of these, the spreadsheet is already doing a system’s job:
- Several copies circulate and someone has to decide which one is “the real one”.
- File names carry “final”, “v3”, or a date, and there are still doubts.
- The same data is entered twice: in the sheet and in another system or an email.
- There are macros or formulas only one person understands, and their absence stops the process.
- There is no way to know who changed a value, or when.
- A report leadership asks for every week takes days to put together.
- Approvals live in emails and chat messages, outside any record.
- Personal or sensitive data sits in files that get forwarded without access control.
- A formula error has already led to a wrong decision.
What to do before building anything
The most common mistake is moving the spreadsheet as-is onto a screen. The sheet reflects how the team adapted to a limited tool, not necessarily how the process should work. Before deciding, document:
- The real process, step by step, including the exceptions that are handled “by hand” today.
- Who enters data, who reviews, who approves, and who only looks.
- The business rules hidden in formulas and validations.
- Master data —customers, products, catalogs— and who owns each one.
- Which reports are actually used to make decisions, and which are produced out of habit.
Three possible paths
Clean up the spreadsheet. If the problem is discipline more than tooling, a single shared sheet with validations, permissions, and an owner can be enough for quite a while. It is the fastest option, and worth ruling out before the other two.
Adopt an off-the-shelf product. If your process looks like many other companies’ —invoicing, basic inventory, sales—, an existing product solves it without development. The price is adapting the way you work to the way the product works.
Build a custom platform. It makes sense when the process is your own, when it is part of what sets you apart, or when it has to integrate with systems no product connects well. Our first custom system was exactly that: an ERP built on a client’s actual business rules, not on a generic product’s.
How to start without a huge project
You do not need to replace everything at once. We recommend starting with the workflow that hurts the most, with only the data that workflow needs, and leaving the rest in the spreadsheet for now. A first module in production teaches more than any requirements document.
And the spreadsheet does not disappear: a good platform still lets you export to Excel. The difference is that the sheet goes back to being an analysis tool and stops being the place where the truth lives.