how we work.
The same 5 phases on every project. You approve a fixed scope before we build, see working software every two weeks, and always know what happens next.
01
Discover
1 week
We learn the problem, the users, and the constraints, then agree a fixed scope and price before any code is written.
What happens
- Kick-off workshop with your decision makers
- User and stakeholder interviews
- Review of any existing product, data, and integrations
- Technical feasibility checks on the risky parts
What you get
- Scope document with a feature list and what's out of scope
- Fixed quote and milestone plan
- Architecture outline
Your part: Two or three working sessions and access to the right people.
02
Design
1–3 weeks
Flows, screens, and architecture take shape together, so what looks right is also buildable.
What happens
- User flows and wireframes for every key journey
- Clickable prototype tested with real users
- High-fidelity UI and a component design system
- Data model and API design
What you get
- Approved Figma designs for every screen and state
- Clickable prototype
- Technical design document
Your part: Feedback on each design round within a couple of days.
03
Build
3–16 weeks
We ship in two-week cycles with a working demo at the end of each one. No black boxes, no months of silence.
What happens
- Two-week sprints against the agreed milestone plan
- Code review and automated tests on every change
- A staging environment you can click through any time
- Weekly written update and a live demo every sprint
What you get
- Working software at the end of every sprint
- Shared delivery board with live status
- Test suite and CI pipeline
Your part: A 30-minute demo every two weeks and quick answers on open questions.
04
Launch
1–2 weeks
We harden, test, and release, with monitoring in place from the first minute in production.
What happens
- Full regression and performance testing
- Security review and dependency audit
- Production setup, data migration, and go-live
What you get
- Live product with monitoring and alerts
- Runbooks and admin documentation
- Recorded hand-off walkthrough
Your part: Final acceptance testing and the go-live decision.
05
Support & grow
Ongoing
After launch we stay on for fixes, improvements, and the next set of features, or hand over cleanly to your team.
What happens
- 30 days of included post-launch fixes
- Monthly retainer for new features and maintenance
- Usage review to decide what to build next
- Knowledge transfer if you're building an in-house team
What you get
- Agreed response times for production issues
- Monthly report on uptime, usage, and changes
Your part: Tell us what your users are asking for.
ways to work together.
Pick the shape that fits. We'll recommend one on the discovery call and quote it in writing.
New products and well-defined builds
Fixed-scope project
We agree exactly what gets built, by when, and for how much. You pay by milestone, and the price doesn't move unless the scope does.
- Fixed price, paid per milestone
- Scope locked after discovery
- Changes quoted before they're made
Products with a long roadmap
Dedicated team
A stable team of designers and engineers works on your product full time, alongside your own people, in your tools.
- Monthly rate per team member
- Scale up or down with a month's notice
- Same people, sprint after sprint
Live products that need steady care
Monthly retainer
A set number of hours each month for maintenance, improvements, and production support, with agreed response times.
- Fixed monthly hours
- Priority response for production issues
- Unused hours roll over one month
Phase one starts with a 30-minute call.
Book a free call