How It Works
How It Works
Four phases, each ending in something you own. No phase assumes you have bought the next one, and nothing is designed so that leaving us is expensive.
Delivery Phases
-
01 1–3 weeks
Diagnose
Understand the problem properly before anyone commits a budget to it.
We interview the people doing the work, review the systems and data involved, and map the constraints that will actually govern the solution — regulatory, commercial, and technical. The output is a written diagnosis, not a proposal.
You end up with
- Opportunity or process map
- Data and systems assessment
- Risk register
- Costed recommendation
-
02 2–4 weeks
Design
Make the solution concrete enough to price honestly.
Architecture, data model, interface design, and integration contracts. For conversational work this is where persona and dialogue design happen; for apparel it is where the tech pack is built. We finish with a fixed price for the first build phase.
You end up with
- Technical specification
- Clickable prototype or design files
- Integration contracts
- Fixed price for phase one
-
03 6–24 weeks
Build
Two-week iterations, each ending in a demo of working software.
You see the system running in a real environment every two weeks and can change direction at each boundary. Testing, CI, and documentation are written as we go rather than promised for the end, because the end is where they get cut.
You end up with
- Working software in your repository
- Automated test suite
- CI/CD pipeline
- Runbook and documentation
-
04 Ongoing or handover
Operate
Run it with you, or hand it over cleanly.
Launch support, monitoring, and a defect warranty. Then either a support retainer, or a structured handover with recorded walkthroughs so your team can own it. Both are normal endings and we price them the same way.
You end up with
- Monitoring and alerting
- Defect warranty
- Recorded handover sessions
- Optional support retainer
How We Manage Software Project Risk and Communication
Bad News Travels Fast
If a date is going to slip or an estimate was wrong, you hear it in the next weekly update, not at the deadline. Late disclosure is the most expensive thing an agency can do to a client.
One Named Team
The people at the pitch are the people doing the work. We will not sell you a senior team and staff a junior one.
Your Infrastructure from Day One
Code goes into your repositories and deploys into your cloud accounts from the first week, so there is never a point at which we hold the system.
Written Over Verbal
Decisions, trade-offs, and their reasoning are recorded where you can find them later, which matters most when the people involved have moved on.
Scope Changes Are Priced, Not Absorbed Silently
Changes get an estimate and a schedule impact at the iteration boundary. Silent absorption is how quality quietly degrades.
We Say No
To work outside our competence, to timelines that require cutting testing, and to projects we think should not go ahead. Saying yes to those helps nobody.
What Happens in the First Two Weeks?
How Often Will We Hear from You?
What If We Want to Stop Mid-Project?
Do You Work Fixed Price or Time and Materials?
Who Is on the Team?
Tell Us What You Are Building, and We Will Put Real Numbers on It.
Thirty minutes with the engineer who would run your project. You leave with a scope, a cost range, and a recommended next step — whether or not you work with us.
A 30-minute call with an engineer, not a salesperson. You leave with a scope, a rough range, and a recommended next step — whether or not you work with us.
- Written scope before you commit
- NDA signed on request
- You own all work product