The 10‑Metric Launch Dashboard: Exact KPIs, Formulas & a Google Sheet Template Founders Should Ship with Every Launch Brief

These are the ten metrics every founder should track on launch day and keep monitoring for the first 30 days. Each metric includes the precise formula you can paste into a Google Sheet and an opinionated SLO (service‑level objective) to judge success or signal triage.

Pick the exact definitions you will use ahead of time (e.g., what counts as an ‘activation’). In production, use event names that your analytics system supports (GA4 'event' / Mixpanel 'event') so numbers align. The formulas below assume event-level counts and standard payment reporting (Stripe/processor) for revenue metrics.

3) Signup → Activation Rate (activation %): your single product activation event is the most important early filter. Formula: (users who fired activation_event / total new signups) × 100. SLO: ≥ 40% in the first 48 hours for strong onboarding flows.

4) Median Time‑to‑Activation (hours): median of (timestamp_activation − timestamp_signup) for new users. SLO: < 24 hours for self‑serve; < 72 hours for product with setup steps.

5) Day‑1 Retention (cohort retention %): for cohort C (users who signed up on day X), Day‑1 retention = (users from C who return on day X+1 / size of C) × 100. SLO: ≥ 25% (consumer) or ≥ 40% (sticky B2B features). Retention calculations and cohort tools are available in product analytics platforms. (mixpanel.com)

6) Day‑7 Retention: same formula for day+7. SLO: relative to Day‑1 — target Day‑7 ≥ 40% of Day‑1 value.

7) Free → Paid Conversion Rate (trial or freemium conversion): (new paying customers during period / new signups during period) × 100. SLO: 2–5% first 30 days for freemium; 10%+ for high‑intent trials (benchmarks vary by model).

8) New MRR (daily normalized) — for subscription launches you want revenue visibility from day 0: New_MRR_day = sum(monthly_equivalent_value of new subscriptions activated that day). Use your billing system to normalize intervals. SLO: positive New MRR every day during launch week; net MRR growth week‑over‑week. Stripe’s guidance on MRR components (new, expansion, churn) is useful when building these calculations. (stripe.com)

9) CAC (customer acquisition cost): CAC = (Total Marketing + Sales spend for period) / New Paying Customers in that period. SLO: CAC payback < 12 months for seed‑stage SaaS; shorter is better.

10) LTV and LTV:CAC ratio: LTV (simple) = ARPU / Monthly Churn Rate (where ARPU = revenue in period / active customers in period). LTV:CAC = LTV / CAC. SLO: target LTV:CAC ≥ 3 for scalable models (interpret cautiously for very early launches).

Week‑zero is where launches win or fail. Instrument the 10 metrics before you go live so every metric is populated from minute one. Minimal week‑zero checklist:

1) Events & conversions: implement and test the following GA4 or product events: page_view, session_start, signup, activation_event, trial_start, subscription_created, purchase, error/crash. Mark signup and activation_event as conversions in GA4 so conversion columns populate. Use Google Tag Manager or your app backend to fire the events. (support.google.com)

Create simple alert rules that map to the SLOs above so the team knows what to triage immediately. Alerts should be binary and low‑noise (only fire when human action may be required). Example rules:

1) Conversion drop: Session→Signup Conversion Rate drops > 30% vs prior 24h and traffic is within ±15% of yesterday → page/form error triage.

2) Activation collapse: Signup→Activation Rate drops > 30% for today vs 7‑day average → check backend job queues, feature flags, onboarding flows.

3) Payment failures: Daily payment success rate < 98% → check webhook failures, payment processor status, retry queues.