Engagements

How a project runs.

Every engagement has the same three phases. What changes is the shape of the work inside them.

Three phases

  1. PHASE 1

    Assess

    We read the code, the infrastructure and the tickets, and talk to the people who use and run the system. You get a written assessment and a proposed scope before any work starts.

  2. PHASE 2

    Deliver

    Work ships in small releases you can see running. Each one has tests, a deploy path and a short note on what changed and why.

  3. PHASE 3

    Step back

    We pair with your team, write the runbooks and architecture notes, and step back once they can run it without us.

Three ways to work with us

Fixed scope

A defined piece of software with an agreed scope and end point.

Suits New services, integrations, and rebuilding one part of a larger system.

Stabilise

A stalled project or a fragile system. We make it stable first, then agree what comes next.

Suits Failing releases, stuck upgrades, and code nobody wants to touch.

Embedded

We work inside your team, in your tools and your routines, for an agreed period.

Suits Teams that need more hands before they are ready to hire.

No prices here. Every engagement starts with a conversation and a written scope, and the price follows the scope.

Start with an assessment.

Describe your system