Scope
Agree the business units, systems and decisions in scope for scoring.
Done when: The scope names decisions, not departments.
One honest picture of what your organisation can actually run with AI today.
The business problem
Pilots get funded, demos impress, yet little reaches daily operations because nobody measured what the organisation can actually run.
What you hear inside the organisation
We have many pilots and nothing in production.
The board asks for our AI strategy every quarter.
Is our problem the data, the people or the platform?
Every vendor says we are ready.
Who it serves and what changes
Client teams and what they need
CEO and board
An honest picture before investing
CDO, CIO, CTO
Priorities by dimension, not by hype
HR and capability
Where skills are missing
Business sponsors
Which use case can start now
The outcome you get
A worked example
The problem we saw
Leadership believed the organisation was ready. Pilots impressed in demos and then stalled with no owner or data access.
How the framework solved it
We scored data, platform, governance, talent, process and value on evidence, not opinion, and showed governance as the real blocker.
The business result
Budget moved from new pilots to fixing ownership and data access, and the strongest pilot became a supported service.
Illustrative example based on common client situations.
In short
AI Readiness Model (AIRM): One honest picture of what your organisation can actually run with AI today.
Ambition is rarely the constraint.
How it works
Levels run from Ad hoc, Repeatable, Governed, Scaled to Self-improving. Most enterprises score unevenly, high on platform, low on governance.
Agree the business units, systems and decisions in scope for scoring.
Done when: The scope names decisions, not departments.
Score each dimension from artefacts and systems, not from self-assessment alone.
Done when: Every score cites the artefact behind it.
Compare current level to the level the target workloads require.
Done when: Each gap is tied to a workload that is blocked by it.
Order the moves so each one unlocks the next rather than running in parallel silos.
Done when: The first ninety days are fundable and owned.
Repeat the scoring each two quarters so progress is measured, not asserted.
Done when: Movement between levels is evidenced by new artefacts.
Is it right for you?
A strong fit if
Probably not yet if
Free assessment
A working session with our senior team. We review what fits your situation, what does not, and where to start.
A focused conversation
We listen to your situation and goals.
Fit review
Which parts of this framework apply to you, and which do not.
A written view
Clear next steps, whether or not you work with us.
Go deeper
Open only the part you need: how it starts, what your team keeps, maturity levels, sector rules and the evidence a reviewer will ask for.
Ambition is rarely the constraint. AIRM scores Data, Platform, Governance, Talent, Process and Value so the roadmap matches the level you are at, not the level of the case study you read.
Version
v2.0
Last reviewed
July 2026
Family
AI Operating System
How this was developed: Built from delivery practice on Saudi and international engagements, then reconciled clause by clause against the published standards below. Revised when a standard is updated or a gate proves unworkable in the field.
One-pager
Stages, exit gates, artefacts, standards crosswalk and FAQs for AI Readiness Model on one printable page, share it with the committee.
Name the two or three workloads the assessment must serve; readiness in the abstract is not useful.
Collect evidence per dimension from the systems themselves, not from questionnaires.
Score, then write the gap statement behind every level so the number can be argued with.
Convert the gaps into a sequenced plan with owners, dates and a re-assessment point.
Scored maturity profile
Six dimensions with the evidence cited for each score.
Blocked-workload map
Which planned use cases are gated by which gap.
Sequenced roadmap
Ninety-day and twelve-month moves with owners and exit criteria.
Capability is personal, not institutional.
Some pipelines and reviews repeat reliably.
Platform, governance and delivery are standardised.
New workloads reuse the platform without new exceptions.
Value, cost and risk are measured and tuned continuously.
Banking & finance
Model risk management practice raises the Governance bar before any customer-facing workload.
Agree the business units, systems and decisions in scope for scoring.
Exit gate
The scope names decisions, not departments.
Evidence: Scoped assessment plan with the workloads in scope named
Artefacts
Score each dimension from artefacts and systems, not from self-assessment alone.
Exit gate
Every score cites the artefact behind it.
Evidence: Evidence pack per dimension, not self-declared scores
Artefacts
Compare current level to the level the target workloads require.
Exit gate
Each gap is tied to a workload that is blocked by it.
Evidence: Scored radar with the gap statements behind each level
Artefacts
Order the moves so each one unlocks the next rather than running in parallel silos.
Exit gate
The first ninety days are fundable and owned.
Evidence: Sequenced remediation plan with owners and dates
Artefacts
Repeat the scoring each two quarters so progress is measured, not asserted.
Exit gate
Movement between levels is evidenced by new artefacts.
Evidence: Re-scored profile showing movement against the first baseline
Artefacts
Scores based on opinion inflate every dimension except the one that blocks you.
A twelve-month plan with no exit criteria becomes a status report.
Platform maturity without governance and process maturity produces expensive pilots.
MLOps and LLMOps maturity practice
Published maturity levels for automation of the model lifecycle.
DAMA-DMBOK and EDM Council DCAM
Data management knowledge areas and capability assessment.
ISO/IEC 42001: AI management systems
International Organization for Standardization, management system requirements for AI.
NIST AI Risk Management Framework 1.0 and Generative AI Profile
National Institute of Standards and Technology, Govern, Map, Measure, Manage.
Citations describe the parts of each standard the framework answers. Bilytica is not an accreditation or certification body.
In Saudi Arabia
The AI operating system frameworks carry a workload from a readiness score to a governed release. These are the Saudi checks each stage is built against.
SDAIA, PDPL
Purpose, lawful basis and disclosure recorded before the first personal-data field is used.
Diagnosis and assurance stages block a build that has no recorded basis.
Processing register entry attached to the release record.
NCA ECC
Authorisation and containment for anything the system can do on its own.
Agent operations defines action classes, dual control and a tested rollback path.
Containment test result and an authority matrix signed by the business owner.
NDMO data management controls
No workload builds on an uncertified data domain.
The data foundation gate certifies ownership, lineage and quality thresholds first.
Signed domain certificate referenced by the release.
Where it runs
Training, evaluation and serving run inside Saudi Arabia on your infrastructure, with any hosted component documented as a boundary.
Arabic, as it is spoken here
Arabic quality is a release condition: evaluation sets include Saudi Arabic content, not translated English.
The scorecard gives an indicative read in minutes. AIRM scores the same dimensions against evidence and produces a funded plan.
Data, platform, security, risk and the business owner of the first workload. Scoring without risk present is the usual failure.
You can start delivery in parallel, but the sequencing decision still needs the scored view to avoid building on an uncertified domain.
Timeline agreed with you, covering interviews, evidence review and a roadmap workshop that ends with a sequenced plan rather than a score alone.
No. Every dimension is scored against evidence you can produce, contracts, tests, controls, releases, which is why the Evidence stage sits before the Gap stage.
It turns readiness into a tracked measure: the same dimensions are re-run after the roadmap's first gates so progress is proven, not asserted.
Google's MLOps maturity levels, DCAM/DAMA for data capability, NIST AI RMF for risk functions, and ISO/IEC 42001 for management-system expectations.
Curated links across our Saudi hubs, sector pages and long-form blog research.