How we work

Our process.

Six stages, from the first scoping conversation through to support after launch. You can see what we are working on at any point, and what it will cost.

01

Discovery & Scoping

1–2 days

We work out what you are actually trying to fix, who it is for, and what a good outcome looks like. If we think the plan is wrong, we say so at this stage.

Problem definitionSuccess criteriaScope documentInitial timeline
02

Planning & Architecture

2–5 days

With scope agreed, we design the architecture and break the build into a sprint plan. We pick tools we can still support two years from now, and write down why each one was chosen.

Technical architectureStack decisionsSprint planRisk register
03

Development

Ongoing sprints

We build in short iterations and put working software in front of you at the end of each one, so you can react to the actual thing rather than a status report.

Working software each sprintDemo sessionsContinuous feedback loopsProgress dashboard
04

Testing & QA

Embedded throughout

Testing runs alongside development rather than waiting until the end: automated tests, manual QA, performance checks, and a security review each sprint.

Automated test suiteManual QA reportsPerformance benchmarksSecurity checklist
05

Launch & Handoff

1–3 days

We handle the full deployment, from DNS to CI/CD pipelines. At handoff, you receive complete documentation, code ownership, and a walkthrough of everything we built.

Production deploymentFull documentationCode transferTeam walkthrough
06

Ongoing Support

Optional retainer

Retainer support after launch, covering bug fixes, dependency and security updates, and new features as they come up.

Bug monitoringDependency managementFeature additionsPerformance tuning

Ready to start?

Tell us what you are building and we will come back with a plan.

Start a project