Seven signs your business has outgrown spreadsheets

Nothing has done more for small business than the spreadsheet, and nothing has quietly cost growing businesses more. The problem is never the spreadsheet itself. It is that it keeps working just well enough, long after it stopped being the right tool, and the failure when it comes is sudden and expensive.

Here is what the last few years before that failure look like.

1. One person is the system

There is somebody who knows how the file works. They built the formulas, they know which tab not to touch, and when they are on leave something waits. That is not a spreadsheet, that is a single point of failure with a salary.

The test: if that person left tomorrow, how long before something breaks? If the answer is days rather than months, you have already outgrown it.

2. There are versions

Final. Final v2. Final updated Oct. The copy on somebody's desktop that has the right numbers. The moment a file has versions, the organisation has stopped having one truth and started having several, and reconciling them is now a job.

3. Numbers arrive at meetings and disagree

Three people bring three figures for the same thing and the first twenty minutes goes on whose is right. This is the most expensive symptom, because it is not the time lost in the meeting. It is that decisions get deferred, and deferred decisions compound.

4. The data is always a bit old

The sheet is accurate as of when it was last updated, which is Monday, or month end, or whenever somebody got to it. Everyone has quietly learned to treat it as history rather than information, and nobody says so out loud.

Information you cannot act on today is not information. It is reporting.

5. People have built private workarounds

Side spreadsheets. A WhatsApp group that is really a workflow. A notebook. These appear when the official system does not fit the real work, and they are the clearest signal you will get, because people do not build workarounds for fun. They build them because they have to.

Go and find them. Each one is a feature specification written by the person who needed it.

6. Mistakes are found rather than prevented

A spreadsheet will let anyone type anything anywhere. The wrong date, the wrong rate, a formula overwritten with a number. Nothing stops it, so quality control becomes somebody checking afterwards, which is slower, more expensive and less reliable than simply not allowing it.

7. You cannot answer a simple question quickly

How many open items are over thirty days. Which customer is least profitable. Which site had the most failures this quarter. If the honest answer is that somebody would need a day to work it out, the data exists but the business cannot use it.

What to do about it, in order

Not all of it at once, and not by buying a large platform. The sequence that works:

• Pick the single process that causes the most arguments. Not the biggest one, the one that generates friction.
• Write down what actually happens, including the workarounds. The real process, not the one in the handbook.
• Check whether an off the shelf product already does it. If one does, buy it. Honestly.
• If nothing fits, build only that one process. Four weeks, one thing, used by real people.
• Live with it for a month before building the next thing. The second build is always better because of what the first one taught you.

The mistake almost everyone makes is going from spreadsheets straight to a single system that does everything. It takes a year, it costs a fortune, and people go back to their spreadsheets because the new thing does not fit either. One process at a time is slower on paper and faster in practice.