Approach

How the work actually gets done.

Most of what a buyer can check before signing is here: the stages, what each one produces, who holds the work at each point, the things we turn down, and what happens to your data. If any of it sounds unlike how your last programme ran, that is the conversation worth having.

Method

Four stages, each with an output you can hold

Step 01

Discover

Find the problems worth solving and rank them by value and feasibility.

You getPrioritised use cases and a business case

Step 02

Prove

Build the riskiest part first, on real data, and measure it against a baseline.

You getWorking prototype with evaluation results

Step 03

Build

Engineer it into your systems with monitoring, guardrails and a human in the loop.

You getProduction system your team can run

Step 04

Scale

Train the people, redesign the workflow, and extend to the next use case.

You getAdoption metrics and a roadmap for what comes next

The shape of it

The handover is the plan, not the ending.

We start holding most of the work and finish holding almost none of it. Your people are on the build from the first stage, so the transfer happens continuously rather than arriving as a document at the end.

Discover: we do 80%, your team 20%. Prove: we do 65%, your team 35%. Build: we do 40%, your team 60%. Scale: we do 10%, your team 90%. By the final stage the system is run by the client's own team. 80%Discover65%Prove40%Build10%Scale
UsYour team
Who holds the work at each stage. The proportions describe the model we design towards, not a staffing guarantee.

Principles

What we will and will not do

Four commitments, each with the trade-off it costs us. A principle whose opposite nobody would choose is not a principle.

01

We build in your environment, not ours

The work lives in your repositories, your cloud and your tooling from the first week. It is slower to start — we spend days on access that a demo on our own laptops would skip — and it is the only way the thing we build is still yours when we leave.

02

The riskiest part gets built first

Not the most impressive part. If the data is unusable or the accuracy fails where it matters, that should surface in week two, not month five. This makes our early demos less flattering than they could be, and it is the point.

03

One stage at a time, priced before it starts

You agree to a stage, not a programme, and you can stop at the end of any of them and keep everything produced — including the code. We give up the certainty of a long contract for the discipline of having to earn the next stage.

04

We work to leave

Every engagement names the people who will run the system afterwards, and training, runbooks and documentation are part of the build rather than a final invoice. A firm that cannot be got rid of has an incentive we would rather not have.

Security and governance

How we handle your data

You are weighing up a firm you cannot yet check with three references, so here is the part most firms make you ask for.

Data handling

Your data stays in your environment wherever the work allows it. Where it cannot, we agree in writing what moves, where it is processed and when it is deleted — before anything moves.

Access model

We ask for the least access that lets us do the job, granted through your process and revoked at the end of each stage. Where access cannot be granted, we work with redacted or synthetic data and tell you what that costs in accuracy.

Commitments

We will sign your DPA, work to your security policy, and assign the IP in everything we build to you. Engagements end on 30 days' notice, from either side.

Questions

How engagements run in practice

How does an engagement start?
With the Starting Point Review: one working session with the people who would own the system, spent ranking what you are considering and scoping the first thing worth building. You leave with that shortlist whether or not we work together. If you decide to go on, the first stage picks up from exactly where the session left off.
How long until something is in production?
The first working version comes out of the Prove stage, built on your real data; a production system follows at the end of Build. What moves that date is almost never the modelling — it is how quickly we get access to real data, how many systems it has to talk to, and how fast decisions get made on your side. We will give you a dated plan at the end of Discover, once we have seen those three things rather than guessed at them.
Will this work with our existing data and tools?
We build inside your environment and on your stack rather than beside it, which is what makes handover possible at the end. What we need from you is access to the real data, one person who knows how the process actually works today, and someone who can make a decision without convening a committee. If the data is not ready, Discover will say so plainly instead of quietly building around it.
How do you handle security and data privacy?
Your data stays in your environment wherever the work allows it, and where it cannot, we agree in writing what moves, where it is processed and when it is deleted before anything moves. We ask for the least access that lets us do the job, granted through your process and revoked at the end of each stage. We will sign your DPA, work to your security policy, and assign the IP in everything we build to you.
Who will we actually work with?
The people in the first conversation are the people who build the thing. We are small and senior on purpose: no pyramid, no handover to a team you have not met, and no junior learning on your budget. You will know exactly who is on your engagement, and what they have shipped before, prior to committing to anything.
How is pricing structured?
Each stage is scoped and priced before it starts, so you are agreeing to one stage at a time rather than to a programme. You can stop at the end of any of them and keep everything produced to that point, including the code. We do not work on open-ended retainers, because an engagement that cannot end is not the same thing as one that succeeds.

Next step

Have a problem worth solving?

You will hear back within a working day, from the person who would do the work rather than someone selling it. If we are not the right firm for what you need, we will say so and tell you who is.