From kickoff to shipped,
in fewer steps than
you'd expect.
Five phases, two-week sprints, no surprises. We trade ceremony for visibility, and we'd rather over-communicate than over-promise.
Five phases. No mystery.
Phase 01
01
Discovery
1 week · fixed-bid
We sit with you (in person, on calls, in your repo) to map the problem. You leave the week with a written brief, a rough architecture, and a fixed-bid range for the build.
- Stakeholder interviews and product walkthroughs
- Technical due diligence on existing systems
- Written brief with scope, risks, and assumptions
- Estimate range and recommended engagement model
- Everything from discovery is yours to keep, build with us or not
Phase 02
02
Scoping & architecture
1–2 weeks
We write the statement of work, what is in, what is out, what the timeline looks like, what could go wrong. You approve it before we touch any code.
- Statement of work with milestones
- Architecture diagrams and ADRs
- Sprint plan and risk register
- Signed contract before engineering starts
Phase 03
03
Build
2-week sprints
Two-week sprints, demos every Friday, code in your repo from day one. You have visibility into commits, decisions, and progress the whole way through.
- Two-week sprints with written demos
- Direct Slack / Linear / Jira access
- Weekly written progress notes
- Every PR reviewed by a second senior engineer
Phase 04
04
QA & handoff
1–2 weeks
Manual QA on real devices, automated checks in CI, documentation that someone actually reads. We walk your team through the code before we leave.
- Manual QA on real environments
- Automated tests for critical paths
- Runbook, architecture doc, and ADR archive
- Live handoff sessions with your engineers
Phase 05
05
Post-launch
Optional
You can hand it off cleanly or keep us around. Retainers cover bug-fix capacity, OS / SDK updates, and ongoing iteration without renegotiating contracts.
- Optional 30-day stabilization retainer
- Ongoing retainer for new features
- Knowledge-transfer week if you take it over
- No vendor lock-in, ever
Three ways to work with us.
Pick the engagement that matches your stage. We have shipped under all three.
Best for defined builds
Fixed-scope project
Defined deliverables, a fixed price, a clear finish line. Best when you know what you want built.
- From ~$25k
- Statement of work
- Milestone billing
- Hand-off included
Best for evolving products
Monthly retainer
Ongoing engineering capacity with flexible scope. Best for evolving products and steady throughput.
- From one engineer-month
- Reserved capacity
- Rolling priorities
- Two weeks' notice
Best for fast scale-up
Embedded team
Engineers integrated into your stand-ups, your repo, your roadmap. Best when you need to scale fast.
- 3-month minimum
- Senior engineers only
- Your tools, our discipline
The four that people ask about.
- Kill clause
Any sprint boundary, two weeks' notice
Stop the engagement whenever it stops earning. You keep everything shipped, documented, and running.
- Code ownership
Yours, from commit one
Your repo, your branches, your reviews. Nothing is staged in a private GitHub and handed over later.
- Review policy
Every PR, a second senior engineer
CI catches the easy failures. A human catches the ones that page you at 3am.
- Estimates
Ranges, with named risks
We give a range rather than a point estimate, and we say which parts are hard before you sign.
Have a project?
Tell us about it. We respond within one business day. No demo decks, no discovery surveys, just a real conversation with engineers.