About
Fourteen people, no salespeople.
We work in small senior teams, publish the numbers our clients agree to share, and measure ourselves on whether your engineers can extend what we built six months later.
How we operate
Four commitments we have turned down work over.
These are not values on a wall. Each one has cost us a project, which is the only test that means anything.
We start where the work happens
Discovery means sitting with the people who will use the software. Two weeks in a depot has changed more of our architecture decisions than any requirements document.
We will talk you out of projects
Three times last year we told a prospective client that a $40 tool would solve their problem. Two of them came back later with something we were actually needed for.
Handover is a deliverable
Before the final invoice, one of your engineers ships a real feature while we watch and stay quiet. Whatever they get stuck on, we fix while still under contract.
Small teams, senior people
Two to four people per project, all of whom write code or design. No account layer between you and the person doing the work.
How we work
Seven phases, and you can see into all of them.
Every phase has an output you can review. If a phase produces nothing you can read or click, it was not a phase.
01 · 1–2 weeks
Discovery
We interview the people who do the work, map the real process rather than the documented one, and write down what success will be measured by.
- Process map
- Success metrics
- Technical constraints
02 · 1 week
Planning
Architecture decisions, a prioritised backlog and a cost range you can take to a board. If the scope does not fit the budget, this is where we say so.
- Architecture doc
- Prioritised backlog
- Cost range
03 · 2–4 weeks
Design
Flows, prototypes and a component library. We test with your users in the browser early, because static mockups hide the interactions that matter.
- Design system
- Clickable prototype
- Accessibility spec
04 · 4–20 weeks
Development
Two-week sprints with a demo at the end of each. Every pull request gets a preview environment, so you review working software rather than a status report.
- Sprint demos
- Preview environments
- Working software
05 · Continuous
Testing
Automated tests run on every commit, with manual QA on real devices. Performance and accessibility budgets fail the build rather than the launch.
- Test suite
- Performance budget
- WCAG 2.2 AA audit
06 · 1 week
Launch
Staged rollout with monitoring and a tested rollback. We run the release with your team watching, then hand them the runbook.
- Runbook
- Monitoring + alerts
- Rollback plan
07 · Ongoing
Support
A named engineer, response times in writing, and a monthly improvement budget so the product keeps moving after the launch post.
- SLA
- Monthly report
- Improvement backlog
Clients
What people say when the project is over.
Every quote below is from a named client on a project we delivered end to end.
They spent two weeks in our depots before writing any code. The result is the first internal system our managers have asked for more of.
Marta Kowalczyk
Chief Operating Officer, Northwind Logistics
ARCHON refused to launch until the evaluation numbers satisfied our clinical governance board. No vendor had ever pushed back on our timeline for the right reason before.
Dr. Priya Raman
Clinical Director, Lumen Health
Our auditors asked how we produced a full row-level access log so quickly. It was a single export. That answer paid for the project.
Daniel Osei
Chief Financial Officer, Atlas Capital
They told us our conversion problem was shipping copy, not our design, and talked us out of a rebuild we had already budgeted for.
Amelia Fournier
Founder, Verdance
Six months after handover our own engineers ship features without calling them. That is the part most agencies never get right.
Tom Bridger
Head of Field Operations, Cadence Utilities
The first fortnight was them documenting how we actually work, including nine steps our own process diagram had missed. The automation almost built itself after that.
Sarah Lindqvist
Managing Partner, Meridian Advisory
Want to meet the team that would build it?
A 30-minute call, no deck. We will tell you whether this is a project we should take, and what we would do first.