From PRD-Driven Context Engineering
Defines launch success criteria and tracking setup for PRD v0.9 Go-to-Market. Outputs KPI entries with funnel targets, dashboards, and alerts.
How this skill is triggered — by the user, by Claude, or both
Slash command
/prd-ce:prd-v09-launch-metricsThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Position in workflow: v0.9 GTM Strategy → **v0.9 Launch Metrics** → v0.9 Feedback Loop Setup
Position in workflow: v0.9 GTM Strategy → v0.9 Launch Metrics → v0.9 Feedback Loop Setup
Default is standard. See .claude/rules/08-skill-execution-modes.md for selection logic.
| Mode | What this skill produces |
|---|---|
| quick | 3 KPIs (one each for Reach/Acquisition/Activation); Day 7 targets; basic dashboard |
| standard | Full funnel (Reach → Referral); Day 1/7/30 targets; dashboards + alerts |
| deep | Full funnel + tier targets + Day 1/7/30/90 + product-type calibration + cohort analysis |
This skill requires prior work from v0.3-v0.9:
This skill assumes GTM- entries are complete and tracking infrastructure is configured.
This skill creates/updates:
All KPI- entries for launch are measurement specifications, not confidence-based. They are:
Example KPI- entries:
KPI-101: Website Visitors (Launch Week)
Tier: Tier 3 (Leading)
Category: Reach
Stage: Launch (v0.9)
Owner: Growth Team
Definition: Unique visitors to marketing website from all GTM- channels
Unit: count
Source: Google Analytics 4 / Plausible
Targets:
Day 1: 5,000 (from GTM-002 PH expectations + GTM-007 paid channel)
Day 7: 25,000 (cumulative from all GTM channels)
Day 30: 50,000 (post-launch momentum)
Day 90: 100,000
Evidence: CFD-025 (competitor benchmarks show 5-10% market awareness for Fast Follow), CFD-008 (our GTM reach model projects this based on channel scale)
Product Type Calibration: Fast Follow — higher reach expected due to known category
Tracking:
Dashboard: Launch Dashboard > Reach panel
Alert: <1,000 on Day 1 (channel distribution problem)
Action Thresholds:
Red: <2,500 Day 7 (channel underperformance)
Yellow: <20,000 Day 7 (80% of target)
Green: >25,000 Day 7
GTM Connection: GTM-002 (Product Hunt), GTM-007 (Website), GTM-008 (Paid ads), GTM-010 (Email)
v0.3 KPI Link: N/A (launch-specific)
---
KPI-102: Trial Signups
Tier: Tier 2 (Conversion)
Category: Acquisition
Stage: Launch (v0.9)
Owner: Product Team
Definition: Completed signup flow (email verified, profile created)
Unit: count
Source: Application database + Mixpanel
Targets:
Day 1: 500 (5-10% conversion from reach)
Day 7: 2,000 (extrapolated from Day 1 + momentum)
Day 30: 5,000 (post-launch plateau)
Day 90: 15,000 (month 3 growth)
Evidence: CFD-030 (developer SaaS benchmarks show 5-10% landing-to-signup), CFD-031 (our onboarding tested with 8% conversion)
Product Type Calibration: Fast Follow = 8-10% expected (higher than average because users understand category)
Tracking:
Event: signup_completed { source, campaign_id, user_segment }
Dashboard: Launch Dashboard > Acquisition panel
Alert: Conversion rate <5%
Action Thresholds:
Red: <100 Day 1 (messaging/channel mismatch — escalate GTM)
Yellow: <400 Day 1 (funnel friction — investigate landing page)
Green: >500 Day 1
GTM Connection: GTM-002, GTM-004 (Landing Page), GTM-005 (Email), GTM-008 (Ads)
v0.3 KPI Link: KPI-001 (Trial Signups baseline from Outcome Definition)
---
KPI-103: Activation Rate (First Value Achievement)
Tier: Tier 1 (Critical)
Category: Activation
Stage: Launch (v0.9)
Owner: Product Team
Definition: % of signups who complete first core action (generate code suggestion) within 24h
Unit: percentage
Source: Mixpanel + Application events
Targets:
Day 1: 40% (from CFD-035 developer tool benchmarks)
Day 7: 45% (slight improvement with onboarding refinement)
Day 30: 50% (post-launch optimizations)
Day 90: 55% (mature product experience)
Evidence: CFD-035 (activation benchmarks for dev tools: 30-50%), CFD-015 (our UJ-001 usability test showed 45% completed core action)
Product Type Calibration: Fast Follow = higher baseline (users already understand AI coding assists)
Tracking:
Event: first_value_achieved { user_id, action_type, time_to_value_seconds }
Dashboard: Launch Dashboard > Activation panel
Alert: Drops below 30% (onboarding broken)
Action Thresholds:
Red: <25% (product experience broken — pause marketing, investigate UJ-001)
Yellow: <35% (friction in onboarding — iterate SCR-001/002)
Green: >45% (strong PMF signal)
GTM Connection: Quality indicator for all GTM- channels (tells us if messaging matches product)
v0.3 KPI Link: KPI-002 (Activation Rate from Outcome Definition)
---
KPI-104: Day 7 Retention
Tier: Tier 1 (Critical)
Category: Retention
Stage: Launch (v0.9)
Owner: Product Team
Definition: % of Day 0 signups who return and take an action on Day 7
Unit: percentage
Source: Mixpanel cohort analysis
Targets:
Day 7: 25% (from CFD-040 B2B SaaS benchmarks)
Day 30: 20% of original (cohort retention)
Day 90: 15% of original (monthly cohort)
Evidence: CFD-040 (B2B SaaS D7 retention benchmarks 20-30%), CFD-015 (our beta test: 22% D7 retention with 50 users)
Product Type Calibration: Fast Follow = critical (users can easily switch back to competitors) — retention signal validates PMF
Tracking:
Event: session_start { user_id, cohort_day }
Dashboard: Launch Dashboard > Retention panel
Alert: Day 7 retention <15% (fundamental problem)
Action Thresholds:
Red: <15% (product-market fit issue — consider pivot in features, messaging)
Yellow: <20% (value delivery problem — investigate UJ-/feature completeness)
Green: >30% (strong retention, ready for growth)
GTM Connection: Quality indicator for all GTM- channels
v0.3 KPI Link: KPI-003 (Retention Rate from Outcome Definition)
Launch metrics are not vanity numbers—they are decision criteria. Each metric should answer: "Is this working? Should we double down or pivot?" If a metric doesn't inform action, don't track it.
| Layer | What to Measure | Timeframe |
|---|---|---|
| Reach | How many saw us | Day 0-7 |
| Acquisition | How many signed up | Day 0-30 |
| Activation | How many got value | Day 1-14 |
| Retention | How many came back | Week 2-4 |
| Revenue | How many paid | Week 2-8 |
| Referral | How many shared | Week 3+ |
Review v0.3 Outcome Definition KPIs
Define launch-specific metrics
Set targets per timeframe
Configure tracking infrastructure
Create visibility
Create/Update KPI- entries for launch
KPI-XXX: [Launch Metric Name]
Tier: [Tier 1 | Tier 2 | Tier 3]
Category: [Reach | Acquisition | Activation | Retention | Revenue | Referral]
Stage: Launch (v0.9)
Owner: [Who monitors this metric]
Definition: [Exact calculation formula]
Unit: [count | percentage | currency | ratio]
Source: [Where data comes from]
Targets:
Day 1: [target]
Day 7: [target]
Day 30: [target]
Day 90: [target]
Evidence: [CFD-XXX or benchmark that justifies targets]
Product Type Calibration: [How product type affects expectations]
Tracking:
Event: [analytics event name if applicable]
Dashboard: [Where to view this metric]
Alert: [When to get notified]
Action Thresholds:
Red: [Below this = urgent intervention]
Yellow: [Below this = investigate]
Green: [Above this = on track]
GTM Connection: [GTM-XXX channels this measures]
v0.3 KPI Link: [KPI-YYY from Outcome Definition if applicable]
Example KPI- entries:
KPI-101: Website Visitors (Launch Week)
Tier: Tier 3 (Leading)
Category: Reach
Stage: Launch (v0.9)
Owner: Growth Team
Definition: Unique visitors to marketing site
Unit: count
Source: Google Analytics / Plausible
Targets:
Day 1: 5,000
Day 7: 25,000
Day 30: 50,000
Day 90: 100,000
Evidence: CFD-025 (competitor launch benchmarks)
Product Type Calibration: Fast Follow = higher baseline expected
Tracking:
Event: page_view (landing pages)
Dashboard: Launch Dashboard > Reach panel
Alert: <1,000 on Day 1
Action Thresholds:
Red: <2,500 Day 7 (50% of target)
Yellow: <20,000 Day 7 (80% of target)
Green: >25,000 Day 7
GTM Connection: GTM-002 (Product Hunt), GTM-007 (Website)
v0.3 KPI Link: N/A (launch-specific)
KPI-102: Trial Signups
Tier: Tier 2 (Conversion)
Category: Acquisition
Stage: Launch (v0.9)
Owner: Product Team
Definition: Completed signup flow (email verified)
Unit: count
Source: Application database + Mixpanel
Targets:
Day 1: 500
Day 7: 2,000
Day 30: 5,000
Day 90: 15,000
Evidence: CFD-030 (industry signup rate benchmarks 5-10%)
Product Type Calibration: Fast Follow = 8-10% expected conversion
Tracking:
Event: signup_completed
Dashboard: Launch Dashboard > Acquisition panel
Alert: Conversion rate <5%
Action Thresholds:
Red: <100 Day 1 (messaging/channel mismatch)
Yellow: <400 Day 1 (funnel friction)
Green: >500 Day 1
GTM Connection: GTM-002, GTM-004 (Landing Page)
v0.3 KPI Link: KPI-001 (Trial Signups, general)
KPI-103: Activation Rate (First Value)
Tier: Tier 1 (Critical)
Category: Activation
Stage: Launch (v0.9)
Owner: Product Team
Definition: % of signups who complete first value action within 24h
Unit: percentage
Source: Mixpanel + Application events
First Value Action: Complete first [core action - e.g., generate code suggestion]
Targets:
Day 1: 40%
Day 7: 45%
Day 30: 50%
Day 90: 55%
Evidence: CFD-035 (activation benchmarks for dev tools 30-50%)
Product Type Calibration: Fast Follow = higher baseline (users know the category)
Tracking:
Event: first_value_achieved
Dashboard: Launch Dashboard > Activation panel
Alert: Drops below 30%
Action Thresholds:
Red: <25% (onboarding broken)
Yellow: <35% (friction points)
Green: >45%
GTM Connection: Measures effectiveness of all GTM- channels
v0.3 KPI Link: KPI-002 (Activation Rate, general)
KPI-104: Day 7 Retention
Tier: Tier 1 (Critical)
Category: Retention
Stage: Launch (v0.9)
Owner: Product Team
Definition: % of Day 0 signups who return on Day 7
Unit: percentage
Source: Mixpanel cohort analysis
Targets:
Day 7: 25%
Day 30: 20% (of Day 0)
Day 90: 15% (of Day 0)
Evidence: CFD-040 (B2B SaaS retention benchmarks)
Product Type Calibration: Fast Follow = retention critical (easy to switch back)
Tracking:
Event: session_start (Day 7 cohort)
Dashboard: Launch Dashboard > Retention panel
Alert: Day 7 retention <15%
Action Thresholds:
Red: <15% (critical product-market fit issue)
Yellow: <20% (value delivery problem)
Green: >30% (strong PMF signal)
GTM Connection: Quality indicator for all GTM- traffic
v0.3 KPI Link: KPI-003 (Retention Rate, general)
Track conversion at each stage:
REACH → ACQUISITION → ACTIVATION → RETENTION → REVENUE → REFERRAL
100% 10% 50% 25% 20% 10%
| Stage | Key Metric | Benchmark |
|---|---|---|
| Reach → Acquisition | Signup Rate | 5-15% |
| Acquisition → Activation | Activation Rate | 30-60% |
| Activation → Retention | D7 Retention | 20-40% |
| Retention → Revenue | Conversion Rate | 2-10% |
| Revenue → Referral | NPS / Referral Rate | 10-30% |
Expectations vary by product type (from v0.2 BR-):
| Product Type | Acquisition | Activation | Retention | Revenue |
|---|---|---|---|---|
| Fast Follow | High (known category) | High (familiar UX) | Medium (easy to switch) | Quick |
| Slice | Medium (niche) | High (focused value) | High (workflow fit) | Medium |
| Innovation | Low (education needed) | Low (learning curve) | High (if activated) | Slow |
| Component | Purpose | Tool Examples |
|---|---|---|
| Product Analytics | User behavior | Mixpanel, Amplitude, PostHog |
| Web Analytics | Traffic, sources | GA4, Plausible, Fathom |
| Event Tracking | Specific actions | Segment, custom events |
| Error Tracking | Failures, issues | Sentry, LogRocket |
| Session Recording | User experience | Hotjar, FullStory |
| A/B Testing | Experiments | LaunchDarkly, Statsig |
Define standard events for launch tracking:
# Acquisition Events
signup_started: { source, campaign, referrer }
signup_completed: { source, campaign, user_id }
signup_abandoned: { step, source, reason }
# Activation Events
onboarding_started: { user_id }
onboarding_step_completed: { user_id, step }
first_value_achieved: { user_id, action, time_to_value }
# Engagement Events
feature_used: { user_id, feature, context }
session_start: { user_id, day_number }
session_end: { user_id, duration }
# Conversion Events
upgrade_started: { user_id, plan }
payment_completed: { user_id, plan, amount }
┌─────────────────────────────────────────────────────────────┐
│ LAUNCH DASHBOARD Last updated: [time] │
├─────────────────────────────────────────────────────────────┤
│ REACH │ ACQUISITION │ ACTIVATION │
│ Visitors: X │ Signups: Y │ Activated: Z% │
│ Target: X │ Target: Y │ Target: Z% │
│ [trend chart] │ [trend chart] │ [trend chart] │
├─────────────────────────────────────────────────────────────┤
│ RETENTION │ REVENUE │ CHANNELS │
│ D7: X% │ MRR: $Y │ Product Hunt: X │
│ Target: X% │ Target: $Y │ Direct: Y │
│ [cohort chart] │ [revenue chart] │ [breakdown chart] │
└─────────────────────────────────────────────────────────────┘
| Pattern | Signal | Fix |
|---|---|---|
| Vanity metrics only | Tracking visitors but not activation | Focus on funnel progression |
| No targets | "We got 1000 signups!" (is that good?) | Set explicit targets per timeframe |
| Lagging only | Only tracking revenue | Add leading indicators (activation) |
| No action thresholds | Metrics exist but no response plan | Define red/yellow/green zones |
| Over-instrumentation | 200 events, can't find signal | Focus on 10-15 key events |
| No attribution | Don't know which channel works | Track source for all signups |
Before proceeding to Feedback Loop Setup:
| Consumer | What It Uses | Example |
|---|---|---|
| Feedback Loop Setup | KPI- thresholds trigger feedback collection | KPI-103 <30% → investigate with CFD- |
| Daily Standup | KPI- dashboard for launch status | "Activation at 42%, on track" |
| Pivot Decisions | KPI- data informs strategy | KPI-104 <15% → fundamental problem |
| Investor Updates | KPI- for launch performance | "Day 30: 5000 signups, 45% activated" |
| v1.0 Planning | KPI- baselines for growth targets | KPI-102 baseline → 10% MoM growth |
references/metric-examples.mdassets/kpi-launch-template.mdreferences/dashboard-design.mdreferences/event-schema.mdnpx claudepluginhub mattgierhart/prd-driven-context-engineering --plugin prd-ceSets up pre-launch tracking for product launches with UTM parameters, analytics events, baselines, and dashboards; runs post-launch retros using KPIs and benchmarks.
Sets up PostHog metrics tracking plans for iOS/web projects with event funnels, KPI benchmarks, North Star metrics, and kill/iterate/scale decision rules.
Designs product metrics dashboards with North Star metrics, input KPIs, data sources, visualizations, alert thresholds, and review cycles. Useful for KPI setup, analytics, monitoring plans.