How we work
No big-bang launches and no year-long silences. One real workflow goes live within weeks, you get a working demo every week after that, and every scope decision is written down.
The four stages
We sit with the people who do the work and write down how your business actually runs — the entities, the approvals, the exceptions.
One real workflow goes live early, end to end, on your data. You see working software in weeks, while everything is still cheap to change.
A small group runs their actual work on the system. We watch what breaks, fix it, and only then widen the rollout.
Full rollout in stages you can keep trading through, then ongoing support and improvement — or a clean handover to your team.
How to buy
We quote after discovery, once there is a written scope to quote against — not before.
1–2 weeks · fixed fee
We sit with the people who do the work and write down how your business actually runs — the entities, the approvals, the exceptions — then scope and estimate the build against it.
You keep: The scope document, architecture outline and estimate — yours even if you stop here.
Defined outcome · staged payments
A written scope, milestones you pay against, and working software in your hands early. Ninety days of defect warranty from go-live, measured against the scope we agreed.
You keep: Source code, documentation and infrastructure configuration, handed over in full.
Monthly · senior engineers
Senior engineers working your backlog to your priorities, in your ceremonies. Useful when the destination is still moving, or when you need to add capacity to a team you already have.
You keep: Everything, continuously — you hold the repository throughout.
Ongoing · agreed response times
We operate and improve what's live: monitoring, patching, enhancements, and agreed response times for when something breaks. Business hours, with extended cover available.
You keep: The option to take it in-house whenever you want, with a clean handover.
Working rhythm
Everything below is something we do every week, not an aspiration.
Thirty minutes, running software on real data — not a slide deck or a percentage. Recorded, so anyone who missed it can catch up.
What shipped, what's next, what's blocked, and what we need a decision on. Short enough that busy people read it.
Reachable directly. Not a ticket queue, and not an account manager relaying messages to the people doing the work.
Day-to-day questions on whatever you already use — Slack or Teams. Email for anything contractual.
What's in flight, what's queued, what we've deprioritised — visible at any time in GitHub, without having to ask.
Every scope decision recorded with the date, the reasoning and who made it. This is what prevents the “we never agreed to that” conversation six months in.
From your side
Stated plainly, because engagements fail on these far more often than they fail on technology.
Ownership
Custom builds are handed over completely. There is no licence to keep paying, and no dependency on us to make a change.
Ninety days of defect warranty runs from go-live on fixed-scope projects, measured against the agreed written scope. Changes of scope are not defects — which is exactly why the discovery document matters.
One to two weeks, fixed fee. You keep the scope document, architecture outline and estimate even if you decide to stop there.