Discovery
We do not start building until we can explain your system back to you.
You get A written technical brief and a fixed quote
How we work
Our process, our models, and our exit terms.
Published here because the thing that stops people hiring an unfamiliar firm is not price — it is not knowing what they are agreeing to.
01Delivery
Every stage hands you something.
Architecture
Decisions recorded with the options we rejected and what we traded away.
You get Architecture decision records, estimated by component
Build
Working software in a real environment from the first week, not the last.
You get A staging URL you can open from week one
Hardening
Tests, observability, and the alerting that tells you before your customers do.
You get A runbook and meaningful test coverage
Care
We stay. The people who built it are the people who maintain it.
You get A monthly written report
02Engagement models
Four shapes of working together.
Fixed-scope build
- Best for
- A defined piece of work with a clear finish line.
- How it is priced
- Fixed quote, after a paid discovery.
- Typical length
- PLACEHOLDER — typical range
- What we need from you
- A decision-maker available weekly, and access to the systems involved.
Embedded engineer
- Best for
- You have a team and need senior capacity on one area.
- How it is priced
- Monthly rate for an agreed number of days.
- Typical length
- PLACEHOLDER — minimum commitment
- What we need from you
- An existing backlog and someone to prioritise it.
Ongoing care
- Best for
- A system that must keep running and keep changing.
- How it is priced
- Monthly retainer, scaled to the system.
- Typical length
- Rolling, cancellable with notice.
- What we need from you
- Agreed response expectations and access to monitoring.
Assessment
- Best for
- You inherited something and need to know what you have.
- How it is priced
- Fixed price. You keep the report either way.
- Typical length
- PLACEHOLDER — typical range
- What we need from you
- Read access to the code and a conversation with whoever knows it.
03Ownership and exit
What you can hold us to.
- 01
You work with the engineers
PLACEHOLDER — founder name and photograph. The person who scopes your project writes or reviews the code.
- 02
Published rates and models
Our engagement models and pricing method are on the site, before you ask.
- 03
We reply within one business day
From an engineer, with a real technical observation — not a form letter.
- 04
You own everything
Code, repositories and infrastructure accounts are yours from day one. Handover terms are stated up front.
FAQWhat people ask before signing
What people ask before signing
What if we want to stop mid-engagement?
You can, with notice. Work is invoiced to the point of stopping, you keep everything produced so far, and we will write a handover note covering where things stand.
Who owns the code?
You do, from the first commit. Repositories and infrastructure accounts are created in your name, not ours, so there is nothing to transfer at the end.
What if the estimate turns out to be wrong?
We re-quote the changed part and tell you as soon as we know, rather than absorbing it silently or stopping. Discovery exists to make this rare, not to pretend it cannot happen.
Do you work with our existing developers?
Often, yes. We are usually either leading the architecture or taking one well-defined part end to end, and both work alongside an internal team.
—Start a project
Tell us what is broken.
We will tell you what we would do about it — before you have paid us anything.
- 01
Send a short brief
Five minutes. What you are building, or what is broken.
- 02
We reply within one business day
From an engineer, with a real question or observation.
- 03
A 30-minute technical call
Free, no deck, no obligation.