Your business runs on one person's head — and that's a problem

We sat in a meeting recently with the owner of a successful contracting business. Fifteen people, healthy order book, good reputation, growing steadily. When we asked how they schedule work, he pointed at a whiteboard behind his desk.

"It's all on there. And in my head."

He said it with a slight grin, the way people do when they know something is a bit ridiculous but it's been working fine for years. And he's right — it has been working fine. That's exactly the problem.

Could your business pass the bus test?

Here's a question worth asking about your own business: if you disappeared for two weeks with no notice, what would stop?

Not "would things be harder" — of course they'd be harder. We mean what would actually grind to a halt because the knowledge to do it exists only in your memory?

For a lot of UK small businesses, the honest answer is: scheduling, pricing decisions, supplier relationships, knowing which jobs are urgent and which can slip, and the dozen daily judgement calls that keep everything moving. When the owner is away, staff either guess or they wait.

This isn't a criticism of how the business is run. It's the natural result of a business that grew organically from one or two people doing everything. The systems that worked at three people are still in place at fifteen, held together by the owner's memory and a lot of goodwill.

But it's fragile in ways that only become obvious when something breaks.

What are the four symptoms we see most often?

Over the years we've walked into a lot of small businesses to look at their operations. The same patterns come up again and again.

The whiteboard problem

Scheduling lives on a physical board, in a spreadsheet on one person's PC, or in someone's head. If it's not on the board, staff have to ask. That question — "where am I supposed to be tomorrow?" — gets asked dozens of times a week, and it always goes to the same one or two people.

The cost isn't just the interruption. It's that nobody else can plan, cover, or make decisions without checking first. You've accidentally made yourself the bottleneck for every operational question in the business.

Paper is a hidden tax

Job sheets, timesheets, test certificates, delivery notes. They get filled in on site, come back in a van, sit in a pile, and eventually get typed into an accounting system by someone in the office.

Every one of those steps is a chance for something to go missing, get misread, or be delayed. And the real cost isn't the typing time — it's that you don't know whether a job was profitable until weeks after it finished. By then it's too late to do anything about it.

Paper also means no audit trail. When a customer queries something six months later, the answer is either in a filing cabinet or it isn't.

Backups that aren't really backups

We've seen businesses running their entire operation off a local server with backups going to USB drives that are a decade old, rotated manually, and stored in someone's house. Nobody has ever tested a restore.

That's not a backup strategy. That's a hope. One ransomware attack, one hardware failure, one fire, and the business loses its customer records, its job history, its invoicing data, and its ability to trade. Some businesses don't come back from that.

Slow responses cost deals

When enquiries land in an inbox that one busy person checks between other tasks, response times stretch. A day. Sometimes two. In a competitive market where the customer has emailed three suppliers, the fastest response very often wins — not the best price, not the best company, just whoever replied first.

You'll never see the deals you lost this way. They just don't come back.

Why doesn't "finding the right app" fix it?

The most common response we hear is: "Yeah, we've been meaning to sort this. We keep looking at apps but never get round to it."

That's not a failure of willpower. It's that the problem has been misdiagnosed.

Looking for software to fix an operational problem is like buying a filing cabinet to fix disorganisation. The cabinet doesn't decide what goes where, who's responsible for filing, or what happens when something is missing. Without those decisions, you now have a disorganised filing cabinet.

Businesses stall on "finding the right app" because there is no right app for a process that hasn't been defined. What actually needs to happen first is deciding how the business should operate — then choosing tools that support it.

What does "sorted" actually look like?

The target state is simpler than most people expect. Every job in the business needs:

• One record. A single place where the job number, customer, site, status, key dates, documents, and notes all live. Not spread across a whiteboard, an email thread, a folder on the server, and someone's memory.
• One schedule. Who is where, when, and why. Visible to everyone who needs it, without asking.
• Digital capture in the field. Timesheets, job sheets, test results, and photos entered once, on site, by the person doing the work. No re-typing.
• Document control. Every job has its documents in one findable place, with version history, accessible from a phone on site.
• A link to the money. Costs and time flow through to job costing automatically. Invoices trigger from job milestones. Overdue payments are visible without someone having to go looking.

That's it. Whether you build that on ERPNext, Microsoft 365, a purpose-built industry package, or something else matters far less than getting the five things above nailed down.

Why does the order matter?

If you take one thing from this: define the operating model first, then pick the tools.

Write down what a job looks like from enquiry to payment. What are the stages? Who does what at each stage? What has to be true before it moves to the next stage? What information needs to be captured, and by whom?

That document — even if it's two sides of A4 — will tell you more about what software you need than any amount of demo-watching. And crucially, it means that when you do implement something, you're digitising a process that works rather than automating chaos.

The businesses that get stuck are the ones trying to solve a process problem with a purchasing decision. The ones that succeed decide how they want to work, then find tools that fit.

Where should you start?

You don't need to fix everything at once. If your business looks like the one we described at the start, here's the order we'd tackle it in:

• Step 1. Stop the existential risk first. Get your data somewhere it can't be lost. Cloud storage with proper versioned backups, multi-factor authentication on your email. This is boring and it isn't exciting to talk about, but everything else is pointless if you lose the business to a ransomware attack next month.
• Step 2. Get the work out of your head. A shared, live job list — even a simple one — that shows what's happening and what's next. This alone changes how a business feels to work in, because people stop asking and start knowing.
• Step 3. Kill the paper loop. Digital forms for the things that currently come back on paper. One entry, no re-typing.
• Step 4. Connect it to the money. Job costing, invoicing triggers, payment tracking.
• Step 5. Then optimise. Automation, analytics, AI-assisted responses. All useful, all worth doing — but only once the foundation is there.

Frequently asked questions

What is the bus test?

It's a simple thought experiment: if you disappeared from your business for two weeks with no notice, what would actually grind to a halt? Anything that stops because the knowledge exists only in your memory — scheduling, pricing, supplier relationships, daily judgement calls — is a key-person dependency your business is carrying.

Should we choose software first or define our processes first?

Processes first, always. Write down what a job looks like from enquiry to payment — the stages, who does what, what has to be true before work moves on, and what information gets captured. Even two sides of A4 will tell you more about what software you need than any amount of demo-watching, and it means you end up digitising a process that works rather than automating chaos.

What should a small business fix first?

The existential risk: get your data somewhere it can't be lost, with proper versioned cloud backups and multi-factor authentication on your email. After that, a shared live job list, then replacing paper with digital capture, then connecting operations to job costing and invoicing. Automation and analytics come last, once the foundation is in place.

Do we need a full ERP system to fix this?

Not necessarily. What matters is that every job has one record, one visible schedule, digital capture in the field, document control, and a link to the money. Whether you build that on ERPNext, Microsoft 365, or a purpose-built industry package matters far less than nailing those five things down.

A final thought

The business we described at the start is doing well. Good margins, loyal customers, skilled staff. Nothing is on fire.

That's precisely the right time to fix this. Not when you've hit a crisis, not when you've lost a week to a server failure, and not when you're trying to scale and everything starts falling over at once. When things are calm and there's headroom to make changes properly.

If the whiteboard is working today, brilliant. Just make sure someone other than you knows what's on it.

If any of this sounds familiar, book a free 30-minute discovery call and we'll talk through where your business is most exposed. No pitch and no obligation — just a straight conversation about what your business actually needs, and an honest steer if the answer is "nothing yet".