Process
How a project runs, start to finish
The same six steps, in the same order, whether the project is a two-week automation or a three-month platform build.
- 01
Discovery call
A focused conversation about what's broken, what you're trying to achieve, and who the software is actually for. No sales pitch — we ask questions until the problem is clear.
- 02
Scope & proposal
You get a written scope of work, timeline, and fixed price before anything is signed. If something's unclear, we run a short paid discovery sprint rather than guess.
- 03
Design
Screens, flows, or architecture diagrams — whatever the project needs — reviewed with you before development starts, so changes happen on paper, not in code.
- 04
Build
Development happens in short cycles with a working preview you can check in on, not a single black-box delivery at the end.
- 05
QA & launch
Testing against real devices and real data, a staged rollout, and a launch day where we're on call in case anything needs attention.
- 06
Support & growth
Every project includes a fixed support window after launch. After that, most clients move to a monthly retainer for updates, new features, and maintenance.