Skip to content
PLAYBOOK10 min

The Post-Launch 90-Day Playbook

The early post-launch period is both valuable and fragile. Here's the week-by-week playbook, including the recovery pattern for when cohort one disappoints.

// contents
  1. 01.Week 1: instrument, don't optimise
  2. 02.Weeks 2–4: earn category signal
  3. 03.Weeks 5–8: first optimisation loop
  4. 04.Weeks 9–12: compound or diagnose
  5. 05.Recovery pattern
01

Week 1: instrument, don't optimise

Do not test anything in week one. Instrument the funnel end to end. Confirm attribution. Establish the baseline. Anything you 'optimise' in week one is superstition, because you have no baseline to compare against.

02

Weeks 2–4: earn category signal

Publish the launch. Prompt reviews from the initial cohort. Respond to every review. Ship the first metadata refresh with the vocabulary you've learned from real reviews. Do not test yet, the category algorithm is still learning who you are.

03

Weeks 5–8: first optimisation loop

Screenshot test (one variable). CPP for the strongest paid channel. Icon variant if D1 install-through-rate is below your category benchmark. Publish week-eight report with cohort-one performance versus benchmark.

04

Weeks 9–12: compound or diagnose

If cohort one is above benchmark: double down on the winning motion. If below: diagnose, is it a product problem (retention), a promise problem (screenshots), or a category-fit problem (category selection)? Each has a different fix.

05

Recovery pattern

Below-benchmark launches can recover with the right diagnosis. Avoid changing everything at once because that destroys attribution; sequence changes so each learning remains legible.

// next step

Want this applied to your app?

Request a free app audit
// ready to ship this?

Get an audit that lands actions, not slides.

Request a free app audit