The Exit Ready Series · Post R.23
View the full series →The Spreadsheet Empire
Fourteen spreadsheets ran the business for fifteen years. At exit, the buyer priced the migration to replace them.
The buyer's IT diligence team asks Janet to show them how the business runs. She opens the shared network drive, navigates to a folder called Operations, and begins.
- Dispatch_Master.xlsx
- Fleet_Maintenance.xlsx
- Inventory_Reorder.xlsx
- Inventory_Counts.xlsx
- Customer_Pricing_Exceptions.xlsx
- Tech_Certifications.xlsx
- Tech_CE_Deadlines.xlsx
- Commission_Calc_Sales.xlsx
- Commission_Calc_Service.xlsx
- Job_Costing_Master.xlsx
- Vehicle_Assignment.xlsx
- Annual_Maintenance_Calendar.xlsx
- Warranty_Tracking.xlsx
- PTO_Tracking.xlsx
Fourteen workbooks. Janet thinks there are one or two she is forgetting.
The senior consultant nods. He does not write down the names. He has seen this list before.
The empire
Every business has spreadsheets. The question is whether the spreadsheets run the business or support it.
Think about a restaurant kitchen. A prep list on a clipboard is fine. A clipboard that tracks inventory, schedules staff, prices the menu, calculates food cost, and manages vendor orders — that is not a prep list. That is the operating system. When the clipboard goes missing, the kitchen stops.
That is The Spreadsheet Empire — the pattern where a business runs its daily operations on standalone workbooks, maintained by specific people, with no integration between them and no documentation of the logic inside them.
The buyer's IT team is asking two questions. First: what does it cost to migrate this business onto the portfolio-standard platform? For a business Meridian's size, the direct cost runs $200K to $300K in vendor fees, configuration, data migration, and training. Nine to twelve months of implementation.
Second: what is the risk during the migration window? The spreadsheet system is held together by people who know which files matter, what the formulas mean, and how data moves between them. Janet is one. The dispatch lead is another. If either leaves during the transition — and at exit, some people always do — the migration becomes an emergency instead of a project.
The notes column
The Inventory_Reorder.xlsx workbook is the artifact the diligence team spends the most time on. Four hundred line items — capacitors, contactors, fan motors, refrigerant cylinders. Each line has a current count, a reorder threshold, a preferred vendor, a lead time, and a notes column.
The notes column is the finding.
Don't reorder from Allied, they were three weeks late twice — use Midstate instead. And: This part is being phased out by the manufacturer in 2027, switch to the new SKU when it hits. And: We keep extra stock for the hospital account. They need it within twenty-four hours when the call comes.
Twelve years of institutional memory, maintained by one person, buried in cell-level annotations that are not easy to find, not shared with the team, and not documented anywhere else.
The consultant's note: Inventory management contained in unstructured annotations maintained by a single individual. Migration requires interview-based knowledge extraction — two to three weeks of full-time effort — in addition to standard data migration.
That note is why Janet's retention through the migration becomes a covenant (a condition of the deal) — and why the cost of keeping her comes out of Ed's escrow, not the buyer's budget.
What Ready Looks Like
Operations run on systems, not spreadsheets. The threshold is not zero spreadsheets. But dispatch, inventory, customer relationships, and commissions each run on a purpose-built system with defined integrations.
The systems are documented. A new employee learns from standard operating procedures, not from sitting next to Janet for three months.
No single individual holds the institutional memory of how the systems work. Knowledge is distributed and stored in documents anyone can read.
For Meridian, none of these were true.
Janet prints all fourteen workbooks after the diligence team leaves. Not the data — the structural views. Tab lists, column headers, formula audits, named-range inventories. The output is 260 pages, double-sided. Four inches high.
She stacks them on the empty conference room table and puts a sticky note on top: Operating systems, March 2026.
The stack is the answer. It has always been the answer.
What this cost Ed: $115K.
The buyer priced the spreadsheet empire as a migration cost — moving fourteen standalone workbooks onto the portfolio-standard platform. The $115K covers vendor implementation, data extraction, configuration, and the interview-based knowledge transfer required to capture the institutional memory embedded in Janet's notes columns and formula logic.
The migration Ed could have done over three years at his own pace, the buyer will now do in twelve months at Ed's expense.
Don't be Ed.