A predictable path,
from kickoff to handoff.
Four phases. Fixed scope per phase. Weekly cadence. No Jira ceremonies, no 80-page discovery decks, no surprise invoices.
Four phases.
One predictable cadence.
Frame
3–5 stakeholder interviews, a technical audit of what exists, and a one-page brief. No 80-slide discovery decks.
- Engagement brief
- Architecture sketch
- Slack + Linear access
Build
Working code in week 2, not week 12. Two-week sprints, Friday demos, preview URLs on every PR. Slack + Linear, no Jira ceremonies.
- Live prototype
- Linear board access
- Design tokens + system
Launch
Staged rollout with metrics gates and a one-click rollback. We cover on-call for the first week in production.
- Production deploy
- Incident runbook
- SLO dashboards
Care
Thirty days of hypercare — bug fixes, pair sessions with your engineers, and a full code walkthrough. Then we step back.
- Trained team
- Full repo ownership
- Zero lock-in
What happens,
week by week.
Typical 8-week engagement. Longer engagements extend the Iterate phase — everything else stays fixed.
What we use
to run the work.
Engagement
questions.
What if scope changes mid-engagement?
We flag it in the weekly demo. If the change is small, we absorb it. If it's significant, we issue a one-page change order with a revised price and timeline. No surprise invoices.
How do you handle fixed price + uncertain scope?
We price by phase, not by feature. Phase 1 (Frame) has a fixed price. Phases 2–4 are priced at the end of Phase 1, when scope is concrete. You never commit to a price for work that isn't yet defined.
Do we own the IP?
Yes. All work-product is yours from day one. Your repo, your accounts, your domain. We retain rights to nothing except the right to list the engagement in our portfolio.
What if we want to extend an engagement?
Common. We re-scope at the end of Care and sign a follow-on if both sides want it. No auto-renewals, no lock-ins.