How the audit works, in detail
The method, the arithmetic and the refusals, written out properly. Everything here describes what the product actually does, including the parts that make the number smaller.
What a fifteen-minute interview actually asks
Why the questions are about yesterday rather than about your job, and what gets written down.
How to put a number on work before you automate it
The arithmetic behind the headline figure, and the four places it usually goes wrong.
Why the biggest process is usually the wrong pilot
Ranking by value alone points straight at the work that is hardest to automate. Feasibility comes first, and the rubric is printed on the page.
The work nobody owns
Everyone describes their own step accurately. Nobody describes the waiting in between, because nobody experiences it.
What we will not automate
The categories scored low on purpose, and why refusing them makes the rest of the number worth more.
Paying on acceptance rather than on delivery
How the fees are structured, why there is no percentage-of-savings deal, and what happens when an automation breaks.
Is your team big enough for an audit to pay for itself
Who this works for, who it does not, and the arithmetic you can do yourself before speaking to anyone.
Why we ask people instead of measuring them
Time-tracking produces better data about a worse question. What asking gets you, and what it costs.
What to do with the map when the audit is over
Three routes out of a process map, including the two where you do not hire anybody.
Who this is not for
Five situations where the audit produces a real map and still does not pay for itself.
How this differs from hiring a consultant
Both produce a document. The difference is how many people were asked, and what the number is allowed to claim.