First release
14d
for a scoped MVP with a signed backlog
Product launchMVP, CI/CD, analytics & go-live
From idea to live.
A first version in market, with the pipeline, analytics and runbook to keep shipping after day one.
Go-live window
3 days
rehearsed cutover
Analytics
Day 1
100%
of the launch checklist signed
Launch readiness
CIGreen
QAPassed
OBSLive
Why it matters
Built to ship, then keep shipping.
14d
To a first release
A scoped MVP with the one workflow that proves the product, not a tour of every idea.
Day 1
Analytics on
The events that tell you if anyone finished the job, wired before launch.
3 days
Rehearsed go-live
A runbook, a rollback and a window you have already practised.
Weekly
After launch
The next slice is already in the backlog when the first version goes out.
What we build
Everything a launch needs.
The unglamorous work that decides whether day one is a launch or an incident.
01
MVP scoping
The smallest version that tests the bet, written down and signed before we build.
02
CI/CD
A pipeline that builds, tests and deploys without a hero at a laptop.
03
Analytics
Funnels and the few events that answer whether the product is working.
04
QA & polish
The paths a real user takes, including the ones that fail.
05
Go-live runbook
Who does what, in what order, and how we roll back.
06
Launch support
Someone watching the release, not a handover email and silence.
How a launch runs
Five steps. Then it is live.
A tight MVP can be in market in a few weeks. Larger products use the same sequence, with longer build weeks.
Book a discovery callBet & scope
Week 1The one outcome the launch has to prove, and everything that can wait.
Design the slice
Week 1–2The screens and states for that outcome, nothing else.
Build
Weeks 2–4The slice, on a pipeline, with a demo at the end of each week.
QA & rehearse
Final daysTest the paths, rehearse the cutover, write the rollback.
Launch
Go-liveShip, watch the numbers, and start the next slice.
The launch stack
Product
- Next.js
- React Native
- TypeScript
- Figma
Pipeline
- GitHub Actions
- Vercel
- Fastlane
- Preview deploys
Insight
- PostHog
- GA4
- Sentry
- Uptime
Release
- Feature flags
- Runbooks
- Rollback
- Status page
Related work
Products we've launched.
Launch FAQ
Launch questions, answered.
What counts as an MVP?
The smallest release that lets a real user finish the core job. Everything else is a later slice, written into the backlog before we start.
Do you stay after go-live?
Yes. Launch includes a watched release window, and most teams keep us on a support or build retainer afterwards.
Can you launch something we already started?
Yes. We audit what exists, keep what is sound, and put a pipeline and a date around the rest.
How do you decide what to cut?
Against the one outcome the launch has to prove. If a feature does not change that outcome, it waits.