The invisible cost of running a business on spreadsheets

The short answer: a spreadsheet is free until you count what surrounds it. The license costs nothing, but the hours spent retyping data, the errors that compound silently, the risk of a single person owning the file, and the decisions made on last month's numbers all carry a real price. None of it shows up on an invoice, which is exactly why it keeps getting paid.

This is not an argument against spreadsheets. They are one of the best tools ever built for thinking with numbers. The problem starts when a sheet stops being a thinking tool and becomes the system a business runs on, without anyone deciding that on purpose.

Where the cost actually hides

The cost of a spreadsheet-run operation almost never appears as a line item. It hides in the daily routine of the people who keep it alive:

• Hours spent retyping the same data: from a receipt into a sheet, from one sheet into another, from a sheet into an email or an ERP
• Errors that compound silently: a broken formula or a pasted-over cell does not crash anything, it just quietly produces wrong numbers that get trusted
• The one person who understands the sheet: when they are on vacation, sick, or gone, the operation slows down or stops
• Data that is stale the moment it is exported: every copy of the sheet starts aging immediately, and nobody is sure which version is the truth
• No history of who changed what: when a number looks wrong, there is no reliable way to find out when it changed, who changed it, or what it was before

The moment a spreadsheet becomes a system requirement

There is a point where the file stops being a personal tool and becomes infrastructure. In our experience, three signals mark that line, and any one of them is enough to take seriously:

• More than one person edits it: the sheet is now a shared database with no locks, no permissions, and no audit trail
• It feeds decisions on a weekly rhythm: pricing, purchasing, payroll, or scheduling now depend on the file being right and current
• A customer, a partner, or an auditor depends on it: an error is no longer internal, it reaches someone who can hold you to it

Once a sheet crosses that line, treating it as free is an accounting trick you play on yourself. It is a system, it is just a system with none of the protections systems are supposed to have.

What replacing it actually looks like

The honest answer is that replacing a spreadsheet does not mean buying a big ERP and reorganizing the company around it. Big-bang replacements fail for the same reason the spreadsheet won in the first place: the sheet fit the real workflow, and the generic system did not. What works is smaller and less dramatic: small operational systems shaped on the workflow that already exists, replacing one manual step at a time.

Two examples from Cazullo's own client work, both anonymized. For a construction operation, expense tracking lived in photographed receipts and manual retyping; we built DWC Tracker so receipts are photographed once and categorized by AI, and the numbers land in a system instead of a sheet. For a freight forwarding operation, reporting meant exporting from the ERP into spreadsheets by hand every time someone needed an answer; we built FreightOps as a read-only workspace on top of the ERP data, so the team reads live numbers instead of maintaining exports.

Neither project asked anyone to abandon their tools overnight. Each one took the most expensive manual loop, the retyping, and removed it. That is usually the whole trick: find the loop where humans move data between places, and give that loop a system.

When a spreadsheet is the right tool

It would be dishonest to pretend every sheet needs replacing. Spreadsheets remain the right tool when:

• One person owns it and nobody else edits it
• The work is exploratory analysis: modeling a scenario, testing an idea, poking at data to see what it says
• The calculation is throwaway: it answers today's question and nobody needs it next month

The pattern is simple: spreadsheets are excellent for thinking and terrible for operating. Keep them for the first job and be suspicious when they drift into the second.

Checklist: is your spreadsheet quietly running the company?

Count how many of these are true for your most important sheet:

• More than one person edits it in a normal week
• Someone retypes data into it from paper, photos, emails, or another system
• A recurring decision (pricing, purchasing, payroll, scheduling) waits on it
• Only one person really understands how it works
• There are multiple copies and you are not always sure which one is current
• A wrong number in it could reach a customer, a partner, or an auditor
• Nobody can say who changed a given cell, or when
• Someone has said 'do not touch that tab' in a serious tone

Two or more, and the sheet is already infrastructure. Our recommendation: do not plan a grand migration. Pick the single most painful manual loop the sheet creates, usually the retyping, and replace that loop with a small system built on the workflow you actually have. Keep the spreadsheet for thinking. Stop asking it to run the company.