Signs your business has outgrown spreadsheets

Almost every established SME we speak to runs something important on a spreadsheet. Stock, jobs, quotes, bookings, compliance records, commissions. Usually one file, usually built by whoever was closest to the problem at the time, usually years ago.

That was not a mistake. A spreadsheet is the fastest way to get a process out of someone's head and into something the business can share. The problem is that it keeps working just well enough, long after it has stopped being the right tool, because the cost of keeping it is spread thinly across everybody's week rather than showing up as a line on the P&L.

Here is how to tell the difference between a spreadsheet that is fine and one that has quietly become a risk.

1. Only one person really understands it

There is a file, and there is a person, and the business depends on both. They built the formulas, they know which tab is live and which is the old version, and they know the two cells you must never touch.

Ask yourself what happens if that person is off for a fortnight, or leaves. If the honest answer involves a scramble, you are not looking at a spreadsheet any more. You are looking at an undocumented system with a single point of failure, and no supplier to call.

2. Versions travel by email

The moment a file goes round as an attachment, you have lost the ability to say which copy is true. People work from the version in their inbox, changes get made in two places, and someone spends an afternoon merging them back together.

Shared drives and cloud versions of Excel and Sheets help, but they do not actually solve it. Two people can still overwrite each other's work, and nothing stops anyone from taking a private copy "just to try something".

3. You find the errors by accident

Spreadsheets do not object to nonsense. Text in a number column, a formula dragged one row short, a decimal in the wrong place, a filter left applied when someone printed the report. None of it is flagged, because there is nothing in a spreadsheet that knows what a valid order or a valid referral looks like.

The tell is not that mistakes happen. It is how you find them: a customer rings up, or a figure looks odd at month end, and then someone goes hunting. Errors that surface through complaints are expensive twice over.

4. The same data gets typed in more than once

Watch what happens after the spreadsheet is updated. Does someone then key the same details into the accounts package? A job sheet? A separate stock file? An email to a supplier?

Double keying is the clearest signal of all, because it is measurable. Count the number of times a single piece of information is typed into your business, and multiply by how often it happens a week. That number is what a system integration or a purpose built system is actually competing against, and it is usually larger than people expect.

5. You cannot answer simple questions about your own business

Which customers order most often. How long a job really takes from enquiry to invoice. Which product line quietly loses money. How many enquiries came in last month, and how many turned into work.

If getting those answers means an afternoon of exports and pivot tables, you are not getting them. You are guessing, and making decisions on the guess. A spreadsheet stores what happened. It is not built to tell you what is happening.

6. You have stopped asking it to change

This one is subtle and it matters most. When a spreadsheet gets fragile, people stop suggesting improvements, because everyone knows change is risky. The process freezes around the tool.

So the business adapts to the file instead of the other way round: extra columns nobody uses, a colour code that means something to three people, a monthly ritual of copying last month's tab. The workarounds get workarounds. That is the point at which the spreadsheet is no longer supporting the business, it is defining it.

What replacing it actually means

Not a bigger spreadsheet. Not a database that looks like a spreadsheet. The things a proper system gives you that a file cannot:

• Validation. The system knows what a valid record looks like and refuses the rest, so bad data never gets in.
• Real multi-user access. Several people working at once, on one set of records, with no merging afterwards.
• Roles and permissions. People see and change what their job requires, and nothing else.
• A history. Who changed what, and when. Invaluable the first time something is disputed.
• Reporting as a feature, not an export. The questions you ask every month answered on screen, up to date, without anybody building anything.
• A supplier. Someone whose job it is to fix and extend it, rather than a colleague doing it in the gaps between their real work.

This is the most common project we take on. Comp Performance Limited is a good example of the shape it takes: a multi-user system replacing a single owner spreadsheet, with stock updating automatically as orders go through. You can read the detail in the Comp Performance case study, and the approach is set out on our replace spreadsheets page.

When you should leave the spreadsheet alone

We would rather say this before you spend anything.

Keep the spreadsheet if the process is genuinely simple, if one person owns it and that is fine because the work is theirs alone, if it changes shape constantly and you need that freedom, or if it is a piece of modelling rather than a record of what the business did. Spreadsheets are superb at analysis and at anything one person does once.

Keep it too if the process itself is about to change. Building software around a process you are already unhappy with just makes the wrong shape permanent. Sort out the process first, then automate what survives.

Working out whether it is worth it

The maths is not complicated. Take the hours a week the current way of working costs you, in admin, in re-keying, in correcting errors, in chasing information that should be one click away. Cost those hours honestly. Compare the annual figure against a one off build.

Most bespoke projects for SMEs fall between £15k and £60k, and we publish the bands and what moves a project up them on our bespoke software development page, so you can do that sum before you speak to anybody.

If you would like help with the first half of it, the free process audit is a 60 minute session, usually on site, where we map what actually happens and where the hours go. You will get a straight answer at the end of it, including "your spreadsheet is fine" if that is the answer.