SERVICES / AI REALITY CHECK
Find out where AI pays. In writing
Two to three weeks inside your real workflows. One fixed fee. A report with verdicts you can act on — or hold us to.
01 / WHAT YOU GET
Five deliverables, one report
The walkthrough below mirrors the sample report, section by section.
-
Workflow audit
One to three nominated processes, mapped from the artefacts your team actually uses. Not a survey. Not a maturity matrix.
-
Quantified opportunity map
Hours and cost recoverable per process, with the basis of every number shown. Where the data only supports a range, you get an honest range.
-
Scored use-case shortlist
Every candidate scored for value, complexity and readiness, each carrying GO / NOT YET / NO-GO — and the not-yets name their unlock conditions.
-
Sequenced roadmap
What to do in the next 90 days, what waits for its preconditions, what to park. The first GO arrives build-ready: scope, gates and measurement plan included.
-
Executive readout
60 to 90 minutes with your leadership, arguing for the verdicts and taking every hard question.
Recoverable hours per month, per process. Ranges reflect what the data supports. Illustrative sample — process names redacted.
02 / WHAT IT ASKS OF YOU
About four hours of your team's time
About four hours of interviews across two to four process owners, read access to the relevant systems, and an executive sponsor at the readout. If you can't free that up, you're not ready to buy this — and we'd rather tell you that now.
03 / THE COMMERCIAL SHAPE
One fixed fee, fully credited
One fixed fee, agreed before we start. 100% credited to your first build phase if commissioned within 60 days. No obligation to build anything — a third of the value is usually in what we tell you not to do.
04 / VERDICTS, ILLUSTRATED
What a verdict looks like on the page
| Use case | Value | Readiness | Score | Verdict |
|---|---|---|---|---|
| Document intake triage | High | Ready | 82 | GO |
| Report drafting | Med | Data gap | 54 | NOT YET |
| Client-facing advice responses | Med | Low | 31 | NO-GO |
The NO-GO reasoning is part of the deliverable: failure cost lands on a customer or regulator, and the accuracy ceiling isn't high enough. Illustrative sample.