Our process
A clear path from first conversation to launch — and beyond.
Seven stages, each with a defined output and a clear role for you. Timelines are estimated per project in your proposal rather than promised up front.
The seven stages
- Stage 01
Discovery
We learn about your business, users, goals and constraints before anyone talks about features.
What happens
A discovery call and a short set of written questions. We explore what success looks like, who the users are, what exists today and what could get in the way.
You receive
- A written summary of goals, constraints and open questions
- An initial view of the right approach
Your involvement
A call, plus any documents, designs or examples you can share.
- Stage 02
Scope and proposal
Discovery becomes a written scope with milestones, assumptions and a quotation in USD.
What happens
We define what is included and what is not, list our assumptions, split the work into milestones and estimate effort. Anything uncertain is called out rather than buried.
You receive
- A proposal with scope, exclusions and milestones
- A quotation and payment schedule
- Agreement terms, including ownership
Your involvement
Review, questions and sign-off before work begins.
Development begins only after you have reviewed and approved a written scope and proposal.
- Stage 03
Design and architecture
User flows and interface designs for you to approve, plus a technical plan for how it will be built.
What happens
For user-facing work we produce flows and interface designs. In parallel we plan the data model, integrations, hosting, security and how the system will be tested and deployed.
You receive
- Wireframes or designs for approval
- An architecture outline in plain language
Your involvement
Feedback rounds on designs and confirmation of technical decisions that affect cost.
- Stage 04
Development
Built in milestones, with working demos you can click through — not just status reports.
What happens
We build milestone by milestone in a version-controlled repository, deploy progress to a staging environment and share written updates at an agreed cadence.
You receive
- Working software at each milestone
- Regular written progress updates
- Repository access as agreed
Your involvement
Milestone reviews and quick answers to questions that unblock the work.
- Stage 05
Testing and quality assurance
Functional, cross-device, accessibility and performance checks before anything reaches your users.
What happens
We test features against the agreed scope across browsers and devices, review accessibility and performance, and add automated tests where they protect critical behavior.
You receive
- A tested release candidate
- A clear list of any known issues
Your involvement
User acceptance testing and final approval for launch.
- Stage 06
Deployment and handover
We launch to production and hand over everything you need to own what we built.
What happens
Production deployment, domain and HTTPS configuration, environment secrets and a final check in the live environment, followed by a handover session.
You receive
- Your live product
- Technical and admin documentation
- Credentials and repository access per your agreement
Your involvement
Access to domains or accounts we need for launch, and a handover session.
- Stage 07
Maintenance and support
Optional ongoing care: updates, fixes and improvements under a clearly defined plan.
What happens
Dependency and security updates, monitoring, bug fixes and continued improvements — with scope, hours and response expectations written down.
You receive
- A maintenance plan with defined scope
- Regular update summaries
Your involvement
Prioritizing requests and periodic check-ins.
Throughout the project
How we keep projects on track.
Written, regular updates
Progress, decisions and open questions shared in writing at an agreed cadence — so nothing lives only in a meeting.
Demos over status reports
You see working software on a staging environment at every milestone.
Changes agreed before they happen
Every change request is assessed for scope, schedule and cost, and only proceeds with your approval.
Security throughout
Least-privilege access, secrets kept out of code, server-side validation and dependencies kept current.
Ready for the first step?
Discovery starts with a conversation. Share a few details and we will take it from there.