Skip to content
Discuss Your Project
How we work

Three Stages, And A Date We Leave

Every stage has a written output you keep, whether or not you continue to the next one.

01

Data Platform Assessment

Two to three weeks. We inventory your sources, sit with the people who own them, and find where they disagree. You get a written architecture scope, a risk list, and the parts we would decline to take on.

The document is yours. It is specific enough to hand to another firm, which is the point.

What it costs you

Roughly six hours from the people who own your source systems. If that time is not protected, tell us before we start.

02

Build

Your engineers work alongside ours from the first sprint, in your repositories, with your review process. Governance and access control go in at the start rather than after the first audit question.

Business rules get written down and signed off before anything automates them.

What it costs you

A named owner on your team with real hours protected. Without one, the handoff at stage three does not hold.

03

Handoff

Schema documentation, runbook, monitoring and alerting your team can read, and a working session where your owner runs the platform while we watch. The engagement has an end date written into it.

Ongoing support is available as a separate agreement. The default is that we finish and leave.

What you own

All of it. Code, infrastructure definitions, documentation, and the data. In your accounts, under your keys.

On Becoming Load-Bearing

Every consultancy is structurally rewarded for making itself hard to remove. The counterweight has to be contractual rather than cultural, so it is written into the engagement: an end date, your accounts, your keys, your owner trained before we go.

Ask us for the handover artifacts from a completed build during the assessment. That is the test that matters, and it is a fair one to run on us.