Get briefed
How it works

Earned, one stage at a time

An engagement starts with a brief and a supervised pilot. What happens after that is a sequence you control, with the log as the record of what was earned.

How an engagement runs

From a brief to a colleague

  1. 01

    Mission Brief

    A paid first engagement. We map the process with the people who run it, agree the scope a crew member would hold, and say plainly what we would not put inside it.

  2. 02

    Supervised pilot

    Onboarding runs in three phases, starting read-only: access and mapping, then drafts checked by a named reviewer, then scoped work with a rollback you have already rehearsed.

  3. 03

    The value decision, day 30

    At day 30 you decide whether the pilot has earned an ongoing crew member. The log is the evidence — what it did, who approved it, what it never touched.

  4. 04

    An ongoing crew member

    Responsibility moves in either direction from there, one stage at a time, and you decide when it moves. First value is a matter of days; the rest of the arc is not on a schedule.

Two crew members examining a rock on a lunar surface, their lander behind them
Five crew members around a chart table, planning a route between orbits
The stages

From reading to running

Responsibility isn’t granted on day one. It’s earned, step by step.

  1. 01

    Discover

    Responsibility
    Minimal

    Finding the fit

    First, we figure out whether there’s a responsibility worth handing off at all. If there isn’t, we’ll tell you.

  2. 02

    Understand

    Responsibility
    Minimal

    Mapping the business

    Before any system gets connected, we sit down and map how the work really runs. Together we look at:

    How the team works Which systems are used Where time is being lost Which workflows are repeated What expertise is missing Which responsibilities could be delegated
  3. 03

    Onboard

    Responsibility
    Read-only

    Learning the ropes

    The crew member gets access to the systems, documents and knowledge it needs, and starts figuring out how things work around here.

    Like any new colleague, it learns before it contributes.

  4. 04

    First value

    Responsibility
    Supervised

    Doing real work

    It starts with everyday tasks, and a named reviewer checks everything it produces.

    What it does
    Preparing customer meetings Summarising conversations Creating reports and decision briefs Answering internal questions Automating repetitive work Coordinating workflows across systems
    What that produces
    Less time on manual work
    Meetings that start prepared
    Decisions with a brief behind them
    A log of every action
  5. 05

    Grow

    Responsibility
    Scoped

    Taking on more

    As its track record builds, you can widen its scope — more systems, more decisions, less checking. That’s always your call, and you can always dial it back.

    What starts as support turns into ownership.

  6. 06

    Belong

    Responsibility
    Infrastructure

    Becoming part of the company

    By now it’s woven into how work moves between your teams. It still has a scope, a person it answers to and a log — that part never changes, however much it takes on.

    It started with one process. Now the business runs on it.