Do You Need New Software or a Better Process?

Most enquiries we get start the same way. Someone has decided they need a system, or been told to start a portal for clients, an app for the team, or a dashboard that finally pulls everything into one place.

Sometimes they're right, but often they aren't. My honest answer is that building the thing they've asked for would cost them thousands of pounds and leave the underlying problem exactly where it was.

So before we quote for anything, we ask a different question: what is actually going wrong, and would software fix it?

The Short Answer to Whether You Need That Software

If your team is doing the right work but doing it slowly, manually, or twice, software will help. If your team is doing work that shouldn't exist at all, chasing information, correcting errors, working around a step that no longer makes sense, then software will just make that work happen faster.

Automating a broken process gets you the wrong answer sooner. That's literally the whole problem in one sentence.

Why Does This Actually Matter?

One of the real patterns I see constantly is that a business wants to automate its quoting. Quotes take three days to get out, they've lost work because of it, and they want a system that generates them instantly.

Sounds reasonable, right? But when you actually trace where the three days go, the software isn't the bottleneck. Half a day is the enquiry sitting unread in a shared inbox nobody owns. A day is waiting on a supplier price that could have been agreed in advance as a standing rate. Another day is a director signing off quotes under £500 that arguably don't need signing off at all.

Build the instant quoting tool and you'll go from three days to two and a half. The tool works perfectly. The delay was never in the bit you automated.

Fix the inbox ownership, agree standing rates, and raise the sign-off threshold, and you're down to under a day before anyone writes a line of code. Then automating the quote build is worth doing, and it's a smaller, cheaper, more focused piece of work, because you're automating a process that already makes sense.

Five Signs the Problem is Your Process, Not Your Software

1. The same information gets entered more than once. If a customer's details are typed into an enquiry form, then a spreadsheet, then an invoice, that's rarely a software gap. It's usually that nobody has decided which system is the source of truth.
2. Work stops while waiting for a person. Approvals, sign-offs, "I'll check with Dave." If your delays are made of waiting rather than doing, a new system inherits the waiting.
3. Everyone has a workaround. A personal spreadsheet, a WhatsApp group, a folder on someone's desktop. Workarounds are a map of where your official process doesn't match reality.
4. Nobody can explain why a step exists. "That's just how we've always done it" usually means a client left in 2019, or a problem got solved another way, and the step outlived the reason.
5. The exceptions have become the norm. If a third of jobs go "off-process", you don't have a process with exceptions. You have several undocumented processes competing with each other. Software built to the official one will be abandoned within a month.

Four Signs you Genuinely do need to Build Something

1. The manual work is correct, just repetitive. Someone spends six hours a week copying data between two systems that both work fine. That's an integration, and it will pay for itself quickly.
2. You've outgrown the tool, not misused it. Spreadsheets are excellent until multiple people need to edit them at once, or you need an audit trail, or the file takes thirty seconds to open. Those are structural limits, not user error.
3. The work only happens when someone remembers. Reminders, follow-ups, renewal chasing, review requests. Anything that depends on human memory is work that a system should own.
4. Off-the-shelf almost fits, but not quite. Sometimes the honest recommendation is a £40/month subscription rather than a custom build, and we'll say so. But when your process is a genuine competitive advantage and no product supports it, building is the right call.

Quick Diagnostic

What you're experiencing	Likely cause	First thing to do
Things take too long	Waiting, not working	Map where time is spent idle vs active
Mistakes keep happening	Re-keying or unclear ownership	Identify the source of truth for each data type
Team ignores the system	Process doesn't match reality	Ask what workaround they use instead
You can't answer basic questions about the business	Data scattered across tools	Consolidate before you automate
Same task, every week, forever	Genuine automation candidate	Cost the hours, then build

How to Run a Rough Process Review Yourself

You don't need a consultant to make a start. Pick your most painful process and do this:

1. Write down every step, including the boring ones. Not how it's supposed to work, how it actually worked last Tuesday. Include the emails, the chasing, the double-checking.
2. Mark each step as active or waiting. Most businesses are shocked by the waiting-to-active ratio. Waiting is almost always cheaper to fix than active work, and it rarely needs software.
3. Count the handoffs. Every time work passes between people or systems is a place it can stall. Fewer handoffs beats faster handoffs.
4. Ask who owns it. If more than one person owns a step, nobody does.

If that exercise produces obvious fixes you can make on Monday, brilliant. Do those first and see what's left. Whatever's still painful afterwards is a genuine candidate for automation or a custom build, and you'll be commissioning it from a much better-informed position.

Where Software and Automation Come In

To be clear: we still build things. Custom web applications, internal tools, Android apps, integrations between systems that don't talk to each other, AI-assisted workflows for the repetitive communication nobody enjoys. That work is often exactly what a business needs.

The difference is sequencing. We'd rather spend a week understanding your operation and recommend three process changes and one small build, than spend three months building something impressive that solves the wrong problem. It's less revenue for us in the short term. It's the reason clients stay with us for years.

Frequently Asked Questions

How long does a business process review take? For a single process, usually a few days. For a whole small business, one to two weeks including interviews with the people actually doing the work. You get a written summary of where time and money are going and what to change first.

Can we hire you for advice without committing to a build? Yes. Plenty of clients take our recommendations and implement them in-house, or with tools they already pay for. There's no obligation to build anything with us, and we'll tell you when off-the-shelf software is the better answer.

We're a small team, is this only for bigger businesses? It's more valuable for small teams, not less. When five people run an operation, an hour a day lost to admin is a meaningful share of your capacity. Large companies can absorb inefficiency; small ones feel it immediately.

What if the answer is that we don't need anything? Then we'll say so. We've told businesses their process is fine and their real problem is pricing, or hiring, or that they need to say no to a difficult client. It's a short conversation and it costs you very little to have it.

Start With a Conversation

If something in your business is taking longer than it should and you're not sure whether the fix is a new system or a better way of working, that's exactly the question we like being asked.

Get in touch. No obligation, no pushy follow-ups, and we reply to every message within one business day.