Create a Weekly KPI Dashboard Report

Build a weekly KPI dashboard report template for [product name], a [one-sentence product description] at [stage, e.g. "pre-seed with 200 users" or "Series A with $30K MRR"]. This report will be generated every Monday and shared with [audience, e.g. "the founding team" or "investors and advisors"].

The report should have these sections:

**1. Snapshot header**
A single-line summary of the week: "[Week of MM/DD] — [one sentence takeaway, e.g. 'Signups up 18%, churn stable, NPS trending down']"

**2. North Star metric**
- Metric name: [your north star, e.g. "weekly active users" or "transactions processed"]
- This week's value: [X]
- Last week's value: [Y]
- % change: calculated automatically
- 4-week trend: show as a simple spark line or arrow indicators (up/down/flat)
- One sentence explaining the movement

**3. Growth metrics table**
Create a table with these rows (customize as needed):
| Metric | This week | Last week | % Change | 4-week avg | Status |
- New signups
- Activation rate (% who complete [key action] within 48 hours)
- Free-to-paid conversion rate
- MRR (monthly recurring revenue)
- Net revenue retention

Status column should use: [on-track], [watch], or [action-needed] based on whether the metric is above, near, or below target.

**4. Engagement metrics**
- DAU/WAU ratio
- Average session duration
- Feature adoption: top 3 features used this week + any features with declining usage
- Support ticket volume and median response time

**5. Churn & retention**
- Customers lost this week (count + MRR impact)
- Top 2 churn reasons (from exit surveys or support tickets)
- Customers at risk: list accounts with declining usage or open complaints
- One specific action item to reduce churn this week

**6. Wins & lowlights**
- 3 wins from the week (new customers, milestones, positive feedback)
- 2 lowlights or risks (honest assessment, not sugarcoated)

**7. Next week focus**
- Top 3 priorities for the coming week
- Any experiments launching
- Key meetings or deadlines

Formatting rules:
- Use color coding: green for on-track, yellow for watch, red for action-needed
- Keep the entire report to one page when printed or screenshotted
- Write commentary in plain English — no jargon, no filler
- Every metric should have a "so what" — a one-line interpretation
- Include [data-source] placeholders where numbers should be pulled from analytics tools