A business drowning in spreadsheets, and the system that fixed it
The scenario below is a composite drawn from patterns I’ve seen across different engagements, not one specific client. Details are changed accordingly.
A business I worked with had eleven spreadsheets running its operations. Not eleven categories, eleven actual files, each owned by a different person, each slightly out of sync with the others. Sales tracked leads in one. Fulfillment tracked orders in another. Someone in finance kept a third “master” sheet that reconciled the first two, badly, about once a week.
Nobody had planned this. It grew one spreadsheet at a time, each one a reasonable fix for a specific fire at the time it got built. Three years later, the fires were still getting put out, just slower, and by more people. The instinct in that situation is always to fix the business with more software. Usually the wrong instinct, and this is the story of why.
The first instinct was wrong
The owner’s read on the problem was “we need better software.” That’s the natural conclusion when everything feels chaotic, buy a tool, the tool imposes structure. It’s also usually the wrong first move, because it skips a step: nobody had actually agreed on what the structure should be. Buying a CRM on top of eleven undocumented, disagreeing spreadsheets just gives you a twelfth source of truth to reconcile.
Before touching any tooling, the real work was mapping what each spreadsheet was actually being used for versus what everyone assumed it was for. Turned out three of the eleven were duplicates nobody remembered to retire. Two were tracking things that didn’t need tracking at all, leftover habits from a process that had already changed. That’s six gone before a single dollar got spent on software.
What the fix actually was
The remaining five got collapsed into one system, but the software part was almost boring: a single shared source of truth, one owner per record type, and a written handoff rule for the moments where sales, fulfillment, and finance actually needed to touch the same data. That handoff rule was the real fix. The tool just gave it somewhere to live.
Three things made it stick, worth stealing regardless of your situation:
- One owner per data type. Not one team, one person. Shared ownership is how “master” spreadsheets rot in the first place.
- A named handoff point, written down, for every place two roles touch the same information. Most operational chaos lives in the gaps between roles, not inside them.
- A kill list. Anything that duplicated another source got retired on a set date, not “eventually.” Eventually never comes.
What changed
Within a month, the reconciliation meeting that used to eat two hours a week just stopped happening, there was nothing left to reconcile. The bigger shift was quieter: decisions that used to wait on “let me check the sheet” started happening in real time, because there was exactly one place to check.
The lesson, generalized
This wasn’t a software problem wearing a software costume, it was an ownership and handoff problem that software alone can’t fix, and often makes worse by giving the mess a shinier home. If your business feels like it’s drowning in tools or trackers, the diagnosis usually isn’t “buy something better.” It’s “figure out who owns what, and where the handoffs actually happen.” The tool comes after that, not instead of it. You can fix a business without more software far more often than the software industry wants you to believe.
Spotting that difference, tool problem or ownership problem, is the actual skill. It’s not something a single specialist vendor is positioned to tell you, since their answer is always “buy the tool.” A generalist who’s mapped enough of these messes to see the pattern usually catches it faster, and cheaper, than another subscription would.