Assess AI readiness. Prioritize high-impact opportunities. Build a practical roadmap for enterprise AI adoption.
A diagnostic, not a demo. It does not select a vendor and it does not sell a platform. It produces a sequencing decision — what to build first, what to build second, and what not to build at all.
Not because the technology fails. Because the order is wrong. A pilot is funded in the department that shouted loudest, on data that could not support it, with no sponsor past month three.
It scores readiness, ranks every department, and sequences AI adoption into waves. Every call is defended by the company's own evidence.
Score the organisation's real capacity to absorb AI — data, leadership, systems, people, governance, existing AI. Capacity, not appetite.
Score every function on value and feasibility, multiply to a Priority Index, and let the engine pick the top three.
Wave 1, Wave 2, Wave 3 — and a Do-Not-Start list, each call defended by your own evidence.
Every Part 1 question maps to one of these. They describe your capacity to absorb AI, not your appetite for it. Weighted into a single Readiness Score out of 100. Click any card.
They run automatically once your answers are scored. They exist to stop you funding a pilot that cannot succeed — the one that dies in month five, after the budget is committed and the sponsor has moved on.
No department enters Wave 1. The first ninety days go to data, not to AI.
The roadmap stops at Wave 1. A twenty-four-month plan with no sponsor helps nobody.
Wave 1 is restricted to internal, non-customer-facing use until controls are fixed.
198 questions in two parts. It is deliberately not answered by one person — nobody in a company of this size can credibly speak to production data quality, invoice cycle times and service volumes at once. Five to eight function heads respond. Your coordinator reconciles and submits once.
| Part | What it covers | Who answers | Questions |
|---|---|---|---|
| Part 1 | Readiness Core — the six foundations (Modules M1–M7) | CEO, COO, CIO | 78 |
| Part 2 | Department Assessment — the same twelve questions each | Each function head | 12 × |
Six modules, each addressed to the person who can actually answer it. Click any module for a real sample question and the hint that guides a strong answer.
That symmetry is what lets the analysis rank functions fairly. The twelve questions are really five measurements wearing different clothes — three decide whether it is worth doing, two decide whether it can be done.
Questions 10–12 are not scored. They supply the candidate use case, the person-hours, and the failure mode that appear in your report.
A board-facing document, not a slide pack. Every number in it is derived from your own answers — none of it is illustrative, and none of it is borrowed from someone else's industry.
The complete blueprint for a fictional ₹1,400 Cr formulations manufacturer — plants under CDSCO, Schedule M and US FDA oversight. Real structure, real engine output, nothing redacted.
The clock starts when your questionnaire is submitted — not when you pay. Take the time you need to assemble your function heads.
A 28-page board-facing document. Readiness scored, ten departments ranked, three waves sequenced, and a defended Do-Not-Start list.
Every candidate use case your function heads named, scored and ranked in Excel. The working file your team takes forward.
Sixty minutes on the findings, the ranking, and the three arguments your leadership will make against it.
Create your account. The questionnaire is issued on payment.
Part 1 with your CEO, COO and CIO — 40 to 55 minutes. Then 25 to 30 minutes per function head.
Your coordinator reviews and submits once. The fifteen-day clock starts here.
Your blueprint is published to your account. You are emailed the moment it is live.
The diagnostic is a complete piece of work with a defined end. You are not buying the first step of a programme you have not agreed to.
Tell us about your organisation and we'll share pricing tailored to your revenue band.
Fifteen working days from submission, you will know where to start, in what order, and what not to build at all.