DEEP DIVE
The Spreadsheet Nobody Told the AI Consultant About
The software stack on the discovery call is rarely the software stack the business actually runs on.
Every business has a system nobody mentions during the first conversation.
Sometimes it is a spreadsheet. Sometimes it is an inbox folder. Sometimes it is a Slack channel. Sometimes it is one employee's memory.
And sometimes it is a file called something like FINAL_PIPELINE_V7_REAL.xlsx.
The official company and the real company
Ask a business owner what software they use and you will hear the clean version: HubSpot. QuickBooks. Google Workspace. Asana. Maybe Zapier.
Then sit next to the team and watch how work actually moves.
Now you discover the estimate tracker in Google Sheets because the CRM report is wrong. The inbox label the owner checks every morning. The calendar reminder that triggers a billing task. The Slack message someone sends because there is no real handoff.
THE DEMO
CRM → Project Management → Accounting
Clean systems. Clear ownership. Nice arrows.
REALITY
CRM + spreadsheet + inbox + Slack + calendar reminder + one person's memory.
The undocumented pieces are often where the most important business logic lives.
Shadow systems exist for a reason
It is easy to look at the spreadsheet and say, “We should eliminate that.” Maybe. But first I want to know why it exists.
Usually somebody created it because the official system did not answer a question they needed answered. The spreadsheet is often a symptom, not the disease.
Discovery cannot be a software inventory
“What tools do you use?” is useful. It is not enough.
A better question is: “Show me exactly what happens when a new customer comes in.”
Then follow the work. Where is the customer created? Who gets notified? What gets copied? Where does somebody leave the system and open a spreadsheet? What happens if nobody does the next step?
The tribal knowledge problem
The most dangerous system in a small business often has no login. It is the person who “just knows” how everything works.
They know Customer A needs a different invoice. They know the owner promised a special rate. They know which CRM field everyone ignores.
When you automate without capturing that knowledge, the automation looks right and behaves wrong.
Before you automate the process on paper, find the process people actually use.
STEAL THIS
The Shadow System Audit
01 · Have the employee perform the process instead of describing it.
02 · Write down every system, spreadsheet, inbox, chat, document, and manual note they touch.
03 · Ask what they do when the normal path fails.
04 · Ask what information they do not trust in the official system.
05 · Ask what they keep outside the system and why.
06 · Ask what only they know that a new hire would miss.
Do not automate the fiction
The documented process is useful. The software architecture is useful. The SOP is useful.
But none of them matter as much as what happens on Tuesday morning when a real customer needs something and the team has to get the work done.
If you have not found the weird spreadsheet yet, you probably have not finished discovery.
BUILD SYSTEMS THAT SURVIVE REALITY
If you have a workflow that works on the whiteboard but keeps breaking inside the real business, this is exactly the kind of problem we work on at SMB Ops.
Drew Reynolds
The SMB Operator