Request the auditRequest audit

How it works

Map first. Build only what earns its place.

We read the picture in the free audit, design the change in the paid Blueprint, and build only what you have seen and agreed. You know what is coming before it arrives.

Request the auditView the sample operating blueprint

Four words we use

Plain meanings, so the rest of this page reads easily.

Record
One place that holds the current state of a piece of work: who has it, what has happened, what comes next.
Handoff
The moment work passes from one person or system to another. Most drag lives here.
Operating layer
The records, queues, permissions and handoffs that connect the systems you keep. Not a new product; the connective tissue between the ones you have.
Blueprint
The paid document that maps how work runs today and designs what will change, so you can see the decision before you pay for the build.

The six commercial layers

Where the money starts, and what it does not commit you to.

The audit is free. The Blueprint is the first paid layer. Nothing is built, scheduled or invoiced before its layer is agreed in writing.

These six layers make up the offer. The free Operating Infrastructure Audit carries no purchase obligation. Each paid layer is accepted on its own terms. See how each layer is priced

The six delivery phases under the layer each runs inAfter the free Free Operating Infrastructure Audit, Map and Design run inside the Paid Operating Infrastructure Blueprint; Deploy, Migrate and connect, Operationalise, Handover run inside the Premium Core Infrastructure Deployment. A written sign-off closes each layer and each phase. After handover, Managed Infrastructure and Managed Operations are agreed separately.THE PATHFREEPAID, ONE LAYER AT A TIMEFree Operating Infrastructure AuditFreeA written read of what to fix firstPaid Operating Infrastructure BlueprintA fixed fee, confirmed after scopingThe architecture and the scope of what wouldbe builtPHASES 1 AND 2Map · DesignPremium Core Infrastructure DeploymentA project fee, priced from the BlueprintA configured, documented environment, handed overPHASES 3 TO 6, EACH SIGNED OFFDeploy · Migrate and connect · Operationalise · Handoveryou sign offyou sign offAFTER HANDOVER, EACH AGREED SEPARATELYManaged InfrastructureA monthly fee, confirmedafter scopingManaged OperationsA monthly retainer,scoped separatelyDedicated / White-Label InfrastructureIts own scope, when justifiedAn alternative architecture, not a stepNothing is built, scheduled or invoiced before its layer is agreed in writing. Stop at the end of any phase and keep everything accepted so far.Price is set by what has to be built and kept running, not by how many people log in.

Delivery phases

Six delivery phases, once the Blueprint is commissioned.

Map and Design run inside the Blueprint; the other four inside Deployment, as the drawing above shows. At the end of each phase you hold something you can use, and you decide whether the next one starts.

  1. Map

    We record how the agreed workflows run today: systems, owners, handoffs and where work stalls.

    You receive:
    A current-state map of the agreed workflows, their systems, owners and handoffs.
    You provide:
    Time with the people who run the work, and an honest account of how it moves.
    Before the next phase:
    You have read the free audit and commissioned the paid Blueprint.

  2. Design

    We decide what stays, connects or is replaced, who can do what, and what will be built.

    You receive:
    The Operating Infrastructure Blueprint: architecture, access, scope, responsibilities, exclusions and what done looks like.
    You provide:
    Decisions on which systems stay or go, and a named owner for each workflow.
    Before the next phase:
    You have signed off the current-state map and the design decisions.

  3. Deploy

    We configure the agreed workspaces, applications, permissions and operating structures.

    You receive:
    A configured environment for the agreed scope, recorded as built.
    You provide:
    Admin approval for the workspaces, plus the accounts and licences they depend on.
    Before the next phase:
    You have accepted the Blueprint, the deployment scope and the commercial proposal.

  4. Migrate and connect

    We move the agreed data, connect the systems and build the integrations in scope.

    You receive:
    A record of what was moved, what was connected and which checks were run.
    You provide:
    Confirmation of the data in scope, and sign-off on the checks for each move.
    Before the next phase:
    You have signed off the configured environment and the migration plan.

  5. Operationalise

    We switch on the live workflows: queues, approvals, dashboards, alerts and escalation paths.

    You receive:
    Live workflows, queues, approvals, dashboards and escalation paths, documented as configured.
    You provide:
    The operating rules, approval limits and escalation contacts your team wants applied.
    Before the next phase:
    You have signed off the migration and connection checks.

  6. Handover

    We hand over access records, architecture maps, procedures and training. Any managed layer is separately agreed.

    You receive:
    A handover pack: access records, maps, procedures, training notes and the acceptance evidence for each phase.
    You provide:
    The named owners who take handover, and a written decision on any recurring managed layer.
    Before the next phase:
    You have signed off the final acceptance record. Any recurring layer needs its own written agreement.

How the work is controlled

Three rules that apply to every phase.

Each phase waits for the last
Nothing later is built, scheduled or invoiced while the phase before it is open, so you always know what you are paying for.
Sign-off is written down
A phase closes when you have read its output and accepted it in writing. Silence never counts.
You can stop at the end of any phase
Everything accepted to that point stays with you, documented. No phase obliges you to commission the next.

What this is not

No build before an agreed scope. No blanket replacement.

Accepting the paid Blueprint does not authorise any later commercial layer. Deployment, Managed Infrastructure and Managed Operations are each agreed on their own, in writing.

The full shape of the design-phase output is published as a worked example, with every business, role and system invented. View the sample operating blueprint

Start

Start with the free Operating Infrastructure Audit.

A written read of where operating drag sits today and what to fix first. No purchase obligation, no automatic progression to the paid Blueprint, and no commitment to any paid layer after it.

Request the audit