Two to four weeks to answer three questions: where your team's hours go, which of those AI would genuinely improve, and what each is worth in your own numbers.
What happens, step by step
Shown at the Starter audit’s pace, about two weeks. The Standard audit runs the same steps over three to four weeks, across more functions.
-
Scoping call, 30–45 minutes
Scope agreed, NDA signed before any data changes hands.
-
Pre-audit questionnaire
Each person lists their recurring tasks — fifteen minutes that makes the interviews far sharper.
-
Interviews and observation, week one
Owner, operations, customer-facing staff, finance. Managers describe the process as intended; staff describe the real one.
-
Workflow maps
Trigger, steps, handoffs and waiting — marking where data is re-entered and where one person knows how it works.
-
Systems and data review, week two
What you pay for, what is used, and whether the data is good enough to build on.
-
Score and sequence
Scored against the readiness table below, then sorted: build now, fix first, or not worth pursuing.
-
A working prototype
A rough build of the top opportunity on your sample data, so the readout shows something running.
-
Readout, 60–90 minutes
The report, the prototype and a priced proposal.
How readiness is scored
We score each opportunity on four things, from evidence rather than enthusiasm.
| Dimension | 1 — not ready | 3 — partial | 5 — ready |
|---|---|---|---|
| Data | Scattered, inconsistent or unreachable | In one system, uneven quality | Enough volume, consistent, reachable by tools |
| Workflow | Different every time | Exists with known variations | Repeatable steps, measurable volume |
| Tooling | Capability missing and unaffordable | Available, integration needed | Already in the stack you pay for |
| Adoption | No owner, staff opposed | Owner named, capacity tight | Owner named, staff involved, time protected |
What you get told
Three groups: build it now, fix something first, or not worth doing — each with the reason.
How value is calculated
Hours saved times your own loaded hourly cost, beside a downside case at half the saving. Never presented as a headcount reduction.
What you get at the end
- A workflow map for each process in scope, including the parts nobody documented
- A ranked list of opportunities with a readiness score and a dollar estimate on each
- A software inventory with cost, owner and actual usage
- A working prototype of the top opportunity, running on your sample data
- A roadmap with sequencing, and a fixed price for the first build
- A plain statement of anything that isn't ready, and what would make it ready
Half the audit fee is credited toward any build signed within 60 days of the readout.
Two things we tell every team
This is about tedious work, not jobs
Every interview opens the same way: the goal is removing repetitive work, not people. Staff who fear layoffs describe the process they are supposed to follow, and the audit is worth nothing.
Sometimes the answer is no
If the data is not there, what you build breaks in month two. The report says so — a large part of what you are paying for.
Start with a conversation
Twenty minutes, no preparation. If an audit is not worth it, we will say so.
Limited time · 40% off an audit. Terms