Working With Us — Engagement & Commercials

How an engagement unfolds

From first conversation to owned capability — one governed journey.

Six moments. At every one, you decide.

First conversation

Talk to the builders

Scoping

You set the cap

System set-up

Guardrails arm

Small, reviewed steps

Engineer at every gate

Evidence & decision

Renew, or stop

Scale, or hand over

IP is yours

Why this journey is different: speed and governance are usually a trade. We don’t make you choose.

Fast teams ask you to accept risk; safe teams ask you to accept delay. With us you accept neither — AI speed, your rules enforced at the boundary, a named engineer at every gate.

For procurement: deliverables, gates, and caps are contractual; the record gives full auditability of what was built, by whom, under whose approval.

Engagement shapes

Three shapes. The same governed practice inside.

Stage 1 · See it work

Focused start

One use case, fixed cycles, capped budget — ending at a decision gate with working software and proof.

Working software · proof pages · your decision

Stage 2 · Trust it further

Programme

A portfolio under one organisation — shared blueprints, compounding quality.

Portfolio · shared blueprints · certification begins

Stage 3 · Make it yours

Enterprise

Pods across the organisation, governed by your standards — your team directing.

Org-wide pods · your governance · your direction

The commercial model

Two costs. Both visible. No third.

Cost one

The delivery fee

Agreed for the engagement scope before work starts — the practice, the senior engineers, the proof. Known in advance, every time.

Cost two

AI usage — at cost, on your subscriptions

Runs on your own subscriptions — any cloud, or an in-country model. Metered, capped by you, 0% markup.

How AI usage works, by engagement stage

See it work

One cap agreed up front on your existing subscriptions — we pause and ask before it is reached.

Trust it further

Caps set per workstream as the portfolio grows — spend visible on every proof page, next to what it produced.

Make it yours

Your enterprise agreements or in-country models, under your governance and budgets.

Common questions

Asked by every serious buyer. Answered plainly.

Who owns the code and the record?

You do, from the first commit. Code, documentation, and the complete delivery record are yours — there is nothing to negotiate at exit.

What happens if we stop after the first engagement?

You keep working software, its proof pages, and everything above. Stopping is a decision gate we design in — not a failure mode.

Can this run in our environment, under our policies?

Yes. Engagements run with your standards and policies loaded, against your repositories and clouds, and can use in-country models where data sovereignty requires it.

How do you protect our data and credentials?

AI roles never hold credentials — they hold a name, a scope, and a pointer. Every access is brokered at the boundary and recorded. Controls fire whatever the agent decides.

What does AI usage actually cost us?

It runs on your subscriptions at cost, with 0% markup — metered against a cap you set. If usage approaches the cap, we pause and ask.

Who is accountable when something goes wrong?

A named senior engineer — the person who opened the gate. The record shows every decision and its approver, so accountability is a lookup, not an investigation.

How do we start?

Email us from the Contact button in the header (or the footer of any page) and tell us about your use case. A senior engineer replies personally, and the first step is a single scoping conversation — no commitment attached.

A delivery practice that arrives already disciplined — your standards, enforced from day one.

One conversation with the engineers who would build the work — email us and a senior engineer replies.