Run Your First 90 Days Post-Launch
The 90 days after launch is where most products either compound into a real business or quietly fade. Founders walk into this window exhausted from launch, drift into reactive ticket-clearing for two weeks, then spend the next 75 days vaguely "doing growth" without a structured plan. Three months later they have ten more customers, no clear signal on what worked, and no system to compound.
The version that works is structured. Three distinct phases (Foundation, Acceleration, Compounding), each with a single primary metric, each with concrete weekly rituals. By Day 90 you should know what's working, what's not, and what the next quarter looks like — not be guessing.
Why the 90-Day Window Specifically
Three reasons 90 days is the right unit:
- Long enough to see compounding. SEO traffic, newsletter audience, referrals, organic word-of-mouth — none compound visibly in 30 days. By 90 days, the early signal emerges.
- Short enough to course-correct. A bad strategy detected at month 3 costs you 90 days; the same strategy detected at month 6 costs 180. The 90-day cadence catches problems early.
- Long enough to test channels honestly. A single 30-day test of any channel is too noisy. 90 days lets each channel run through 2-3 iteration cycles.
The honest counter: founders are tired post-launch and want to coast. The 90-day plan is exactly the structure to push past that.
This guide pairs with Post-Launch Week 1 Review (the immediate post-launch window), Find Your First 10 Paying Customers (you may still be doing this in days 1-30), Channel Selection Framework (the 30-day channel tests live inside this 90-day plan), and Reduce Churn (retention work intensifies in days 30-90).
The Three Phases
The 90 days breaks into three distinct phases. Each has different priorities, different metrics, different rituals.
Phase 1: Foundation (Days 1-30)
Primary metric: paying customers + activation rate of new signups Goal: get to your first 50-100 paying customers and instrumented activation funnel
The first 30 days post-launch is where you finalize the muscle memory of customer-led growth. Every signup is high-attention; every customer interaction informs the next product / pricing / messaging change.
Critical rituals:
- Personal contact with every paying customer in the first 14 days — per Founder-Led Onboarding Calls, Tier 1 / Tier 2 calls fire here
- Daily customer support — founder responds to every ticket personally; this is research as much as service
- Activation funnel instrumentation — per Activation Funnel Diagnosis, wire the events and measure
- Pricing and packaging final tune — react quickly to early signals about willingness-to-pay
What NOT to do in Phase 1:
- Run paid ads — too early; messaging isn't fully validated yet
- Hire your first sales / CS person — you need the founder customer-research time
- Build major new features — finish what you launched; iterate based on real feedback
- Ignore support — every ticket is a signal; respond personally
Phase 2: Acceleration (Days 31-60)
Primary metric: paid signups per week (week-over-week) Goal: identify your winning channel(s) and double down
Days 31-60 is when channel tests produce signal. Per Channel Selection Framework, you should be running 3 channels in your bullseye; by day 60 you'll know which one(s) are converting.
Critical rituals:
- Run your bullseye channels — 3 channels, 30-day test, kill criteria explicit
- Weekly conversion / activation review — per PostHog Setup, spot trends in cohort retention
- First content push — if SEO/AEO is your inbound channel, ship 5-10 cornerstone articles in this window
- First reference assets — per Customer Reference Program, get 3-5 testimonials and 1-2 case studies from Phase 1 customers
- First Founder Newsletter issues — if newsletter is your channel; weekly cadence locked in
What NOT to do in Phase 2:
- Keep all 3 channels running indefinitely if 2 aren't converting — kill ruthlessly per channel-selection criteria
- Avoid adding founder-personal time on the winners — Phase 2 is when you DOUBLE DOWN on what works
- Wait for "everything to be ready" before publishing — ship cornerstone content even when imperfect; iterate
Phase 3: Compounding (Days 61-90)
Primary metric: ARR / MRR + organic-traffic growth + retention curve Goal: turn the winning channel into a flywheel; instrument the next 90 days
Days 61-90 is where the work shifts from doing the work to systematizing it. The channel that's working in Phase 2 needs to keep working without burning the founder out.
Critical rituals:
- Document the playbook for the winning channel — exactly what's working, exactly how to repeat, even if delegated
- First quarterly retro (at day 90) — what worked, what didn't, what's the next 90-day plan
- Pricing review — per Raise Prices, the first pricing-tune signal usually emerges by day 60-90
- First retention measurement — per Reduce Churn, your earliest cohorts are now 60 days in; their retention shape is the leading indicator for everything
- First product roadmap based on real customer signal — by day 90 you have enough data to build the right things instead of guessing
What NOT to do in Phase 3:
- Quit running winning channels because "they're tired" — they're working; keep going
- Add new channels before mastering the current one — depth beats breadth at this stage
- Ignore the 90-day retention data — it's the leading indicator for product-market fit
The Daily / Weekly / Monthly Cadence
Through all 90 days, the operating cadence stays consistent.
Build my 90-day operating cadence.
**Daily (~30 min)**:
- Check support inbox; respond to anything fresh personally
- Quick metrics scan: signups today, payments today, any churn?
- One customer message proactively — onboarding follow-up, casual check-in, etc.
**Weekly (~2 hours, dedicated block)**:
- Friday afternoon review: pull the week's metrics
- Signups this week vs last
- Activation rate cohort
- Paid customers added vs lost
- Top 3 customer-conversation themes (what did 5+ customers mention?)
- Plan the next week:
- One channel push to focus on
- One product change to ship
- One content piece / customer call to schedule
- Update [Founder Newsletter](../2-content/founder-newsletter.md) and [Building in Public](../3-distribute/building-in-public.md) — weekly cadence
**Monthly (~4 hours, dedicated block)**:
- 30-day retro: what worked, what didn't, what's the highest-leverage thing to add / cut
- Pricing review (per [Raise Prices](../4-convert/raise-prices.md)): are signals showing pricing is right? wrong?
- Channel kill / amplify decisions per [Channel Selection Framework](../3-distribute/channel-selection.md)
- Update product roadmap based on the month's customer feedback
- Share the monthly retro publicly — it's both content and accountability
**Day 90 (1 day, dedicated)**:
- Full quarterly retro
- Plan the next 90 days
Output: my recurring calendar template + the metric tracking sheet
The discipline that separates productive 90-day windows from drifting ones: the calendar block is non-negotiable. The founder who blocks Friday 2-4pm for the weekly review every week ships 90 days of compound progress. The founder who "does it when there's time" ships scattered output.
What to Track (and What Not To)
Most founders track too much in the 90-day window and obscure the signal. The right tracking is narrow.
Build my 90-day metric tracking sheet.
The metrics that matter:
1. **MRR / ARR per week** — the signal that compounds matter
2. **Paid signups per week** — the leading indicator
3. **Trial-to-paid conversion** (or free-to-paid) — segmented by acquisition channel
4. **Activation rate per cohort** — per [Activation Funnel](../../../VibeWeek/6-grow/activation-funnel-chat.md)
5. **30-day retention** — the leading indicator for product-market fit
6. **Top 3 acquisition channels** — sources of paid customers
7. **Top 3 customer-conversation themes** — what did 5+ customers tell me this week?
8. **Founder hours by category** — support / customer calls / shipping / marketing
The metrics that DON'T matter (much):
- **Total signups** — meaningless without conversion
- **Total page views** — meaningless without channel-source attribution
- **Twitter / LinkedIn engagement** — vanity unless it's converting
- **Number of feature flags shipped** — sometimes shipping is dilutive
- **Time logged on product** — quality of work matters; quantity rarely
Updates per cadence:
- Daily: just the leading indicators (signups, payments, churn) — 5 minutes
- Weekly: the full metric set — 30 minutes during Friday review
- Monthly: trends + decisions
For my product:
- The exact metric definitions (what counts as "activated"? what counts as "paid"?)
- The data sources (PostHog / Stripe / DB / spreadsheet)
- The dashboard tool (PostHog dashboards, a Notion sheet, simple Google Sheet — anything queryable)
- The Friday review template
The "founder hours by category" metric is the most-overlooked. Founders who don't track time end up with the same complaint at day 60: "I spent the whole 60 days on support and never shipped anything." Tracking forces the visibility; visibility forces the rebalancing.
The Specific Rituals That Compound
Beyond the cadence, four specific rituals consistently differentiate productive 90-day windows from chaotic ones.
Build the four compounding rituals.
**Ritual 1: Customer Quote Database**
After every customer call, support ticket, or significant email exchange, capture:
- 3 verbatim quotes
- Tag by theme (problem they have / outcome they want / objection / praise)
- Source: customer name, date, context
By day 90, this database has 100-200 quotes — invaluable input for landing-page copy, pricing-page testimonials, sales decks, ad copy, customer-discovery synthesis. Per [Customer Discovery Interviews](../1-position/customer-discovery-interviews.md), this is the same muscle.
**Ritual 2: Public Building-in-Public Posts**
Per [Building in Public](../3-distribute/building-in-public.md), weekly cadence locked in. By day 90 you've published 12 posts, each with metrics + lessons. Compounding distribution asset.
The discipline: same day every week, no exceptions. If sick / traveling, ship a 200-word "personal note" version.
**Ritual 3: Public Changelog Updates**
Per [Public Changelog and Roadmap](../../../VibeWeek/6-grow/changelog-roadmap-chat.md), weekly. Even small changes count. The cadence signal compounds — visitors who see weekly updates trust the project more than visitors who see one entry from 6 weeks ago.
**Ritual 4: Customer Spotlight Posts**
Once per month: a featured customer story (per [Customer References](../4-convert/customer-references.md)). Done early in the 90 days, your first customer spotlights are also reference assets and double as marketing content.
For my product:
- The customer-quote database template
- The building-in-public schedule
- The changelog publishing flow
- The customer-spotlight cadence + first 3 candidate customers
Output: the rituals checklist + the calendar blocks
The customer-quote database is the most-skipped ritual and the highest-leverage. Founders who don't capture quotes write generic landing-page copy from imagination; founders who do capture quotes write copy that quotes their actual buyers back at them — converting at meaningfully higher rates.
When Things Aren't Working: The Pivot Decision
Not every product reaches Day 90 with a clear path forward. The honest 90-day window includes a "pivot or persevere" decision.
At Day 60, run the pivot-or-persevere check:
**Persevere signals** (good news, keep going):
- Paid signups growing week-over-week
- 30-day retention above 60%
- Customers spontaneously refer others
- Multiple specific customer quotes about the product's unique value
**Pivot signals** (consider major change):
- Paid signups flat or declining over 4+ weeks
- 30-day retention below 30%
- Customers can't articulate why they pay
- Multiple customer interviews surface the same fundamental gap
**Hard pivot patterns** (when the math says go):
1. **Pivot the customer**: same product, different ICP. The product works; the audience is wrong.
2. **Pivot the wedge**: same audience, different problem to solve first. The audience is right; the entry point is wrong.
3. **Pivot the pricing model**: same product, same audience, restructured pricing. The product is right; the way to capture value is wrong.
4. **Pivot the entire thing**: rare, expensive, sometimes correct. Reserved for "we've spent 90 days proving the original assumption was wrong."
How to decide:
- Don't pivot at day 30 — too early, signal is too noisy
- Don't pivot at day 60 — borderline; do another 30 days first if uncertain
- DO consider pivot at day 90 — this is the right cadence for major direction changes
- After pivot: restart the 90-day clock; the new direction needs the same rigorous foundation phase
Anti-patterns:
- Pivoting because of one bad week
- Persevering because the founder is emotionally attached to the original idea
- Pivoting to "follow what works for someone else" instead of from real customer signal
- Telling yourself "we just need more time" when the metrics say otherwise
For my product, output:
- The decision criteria for Day 90
- The "pivot or persevere" memo template (write at Day 90 regardless of decision)
- The communication plan if pivoting (employees / customers / investors)
The "write the memo regardless" discipline is the move that produces clearer thinking. Even if you persevere, writing why forces you to articulate the bet you're making for the next 90 days.
The Day 90 Quarterly Retro
The Day 90 retro is the most important meeting of the first quarter. It's where the next 90 days gets planned.
Build the Day 90 quarterly retro.
The 4-section structure:
**Section 1: What happened**
- Final metrics: ARR, paid customers, activation rate, retention, top channels
- Compare against Day 0 / Day 30 / Day 60 expectations
- Identify the surprises (positive and negative) — what did I not see coming?
**Section 2: What worked**
- Top 3 things that produced outsized impact
- Why did they work? What was the underlying mechanism?
- Are they repeatable? What would 10× them look like?
**Section 3: What didn't work**
- Top 3 things that failed expectations
- Why did they fail? Was it execution, or was the strategy wrong?
- What would I do differently?
**Section 4: Next 90 days**
- Primary metric for next quarter (one number)
- Secondary metrics (max 3)
- The 3 things I'll focus on
- The 3 things I'll explicitly NOT do
- Resource allocation: how does my time split?
The retro is a written document, not a meeting. Write it (60-90 minutes), share publicly (per [Building in Public](../3-distribute/building-in-public.md)), reference it weekly during the next 90 days.
For my product, output:
- The retro template
- The first published version after Day 90
- The calendar block for Day 90 (4 hours, no interruptions)
The "publish the retro publicly" move is the move that compounds. Public retros build founder credibility, attract talent and customers, and force you to write more honestly than a private retro would. It's the highest-leverage piece of content in the 90-day window.
Common Failure Modes
"Day 60 and I have no idea what's working." Probably tracking too much / wrong things. Cut to the 8 metrics in the tracking section; commit to the weekly review block.
"I'm spending all my time on support." Section 1 expected this for Phase 1 (Days 1-30). If still in Phase 2 (31-60), tighten support per Customer Support and use the saved time on growth.
"I burned out at Day 45." Cadence too aggressive or no rest blocks. Add explicit downtime; remember the 90 days is a sustainable cadence, not a sprint.
"I shipped 12 features in 90 days but no growth in customers." Building over selling. Days 31-60 should be channel work, not feature work. Re-balance.
"Customers love the product but I'm not getting referrals." Per Referral Program, the referral mechanism may need explicit asks and incentives. Don't assume happy customers refer — many won't unless prompted.
"I'm at Day 90 with $500 MRR and unsure if I should pivot." Probably need another 90 days; the early stage signal is real but $500 MRR is too early for the pivot decision. Run another foundation-phase cycle with sharper instrumentation.
"My weekly review hasn't happened in 4 weeks." Calendar discipline broke. Re-instate; the review IS the work — without it, the 90 days drifts.
Related Reading
- Post-Launch Week 1 Review — the immediate post-launch window before Phase 1 starts
- Find Your First 10 Paying Customers — Phase 1 work
- Channel Selection Framework — Phase 2 channel selection lives here
- Founder-Led Onboarding Calls — Phase 1 call cadence
- Customer Reference Program — Phase 2 reference asset capture
- Reduce Churn — Phase 3 retention measurement
- Raise Prices — Phase 3 pricing review
- Building in Public — weekly cadence throughout 90 days
- Founder Newsletter — weekly cadence throughout 90 days
- PostHog Setup — the analytics layer feeding the metrics
- Public Changelog — weekly publishing throughout 90 days