AI Opportunity Score
Where would AI earn its place?
Eleven questions. A scored range, and the arithmetic behind it.
It runs in your browser. It does not pretend an estimate is a business case.
Your business
1 / 11
How many people work in the business?
Scale sets how much a recovered hour is worth, not whether the opportunity exists.
01The full assessment
What arrives at the end of it.
The score above is a compressed, self-serve version. A real assessment measures your actual volumes and produces the documents below — yours to act on with or without us.
- Enquiry arrives
- Read next morning
- Called to qualify
- Re-typed into CRM
- Follow-up, if remembered
4 of 5 steps need a person
- Enquiry arrives
- Qualified conversationally
- Scored, written to CRM
- Agent opens a warm lead
- Nurture runs on schedule
1 of 5 steps needs a person
| Workflow | Volume | Rep. | Human | Data | Risk | Score | Treatment |
|---|---|---|---|---|---|---|---|
| Lead response & qualification | 1,200/mo | 9 | 8 | 9 | 3 | 86 | Automate |
| Invoice & document processing | 1,842/mo | 8 | 9 | 7 | 7 | 74 | Prepare, approve |
| Repeat customer questions | 2,100/mo | 8 | 6 | 8 | 2 | 68 | Automate |
| Management reporting | 40/mo | 9 | 5 | 6 | 2 | 52 | Automate |
| Quoting & pricing | 500/wk | 6 | 7 | 5 | 8 | 44 | Prepare, approve |
| Supplier selection | 12/mo | 2 | 4 | 2 | 9 | 12 | Keep human |
- 01Month 1
Foundation
- Systems access confirmed
- Baseline measured on two workflows
- Scope of authority drafted and signed
Risk. If the CRM has no usable API this month extends.
- 02Month 2
First workflow live
- Lead response built and integrated
- Piloted with one team
- Exception queue triaged daily
Risk. Adoption, not capability, is the usual failure here.
- 03Month 3
Second workflow + measure
- Document processing built
- Before/after reported against baseline
- Handover and configuration training
Risk. Document corpus quality decides the straight-through rate.
Extracts from a worked example. Your register would carry your workflows, your measured volumes and your systems.
02Deliverables
Six things, every time.
- 01
Workflow maps of the areas we examine
Drawn from what your team actually does, including the workarounds — not from the process documentation. If the people doing the work do not recognise the map, it is wrong.
- 02
A scored opportunity register
Every workflow scored on the same eight factors, ranked, with the treatment stated: automate, prepare for approval, assist a person, or fix the process first.
- 03
Measured volumes, not estimates
Cases per month and minutes per case, counted rather than recalled, so the value at stake is a number you can defend internally.
- 04
A 90-day implementation sequence
What first, what second, and why that order — with the dependencies, the risks, and the pilot we would recommend starting with.
- 05
The scope of authority we would propose
What the system may do unattended, what it must propose for approval, and what stays entirely human. Written before any code.
- 06
An honest answer if the answer is no
If your highest-value fix is a process change rather than software, that is what the report says. You keep the analysis either way.
Next step
Get the full AI Opportunity Report.
We will map your actual workflows, score the highest-value AI opportunities, and return a 90-day implementation sequence with risks, dependencies, expected impact, and the first pilot we would recommend.
Fixed fee, 7–10 days. It can conclude that AI is not your highest-value fix — that has happened, and you keep the analysis regardless.