Skip to content

How we work

We don’t sell hours.We take responsibilityfor outcomes.

Large results are rarely the product of one big decision. They come from many small pieces of work, done carefully and in the right order. Micro work, macro results — that is the whole method.

01Phase

2–4 weeks

Discover

We learn how your organisation really works — the systems, the people and the numbers — before we recommend anything.

Interviews, process walks and data. We follow real work end to end and measure where time and money go, then agree with you what success looks like in numbers.

Deliverables

  • Current-state assessment
  • Measured baseline
  • Prioritised problem list
  • Success criteria

02Phase

2–6 weeks

Design

We shape the solution with the people who will use and run it, and test the riskiest ideas early and cheaply.

Architecture, service design and prototypes, tested with users and challenged by the engineers who will build them. You see costs and trade-offs before you commit.

Deliverables

  • Target architecture
  • Validated prototypes
  • Delivery plan and budget
  • Risk register

03Phase

3–12 months

Deliver

Small, senior teams ship working software and infrastructure every two weeks, in production as early as possible.

Short iterations, each ending in a demonstration of working software. We release early to a small group, measure against the baseline and adjust.

Deliverables

  • Working releases every two weeks
  • Automated tests and pipelines
  • Runbooks and documentation
  • Progress against baseline

04Phase

Ongoing

Sustain

We stay to run what we built, or hand it over to your team with the skills and documentation to own it.

Managed service with clear commitments, or a planned handover with pairing, training and a support period. Either way, the system keeps improving.

Deliverables

  • Service-level objectives
  • Monthly service reviews
  • Handover and training plan
  • Improvement roadmap

05Engagement models

Four ways to work together.

Comparison of engagement models
AdvisoryProject deliveryEmbedded teamsManaged services
Best forDecisions, plans and second opinionsA defined outcome with a clear endAdding senior capacity to your teamsRunning critical systems day to day
Typical length2–8 weeks3–12 months6–24 months12 months+
Team1–3 senior consultantsCross-functional team of 4–8Individual specialists in your squadsDedicated service team
CommercialsFixed feeFixed fee per phase or monthlyMonthly per personMonthly fee with SLAs
You ownThe decisionThe product and codeThe roadmapThe outcome; we own the operation
Our commitmentA clear recommendationAgreed outcomes, on scheduleSkills transferred to your teamContracted uptime and response

06Principles

What we hold to.

  1. 01

    The people who advise you are the people who deliver.

  2. 02

    We measure before we recommend, and after we deliver.

  3. 03

    Small, senior teams beat large, junior ones.

  4. 04

    Working software is the only real progress report.

  5. 05

    Your team should need us less every year.

  6. 06

    We tell you what you need to hear, early.

Start a conversation

Let’s talk aboutwhat you’re building.