The spreadsheet that runs your business

Somewhere in your business there is probably a spreadsheet that matters more than it should. It tracks the jobs, or the stock, or the deals, or who owes what. One or two people really understand it. Everyone else is slightly afraid of it.

That spreadsheet is not a failure. It's usually the most honest piece of software in the building, because someone built it to fit exactly how the work happens. The question isn't whether it should exist. It's whether it has quietly become a system without being treated like one.

Why it happened

Spreadsheets win early for good reasons. They are flexible, everyone has one, and you can change them the moment the business changes. When a new process appears, adding a column is faster than buying software or waiting for someone to build something.

So the sheet grows. A tab for each branch. A formula someone wrote two years ago. A colour code that means something to the person who invented it. Data copied in from two other systems every Monday. It works, mostly, because the people who run it are careful.

Signs it has outgrown itself

A few patterns show up again and again when a sheet has crossed the line:

• One person is the system. If they are on leave, the process slows or stops.
• Copying is the job. Someone spends hours each week moving data into the sheet from elsewhere, and back out again.
• Versions multiply. There is "the real one", a copy someone emailed, and a filtered version that somebody else edits.
• Errors are found late. A broken formula or a pasted-over row is discovered weeks later, after decisions were made on it.
• Nobody can answer "what changed?" There is no clear record of who edited what, or why.

Any one of these is manageable. Three or more usually means the sheet is costing real hours and real risk every month, even though nobody sends you a bill for it.

Moving off it without losing what works

The instinct is to replace the spreadsheet with a big new system. That often goes badly, because the sheet encoded years of small, practical decisions, and a generic tool throws them away.

A safer path keeps the logic and changes the plumbing:

1. Write down what the sheet actually does. Not every cell, but the decisions it supports and the rules hidden in its formulas.
2. Find the source of each column. Most of the data already lives in another system. Those columns should be fed automatically, not typed.
3. Give it a proper home. Move the core records into a structured database with clear fields, permissions and a history of changes. People can still see it as a table if that is how they like to work.
4. Keep a human check where judgement matters. The point is to stop the retyping, not to remove the person who knows when something looks wrong.

Done this way, the people who relied on the spreadsheet usually recognise their own process in the new setup. It just stops breaking, stops depending on one person, and stops eating Mondays.

The honest version

Not every spreadsheet needs replacing. A sheet that one person uses to think is a fine tool. The ones worth fixing are the ones the business can't run without, fed by hand, understood by few. If you know exactly which sheet that is in your business, that is usually the right place to start.