60/30/10 Audit. The map before you build.
A 1 to 2 day diagnosis that splits your operation into three layers: what code solves, what rules solve, and the little that truly needs AI. Delivered in writing.
What it is
Most companies ask for AI to fix pains that are not AI pains. A typical process breaks down like this: about 60% is deterministic logic solved with a script or an integration, 30% is known business rules automated with workflows, and only 10% requires real judgment over unstructured information. There, and only there, AI adds value.
The Audit maps your processes into those three layers and delivers the diagnosis in writing: what to automate first, with which kind of tool, and in what order of return. We build nothing during the Audit: you get the map so you can decide where to invest before buying tooling.
Who it's for
- Teams that want to adopt AI and don't know where to start
- Companies with several candidate processes and doubts about priority
- Leaders who already tried ChatGPT or Zapier and need a serious plan
- Boards that want the business case before approving a build
- Teams where “how much did we sell last month” gets a different answer depending on who you ask
What you get
- 01A 60/30/10 map of your processes, prioritized by return
- 02Written diagnosis: each finding with a score, evidence from your own operation, and a concrete fix
- 03An explicit list of what NOT to automate
- 04Tool recommendation per process: which type, which integrations, in what order
- 05A suggested route if you later decide to move to the MWP Sprint
How we work
- Day 1
Immersion
Sessions with your operating team, workflow mapping, identification of quantifiable pains.
- Day 2
Diagnosis
60/30/10 classification of each process, prioritization by return, writing of the deliverable.
- Post-delivery
Walkthrough
A 60 minute session to walk the map with your team and answer questions.
What it does NOT include
- It does not build or configure anything in your systems: that is the MWP Sprint.
- It does not promise outcome metrics: it estimates based on data your own team declared, always citing it.
- It does not recommend tools that clash with your declared constraints. The ERP you said is off-limits stays off-limits.
Specific questions
Does the Audit build anything, or is it just a document?
Just the map. We don't set up workflows or touch code during the Audit: that work is the Sprint. The Audit exists so you decide with real information where to invest, before spending on the wrong tooling.
How much of my team's time does it take?
3 to 4 hours total: one 90 minute session with the sponsor and two 60 minute sessions with operations or your technical lead, spread over 1 or 2 days.
If we hire the Sprint afterwards, is the Audit discounted?
Yes, partially, if the Sprint starts within 60 days. It's documented in the agreement before we start.
We want to query our data in plain language. Does the Audit help with that?
It tells you whether you're ready. A system that answers questions in plain language is quick to build; the real problem is elsewhere. If two areas in your company calculate “monthly sales” differently, the system will pick one of them without telling you and hand back a number that looks right. The Audit catches that before you build, because agreeing on the definition now is cheaper than finding out six months in that the dashboard has been confidently wrong.