Data & documents
Critical work running on disconnected spreadsheets
Somewhere in your company there is a workbook with fifteen tabs that the operation cannot run without. One person built it, one person understands it, and it has no permissions, no validation, no backup plan, and no owner in IT. It is, by any honest definition, business-critical software. It is also a spreadsheet.
Nobody decided this. The spreadsheet filled a gap the real systems left open, and it kept filling it for years.
What it looks like
- The pricing spreadsheet and the ERP disagree, and the only way to know which is current is to ask the person who maintains the spreadsheet.
- Files named FINAL_v7_REVISED get emailed around, and two people edit their own copies, then reconcile by phone.
- The scheduler, the buyer, or the service coordinator takes a week of vacation and a process stops with them—the workbook is in their head as much as on their drive.
- A formula breaks, or a row gets sorted wrong, and the mistake travels downstream for days before anyone connects it to the spreadsheet.
- Every department keeps its own version of the same truth—customer lists, price tables, equipment status—and none of them match.
Why it happens
Spreadsheets did not take over because people love spreadsheets. They took over because the work they do—special pricing logic, scheduling, tracking, reconciliation—needed doing and no system did it. The spreadsheet was the only tool flexible enough to start today.
The problem is what spreadsheets lack as they grow into systems: no validation, so bad data enters silently; no permissions, so anyone can change anything; no history, so mistakes can't be traced; and no shared state, so copies multiply. Each department's copy becomes its own version of the truth, and the company's real system of record is whichever version the most confident person is holding.
What it costs
The honest answer is that it depends on your volumes, your margins, and how long it has been going on. What is consistent across companies is where the cost shows up:
Labor
Hours each week go to maintaining, copying, and reconciling spreadsheets—skilled people doing data janitorial work.
Errors with reach
One bad formula or stale price table propagates into quotes, orders, and invoices before anyone notices the source.
Key-person risk
When the workbook's author leaves, you inherit a system with no documentation and no one who knows why column N exists.
Decisions on wrong numbers
Leadership reads reports assembled from competing versions of the truth—and argues about whose number is right instead of what to do.
How a purpose-built system fixes it
The fix is not banning spreadsheets—it is promoting the ones that became systems. A purpose-built internal tool keeps the exact fields, logic, and views your team already knows, because it is modeled on the workbook they built. What changes is everything the spreadsheet could not give them.
Data enters through validated forms instead of free cells. Changes are recorded with who and when. Everyone looks at the same current version because there is only one. And the pricing logic or scheduling rules live in the system, documented by its behavior—not in one person's memory.
Illustrative Workflow
Teams rarely mourn the spreadsheet. They built it because they had to, and they keep the part they actually liked—the logic—while losing the fragility.
When a simpler fix is enough
If a spreadsheet is genuinely single-user reference data—a lookup table one person maintains—it is fine. Leave it. The problem is multi-user operational truth: many editors, downstream consequences, no tolerance for stale copies.
Sometimes the honest fix is discipline, not software: one shared workbook in one location, locked structure, a named owner. But when a workbook has crossed into being business-critical software, and the question is when—not if—it breaks, it deserves a real home: a purpose-built internal tool.
Related systems and industries
- Custom internal toolsThe spreadsheet's logic rebuilt as a real system—validation, permissions, history.
- Internal portalsOne place each role sees their current version of the truth.
- Wholesale distributionWhere pricing workbooks and buying spreadsheets quietly run the business.
- Contract manufacturingWhere scheduling and quoting workbooks carry the whole plan.
Common questions
- They love what the spreadsheet lets them do, not the fragility. The smoothest projects we see keep the team's exact logic and views—modeled directly on their workbook—and remove only the parts that hurt: version chaos, broken formulas, re-keying. Adoption is easy when the tool is recognizably theirs.
- A shared drive fixes the copies problem but not validation, permissions, or history—and adds the 'who has it open' problem. BI tools read data well but cannot run a process: you cannot approve, schedule, or claim inside a dashboard. When the spreadsheet is doing work rather than displaying it, it needs an application, not a viewer.
Your most important software is a file on someone's desktop.
A Workflow Review identifies which spreadsheets have quietly become systems—and which one to fix first.