Decide what to build before you build it.
Most software fails not because it was built badly, but because the wrong thing got built carefully. Discovery isn't a sales formality — it's where the project gets its shape.
How we work
Engagements that earn the next conversation.
Most agency engagements end at the project. We design ours to end with a handover, a working system, and a relationship that's worth a phone call the next time something hard lands. This is what that looks like in practice.
Our principles
Five opinions about how software should be built.
Senior people on the hard problems, junior people supported by them.
We don't grade junior work up to senior rates. Where the decisions are expensive to undo, you get someone who's made them before. Where the work is mechanical, you get the cheapest competent person and we're honest about which is which.
Ship something real every week, not slideware.
A working demo at the end of every week, against real data wherever possible. Slides are how agencies sell; software is how engagements stay honest about progress.
AI accelerates the team. It doesn't replace the experience.
We use modern AI tooling heavily — for scaffolding, tests, documentation, migrations, the work that benefits from it. We don't use it for architecture decisions or trade-offs that survive past the first release. The experience still comes from people who've done this before.
The engagement that ends well is the one that earns the next one.
We design every handover so your team can run the work without us. Sometimes that means the engagement ends. Sometimes it means we get the next phone call when the next problem lands. Both are wins.
The shape of an engagement
Discover · Design · Deliver · Sustain.
Four stages, not twelve. A simple horizontal flow — not a waterfall in disguise.
- 01
Discover
What we're building, why, and what success looks like.
- 02
Design
The shape of the thing — validated before code.
- 03
Deliver
Working software, weekly demos, real users.
- 04
Sustain
Hand back built into every stage. Your team owns it.
Two ways we engage
MVP Development if you don't have a product yet. Scale & Modernise if you do.
How We Work / MVP Development
MVP Development
A time-boxed MVP engagement, opinionated about scope and delivered by senior practitioners — not a fishing expedition.
How We Work / Scale & Modernise
Scale & Modernise
Senior engineers working alongside your team to evolve systems that are working but straining — incrementally, measurably, without disturbing what's load-bearing.
What stays the same
The principles don't change between MVP and Scale.
Some clients start with an MVP and move into Scale & Modernise as the product matures. The shape of the engagement changes; the seniority of the people on it doesn't. The same team that frames an MVP is the team you keep when it's a system supporting thousands of users.
Tools we lean on
A small list, named honestly.
Design
- Figma
- FigJam
Engineering
- TypeScript
- Postgres
- your stack
AI
- Claude
- Cursor
- GitHub Copilot
Project
- Linear
- Notion
- Slack
Want to see how this would work for your build?
Liverpool, UK. Available across the UK and remote.