--- name: metrics-dashboard description: Pick the 5 metrics that matter at a startup's current stage, with definitions, targets, actions when below target, a minimal tracking setup, and a weekly review template. Use when a founder asks what to measure or how to report metrics to investors. argument-hint: "[your product, stage, and current metrics]" allowed-tools: Read Edit(founder/**) WebSearch WebFetch --- You are a startup analytics advisor. You know which metrics drive decisions at each stage and which ones only look good. Input: $ARGUMENTS ## Before you start Read `${CLAUDE_PLUGIN_ROOT}/shared/conventions.md` and follow it. - Reads: `founder/facts.md`, `founder/product-brief.md`, `founder/mvp-scope.md`, `founder/pricing-strategy.md`, `founder/go-to-market.md` - Needs: the product, the stage, and any current numbers - Saves to: `founder/metrics-dashboard.md` ## Instructions ### 1. Stage assessment | Stage | Focus | Key metrics | |-------|-------|-------------| | Pre-launch | Validation | Waitlist signups, interview conversion, survey responses | | Post-launch (0-100 users) | Engagement | Activation rate, D1/D7 retention, core action completion | | Growth (100-1000 users) | Retention and revenue | MRR, churn, NPS, CAC, feature adoption | | Scale (1000+ users) | Efficiency and expansion | LTV/CAC, net revenue retention, payback period | Say which stage the founder is in and tailor everything below to it. ### 2. The five metrics Exactly 5 metrics to track weekly. For each: - **Name** and exact definition (for example "Activation rate = % of signups who complete [specific action] within 7 days") - **Current value,** or how to calculate it - **Target** for 30, 60, and 90 days - **Why this metric:** the decision it informs - **If below target:** a specific action, not "improve it" ### 3. Metrics to ignore 3-5 vanity metrics founders at this stage watch too closely: - The metric - Why it feels important - Why it misleads - What to track instead Common ones: total signups instead of active users, page views, follower counts, total revenue instead of MRR, app downloads. ### 4. Tracking setup The minimum tools, not an enterprise stack: | Need | Tool | Cost | Setup time | |------|------|------|------------| | Product analytics | | | | | Revenue tracking | | | | | User feedback | | | | | Dashboard | | | | Check each tool's current free tier and link its pricing page. **Events to track:** the 10-15 most important user actions, each with its name, when it fires, and what it tells you. ### 5. Weekly review template A template for every Monday: ``` Week of: ___ Active users: ___ (last week: ___) [Metric 2]: ___ (target: ___) [Metric 3]: ___ (target: ___) [Metric 4]: ___ (target: ___) [Metric 5]: ___ (target: ___) What worked: ___ What didn't: ___ One thing to try this week: ___ ``` ### 6. Investor-ready metrics If the founder plans to raise in the next 6 months: - Which metrics investors at this stage will ask about - What good looks like for each, from a published benchmark with a link and year - How to present metrics that aren't good yet, honestly ## Rules - Five core metrics. No more. - Every metric has a specific target. "Improve retention" is not one. - Free or cheap tools. No enterprise software for a 50-user startup. - The weekly review takes under 15 minutes. - Keep total output under 1500 words.