In every other small manufacturing, trading or service company we walk into, the critical operational process runs on Excel. Not on the ERP. Not on the CRM. On a single file with twenty tabs that nobody wants to touch, because everybody is scared of it.
This isn't pathology — it's the natural way things grow. Somebody built a sheet to track orders back in 2014. It worked great for 30 orders a month. In 2020 it was handling 300. Today it processes 1,500, has 47 tabs, a VBA macro that even its author doesn't fully understand, and it's the only place where you can see how much the company actually earned.
The point isn't to ditch Excel. The point is to recognise the moment when the spreadsheet stops being a tool and becomes a risk — and to leave it before it blows up.
Signs Excel has outgrown you
There are a few concrete symptoms. If three of these sound familiar, you have a problem:
- Only one person in the company can really operate the key file. When they go on holiday, part of the business stops.
- The file has more than 20 tabs or weighs over 30 MB. It takes 40 seconds to open, runs slow, sometimes freezes.
- Several people edit it in parallel even though they shouldn't. Every so often someone has to merge changes by hand from two copies.
- Nobody knows who changed cell B17 in the "2024-Q3" tab. The version history is filenames:
orders_v17_FINAL_really_final_KK.xlsx. - Excel drives money, but there's no backup newer than a day. Actually, there's only OneDrive — because "it syncs, doesn't it?".
- Data has to be copied by hand between the sheet and the ERP (Comarch Optima, Subiekt, enova365), because the two systems don't know about each other.
These aren't Excel's flaws. They're symptoms that the process has outgrown the tool.
What you're losing without realising
The cost of Excel-as-a-system is invisible until somebody measures it. Three categories of waste come back almost every time:
Time. Manual copying between the sheet and the ERP typically takes 30–60 minutes per person per day. In an eight-person back office that's four hours a day — half a full-time job that nobody is booking.
Errors. A figure typed into the wrong tab, a formula that didn't get pulled down, a macro that stopped working after the last Office update. Every mistake costs. Sometimes a thousand zloty, sometimes a complaint from a strategic customer.
Decisions. The board looks at a two-week-old report because nobody had time to "refresh the file". Pricing, stock levels, sales bonuses — all delayed, because the data is buried in tabs rather than living in a system.
A real example
One of our clients — a 25-person industrial parts wholesaler in western Poland — ran their entire order process through a single file, Orders_2025.xlsx, with 47 tabs and two macros. Five people from the back office edited it in parallel. About once a week the file fell apart and someone had to manually reconcile two OneDrive versions — an hour's work plus the stress of wondering what got lost. Issuing a single order took on average eight minutes, because data had to be retyped from the sheet into Comarch Optima, then from Optima onto the shipping label.
We built them a simple web app in .NET on top of SQL Server, integrated with Optima via API. Three months of work, one developer and our analyst on the process side. After go-live: issuing an order takes 90 seconds, no orders go missing, and their PLN 23 million annual turnover no longer depends on whether someone remembered to save the Excel before logging off. The project paid for itself in 11 months from saved back-office time alone.
This wasn't a 400-thousand-zloty ERP migration. It was one application wrapped around one process where the company was bleeding money.
The most common Excel-migration mistakes
Leaving Excel is a project where it's easy to make a mistake more expensive than staying put. The four we see most often:
- Jumping straight to a big ERP. Instead of closing out one painful process, the company buys a system that does "everything". The rollout drags on for eighteen months, the team rebels, Excel stays alongside the ERP as shadow IT. The size of the disaster depends only on the licence fee.
- A 1:1 migration. The new app mirrors all 47 Excel tabs, including the quirks that grew because "that's just how it was always done". In the new system those quirks are even harder to change than in a spreadsheet.
- Skipping the ERP integration. You build a web app but leave the manual re-keying into Comarch Optima in place. Half the pain stays, the project budget is already spent.
- No process owner on the client side. The developer doesn't really know how the back office works. Without somebody who sits with the team for three hours a week, you end up with an application nobody wants to use.
Where to start
If your Excel is starting to hit three of the signals from the first list, begin with three steps before you even start picking technology.
- Pick ONE process where the spreadsheet hurts most. Not "everything". One.
- Measure the current state: how long it takes, how many errors you catch a month, how often per week the file falls apart. Without those numbers you'll never prove the new system delivered anything.
- Write the process down on paper step by step — no Excel, no system, just a sequence of human decisions. If you can't do that in an hour, the process itself is broken, not just the tool.
Only then is it worth asking somebody like us whether the answer is a web app, a module inside your existing ERP, or maybe a small integration that keeps Excel as a front end but plugs a proper database in behind it.
Excel stays in the company. It just stops being the company's system.
Leaving Excel isn't about buying a bigger system. It's about understanding which process outgrew the tool — and closing out that one.