Almost every company has one of these sheets. It started as someone's private notes, over time three more people started using it, and today something important depends on it: orders, schedules, billing, stock. Nobody planned it as a system, but it behaves like one.
Excel isn't the problem. The problem is the moment the sheet outgrows what Excel is good at, and nobody notices until it breaks.
Signs the sheet has outgrown itself
You don't need all of them. Three of these are enough:
There's a "master" version and nobody is quite sure which one it is. schedule_final.xlsx, schedule_final_2.xlsx and schedule_final_NEW.xlsx are all going around.
One person is the only one who knows how it works. When that person is on holiday, part of the work stops. This is the most serious sign and usually the one ignored the longest.
Opening it takes a while. The sheet takes seconds to load, formulas recalculate, someone has turned off automatic calculation just to be able to work.
The same data is entered in two places. A number from the sheet is retyped into another system, or the other way round.
Mistakes have started happening. Someone retyped the wrong row, a formula got stretched over the wrong range, a filter was left on so half the data was invisible.
Several people are in it at once. A shared sheet in the cloud solves this to a point, but two people editing the same row is still a problem.
There's no history. Nobody can say who changed a number or when, and the change matters.
What happens when it breaks
A sheet rarely breaks dramatically. Usually it goes quietly:
- Someone accidentally sorted one column without the others, and the data no longer belongs to its rows. You don't see it straight away.
- The file gets corrupted and the last version that opens is three weeks old.
- The person who ran it has left, and with them the knowledge of what each tab means.
In all three cases the cost isn't in the sheet but in what depended on it: orders that can't be reconstructed, billing done from scratch, a customer left waiting.
What an internal tool does differently
A custom internal tool isn't "Excel with a nicer interface". The difference is in a few things Excel by its nature doesn't do:
The data has rules. A quantity field takes a number. A date field takes a date. A code that doesn't exist can't be entered. A large share of mistakes disappears at that level.
One version, several people. No copies going around by email. Everyone sees the same state.
Who changed what, and when. The change history is built in, not something someone remembers.
Access levels. The warehouse worker sees stock, not margins.
Reports put themselves together. What's now done by hand on Monday morning becomes a screen that's always correct.
Connections to other systems. Data that's now retyped by hand can travel on its own.
What the switch looks like
You don't start from zero and you don't do it all at once.
- First you look at the existing sheet. It's the best documentation of the process there is: it holds every rule someone came up with over the years, including the ones nobody wrote down.
- Separate what matters from what's legacy. Some columns have been filled in for years and nobody looks at them anymore.
- The data is moved over and cleaned up. This step is routinely underestimated. If the sheet has three ways of writing the same name, that has to be sorted out before anything starts.
- The tool runs alongside the sheet, not instead of it. Two to three weeks of working in parallel show what was missed while it's still cheap to fix.
- The sheet is switched off only when the tool works.
How much it costs
It depends on what the sheet does. Replacing one sheet with a clear process behind it is in the range of €800 to €3,000. Simpler automation that takes one repeating job off your hands starts at €300.
The payback maths and the breakdown by level are in what goes into the price of automation.
When to leave the sheet alone
The honest side:
- One person uses it and it works. There's no reason to touch it.
- The process is still taking shape. Excel is great for thinking out loud while you don't yet know how the work will go. A tool is built once the process settles.
- It's done rarely. Something done twice a year doesn't need a system.
Excel is still one of the best tools there is for what it's meant for. The problem starts when it's used as a multi-user database, because it never even tried to be one.
Frequently asked questions
Do we have to stop using Excel completely?
No. Export to Excel is almost always part of the tool: for the accountant, for reports, for sending to someone outside the company.
What about the data in the old sheets?
It's moved over. That's part of the work and included in the project.
How long does it take?
Three to six weeks in most cases, depending on how much existing data there is and how tidy it is.
Who owns the tool?
You do. The code is yours, with no subscription for the tool itself and no per-user fees. The comparison with off-the-shelf products is in internal tools or another SaaS subscription.
Where to start
If while reading this you thought "that's our sheet", send it over. It shows almost everything needed for an estimate.
Describe your case or see what I've built.