Four stages from first conversation to running software
Every project runs the same way, whatever it is for: understand the work, make the solution concrete, ship in short cycles, launch carefully, and keep improving.
Designed to remove the usual surprises
AI where it pays off, not everywhere
We add AI to the steps where it saves real time, and keep a person responsible for the result.
Built around how your business actually runs
We start from your operations, not from a feature list, so the software fits the work instead of the other way round.
One team from first sketch to launch
Design, engineering and delivery sit with the same people, so nothing is lost in a handoff.
You own everything we build
Code, accounts, infrastructure and documentation are in your name from the first week.
The same stages apply whether a project takes two weeks or a year. Each stage can vary in size, but we never skip one.
01. Discover
Understand the business before touching the software.
- Map how the work runs today: who does what, in which tools, where time is lost.
- Agree the outcome the project must produce and how we will measure it.
- Identify the riskiest assumptions and decide how to test them early.
- Written scope with boundaries
- Prioritised feature list
- Estimate and plan for the next stage
02. Plan & design
Make the solution concrete before building it.
- User flows and wireframes for the screens that matter most.
- Data model, integrations and architecture written down in plain language.
- A clickable prototype where it helps you and your team react to something real.
- Prototype or wireframes
- Technical plan
- Milestone schedule
03. Build & integrate
Ship working software in short cycles, connected to your systems.
- Work is delivered in milestones you can use and review, not just read about.
- A demo at the end of every cycle, with a written summary of what changed.
- Integrations with your existing systems, automated tests and code review on every change.
- Working increments
- Demo recordings and notes
- Test coverage for critical paths
04. Launch, support & improve
Go live with the boring parts handled, then keep it useful.
- Environments, monitoring, backups and access set up in accounts you own.
- Data migration, a rollback plan and a walkthrough for the people who will run it.
- Support sized to what you need: updates, fixes and a usage review to pick what comes next.
- Production release
- Runbook and handover
- Support agreement
- Improvement backlog
What we need from you
Access to the right people
The people who do the work today, and someone who can make decisions.
Feedback on working software
A short review after every demo so the next cycle starts from what you saw.
Decisions on time
Approvals for scope changes and milestones, in writing, so the schedule stays honest.
Questions about working together
It depends on scope. Discovery ends with a written scope and an estimate you can take elsewhere. Larger builds are priced by milestone, so you always know what the next payment covers. [Add price bands once decided.]
Ready to start with discovery?
A short first conversation tells us both whether there is a fit. If there is, we start with discovery. You keep everything it produces.