Process
Fast, without the usual risk.
Most software projects fail slowly and quietly — months of activity, nothing running, and a difficult conversation at the end. The way we work is designed so that if something is going wrong, you find out in week one rather than month four.
The method
From first call to production.
The same four steps whether the work takes three weeks or nine months. Week-one software is not a claim about how short your project is — it is how you find out early that it is going the right way.
Scope
A 30-minute call. We pressure-test the idea, define what winning looks like, and agree a scope you can see written down.
Architect
We design the system — data, integrations, infrastructure — and hand you the plan before a line of code is written.
Build
Working software in week one. Every week after, you see it run rather than reading a status update about it.
Ship & own
We deploy to production, hand over the keys, document everything, and stay reachable. It is yours.
Long programmes
Six to nine months is normal work here.
Enterprise integrations, platform rebuilds, and multi-system programmes do not fit in a few weeks, and we do not pretend otherwise. What changes on a long programme is not how we work — it is that the discipline matters more. A nine-month project is exactly the kind that fails quietly in month five.
Discovery & integration map
Two to three weeks. We get into the actual systems — the ERP, the CRM, the twenty-year-old database nobody wants to touch — and map what talks to what. You get the integration map and a phase plan whether or not you continue with us.
Thin slice, end to end
One narrow path through the whole system, working in production. Not a prototype: one real record moving through every integration point. This is where the surprises surface, at week four rather than month five.
Phase delivery
Six to ten week phases, each one fixed-price and independently useful. Value lands as you go rather than everything arriving at the end, and you can stop between phases without stranding half a system.
Handover, phase by phase
Documentation, runbooks, and knowledge transfer at the end of every phase rather than saved up for the finish. Your team can operate what has shipped so far, continuously.
What procurement always asks
How do we control budget across nine months?
Each phase is separately priced and separately approved. You are never committed to more than the phase you are in, and there is no open-ended time-and-materials meter running in the background.
What if it is going wrong in month five?
You will have known since week two. Something runs from the first week and every week after, so a bad assumption surfaces while it is still cheap to change. This is the entire reason we work that way, and it matters far more on a nine-month programme than on a three-week one.
Can you work with our engineering team?
Usually we own one or two workstreams and integrate with your sprint cadence, your code review, and your release process. We are not trying to become permanent — the point is that you can carry it without us.
Our systems are old and badly documented.
That is most integration work, and it is why discovery is a paid phase rather than a free sales call. We would rather find the undocumented behaviour in week two than commit to a plan built on an org chart.
If you are scoping something that runs into next year, the first conversation is about the integration map — not about us.
How we operate
Six things we hold to.
You see software, not status
Every week you get a working build you can click, not a slide about progress. If a week goes by without something running, something has gone wrong and you'll hear it from us first.
You own everything from day one
Repositories, cloud accounts, domains, credentials — all in your name from the first commit. There is no platform to keep paying for and no hostage situation if you want to take it in-house.
Scope is written down before we start
What's in, what's out, what it costs, and what happens if it changes. Scope creep is a communication failure, not an invoicing opportunity.
We tell you when you're wrong
Including when the answer is that you don't need the thing you asked for, or that it should be bought rather than built. We would rather lose the work than build you something you'll regret.
Senior people do the work
The person who scopes your project is the person who builds it. Nothing gets handed to a junior team after the sales call, because there is no sales team.
It's production or it isn't done
Deployed, monitored, documented, and handed over. Software that only runs on a developer's laptop isn't finished, and we don't invoice as though it is.
Ways to work with us
Three ways in.
Sprint
A fixed, fast strike
1–4 weeks. A proof-of-concept, a single integration, an audit, or a critical feature. Scoped on this page, shipped on a deadline.
Best for: validate fast, unblock a launch
Build Partner
We own the build
2–9 months, delivered in fixed-price phases. We take a product, platform, or multi-system integration from idea to production and run point on architecture, delivery, and ship. Working software every week throughout.
Best for: 0 → 1 products, platform rebuilds, enterprise integrations
Embedded
We plug into your team
Ongoing. Senior engineers and a fractional CTO inside your org — owning a workstream, pairing, and shipping alongside your team on your cadence.
Best for: teams scaling or short on senior capacity
The other side
What we need from you.
Projects rarely fail for technical reasons. They fail because nobody on the client side could make a decision. To move at the speed we quote, we need three things:
One decision-maker
A single person who can approve scope and direction without convening a committee. They don't need to be technical.
Roughly an hour a week
A demo and a decision. That's the whole commitment. If you can't spare it, the timeline stretches and we'll say so upfront.
Access, early
Systems, data, and the people who understand them. Most delays we've seen came from waiting three weeks for a credential.
Ready to scope something?
Thirty minutes, no deck, no pitch. We pressure-test the idea and tell you what it actually takes.
We reply to every serious enquiry within one business day