Spreadsheets and email are not the problem. The problem is when the volume, the number of people involved and the pace of decisions pass what informal tools were ever meant to hold.
Almost every well-run company we meet built its first operating system out of spreadsheets and email, and it worked. Those tools are fast, flexible and free of implementation projects. A founder can change a process on a Tuesday afternoon without asking anyone for permission.
The trouble is that they scale differently than the business does. Volume grows in a straight line; coordination cost grows faster. At some point the spreadsheet is no longer describing the operation — it is the operation, and nobody can see all of it at once.
Below are the seven signals we look for when a leadership team asks whether it is time to change the operating tools. None of them is fatal on its own. Three or more usually mean the informal system is now the constraint.
1. The same fact lives in more than one place
A customer address, a price, an order status or a headcount number exists in a spreadsheet, in someone's inbox and in a system of record — and the three do not agree. Staff learn which copy to trust, which is a form of institutional knowledge that never gets written down.
The tell is not the duplication itself. It is that people have begun to check two sources before acting, and that checking has become normal.
2. Version control is now a human job
Files named final, final_v2 and final_revised_JM circulate by email. Someone reconciles them. That reconciliation is real work with real cost, and it produces no output a customer would ever pay for.
When a person's week contains hours of merging other people's copies, the coordination overhead has outgrown the tool.
3. Work moves between teams by hand
A sale closes, and someone re-keys it into billing. Onboarding finishes, and someone emails service to say so. Each handoff depends on a human remembering to perform it, and each is invisible until it is missed.
Manual handoffs are also where cycle time hides. The task itself takes four minutes; the wait between teams takes two days.
4. Nobody can answer a simple question quickly
"How many open jobs are past their promised date?" should take seconds. When the honest answer is "give me until tomorrow," the business is running on retrospective reporting rather than management information.
Slow answers change behavior in a quiet way: leaders stop asking. Decisions get made on the last number anyone remembers, which is usually the number from the last bad month.
5. One person is the system
There is someone who knows how the master file works, which tab feeds which, and why one formula must never be touched. The operation runs well because of them, and pauses when they take a holiday.
This is not a personnel problem. It is a design problem — the process was never externalized from the person performing it.
6. Reporting arrives too late to change anything
Month-end closes on the fifteenth. Margin on a project is known after the project is finished. Service quality is reviewed a quarter after the customers involved have already decided how they feel.
Information that arrives after the decision window is history. Useful management information is timely and partial rather than complete and late.
7. Errors and rework are climbing faster than volume
Rework is the most reliable of the seven signals because it is measurable. If order volume grew 30 percent and correction work grew 60 percent, the operating system is absorbing the difference — usually in overtime, credits, or the goodwill of long-tenured staff.
What this does not mean
It does not mean spreadsheets are bad, and it does not mean the answer is a large software purchase. Some of the fastest improvements we see come from tightening the process, deciding on one source of truth, and continuing to use tools the team already knows.
The order matters. Clarify what the process actually is, decide who owns each step and what "done" means, then choose the smallest technology that makes that process hard to do incorrectly. Reversing that order is how companies end up with an expensive system that reproduces the old confusion faster.
A reasonable first step
Pick the one workflow where these signals are loudest — usually order to cash, service intake, or job costing. Map it as it truly runs, not as the policy says. Count the handoffs, the duplicate entries, and the days of delay. That single map tends to settle the debate about what to fix and in what order.
If that mapping work is where you are stuck, our Operational & Performance Consulting engagement starts exactly there, and any technology recommendation comes afterward — including the recommendation to build nothing.
Start with a conversation, not a proposal
A 30-minute discovery call. We ask about your operation, you tell us where it hurts, and we tell you honestly whether we can help.