Most businesses that come to us already have a solution in mind. "We need a CRM." "We need an app." "We need AI." Sometimes they're right. Often the real problem sits somewhere slightly different — and building the wrong thing well is still building the wrong thing.
A workflow gap analysis is how we find out before anyone writes code. Here's what it involves and what it tends to uncover.
It starts by watching, not asking
If you ask a team how a job gets done, you'll hear the official version. If you sit with them while they do it, you'll see the real one: the sticky notes, the WhatsApp messages, the spreadsheet only Sam updates, the step everyone skips on busy days.
So the first stage is observation. We follow real jobs from start to finish — a quote request, a booking, an order, an onboarding — and map every hand-off between people and systems. The aim isn't to judge anyone. Workarounds usually exist because the tools didn't fit, and they're the most useful clues we get.
The gaps we find most often
Every business is different, but the same handful of gaps turns up again and again.
Double entry
The same details typed into more than one place: a booking form, then the calendar, then the invoicing tool, then a spreadsheet for reporting. Each copy is a chance for a typo, and nobody's sure which version is right.
Hand-offs that rely on memory
A job moves from sales to operations because someone remembers to send a message. When they're away, it stalls. These gaps are invisible until a customer asks why nothing has happened.
Approvals stuck in inboxes
Quotes, purchase orders and leave requests waiting for a reply that's buried under forty other emails. The work itself takes minutes; the waiting takes days.
Reports built by hand
Someone spends Monday morning pulling numbers from three systems into one spreadsheet, so the owner can see what happened last week. By the time it's done, it's already out of date.
Leads and opportunities that go cold
Enquiries that arrive after hours, quotes that take days to prepare, follow-ups that never get sent. This is where automation and AI often pay off fastest. Logic Building Co, for example, went from hours of measuring plans for every enquiry to a draft estimate waiting before anyone picks up a scale ruler.
Putting a cost on each gap
Finding friction is easy; deciding what to fix first is harder. So for each gap we estimate what it actually costs — roughly, and in the business's own terms:
- Hours lost per week, and whose hours they are.
- Errors that slip through, and what fixing them costs.
- Revenue leaking away through slow replies or missed follow-ups.
These numbers don't need to be precise. They need to be honest enough that the decision becomes obvious. A gap costing two hours a month can wait; one costing a day a week probably can't.
What you get at the end
The output is a short, practical blueprint rather than a thick report. For each gap, it recommends one of four things:
| Recommendation | What it means |
|---|---|
| Change the process | Sometimes the fix is a rule, a checklist or a better template — no software needed. |
| Buy | A mature off-the-shelf tool already does this well. |
| Connect or automate | Your tools are fine; the gap is between them, or a repetitive task a workflow can take over. |
| Build | Nothing fits without heavy workarounds, and the gap is costly enough to justify custom software. |
Each recommendation comes with a rough size and an order of priority, so you can see which pieces deliver the most for the least.
Then: fix the biggest gap first
If you decide to go ahead, the sensible approach is to start with the single highest-impact gap, ship it, and measure the time it saves before moving to the next. That keeps risk low and makes the value visible early. In practice that might mean an AI workflow that reads incoming forms, a business system that replaces a fragile spreadsheet, or a dashboard that ends the Monday-morning reporting ritual.
Bugaboo Landscaping is a good illustration: the gap wasn't "we need software" in the abstract — it was that franchisees had no shared system and clients never saw their before-and-after photos. Fixing those two specific gaps shaped the whole build.
Is it worth doing?
A gap analysis earns its keep when:
- several problems overlap and it's not clear where to start;
- you've been quoted for a big system and want a second opinion on what you actually need;
- the team is busy but you can't pinpoint where the time goes.
If you already know exactly what you need and why, you may not need one — a straight build conversation is fine.
