How We Work · The 10X Operating Model

From operating problem to working system.

The 10X Operating Model turns unclear transformation projects into controlled stages. Each stage has a defined output, a decision gate and evidence your team can inspect before anything proceeds.

Explore the Systems Review See how we handle client data

Principles

Stages, not a blank cheque.

Every engagement — regardless of size — runs on the same operating principles.

Work proceeds in controlled stages — not as one open-ended engagement.

Every stage ends with evidence your team can inspect, not a status update.

You retain ownership of everything completed at each stage, whether or not you continue.

Future stages are never assumed. Continuing is a decision you make each time, not a default.

Human decision authority stays with your team at every commercial and operational decision.

Systems are documented so they remain maintainable without permanent dependence on 10X.

The five stages

Review, Blueprint, Pilot, Build, Operate and Improve.

Each stage is scoped and, where chargeable, priced on its own — the Systems Review is stage one and can be taken standalone.

Stage 01

Review

Purpose: Understand how the operation actually runs today — workflows, tools, data and decision points — and where it depends on specific people.
Client input required: Process walkthroughs with the people who run the work, plus a look at your existing tools and reporting. Access is limited to what is needed to observe the workflow.
10X deliverables: A current systems and workflow map, prioritised automation and AI opportunities, and a key-person and decision-control risk review.
Decision gate: You decide whether the findings justify a Blueprint, and which opportunity to pursue first.
Proof required before proceeding: The systems map and risk review are walked through with your team before any Blueprint work starts.
What the client owns: The systems map, the opportunity list and the risk review — yours to keep whether or not you proceed.
Access and confidentiality: Confidential by default; an NDA can be signed before scoping conversations. Access is for observation, not system changes.
Can you stop here?: Yes. The Review is a standalone, paid deliverable. Stopping here costs nothing beyond the Review itself.

Stage 02

Blueprint

Purpose: Design the target system for the chosen opportunity — data flow, workflow, approval points and ownership — before anything is built.
Client input required: Confirmation of the recommended pilot, sign-off from the people who will use the system, and decisions on approval points and access rules.
10X deliverables: A system design covering data flow, workflow, roles and permissions, and defined human approval points, plus a fixed-price proposal for the Pilot.
Decision gate: You approve the design and the fixed price before Pilot work begins.
Proof required before proceeding: The design is walked through with the people who will operate the system day to day, not just signed off by proxy.
What the client owns: The design and the proposal — usable by your team or another vendor even if you do not proceed with 10X.
Access and confidentiality: No production access is required at this stage. Discussions continue under whatever confidentiality terms were already agreed.
Can you stop here?: Yes. Blueprint is scoped and priced separately from Pilot and Build.

Stage 03

Pilot

Purpose: Prove the highest-leverage system first, scoped small enough to demonstrate value quickly — and to fail cheaply if it does not work.
Client input required: Access to the specific systems or data the pilot touches, a named owner on your side, and time from the people who approve pilot decisions.
10X deliverables: A working pilot version of the system, running against real or representative data, with the approval points from the Blueprint in place.
Decision gate: You decide, based on measured pilot performance against the criteria agreed in the Blueprint, whether to proceed to full Build.
Proof required before proceeding: Pilot results are measured against those agreed criteria — not asserted after the fact.
What the client owns: The pilot system and its results.
Access and confidentiality: Access is scoped to the pilot’s systems only, logged where the platform allows, and revocable by you at any time.
Can you stop here?: Yes. A pilot that does not clear the bar is a contained result, not a sunk-cost trap into a full Build.

Stage 04

Build

Purpose: Ship the full working system your team can own, based on what the Pilot proved.
Client input required: Ongoing availability of the process owners for review checkpoints, and timely decisions at each approval gate.
10X deliverables: The completed system deployed to your environment, documentation your team can maintain without 10X, and a handover session.
Decision gate: You sign off on each checkpoint before the next phase proceeds, and on final handover.
Proof required before proceeding: Working software demonstrated against the agreed scope at each checkpoint — not a progress update.
What the client owns: The system, the source code, and the accounts and data connected to it.
Access and confidentiality: Credentials are handled through managed systems, never documents or chat. Access stays scoped to the build team and is revoked at handover if the engagement ends.
Can you stop here?: Yes, at any checkpoint. You own what has been built up to that point.

Stage 05

Operate and Improve

Purpose: Run, measure and improve the system in production, with authority for commercial decisions staying with your team.
Client input required: A named owner on your side for ongoing approvals, and feedback on what the system should measure or change next.
10X deliverables: Depending on the engagement model: ongoing operation under Build + Operate, or documentation and a support window so your team runs it independently under Build — either way, with regular proof-of-work reporting.
Decision gate: You decide, on a rolling basis, whether to continue the engagement, change its scope, or bring operation fully in-house.
Proof required before proceeding: Reporting shows what changed and what did not — not activity for its own sake.
What the client owns: The system, throughout. Ongoing operation does not change who owns the underlying code, accounts or data.
Access and confidentiality: The same standing commitments apply for as long as the engagement continues, and access is revoked when it ends.
Can you stop here?: Yes. Operate and Improve is not an auto-renewing default — continuing is a decision your team makes each cycle.

Start with Stage 01.

The Systems Review maps your operation, ranks the opportunities, and gives your team a plan — with or without 10X for what comes next.

Explore the Systems Review See how we handle client data