Three ways to work with us.
Not a price ladder — a certainty ladder. Which one you need depends entirely on how much you already know, and being honest about that is the first useful thing we’ll do together.
Where are you starting from?
The offerScoping Sprint
“Is this buildable, what exactly is it, and what will it cost?”
Fixed scope · fixed price1–2 weeks
from £—,—— · TBC02
Proof of Concept
“Does the idea survive contact with real users?”
Fixed-price sprint4–8 weeks, typically
from £—,—— · TBC03
Build & Partnership
“Build it properly, then help me keep it alive.”
Discovery → build → retainerOngoing
Priced after scoping
What a Scoping Sprint gives you
01 — Scoping SprintYou have an idea and a budget in mind, and no reliable way to connect the two. You end up owning a document you could hand to any competent developer — if you never work with us again, it was still worth doing.
- ✦Product definitionUsers, jobs, journeys, and the specific problem release one solves.
- ✦Scope, cut downWhat’s in release one, what’s deliberately deferred, and why.
- ✦Technical approachArchitecture, integrations, and the decisions that will be expensive to reverse.
- ✦Costed delivery planA timeline and a number, with every assumption written down beside it.
What a proof of concept answers
02 — Proof of ConceptScoping tells you what to build. A proof of concept tells you whether you should. We build the smallest real thing that answers your riskiest question — not a clickable mockup, working software people can actually use.
- ✦A working productDeployed, usable, and yours — not a prototype that has to be thrown away.
- ✦The riskiest question, answeredWe agree upfront what would make this a success and what would make it a no.
- ✦A recommendationContinue, pivot, or stop — with the reasoning, in writing. Stopping is a legitimate outcome.
What a full engagement looks like
03 — Build & PartnershipDiscovery, design, build, launch — and then the part most studios treat as an afterthought, which is keeping the thing running while your business changes around it.
- ✦End-to-end deliveryProduct, design, frontend, backend, infrastructure — one person accountable for all of it.
- ✦Handover-ready from day oneDocumented, conventional, and built so another developer could pick it up. No lock-in.
- ✦Ongoing partnershipRetained support, iteration, and someone who remembers why every decision was made.
What we build
CapabilityMostly web applications and the internal systems businesses actually run on — the unglamorous software that decides whether a company works. Some mobile. Some marketing sites, when they’re part of something bigger.
The stack is deliberately conventional. Nothing here is chosen because it’s interesting; it’s chosen because it’s well-documented, widely known, and someone else could maintain it if you ever needed them to.
Seen in practice
ProofTell me what you’re trying to build.
Half an hour. No deck, no discovery theatre. Bring an idea on the back of an envelope or a system that is falling over — either way you will leave the call knowing what I think it takes, and whether I’m the right person to do it.
Zeki Mirza — Founder
Every call is with the person who does the work