Tools · Marketing
Metrics Dashboard
Describe your business — get a north-star, funnel metrics, and a KPI tree.
How it works
Corpus-grounded (funnel/AARRR, north-star, KPI trees via the marketing cluster). Picks the north-star metric, the few funnel metrics per stage, a KPI tree (each KPI → definition → the drivers you can move), guardrail metrics, and a reporting cadence — the few metrics that drive decisions, not a dashboard of everything.
You bring
{ context, cluster? }
You get
{ context_summary, north_star, funnel_metrics[]{stage, metrics[]}, kpi_tree[]{kpi, definition, drivers[]}, guardrail_metrics[], reporting_cadence, riskiest_assumptions[], grounded_in, provenance }
Use it for
- →Marketing-guide reader: define the north-star + the KPI tree under it
- →Get funnel metrics by stage with guardrails
- →Replace a vanity dashboard with the few decision-driving metrics
See it work
example outputContext: "a B2B SaaS invoicing tool for freelancers, goal: grow net revenue retention," rendered as a marketing measurement framework.
Marketing Metrics Framework — Freelancer Invoicing SaaS
Context: A self-serve B2B SaaS that helps freelancers send invoices and get paid; the goal driving this dashboard is growing net revenue retention, not just top-of-funnel signups.
North-star metric
Weekly active invoicing accounts — accounts that send at least one invoice a week. It captures real value delivery (the product only matters when invoices go out) and leads retention better than logins or signups.
Funnel metrics by stage
- Acquisition: visitors, signup-start rate, signups.
- Activation: % of signups who send a first invoice within 7 days.
- Revenue: trial→paid rate, new MRR.
- Retention: weekly active accounts, logo churn, net revenue retention.
- Referral: % of new accounts from "invite a client" / word of mouth.
KPI tree
| KPI | Definition | Drivers you can move |
|---|---|---|
| Net revenue retention | (start MRR + expansion − contraction − churn) ÷ start MRR | activation depth, plan upgrades, churn-save flows |
| Activation rate | % sending first invoice ≤ 7 days | onboarding friction, template quality, import ease |
| Trial→paid | % of trials converting | time-to-value, paywall placement, in-app nudges |
Guardrail metrics
Support tickets per active account, invoice delivery/payment-success rate, and refund rate — none may regress while chasing activation or expansion.
Reporting cadence
Weekly: north-star + activation, reviewed by the growth team. Monthly: NRR, MRR movement, and the KPI tree, reviewed with leadership.
Riskiest assumptions
- That weekly invoicing is the right north star (validate it actually predicts retention).
- That activation (first invoice) is the binding constraint rather than acquisition.
- That expansion revenue is available in a freelancer (single-seat) base — NRR may have to come from reduced churn, not upsell.
Grounded in AARRR funnel, north-star, and KPI-tree thinking (marketing cluster).
Run it now
Define your marketing metrics
Get a measurement framework: the north-star metric, funnel metrics by stage, a KPI tree (KPI → definition → drivers), guardrail metrics, and a reporting cadence.
Prefer code? Call it over the API or hand it to your AI agent via MCP — POST /api/bicycle/metrics-dashboard · define_marketing_metrics. API & agent access →