BLUEHARBOURD0
Book an intro call

Depth D0 · Approach

How the work actually runs

Every engagement with Blueharbour follows the same sequence: written scoping, building in small reviewed changes, a handover your team signs off, and a clear decision about what happens afterwards. The engagement model changes how long that sequence runs, not its order.

The sequence

  1. 01

    Scoping

    We read what you send, ask the questions that matter and write the scope down. It states the input we need, the method, the deliverable and how the result will be measured. Nothing starts on a verbal agreement.

  2. 02

    Building

    Work happens in small changes inside your repositories and accounts, each one reviewed. You see progress as it lands, and a short written note each week says what changed and what is blocked.

  3. 03

    Handover

    We hand over the working system with its documentation: how it runs, how to change it, what it cannot do and who to call. Your team walks through it with us before we call it done.

  4. 04

    After

    Some clients take it from there. Others keep us on a retainer for maintenance or further stages. Either way, the access we held is listed and removed unless you ask us to keep it.

Who does what at each step

Two tracks run side by side. Your track is short, but the work stops when it is empty: we do not build without access or ship without your review.

  1. 01 · Scoping

    You: Describe the problem, grant read access, answer our questions, accept the written scope.

    Us: Read the stack, write the scope: input, method, deliverable, measure, and what is left out.

  2. 02 · Building

    You: Review changes as they land and clear blockers named in the weekly note.

    Us: Ship small reviewed changes in your repositories and write the weekly note.

  3. 03 · Handover

    You: Walk through the system with us and sign it off.

    Us: Hand over documentation, access and a recorded walkthrough.

  4. 04 · After

    You: Run it yourselves or agree a retainer, then remove our access.

    Us: List every access we held and give it up unless you ask otherwise.

Engagement models

Prices are not published. Each model is priced in writing against a scope, and the minimum commitment is set in the contract.

Scoped project
A fixed piece of work with a written scope and an end. It suits a clear problem: an audit, a migration, a rebuild of one process.
Retainer
An agreed amount of time each month for ongoing work such as operations, maintenance or a steady stream of changes. It suits systems that need looking after rather than building.
Embedded
Our engineers work inside your team, in your tracker and your repositories, under your priorities. It suits a team that needs capacity or a skill it does not have yet.

Questions about working together

Pricing, ownership, access, data, AI and what follows handover are answered once, on the questions page.

Start with the scope

Describe the problem in a few lines. We reply with the questions we would need answered to write a scope.

Describe the problem

A written reply first, no call needed.