Clear phases, honest scoping, one accountable team.
Software projects fail in predictable ways: assumed requirements, handovers between vendors, and launches with no plan for what happens next. Our process is designed to remove those failure points.
How the work actually runs
From first conversation to running software.
- 01
Discovery
Typically one to three weeks
We spend time with the people who own the problem and the people who live with it every day. We map the current process, look at the systems already in place, and agree what a good outcome looks like in terms the business already measures.
You get
- Interviews and process maps
- Assessment of existing systems and data
- Agreed definition of success
- Prioritised list of opportunities
- 02
Definition
Ends with a written plan
We turn discovery into options. Each option comes with trade-offs, rough sizing and a recommended architecture. You choose the scope and sequence with a clear view of cost and risk, and you can take the plan to another team if you prefer.
You get
- Solution options with trade-offs
- Recommended architecture
- Phased delivery plan and estimate
- Decision points and dependencies
- 03
Build
Working software from the first weeks
One team covers design, engineering and data, so there is no handover between agencies or departments. We work in short increments, demonstrate working software regularly, and keep a visible backlog so priorities can change while it is still cheap to change them.
You get
- Regular demonstrations of working software
- Tests, documentation and monitoring as standard
- A shared backlog and change process
- Security and accessibility built in, not bolted on
- 04
Run and improve
Ongoing, at a pace that suits you
Launch is the start of the useful part. We monitor what we built, support the people using it, and keep a measured backlog of improvements. Where it makes sense, we hand over fully to your own team with the documentation to do it well.
You get
- Monitoring, alerting and support
- Measured backlog of improvements
- Regular reviews against the agreed outcomes
- Full handover when you want it
Three engagement models.
Most relationships start with discovery and grow from there. We will recommend the model that fits, not the one that is biggest.
Discovery engagement
A fixed-scope, fixed-price piece of work that ends with a plan you own. The right starting point when the problem is clear but the solution is not.
Defined build
A scoped delivery with agreed phases, milestones and budget. Best for a well-understood system with a clear end state.
Ongoing partnership
A retained team working from a shared backlog. Best when the software is central to the business and will keep evolving.
What you can expect from us.
However the engagement is shaped, these four hold. If we ever break one, say so and we will fix it.
Say what we think
If a simpler tool would do, or if AI is the wrong answer, we say so. Our value is in the advice as much as the build.
Small, senior, present
The people you meet in the first conversation are the people who do the work. We keep teams small so decisions are quick and context is not lost.
Leave things better than we found them
Every system we touch ends up with documentation, tests and a clear owner. You should never be dependent on us to understand your own software.
Measure the outcome, not the output
Features shipped is not a result. Hours saved, enquiries answered, errors removed and revenue protected are. We report on those.