The problem is rarely the spreadsheet. It is that there are now nine of them and they disagree.

Signs you have outgrown spreadsheets and your accounts package

How to tell the difference between a business that is busy and a business whose systems have stopped keeping up - and what to do about it.

Almost every business that ends up buying an ERP system started with a spreadsheet, and for a long time the spreadsheet was the right answer. It was free, it was flexible, and it did exactly what the person who built it wanted. Nobody makes a bad decision by starting there.

The trouble arrives gradually. One spreadsheet becomes several. Several become a set that only partly agree with each other. The accounts package holds the invoices but knows nothing about the job, the stock figure is maintained by somebody who is also doing three other things, and the answer to "how did that order do?" takes an afternoon to produce and is challenged when it appears.

This guide is about recognising that point clearly, rather than either ignoring it for another two years or panicking into a project you do not need yet.

The real symptom is disagreement, not effort

Manual effort is not, on its own, a reason to replace a system. Plenty of businesses run efficiently on simple tools because the volume does not justify anything more. The signal that actually matters is when two people can produce two different answers to the same question and both can defend them.

Once that happens, every meeting acquires a preamble about whose numbers are right, decisions get deferred until the figures are reconciled, and the reconciliation itself becomes somebody’s job. That is the point at which the systems have started costing more than they save.

Eight things that usually mean it is time

None of these is decisive on its own. Three or four together generally are.

  • Somebody has to reconcile two systems before anybody trusts a number, and it happens more than once a month.
  • The stock figure is treated as an estimate. Orders are promised on it and then checked physically before anybody commits.
  • Nobody can say what a specific job or order actually made without an afternoon of work, so nobody asks.
  • A key spreadsheet has one owner, and their annual leave is a business risk.
  • The same information is keyed into two or more systems - order to accounts, accounts to stock, stock to a courier portal.
  • Purchase commitment is first visible when the invoice arrives, so budget conversations are always retrospective.
  • An audit, a customer questionnaire or a recall drill requires assembling evidence rather than printing it.
  • Growth is being turned down, or delayed, because the admin behind it would not cope.

If you recognise fewer than three of these, you are probably fine for now. Fixing one specific process well beats buying a platform you are not ready to use.

Why the accounts package cannot fill the gap

The most common intermediate step is to push more work into Xero, Sage or QuickBooks - using their inventory features, adding an app for stock, adding another for quoting. It works up to a point, and the point is usually reached faster than people expect.

Accounting packages are built around the transaction: the invoice, the bill, the payment. They are excellent at that. What they do not model is the work that happens before the transaction - the enquiry, the quote, the specification, the works order, the route through the shop floor, the pick, the pack, the delivery. Those are the things that determine whether the invoice is profitable, and they are exactly what an accounting package is not designed to hold.

This is not an argument for replacing your accounts package. Most of our customers keep theirs, and the operational system posts into it.

What waiting actually costs

The cost of staying put is real but diffuse, which is why it gets discounted. It shows up as stock written off because nobody could see it was ageing, jobs quoted from an estimate that has been wrong for two years, parts fitted on site and never invoiced, rebates unclaimed, and orders promised on dates that were never achievable.

Most businesses find that when they finally measure one of these, it is larger than the annual cost of the system they were hesitating over. That is not a sales argument - it is an argument for measuring one of them before you decide either way.

What to do before you buy anything

  1. 1Pick the single question that causes the most argument - job profitability, stock accuracy, delivery performance - and measure it properly once, by hand if necessary.
  2. 2Write down where data is currently keyed twice. The list is usually longer than anybody expects and it makes the case on its own.
  3. 3Identify which spreadsheet would hurt most if its owner left tomorrow. That is your real risk, and it is worth addressing regardless of what you buy.
  4. 4Agree internally what "better" would look like in numbers, not adjectives. "Fewer errors" is not a target; "stock accuracy above 98%" is.
  5. 5Only then talk to suppliers, and lead with those numbers rather than asking for a demonstration.

In short

What to take away

  • Effort is normal; disagreement between systems is the actual warning sign.

  • Accounting packages model the transaction, not the work that precedes it.

  • Three or more of the eight symptoms together usually justify acting.

  • Measure one problem properly before buying anything - it sharpens the decision either way.

Questions

Asked while people are working this out

  • There is no reliable headcount threshold. We have seen eight-person manufacturers who needed it and forty-person distributors who did not. Complexity of process matters far more than number of staff.

  • You can, and for a while it helps. The difficulty is that each app holds its own version of the data, so you end up managing the interfaces between them - which is the problem you were trying to solve.

  • Often, yes. Stock accuracy is the foundation everything else stands on, and if your data is poor, a broader system will simply be wrong faster. Fixing it first is rarely wasted effort.

  • They almost never are, and that is normal. Documenting them is part of implementation rather than a prerequisite - but expect it to take longer than anybody estimates, because it surfaces disagreements about how things are supposed to work.

  • In places, yes, and any supplier who says otherwise is selling. The right question is which of your processes are real competitive differences worth configuring around, and which are habits that exist because the old system could not do better.

After reading

Bring the questions this raised

If the guide has made you think of something specific about your own business, that is exactly the conversation worth having. No obligation and no scripted demonstration.