This is the one-page map you receive within 48 hours of completing the Back-Office Leakage Calculator — at no charge, drafted with the same AI stack the maps recommend and finished by hand, from your eight answers and your context note. This sample is an anonymised composite; the figures come from the calculator’s own model.
Your thinking in the room is exceptional — and almost none of it escapes the room. The two leaks compound: every engagement re-buys context you already paid for, and every session’s best IP leaves with the client.
Same formulas as your calculator results — your rate, your volume, 46 working weeks. Rounded deliberately: these are planning figures, not invoices.
“I know I should write things down after sessions but I’m usually straight onto a train or another call. I’ve got ten years of workshops in my head and about four documents to show for it.” — from the context note
The 24 hours after a session — when everything is still retrievable — are structurally occupied by travel and the next delivery. Any system that relies on “sitting down to write it up later” will keep failing, because later is already spoken for.
Notes are scattered across email threads and client-owned documents. That’s the 60–75 minutes of re-entry before each returning engagement — paying again for context you already earned.
The frameworks and reframes that make sessions exceptional currently live in memory and other people’s slide decks. The practice’s most valuable asset sits on other people’s servers.
Designed for the train, not the desk — it works inside the window you actually have.
Cost to run: ~12 minutes per session. Attacks the two dominant leaks at the source.
≈ £34,500 of context leakage (72% recovery — re-entry drops to minutes once records are searchable) plus ≈ £13,800 of expertise leakage (60% — the library compounds from session one). Equivalent to ~24 delivery days. Time and relationship workflows come second — sequencing matters more than ambition.