Innovate · Demonstrate · Activate · Operate
IDAO.
A governed route from a consequential opportunity to evidence, adoption and a capability your team can own.
Follow the lifecycle
Humans and AI agents working as one team.
IDAO combines seasoned human judgement with a governed agent workforce. The advantage is not people or automation in isolation; it is knowing which capability should lead, where it should collaborate and where human authority must remain explicit.
Judgement in context.
Human authority · Agent leverage

Scale with control.
They bring the judgement earned through consequential programmes: reading organisational context, challenging the value case, navigating executive decisions and recognising risks that do not appear in a technical brief.
Start with pressure, not technology.
An engagement begins where an important workflow, decision or service is under pressure. Together we identify the value at stake, the people affected and the evidence a leader would need to act.
Not every engagement starts at Innovate. If credible evidence already exists, we enter at the earliest stage whose gate can be responsibly satisfied.
Every stage earns the next.
IDAO is not a gated waterfall. Evidence, risk and assurance travel with the work. If a gate exposes weak evidence, the team reshapes the scope or loops back rather than scaling an assumption.

01 / 1 dayDon’t boil the ocean. 01Innovate
Spot the value · 1 day
Find the consequential opportunity and define why it deserves to move.
We frame the highest-value opportunity, the people it serves and the decision the work must unlock. Controlled inputs and a deliberately narrow scope move effort toward proof, not an expanding brief.
Key work
- Map the work, pressure, affected people and constraints
- Frame the value, risk and adoption hypotheses
- Choose the smallest meaningful decision boundary
Your participation
Bring the priority, operating context and the people accountable for the decision.
What you have in hand
A prioritised opportunity and a clear decision boundary.
Decision gate
Is there a specific opportunity worth proving, with an accountable owner and a measurable outcome?
Evidence to progress
A shared problem frame, baseline signals, named decision-makers and an agreed plan for what the demonstration must prove.

02 / 48 hoursSee it before you buy it. 02Demonstrate
Prototype · 48 hours
Turn the opportunity into decision-ready evidence before committing to a larger build.
Within 48 hours, we turn the agreed decision boundary into a tangible prototype. Stakeholders test the important journey and evaluate value, usability and direction before committing to a larger build.
Key work
- Build the critical journey around representative workflows
- Test data, integration, usability and governance assumptions
- Record value signals, limitations and operational exposure
Your participation
Test the critical journey, challenge assumptions and make the proceed, reshape or stop decision.
What you have in hand
A working proof stakeholders can test, challenge and decide on.
Decision gate
Has the prototype produced enough evidence to proceed—and made the remaining uncertainty visible?
Evidence to progress
Observed user response, evaluation findings, feasible integration paths, known limitations and a recorded proceed, reshape or stop decision.

03 / 2–4 weeks (MVP)Human judgement. Agent scale. 03Activate
Build the solution · 2–4 weeks (MVP)
Turn validated direction into a governed capability that is ready for real use.
In 2–4 weeks, forward-deployed engineers turn the validated direction into a governed MVP. Requirements stay traceable as the team builds, evaluates and secures the capability for real use.
Key work
- Build the MVP against traceable requirements
- Evaluate behaviour, security, accessibility and data handling
- Prepare people, controls, release and support paths
Your participation
Provide timely product decisions, access to subject experts and approval at agreed stage gates.
What you have in hand
A usable MVP with the engineering and controls needed to operate.
Decision gate
Are the people, capability and controls ready to carry the change safely into live work?
Evidence to progress
Evaluation results, control evidence, operational readiness, accepted limitations and accountable approval for release.

04 / 4–12 weeksNo lock-in. Full ownership. 04Operate
Scale & operationalise · 4–12 weeks
Sustain the outcome, learn from live use and transfer a capability the client can own.
We harden the capability, establish observability and data governance, and transfer the operating knowledge. Security, accessibility and handover discipline prepare your team to own and scale it.
Key work
- Monitor performance, value, risk and intervention signals
- Rehearse ownership, support and governance routines
- Transfer knowledge and shape the next improvement cycle
Your participation
Nominate operational owners, rehearse support and governance, and accept the capability against agreed evidence.
What you have in hand
A client-owned capability, operating model and scale plan.
Decision gate
Is the capability delivering the intended outcome, and can the client team operate, govern and improve it?
Evidence to progress
Live operating signals, accepted ownership, tested support routines, governance records and a prioritised improvement backlog.
The loop remains open. Live evidence from Operate can trigger a focused improvement, return a weak assumption to Demonstrate, or reveal a new opportunity for Innovate. Progress is controlled, not artificially linear.
Speed without shortcuts.
A decision-ready prototype within 48 hours and a governed MVP within 2–4 weeks are possible because teams do not begin from a blank page. A reusable delivery system governs how work is framed, produced, evaluated and handed over.
Governed lifecycle
The pace comes from knowing what must be true at every stage.
Each engagement moves through controlled inputs and outputs, shared structures and explicit stage gates. That repeatable route reduces reinvention while keeping scope, evidence and decisions visible.
- InnovateThe opportunity frame names the owner, outcome and proof boundary before work begins.
- DemonstratePrototype findings are recorded against the questions the demonstration was designed to answer.
- ActivateRelease readiness is earned through accepted evaluation and control evidence.
- OperateLive signals reopen the route when an assumption needs to be reshaped.
Reusable intelligence
Governed models, skills and accelerators create a repeatable starting point.
Teams begin with reusable intelligence rather than a blank page. It speeds analysis and production without replacing the judgement needed to fit the work to the client’s context.
- InnovateReusable framing structures help the team compare opportunities without flattening local context.
- DemonstrateGoverned skills accelerate research, prototyping and evaluation inside the agreed boundary.
- ActivateProven delivery patterns give engineers a controlled starting point for the MVP.
- OperateReusable operating routines support monitoring, intervention and continuous improvement.
Traceable execution
The brief, journeys, requirements and evaluation evidence stay connected.
Requirement traceability links what is built to the need it serves. Controlled outputs and recorded decisions make progress easier to review, challenge and change without losing the thread.
- InnovateThe value hypothesis is linked to the workflow, people and baseline signals it concerns.
- DemonstratePrototype observations remain connected to the assumptions they support or challenge.
- ActivateRequirements link through implementation to evaluation results and accepted limitations.
- OperateA live issue can be followed back to its requirement, decision and original value case.
Human decision gates
People remain accountable for direction, risk and release.
Named decision-makers approve the moments that matter. The system accelerates the work between gates; it does not make consequential client decisions or silently widen its own authority.
- InnovateAn accountable leader chooses the opportunity and agrees what evidence would justify progress.
- DemonstrateStakeholders make the proceed, reshape or stop decision after testing the proof.
- ActivateNamed owners approve scope changes, accepted limitations and release readiness.
- OperateClient operators retain authority over intervention, governance and the improvement backlog.
Assurance by design
Evaluation and operational readiness are built into delivery, not added at the end.
Security, accessibility, data governance and observability are considered from the first proof. Evidence, known limitations and handover discipline travel with the capability as it moves toward operation.
- InnovateRisk, data sensitivity and affected people shape the proof boundary from the outset.
- DemonstrateThe prototype tests usability, feasibility and governance assumptions—not only the happy path.
- ActivateSecurity, accessibility, behaviour and data handling are evaluated before release.
- OperateObservable performance, tested support routines and known limitations accompany handover.
The work ends in your hands, not ours.
Handover is prepared from the start. Named owners receive the operating knowledge, traceability, evaluation evidence, known limitations and governance routines needed to run the capability with confidence.
We rehearse support and intervention before acceptance. The outcome is not dependency on a delivery team; it is a client-owned capability with clear authority, observable performance and a route to responsible improvement.
Design roles, rights and adoptionBring one process. Leave with the next evidence to earn.
A Value Scan identifies where the work is under pressure, what value is available and which IDAO stage should begin the route.
Book a Value Scan