Is the NATIVE framework free to use?

Yes. It is published in full, ungated, and you may use it internally without engaging us. A framework you cannot inspect before buying is a sales asset rather than a method.

How is NATIVE different from a maturity model?

A maturity model ranks you against an industry curve. NATIVE asks what your organisation can absorb in the next two quarters and who owns the gap that stops it.

How does NATIVE relate to Proof, Product, Platform?

NATIVE is the advisory loop: how you decide. Proof, Product, Platform is the commercial ladder: what you buy. The stages map onto the ladder, but they answer different questions.

The advisory spine

The NATIVE framework

Six stages for treating AI as an operating-model shift rather than a tool decision. Published in full, free to use, and unchanged whether or not you ever hire us.

Take the free NATIVE Audit The first 90 days

Stages: Notice, Assess, Target, Integrate, Validate, Expand
Gate: Each stage ends in a decision, including the decision to stop

NNotice
What the market is already telling you
What is changing around us that we cannot afford to ignore?
Read the stage
AAssess
Are you ready, really?
What can this organisation actually absorb now?
Read the stage
TTarget
Choosing the battlefield
Where does AI connect to a business outcome worth owning?
Read the stage
IIntegrate
Rewriting workflows and decision rights
How does the work itself need to change?
Read the stage
VValidate
Prove it before you scale it
Did it produce value, quality, adoption, and acceptable risk under real conditions?
Read the stage
EExpand
When the pilot becomes reality
How do we make the gain durable without breaking the system around it?
Read the stage

The commercial ladder

Proof, Product, Platform

NATIVE decides. The ladder delivers. Each rung answers one question and ends in a decision you can defend.

Proof

2 to 3 weeks

A working prototype that makes a decision possible

Question: Is this workflow worth changing at all?
Buyer: Product, innovation, or a function head
What ships: A clickable, working prototype on your own workflow language and sample data. A before-and-after workflow map. A named decision.
Gate to the next rung: A value map exists: metric, named owner, expected benefit, validation method. If it does not, the engagement stops here and that is a legitimate outcome.

We refuseA prototype with no named decision attached to it.

Product

6 to 12 weeks

One real application carrying real work in production

Question: Does the changed workflow actually hold up?
Buyer: Head of Transformation, Operations, or CIO
What ships: A production application with authentication, data boundaries, audit trail, an eval harness where a model is in the loop, documentation, and a named operational owner.
Gate to the next rung: The pilot charter's pass line was met on a fully loaded cost basis, in the real workflow, on the hardest cases and not only the clean ones. Adoption, quality, and risk all cleared.

We refuseProduction deployment without an escalation path and a kill switch.

Platform

2 to 4 quarters, in sequenced waves

A governed capability that lets many teams build safely

Question: Can the organisation do this repeatedly without breaking?
Buyer: CEO, CIO, CTO, or Head of AI
What ships: A platform standard: governance model, decision-rights matrix, publishing and access controls, enablement curriculum, an internal build request intake, adoption instrumentation, and a quarterly review cadence.
Gate to the next rung: The first wave is running in routine operations with monitoring, an owner, and a documented crossover point.

We refuseA rollout with no named owner per department.

The ninety-day scorecard

Evidence, phase by phase

What you should be able to show, and the weak answer that usually appears instead.

The week-by-week plan

Day 30, audit

An inventory of every active pilot and shadow tool, two structural signals in one sentence each, and a four-pillar score with a named owner on the lowest pillar.

"We are exploring several initiatives across the business and building excitement."

Day 60, design

A shortlist of one or two use cases that survived three gates, a completed value map with a written baseline, and Approve, Override, and Escalate named for the specific workflow.

"We have identified a number of high-impact opportunities and are socialising them with stakeholders."

Day 90, execution

A signed pilot charter, results against a pre-written pass line, a fully loaded cost comparison, and a decision: expand, stop, or narrow.

"Early feedback has been very positive and the team is keen to keep going."

Glossary

The terms, defined once

If a term in our proposals is not defined here, tell us and we will define it.

The four readiness pillars: Leadership Commitment, Data Usability, Workflow Clarity, Governance, each scored 1 to 5 in one room, not by survey.; Maps to Assess
The three gates: Strategic consequence, measurability, feasibility. A shortlist that still has eight items has been transcribed, not triaged.; Maps to Target
The value map: Names four things before integration begins: the metric that will change, the single named executive who owns it, the primary expected benefit, and the exact validation method.; Maps to Target
The pilot charter: Five sentences: business problem, metric, baseline, quality bar, stop conditions.; Maps to Validate
The kill switch: The pre-agreed condition under which a pilot stops, written before the pilot starts.; Maps to Validate
Fully loaded cost: Includes review time at the reviewer's rate, not just licence and compute.; Maps to Validate
Crossover point: The volume threshold where variable compute and licensing cost becomes cheaper than the fully loaded human cost it reshapes.; Maps to Expand
Shadow AI: The operational consequence of moving too slowly: employees bypassing sanctioned workflows to get work done, creating invisible regulatory risk.; Maps to Notice, Assess
Native versus standalone integration: Native embeds AI inside a system of record, inheriting its permissions and its vendor roadmap. Standalone connects an independent tool via an integration layer, giving control but requiring you to maintain the plumbing.; Maps to Integrate
Fine-tuning data portability: If you cannot export your calibration data when switching providers, your exit cost is the total loss of organisational learning built during the pilot.; Maps to Expand
The RAO framework: Role, Action, Operational Context. The baseline prompt literacy standard for a workforce.; Maps to Expand, workshops
The ninety-day scorecard: What you should be able to show at each phase, and what a weak answer sounds like.; Maps to All stages

The book

The AI-Native Leader

NATIVE is drawn from the book by our founder, John V. Jayakumar. The framework here is the working version we use in engagements.

About the book About the author

How to use this without us

Run the Notice inventory yourself in week one. Disclosure must carry no disciplinary consequence.
Score the four pillars in one room, not by survey, and record the dissent.
Cut the use-case list through three gates until one or two remain.
Write the pilot charter before the pilot, and name who may pull the kill switch.

FAQ

Questions about the framework

Is the NATIVE framework free to use?: Yes. It is published in full, ungated, and you may use it internally without engaging us. A framework you cannot inspect before buying is a sales asset rather than a method.
How is NATIVE different from a maturity model?: A maturity model ranks you against an industry curve. NATIVE asks what your organisation can absorb in the next two quarters and who owns the gap that stops it.
How does NATIVE relate to Proof, Product, Platform?: NATIVE is the advisory loop: how you decide. Proof, Product, Platform is the commercial ladder: what you buy. The stages map onto the ladder, but they answer different questions.

Next step

Start with a baseline, not a proposal

Take the NATIVE Audit in fifteen minutes, or book a scoping call and bring the pilots you already have running.

Take the NATIVE Audit Book a scoping call