Business Systems

Nine signs your business has outgrown its systems

Outgrowing your systems rarely announces itself. It shows up as small, boring frictions that everyone works around until working around them is the job. Here's what to watch for — and what to do about each one.

5 min read Published 7 September 2026

Quick checklist

  • Is the same information typed into more than one place?
  • Does anything important depend on one person's memory?
  • Does reporting mean exporting and pasting?
  • Are there rules that live nowhere except in people's heads?
  • Has anyone built a workaround that's now permanent?

Nobody wakes up and discovers their business has outgrown its systems. It happens the way a house gets cluttered: one sensible decision at a time, each of which made sense on the day.

What you notice instead is friction. Things take longer than they should. The same conversation keeps happening. Someone is always “just fixing something up” before it can go out.

Here are the signs that turn up most often, roughly in the order they tend to appear.

1. The same information gets typed in twice

The clearest signal there is. A customer’s details go into the quote, then into the job, then into the invoice, then into the accounting package. Each retype is a chance to get it wrong, and every one of them is unpaid work.

Usually means: two tools that should talk to each other don’t.

Cheapest fix: an integration, not a replacement. Most business software will talk to most other business software, and a lot of people replace an entire system when they needed one connection.

2. Someone maintains a spreadsheet nobody else understands

Spreadsheets are excellent, and this isn’t an argument against them. But there’s a moment where a spreadsheet stops being a document and starts being a system — the business depends on it, it has rules baked into it, and one person is the only one who can safely change it.

Usually means: you’ve built software by accident.

Cheapest fix: work out which part is genuinely the system. Often it’s one sheet out of nine, and the rest can stay exactly where it is. There’s more on this in when spreadsheets stop working.

3. Reporting means exporting and pasting

If answering “how did last month go?” requires downloading two CSVs and assembling them by hand, you don’t have reporting — you have an archaeology project that happens monthly.

Usually means: the data is fine, it’s just in separate places.

Cheapest fix: a dashboard fed from the sources you already have. This is one of the smaller jobs on this list and one of the ones people put off longest.

4. Nobody can cover for anyone

The real test isn’t whether your systems work. It’s whether they work when the person who normally does it is away.

If a customer has to wait for a specific person to come back, the information they needed was in someone’s head or someone’s inbox rather than in the business.

Usually means: knowledge is stored socially rather than systematically.

Cheapest fix: usually not software at all — it’s writing down the handful of things that only exist verbally, then deciding where they should live.

5. There are rules that exist nowhere

“We always give that customer the trade rate.” “We don’t schedule those on a Friday.” “That one gets checked before it goes out.”

Every business has a dozen of these. They’re fine while everyone knows them. They become expensive the moment someone new is doing the job.

Usually means: the business has genuine complexity that no off-the-shelf tool has been told about.

Cheapest fix: configuration, most of the time. A surprising amount of software can encode rules like these and simply was never set up to.

6. A workaround has become permanent

Somebody, at some point, invented a way around a limitation. A naming convention. A duplicate record. A status that means something different from what it says. It was meant to be temporary and it’s been four years.

Usually means: the tool doesn’t model the business, and people quietly patched the gap.

Cheapest fix: find out what the workaround is for before changing anything. Workarounds encode real requirements, and replacing a system without understanding them is how you end up with a new system and the same workarounds.

7. You can’t answer basic questions about the business

How many quotes went out last month? What proportion turned into work? Which customers haven’t been back in a year?

If the honest answer is “I’d have to work that out”, the business is being run on impressions. That’s survivable for a long time and it gets expensive slowly.

Usually means: the information exists but isn’t connected.

Cheapest fix: again, usually reporting rather than replacement.

8. New people take a long time to become useful

If it takes months for someone to become productive, some of that is genuine skill — and some of it is that the systems don’t teach them anything. A well-set-up system tells a new person what to do next. A poorly set-up one requires them to already know.

Usually means: the process lives in people, not in the tools.

9. You’ve started avoiding work you could do

This is the expensive one, and the one people mention last. A business that can’t quote quickly stops chasing the jobs that need a quick quote. A business whose scheduling is painful stops taking the work that complicates the schedule.

At that point the systems aren’t just costing time. They’re deciding your strategy.

What to do about it

The mistake is treating all of this as one decision — “we need a new system” — and then either spending a great deal of money or being too daunted to start.

Almost none of these need a rebuild. In order of how often they’re the right answer:

  1. Configure what you already own. An enormous amount of business software can do the thing; it was set up with the vendor’s defaults and never revisited.
  2. Connect two tools. Most double-entry disappears with one integration.
  3. Move the data somewhere more suitable. Sometimes a spreadsheet just needs to be a database.
  4. Build something. Genuinely right sometimes, and the most expensive option — worth it when the way you operate is specific enough that nothing off the shelf models it.

If several of the nine sound familiar and you’re not sure which of the four applies, that’s exactly what a systems review is for. It’s free, and a decent proportion of them end with “this is fine, don’t spend money on it”.

Bottom line

Outgrowing your systems is a good problem — it means the business grew. The mistake is treating it as one big replacement decision instead of a handful of small, cheap ones.

Want a hand with this?

Tell us what you're trying to sort out and we'll give you practical, plain-English advice before you spend money.

Get a quote