Scored use-case inventory
Every candidate, its scores, its owner and the evidence behind the numbers. The single most reused document we produce.
We score your use cases on value and feasibility, check whether the data can support them, and hand you a 12-month roadmap with a business case your board can approve.
Leadership teams come to us with the same three problems. There are a dozen AI ideas and no agreed way to rank them. Vendors are promising outcomes nobody can verify. And the finance team wants a number before anyone has defined the work.
Our strategy engagement fixes the ranking problem first, because everything else follows from it. Each use case is scored on the same criteria, in the open, with the people who will own it in the room. The result is a short list everyone can defend and a long list everyone can live with.
Each use case is scored from one to five on six criteria by the people who would own it, with us challenging the evidence. The totals rank the list; the pattern of scores explains why.
| Criterion (1–5) | Example: support deflection | Example: invoice extraction | Example: demand forecasting | Example: autonomous negotiation |
|---|---|---|---|---|
| Business value (cost saved or revenue) | 5 | 4 | 5 | 3 |
| Technical feasibility today | 4 | 5 | 2 | 1 |
| Data readiness (exists, clean, accessible) | 4 | 4 | 2 | 2 |
| Risk and compliance exposure (5 = low) | 4 | 4 | 4 | 1 |
| Time to first measurable result (5 = fast) | 4 | 5 | 2 | 1 |
| Organisational readiness (owner, process, appetite) | 4 | 4 | 3 | 2 |
| Total (max 30) | 25 | 26 | 18 | 10 |
| Quadrant | Do now | Do now | Plan and de-risk | Avoid |
Illustrative scores for example use cases. Real engagements score 10 to 30 candidates and weight criteria to the client's situation. Regulated industries weight risk more heavily; see our industry pages.
Every candidate, its scores, its owner and the evidence behind the numbers. The single most reused document we produce.
Model policy, retrieval approach, integration points and hosting choices, drawn as the system you will actually run. See LLM app development.
Where the data for the top use cases lives, who owns it, how clean it is and what it will take to make it usable. Read our guide to data readiness for AI.
Sequenced projects with budget ranges, dependencies and decision points. Written so the second project can start before the first is perfect.
Costs, expected benefit range, the metric that proves it and the point at which you would stop. Built with our approach to measuring AI ROI.
An AI policy outline, a risk register and the controls you will need for the EU AI Act or ISO 42001, via our AI governance practice.
Interviews with leaders, process owners and engineers. Inventory of systems, data and existing pilots. Candidate use cases collected, not judged.
Scoring workshops with owners. Data inspection for the top candidates. Build-versus-buy checks against the market.
Target architecture, model policy, security and governance baseline. Cost ranges for the top three projects.
Sequenced plan, business case for project one, leadership readout and a decision meeting with a yes-or-no question.
The most common failure is starting with the most exciting use case rather than the most feasible. Six months and a large invoice later, the team discovers the data was never clean enough, the integration needs a system nobody owns, or the compliance team was never asked. Scoring in week one costs a fraction of that and makes the same discovery on paper.
Every use case on the roadmap carries a build, buy or wait recommendation. Buy when a vendor product covers most of the job and your data is not the differentiator. Build when the workflow is specific to you, the data is yours and the economics at volume favour owning it. Wait when the value depends on a model capability that is improving quickly, or on data you do not yet have. Our guide to build versus buy for AI works through the trade-offs in detail.
Keep the strategy honest month after month with a part-time technical leader.
ExploreDeliver project one with the team that wrote the roadmap.
ExploreHow we sequence projects and set decision points.
ReadFixed scope, retainer or team extension: how the commercial side works.
CompareFour to six weeks for a single business unit, eight to ten for a group with several divisions. The limiting factor is usually access to the people who know where the data lives, so we book those interviews in week one.
A scored use-case inventory, a target architecture, data readiness findings, a 12-month roadmap with budget ranges, a business case for the first project and a governance baseline. All written to be read by a board and used by an engineering team.
No. The roadmap is vendor-neutral and you can take it to any team. Many clients do ask us to deliver the first project through AI implementation, which is why we only recommend things we would be willing to build.
Usually yes. The list is rarely the problem; agreeing which three to fund and which seven to park is. The scoring method gives leadership a defensible way to say no, and the data readiness check stops the favourite idea failing on week two.
The readiness assessment is a ten-minute self-check that gives you a score and a shortlist of gaps. Strategy consulting is a facilitated engagement with interviews, data inspection, architecture work and a funded plan.
Tell us about your systems, your data and your constraints. We reply within one business day with a straight answer and a suggested next step.