Four steps, no surprises
Every project runs the same way, whether it takes a week or half a year. You always know what stage you're in, what you'll get at the end of it, and what it costs.
What actually happens, step by step
Each stage ends with something concrete in your hands. Nothing moves forward until you've seen it.
- 0101
Consultation
One conversation, freeWe work out what the problem really is before anyone talks about building.
Most briefs arrive as a solution â an app, a dashboard, a system. We start one step earlier and ask what breaks today, who it breaks for, and how often. Sometimes the honest answer is that a smaller build fixes it, and sometimes it's that you don't need an app at all. You'll hear either one.
What you get
- A shared, written understanding of the problem
- The shortlist of what has to exist in version one
- A first read on whether ready-made or custom fits
What we need from you
Bring the messy version. Screenshots, spreadsheets, the workaround your team invented â all of it helps more than a polished brief.
- 0202
Proposal
Usually a few daysScope, timeline and cost in writing â before anything is agreed.
You receive a document that states exactly what is being built and, just as importantly, what isn't. It splits the work into stages so you can see where the effort sits, and it names the assumptions we've made so you can correct them. If the numbers don't work, we change the scope together rather than quietly cutting quality.
What you get
- A written scope, stage by stage
- A timeline with the milestones marked
- A cost that matches that scope, with assumptions listed
What we need from you
Read it properly and push back. A disagreement at this stage costs a conversation; the same disagreement later costs a rebuild.
- 0303
Development
Days to months, by scopeBuilt in stages, with something you can open and try at each one.
We design the screens before writing the code, so the flow is settled while it is still cheap to change. From there the app is built in stages, and each stage lands somewhere you can log in and use it â not a screenshot, not a status update. Feedback goes in as we build rather than piling up for the end.
What you get
- Screen designs and the flow between them
- A working environment you can open at every stage
- Regular progress notes, in plain language
What we need from you
Try each stage while it's fresh and tell us what feels wrong. The people who will use it daily should be the ones looking.
- 0404
Handover
On release, then ongoingThe app, the code, the accounts and the documentation all become yours.
Handover is a transfer of ownership, not a goodbye email. Source code, hosting and service accounts, and documentation written for someone who wasn't in the room all move to you. If you want us to keep going â maintenance, fixes, the next set of features â that carries on under terms agreed up front, and it is a choice, never a dependency.
What you get
- Source code and every account, in your name
- Documentation and a walkthrough for your team
- Support terms in writing, if you want them
What we need from you
Pick who on your side takes the keys, and bring them to the walkthrough so the knowledge doesn't sit with one person.
How we behave while it's being built
Process is the easy part to write down. These are the habits that decide whether it holds up.
Plain language
Progress explained in words you can repeat to your team, not in framework names.
Decisions written down
Anything agreed in a call is confirmed in writing, so memory never has to arbitrate.
Smallest useful version first
The part that earns its keep ships first. Nice-to-haves queue behind it.
Bad news travels fast
If something slips or an estimate was wrong, you hear it early â while there are still options.
The app isn't finished the day it ships
What happens next is agreed before release, so the end of the build is never the start of an argument.
Fixes
Defects in what we delivered get corrected under the terms we agreed, not re-quoted.
Updates
Dependencies, security patches and platform changes kept current on a schedule.
Next features
The queue you parked during the build, picked up in priority order when you're ready.
Or nothing at all
You hold the code and the accounts. Continuing with us is always optional.
The first step costs a conversation
No proposal, no commitment and no cost until we both understand what is being built. Tell us what's not working and we'll take it from there.