How we work
Five phases, and you can see into every one of them
Most project horror stories come from the same place: nobody could tell what was happening until it was too late to change. This is how we avoid that.
- 01
Discovery
Week 0 — free
A 30-minute call to understand the problem, then a written scope you own whether or not you hire us.
What you get
- A one-page problem statement in plain English
- Recommended approach, and what we would deliberately leave out
- Fixed price and a delivery window
- An honest answer if software is not the right fix
Your part: Turn up to the call and answer questions candidly.
- 02
Design
Weeks 1–2
Wireframes then a clickable prototype, so disagreements happen over a picture rather than over finished code.
What you get
- User flows for the paths that matter
- Clickable prototype in Figma
- Visual design applied to key screens
- Technical architecture and integration plan
Your part: Review the prototype and tell us what is wrong. Twice is normal.
- 03
Build
Weeks 3–10
Two-week sprints against a live staging environment. You watch it come together instead of waiting for a reveal.
What you get
- A staging link updated continuously
- Sprint demo and written summary every two weeks
- Automated tests on the parts that would hurt if they broke
- Code in your repository from the first commit
Your part: Give feedback within a few days of each demo so it stays cheap to act on.
- 04
Launch
Week 11
Deployment, tracking, store submission and handover — including the boring parts that usually get skipped.
What you get
- Production deployment with monitoring and backups
- Analytics and conversion tracking verified end to end
- App store submission handled, review responses included
- Documentation and a recorded walkthrough for your team
Your part: Approve the go-live and tell your customers.
- 05
Automate & optimise
Ongoing
Where most agencies stop, we connect the software to your operations and keep improving it on evidence.
What you get
- CRM and workflow automation around the new system
- Monthly dashboard covering the metrics you chose
- A prioritised improvement backlog based on real usage
- Hosting, updates and security patching under a care plan
Your part: Decide what to build next from the backlog. We advise, you choose.
Principles
Four rules we do not bend
These are the things clients tell us made the difference, so we wrote them down.
Fixed price, not a meter
You get a figure before we start. If we underestimate, that is our problem, not an invoice you did not expect.
Ship small, ship early
A narrow thing in real hands beats a broad thing in a spec document. Version one is deliberately smaller than you want.
No black boxes
Code in your repo, accounts in your name, documentation written for someone who is not us.
Say the awkward thing
If a feature is a bad idea, or the project should not happen, we will tell you while it is still cheap to change course.
Process FAQs
The practical questions
What if the scope changes halfway through?
It usually does. Anything inside the agreed scope is covered by the fixed price. Genuinely new requirements get quoted separately before any work starts, so you always choose whether the extra cost is worth it.
How much of my team's time will this take?
Expect a 30-minute call each fortnight plus a couple of hours reviewing demos. Discovery and design weeks are more intensive — perhaps half a day each.
What if we need to pause?
Tell us. We finish the current sprint, hand over everything completed, and pick up when you are ready. You are not billed while paused.
Do you work with our internal developers?
Often. We can take a defined component, work alongside your team in the same repository, or hand over entirely after launch with a documented onboarding.
Get a free quote in one working day
Tell us what you need. You get a written scope and a fixed price — no obligation, and it is yours to take elsewhere.
- Reply within one working day
- Fixed price before any work starts
- Talk to the people who build it