How we work
Four phases. One accountable team.
Same team from discovery through launch — no handoffs, no "throw it over the wall." Here's how a typical engagement unfolds.
Phase 01
Discovery
1–2 weeks
Understand the problem before designing the solution.
We start with people, not pixels. We interview your team and customers, audit the current state, and pressure-test the assumptions in your brief. By the end you have a one-page strategy doc — the problem, the bet, the success metric — that everyone signs off on before we touch a Figma file.
Deliverables
- User & stakeholder interviews
- Existing-state audit (UX, performance, code)
- Strategy brief — problem, hypothesis, success metric
- Project plan and budget envelope
What to expect
We need ~6 hours of your team's time. You'll get clarity on what's worth building.
Phase 02
Design
2–4 weeks
Make the solution visible, testable, and unambiguous.
Designers and engineers pair from day one. We move from low-fidelity flows to a clickable prototype, validating with real users in week two. Visual design and the design system land together so engineering can start in parallel by the end of week three.
Deliverables
- Information architecture & flow diagrams
- Clickable prototype (Figma) tested with 5+ users
- Visual design system & token library
- Design-to-dev handoff specs
What to expect
Weekly review sessions. Early decisions cost nothing — late decisions cost weeks.
Phase 03
Build
6–14 weeks
Ship working software in increments, not big-bang reveals.
We work in two-week sprints with a deployed staging build at the end of every one. You see progress weekly. Engineering, QA, and design review happen continuously — bugs caught in the same week they appear, not the same month. We instrument from day one so launch isn't a leap of faith.
Deliverables
- Production-grade codebase, source-code transferred to you
- CI/CD pipelines, observability, error tracking
- Test coverage on critical paths
- Documentation for your engineering team
What to expect
Weekly demos. Async standups. We work to your team's hours and rituals where it makes sense.
Phase 04
Ship
1–2 weeks + ongoing
Launch carefully, then transfer ownership cleanly.
Launches happen in stages — staging, canary, full rollout — with rollback rehearsed. We stay paired with your team for two weeks of post-launch support, watching the metrics, fixing what breaks, and writing the runbooks. After that you own it; we're a phone call away.
Deliverables
- Phased production rollout with rollback plan
- Operational runbooks and on-call docs
- Post-launch metrics review (week 1 and week 4)
- Knowledge-transfer session with your team
What to expect
Two weeks of close support, then optional retainer. No lock-in — your code, your infra, your call.
Next step
Ready to start your project?
A 30-minute call is enough to know if we're the right fit.