Playbook
Idea to Launched Product in 90 Days
Ninety days is enough to launch a real product if the scope is honest and the team is senior. This is the model we use: two weeks to decide what to build, ten to build it, and one to put it live, with quality and evidence built in rather than deferred.
- Two weeks to a plan
- Ten weeks to build
- One week to launch
90 days
Idea to a launched, validated version one
Weekly
Real software in your hands, every Friday
Day 91
Your team can run it without us
The plan
How the 90 days break down
Days 1 to 14: discovery and scope
Define the one thing v1 proves, the users it serves, and the smallest build that does it. Design the core flows.
Days 15 to 75: build
A cross-functional squad shipping weekly, with your team reviewing real software every Friday.
Days 76 to 84: harden
Load testing, accessibility, security review, and the observability to run it.
Days 85 to 90: launch
Phased rollout behind a flag, monitoring in place, and a plan for the first week of feedback.
Why it works
What we do not cut
Tests and CI
A safety net from day one, so the last two weeks are hardening, not firefighting.
Accessibility
Designed in, not audited at the end when it is expensive to fix.
Observability
In place before launch, so the first incident is diagnosable.
A clean handover
Docs and a runbook, so your team can take it forward on day 91.
FAQ
90-Day Launch FAQ
Is 90 days realistic for our product?
For a focused v1 that proves one thing, usually yes. For a platform replacement or a regulated core, no, and we will say so. The first conversation is about whether the scope fits the time.
What size team does this need?
Typically a lead, two to three engineers, a designer and a part-time product strategist. Small and senior beats large and mixed for this kind of work.
What happens after 90 days?
Either we keep going as an embedded team on the roadmap the launch reveals, or we hand over and your team takes it. Both are planned for from the start.
Have 90 days and a product to launch?
Tell us what you're working on. We come back within two business days with a point of view and next steps.