Operating audit
Where the hours go.
Seven questions about the work your team still does by hand. The read appears on screen, no email required. The audit itself happens on the mapping call.
01The questions
Seven questions, one screen at a time.
Answer as you would on the call. Nothing is stored unless you choose to send the answers ahead.
- 01 Industry
- 02 Team
- 03 Repeat work
- 04 Hours
- 05 Friction
- 06 Tools
- 07 In 90 days
How this is read: team size, hours a week, and how much already runs on its own each carry points, and each kind of repeat work adds one, up to three. 9 or more of 14 reads as a department to map. Under that, one process first. Mapping replaces the read with a map.
00The mapping call
Bring one process your company still runs by hand. We map it with you on the call. You leave knowing what we would build, what it would cost, when the first build lands, and when it would go live. If we are the wrong fit, we tell you on the call.
02What the audit covers
What we trace on the call.
We sit with the people doing the work and follow leads, quotes, money, and messages through the tools that carry them today.
- 01Where the work entersEvery lead, message, quote, and payment, and the tool that carries it in.
- 02Who touches itThe people who do the work, in the order they do it, and where it waits between them.
- 03OutputAn operating map and a baseline of repeat work, delays, and exceptions.
- 04ControlYour team reviews the map before scope is set.
Your first department
Bring the process you still run by hand.
One mapping call. You leave with the system design, the price in writing, and the date it goes live. The first build lands in two weeks.
How it works
From the first call to a system in production.
Six steps, the sprint shape, where we start, and the guarantee.
See how it works