Who this is not for

Most pages like this are a sales device: a short list of unlikely disqualifiers designed to make everyone reading feel selected. This one is meant literally. Each of these is a case where the audit produces an accurate map and still does not earn its cost, and it is cheaper for both sides to find that out here than on a call.

If almost nobody does the same thing twice

The audit finds repetition. In a company where the work is genuinely bespoke every time, a studio taking on unlike projects, or a handful of specialists each doing something different, there is little repetition to find. The map will be thin and correct, and thin is not worth paying for.

The signal is not headcount. It is whether two people in the company could describe the same routine.

If the team is too small for the arithmetic

Covered properly in [is your team big enough](/guides/is-your-team-big-enough), but the short version belongs here. Below a certain size the found hours cannot exceed the cost of the work required to remove them, however well the map is built.

If you already know what to automate

Some owners arrive with one specific, well understood problem: the invoices, the onboarding checklist, that spreadsheet. If you can already name the process, its trigger, its steps and roughly what it costs, discovery is not your bottleneck. A map would be paying to be told what you just said.

Go and get that thing built. Come back when it works and you want to know what is next.

If nothing can be acted on for two quarters

An audit that lands in a company with no capacity to change anything produces a document that goes stale before it is used. If a hiring freeze, a system migration or an acquisition means nothing can move until the autumn, run the audit in the autumn. The map will be better then anyway, because it will describe the company you will actually have.

This is the most common of the five, and it usually gets discovered afterwards rather than before.

If the real problem is that people are unhappy

Repetitive work is miserable and removing it helps. But where the underlying issue is trust, management or morale, a process map will surface the symptoms and misattribute them. The interviews will produce genuine grievances, the report will price them as hours, and automating the hours will not fix what was actually wrong.

A process map is a poor instrument for an organisational problem, and it looks confident enough to be mistaken for a good one.

What this leaves

The audit fits companies with enough people doing enough repeated work that a map shows them something they could not see from the inside, and enough freedom in the next quarter to act on it.