AI readiness assessment
Your data, systems, skills and controls scored against what the first project actually needs, with the gaps named.
Two weeks · interviews and system review · a written readiness report
TRANSFORMATION
Your first AI project, shipped in ninety days.
A readiness assessment in your stack and your team's context, a use-case shortlist ranked by return, a ninety-day pilot that proves the highest-value one on real data, and an eighteen-month roadmap with named owners. Bias toward shipping, not slide decks.
How it works
The ninety-day playbook: five stages, two of which can stop it.
Every stage leaves an artefact a board can read: the readiness report, the ranked shortlist with its assumptions, the pilot's decision record, the roadmap with names on it. The programme is run the way our own ISO/IEC 42001 AI management system requires.
- Assess (Readiness). Interviews, a system and data review, and a skills and controls check. A readiness report with the gaps named. Tools: Readiness report, Data inventory.
- Prioritise (Use cases). A ranked shortlist with a return estimate and a risk grade for each, built from your numbers in a scoring workshop. Tools: Scoring model, One-page brief per case. Gate: One use case is chosen on evidence.
- Build (Pilot). The pilot built in your systems, on your data, with a measured baseline from day one and a senior engineer on every change. Tools: Your stack, Weekly demo, Code review trail.
- Measure (Go/no-go). Results against the baseline, presented to the people who own the number. A no is a result the programme paid for. Tools: Baseline comparison, Decision record. Gate: Scale only if the measured result clears the bar.
- Roadmap (Eighteen months). Sequenced initiatives with named owners, dependencies, and the controls each needs before it ships. Reviewed every quarter. Tools: Named owners, Quarterly milestones, ISO/IEC 42001 controls.
What we build
Five things the programme produces, in the order it produces them.
Use-case prioritisation
A shortlist ranked by return, feasibility and regulatory exposure, with a return estimate per case you can challenge.
Workshop · scoring model · a one-page brief per case
Ninety-day pilot
The top use case built in your systems, on your data, and measured against a baseline from day one.
Weeks three to twelve · your systems · a go/no-go on evidence
Eighteen-month roadmap
Sequenced initiatives with owners, dependencies and the controls each needs before it ships.
Named owners · quarterly milestones · a budget envelope per initiative
Governance and operating model
The review board, the controls and the reporting, so the second project is easier than the first.
ISO/IEC 42001 aligned · risk register · model inventory
How we work with you
Start with the assessment. The ninety days begin when a use case is chosen.
- 012 weeks
Readiness assessment
Interviews, a system and data review, and a scoring workshop with the people who own the outcomes.
- 0212 weeks
Ninety-day programme
The chosen use case built on your data and measured against its baseline, then the roadmap written with owners named.
You leave with
A pilot measured against a baseline, a go/no-go decision, and the eighteen-month roadmap.
- 03Ongoing
Programme partner
Quarterly roadmap reviews, a governance board that actually meets, and the next initiative delivered.
You leave with
A roadmap that stays true, and a second project easier than the first.
Five phases, and the artefact the programme hands over at each one.
The full process- 01
Discovery & Strategy
1-2 weeks
Readiness report and the ranked use-case shortlist
Signed off by you, before engineering starts
- 02
Architecture & Design
2-3 weeks
Pilot architecture and success criteria, agreed in writing before the build
Signed off by your security team
- 03
Agile Development
4-12 weeks
The pilot in your systems, with the review trail
Signed off by a senior engineer, every PR
- 04
Quality Assurance
2-4 weeks
Pilot results against the baseline, presented to the people who own the number
Signed off by your QA and compliance teams
- 05
Launch & Evolution
Ongoing
The roadmap with named owners, reviewed every quarter
Signed off by your team, every week
The readiness assessment and the pilot fit inside the ninety days; the roadmap review runs quarterly after it. Every phase ends with a named artefact and a named sign-off, under ISO/IEC 27001 and ISO 9001 controls.
Recent work on this line
Two programmes running on this line now.
ERP / Enterprise Software
Active engagementERP transformation programme and AI-enabled automation for a UK-based consultancy
- United Kingdom
- ERP
- AI automation
Healthcare / Diagnostics
Active engagementDiagnostic-lab platform engineering and AI-driven reporting for a Hyderabad diagnostics centre
- Diagnostics
- Lab platform
- AI reporting
How we work
Built like a product company, shipped like one.
- 01
Audit-engineered by default
Every engagement runs under ISO/IEC 27001, ISO 9001, ISO/IEC 20000, and ISO/IEC 42001 controls. DPDP-aligned, with HIPAA / GDPR / RBI overlays available per project.
- 02
Founder-led delivery
Your discovery call is with a founder. The architecture review is with a senior engineer who stays on the project. No body-shop, no offshore handoff, no account-manager translation layer.
- 03
Bias to ship, not slide
We don't write demos that can't survive a Friday production deploy. Every milestone produces an artifact your team can use immediately: code, diagrams, telemetry.
Questions buyers ask
Straight answers, before the first call.
Is this consulting or engineering?
Both, in that order and with the same people. The assessment and the prioritisation are consulting; the pilot is engineering, built in your systems by the engineers who will stay on it. The roadmap is written by people who have just shipped something in your stack, which is why it has owners and dates rather than themes.
What if the pilot fails?
Then the go/no-go says no, on evidence, and that is a result the programme paid for. The pilot is measured against a baseline agreed before the build; if it does not clear the bar, the roadmap says why and what to try instead. What we will not do is scale something the numbers did not support.
Do we need to change our stack first?
No. The readiness assessment is done in your stack and your team's context, and the pilot is built in the systems you already run. Where a gap would block the first project, the report names it and the roadmap sequences it.
How is the return estimate produced, and can we challenge it?
From your numbers, in a scoring workshop with the people who own them: volume, unit cost, error rate, time. Each use case gets a one-page brief with the assumptions written down, so any of them can be challenged and the ranking re-run.
How does this fit with ISO/IEC 42001?
The governance and operating model is aligned to it: an AI risk register, a model inventory, a review board and the controls each initiative needs before it ships. OrbitNexa is certified against ISO/IEC 42001, so the programme is run the way our own AI management system requires.
Insights
Reading on transformation.
Engineering notes on transformation, written by the engineers on the work.
Ready to ship a first AI project?
Book a transformation workshop. We'll come back with a proposed agenda, not a slide deck.
+91 912-195-7728Hyderabad, IndiaEvery brief gets a senior review. Reply within 1 business hour, 9 AM-7 PM IST.