What a business process review actually finds

People often imagine a process review is a box-ticking audit. Done well, it is the opposite: a practical look at how your business actually runs, and where the quiet costs are hiding. Those costs are usually larger than anyone expects.

The hidden cost of how work flows

Most inefficiency is invisible because it is spread thinly across every day. McKinsey found that the average knowledge worker spends nearly 1.8 hours a day, around a fifth of the week, just searching for information, and about 28% managing email. Add the cost of jumping between tools: Harvard Business Review researchers measured workers toggling between apps around 1,200 times a day, losing close to four hours a week simply reorienting, while Asana’s research puts the average at about 10 apps and 25 switches a day.

None of that shows up on an invoice, which is exactly why it persists.

What a review actually maps

We follow the real path of a job from start to finish, including the workarounds and the steps only one person knows. That picture alone usually surfaces obvious wins. The recurring culprits are familiar:

Friction	What it looks like	The fix
Manual re-keying	The same data typed into three systems	Integration or automation between tools
Tool sprawl	Ten apps that do not talk to each other	Consolidate, connect, or replace
Stalled approvals	Work waiting on one person’s inbox	Clear ownership and a simple workflow
Tribal knowledge	Only one person knows the real process	Document it, then build it into the system

How the review actually runs

The part people worry about is what it will cost them in time, and almost nobody answers it. We ask for about an hour from each person who actually does the job, plus whatever documentation already exists. A small, focused review usually costs the business two to three staff hours in total. A wider one, running across several functions, is nearer ten to fifteen. Those are totals across everyone involved, not people taken out of the business for a day.

If the documentation does not exist, that is fine. We are not going to ask you to document your processes before paying us to understand your processes.

Everything else happens on our time: the mapping, the analysis, the research into options, and the writing. A review takes one to five days of our work depending on how much of the business we need to understand. One process might take a day. Several connected processes across teams and systems will take longer. The price is agreed before anything starts, and it does not move. If it takes us longer than we expected, that is our problem rather than yours.

When a process review is not what you need

Sometimes the honest answer is that you already know. If you can name the problem, name the fix, and nobody in the business would argue with either, you do not need anyone to map it for you. You need to go and do it. Paying for a review in that situation buys you a tidier version of something you could already describe.

A review earns its keep in the other case: when the symptoms are obvious but the cause is not, when three people would give you three different accounts of how the same job gets done, or when the obvious fix is expensive enough that being wrong about it matters. That is also why the first conversation is free. It exists to work out whether there is a problem worth investigating at all, and it can perfectly well end with us saying there is not.

From map to costed plan

A good review does not end with a diagnosis. You come away with a written, prioritised, costed plan: what to fix first, what it is likely to cost, and the expected payback, whether that is better process, the right software, or some practical automation. It is useful on its own, even if you take it no further, and you own everything.

The obvious next question is what the review itself costs. We have written that down rather than making you ask for it: what a business process review costs, including where the pricing starts, what moves it, and when not to buy one.

This is our distinctive heartland. We review your processes and build the software to fix them, rather than handing you a report and walking away.

When that plan needs an owner to deliver it, that is where a fractional project manager comes in.

Suspect there is friction worth removing? A Business Review maps it and turns it into a costed plan. Start a conversation.

A review often surfaces manual, repetitive steps. If yours does, it is worth checking your AI readiness before committing to a solution.

Frequently asked questions

What is a business process review?

A business process review follows the real path of a piece of work from start to finish, including the workarounds and the steps only one person knows, then sets out what is getting in the way and what it costs. It ends in a prioritised, costed plan you own, not a report that gets filed.

How long does a business process review take?

One to five days of our work, depending on how much of the business we need to understand. A focused look at a single process might take a day. Several connected processes across teams and systems will take longer. From your side it is about an hour per person, and two to three staff hours in total for a small review.

How much does a business process review cost?

The first session is free. Paid work starts from £950, which is the smallest engagement worth doing properly rather than a headline price with conditions attached. The price is fixed and agreed up front, and headcount is a poor guide to it: a hundred-person business can have one simple process, and a twelve-person business can have six systems and three workarounds.

What is the difference between a business process review and an audit?

An audit checks your work against a standard and tells you where you fall short of it. A review starts from how the business actually runs and looks for cost, friction and risk, wherever they happen to be. An audit tends to end in findings. A review ends in a plan with an owner, an order and a price.