Contact
Tell us what you’re building.
The first call is 30 minutes and costs nothing. We scope the problem, the stage, and the fit. If we aren’t the right team for it, we’ll tell you on that call rather than three weeks later.
The fastest route. A couple of lines on the problem is plenty to start.
Studio
66 Paul StreetLondon EC2A 4NA
Remote-first. On-site for kickoffs, workshops, and architecture sessions.
What happens next
Most teams build the feature that was asked for loudest. We map the whole opportunity space first, put a return against every item on it, and build in that order — AI-leveraged, with a human accountable at every step.
01Map the world
We go deep on the domain before proposing anything — the operation end to end, where money moves, where time leaks, and what the real constraints are. The output is a map of every opportunity worth naming, not a requirements list.
02Put a return on it
Every opportunity on the map gets a number: what it is worth, what it costs to build, and how confident we are in each. Anything that cannot carry a number gets labelled as such rather than quietly slipped into scope.
03Sequence by return
The roadmap falls out of the numbers — biggest return first, not the loudest stakeholder and not the easiest ticket. Where two are close, the one that unblocks the others goes first.
04Build at speed, human in the loop
We are engineers first, and AI amplifies that rather than substituting for it — which is what collapses delivery timelines the way it does. A person still owns every architectural call, every review, and everything that reaches production. The acceleration is real; the accountability does not move.
05Measure, then re-map
We check the shipped result against the return we projected. Where the projection was wrong, the map gets redrawn — that feedback loop is what keeps the sequence honest as the business moves.
Certified, and boring about it on purpose.
We work in government, banking, and healthcare supply chains. The compliance questions come early, so here are the answers up front.
ISO 27001
CertifiedInformation security management certified against the international standard — covering how we handle, store, and access client data and code.
Cyber Essentials
CertifiedUK government-backed scheme covering the technical controls that stop the overwhelming majority of common attacks.
UK GDPR
CompliantPersonal data handled under UK GDPR and the Data Protection Act. Data processing agreements available on request, with sub-processors disclosed.
- Work-for-hire IP terms — you own everything we produce
- Secure SDLC with SAST, dependency scanning, and secret detection in CI
- Least-privilege access to client systems, revoked at engagement close
- NDAs and DPAs signed before any access is granted
FAQ
Do you build full products, or just provide engineers?
Both. We take products from nothing to production — architecture, build, launch, and the operational work afterwards — and we also embed specialists into teams that already have momentum but are missing a discipline. Some engagements start as the second and become the first.
What does an engagement look like?
It starts with a 30-minute discovery call, then a short paid assessment sprint where we meet the team, read the code, and deliver a written plan. From there it is either a scoped build with a defined outcome, or an ongoing embedded engagement. Assessment findings are yours either way, whether or not we continue.
How many clients do you take on at once?
Deliberately few. Staying small is what lets us go deep enough on a domain to make the calls that matter rather than staffing a project and checking in monthly. It does mean availability is limited, so if you are weighing a call it is worth booking early.
Do you work with existing engineering teams?
Frequently. We work inside your rituals, your repo, and your review process rather than running a parallel track. The goal is that the capability stays with your team after we leave — which means pairing, documentation, and handover are part of the work, not an afterthought.
Do you publish pricing?
No. It depends on scope, stage, and shape — a fixed-scope build and an embedded specialist engagement price very differently. The discovery call is free and we quote on the follow-up.
Are you remote or on-site?
Remote-first, London-based. We travel on-site for kickoffs, workshops, architecture sessions, and any other moment where being in the room actually matters. Expenses billed at cost.
Who owns the IP of work you produce?
You do. Standard work-for-hire terms in every engagement contract — no ambiguity, no IP carve-outs, no licence-back arrangements.
What is the notice period?
30 days either side after the initial assessment. No long tie-ins.
Can you take over an existing codebase?
Yes, and it is a common starting point. The assessment sprint exists partly for this: we read the code, map what is load-bearing, and give you a written view of what is worth keeping, what needs replacing, and in what order — before anyone commits to a rewrite.
Can you do a one-off technical review or due diligence?
Yes. Fixed fee, typically a 5–7 day turnaround, with a written report covering codebase, architecture, security posture, and team — ready to put in front of an investment committee or a board.