Operating model
How we work
Six operating modes, one engineering lifecycle, and an explicit gate at every stage. Engagements enter at the point that matches their situation and progress only when the gate is satisfied.
| Operating mode | ID | VA | BP | AR | EN | AI | PR | SC |
|---|---|---|---|---|---|---|---|---|
| Venture Definition | Idea (Thesis): in scope | Validation (Validation): in scope | Blueprint (Blueprint): in scope | Architecture (Architecture): not in scope | Engineering (Build): not in scope | AI (Intelligence): not in scope | Production (Production): not in scope | Scale (Scale): not in scope |
| Venture Build | Idea (Thesis): not in scope | Validation (Validation): not in scope | Blueprint (Blueprint): in scope | Architecture (Architecture): in scope | Engineering (Build): in scope | AI (Intelligence): in scope | Production (Production): in scope | Scale (Scale): not in scope |
| Product Build | Idea (Thesis): not in scope | Validation (Validation): not in scope | Blueprint (Blueprint): in scope | Architecture (Architecture): in scope | Engineering (Build): in scope | AI (Intelligence): not in scope | Production (Production): in scope | Scale (Scale): not in scope |
| AI Transformation | Idea (Thesis): not in scope | Validation (Validation): not in scope | Blueprint (Blueprint): not in scope | Architecture (Architecture): in scope | Engineering (Build): not in scope | AI (Intelligence): in scope | Production (Production): in scope | Scale (Scale): not in scope |
| Architecture Recovery | Idea (Thesis): not in scope | Validation (Validation): in scope | Blueprint (Blueprint): not in scope | Architecture (Architecture): in scope | Engineering (Build): in scope | AI (Intelligence): not in scope | Production (Production): in scope | Scale (Scale): not in scope |
| Engineering Scale and Readiness | Idea (Thesis): not in scope | Validation (Validation): not in scope | Blueprint (Blueprint): not in scope | Architecture (Architecture): not in scope | Engineering (Build): not in scope | AI (Intelligence): not in scope | Production (Production): in scope | Scale (Scale): in scope |
Entry
Operating modes
A mode describes the shape of an engagement, not its price or duration. The correct mode follows from the situation the system is in.
Venture Definition
Convert an idea or opportunity into a defined, buildable and investable venture. An idea or opportunity exists, but there is no defined venture, no blueprint and no basis on which to build.
Venture Build
Engineer a defined venture from blueprint through to production. The venture is defined and approved, and the system now has to be engineered through to production.
Product Build
Engineer a defined product or platform for an existing organisation. An existing organisation needs a product or platform engineered against a specification it can own.
AI Transformation
Move AI from pilot to governed, evaluated production capability. AI exists as pilots or experiments and must become governed, evaluated production capability.
Architecture Recovery
Assess and reconstruct constrained, fragmented or unreliable systems. A system is fragmented, unreliable or constrained, and the architecture has to be assessed before anything else.
Engineering Scale and Readiness
Extend delivery capacity, reliability, security and production readiness. Delivery capacity, reliability, security or production readiness is the constraint on growth.
Sequence
The engineering lifecycle
Every mode runs through the same lifecycle. An engagement may start at a later stage, but it never skips one silently: the earlier stages are either satisfied or explicitly established.
Thesis
Establish what the venture or system is intended to be and why it should exist.
Validation
Test the problem, opportunity and feasibility before committing to design.
Blueprint
Define the product, scope, logic and delivery model in executable form.
Architecture
Define system, data, AI, security and infrastructure architecture before implementation.
Build
Engineer the system against the approved blueprint and architecture.
Intelligence
Engineer the AI systems, retrieval, evaluation, guardrails and observability.
Production
Establish release governance, reliability, security and operational readiness.
Scale
Extend capacity, performance, governance and organisational delivery capability.
Control
What a gate actually is
A gate is a review with the authority to stop work. It exists so that progression is a decision rather than momentum.
- Stated conditions
Each stage has conditions for progression that are written down before the stage begins.
- Reviewable evidence
Progression is argued from artefacts — specifications, architecture, tests, evaluations — not from assertion.
- A real stop option
Stopping or returning to a previous stage is a legitimate outcome. A gate that cannot fail is not a gate.
- Recorded decision
The decision, its basis and its date are recorded so the engagement remains auditable later.
Boundaries of the operating model
Stated so expectations are set before an engagement is discussed.
- No fixed durations are published for any mode or stage
- No prices, rate cards or commercial terms are published
- No outcome, funding or market result is guaranteed
- Scope is agreed per engagement and reviewed at each gate
- Work does not begin ahead of an approved definition of that work
- Regulatory interpretation and approval remain with the client
Identify the right entry point
The first conversation establishes which mode applies and which lifecycle stage the system is genuinely at.