SaaS Metrics Dashboard for Indie Hackers

An indie hacker's SaaS metrics dashboard should change with the stage of the business: at $0 MRR track human visitors, signups, activation rate and where signups come from; at $1k MRR add MRR, new paying customers, trial-to-paid conversion, churned customers and revenue by source; at $10k MRR add MRR movements, net revenue retention, CAC and payback per channel, and cohort retention. Five or six numbers per stage is enough. Anything more turns a weekly review into an hour of scrolling that changes nothing.

Why should a SaaS dashboard change by stage?

Because the bottleneck moves. With no customers, your problem is finding out whether anyone wants the product — so activation and qualitative feedback matter more than any revenue metric. With 30 customers, your problem is finding a repeatable way to get the next 30, and keeping the ones you have. With 300, small percentage changes in churn or conversion are worth thousands a month, and you finally have enough data for cohorts and per-channel economics to be meaningful.

Tracking $10k-stage metrics at $0 is not harmless. Net revenue retention on eight customers is noise that looks like signal, and a dashboard full of noise trains you to stop looking. For context on how rare each milestone is: RevenueCat's State of Subscription Apps 2026 found that 17.3% of newly launched subscription apps reach $1k in monthly revenue within two years, and 4.6% reach $10k. That's mobile apps, not web SaaS, but the shape — most products never get to $1k — matches what founders see everywhere.

What should you track at $0 MRR?

Ignore for now: MRR projections, LTV, CAC, churn rate, cohort retention, NPS. You don't have the volume, and they distract from the only question that matters at $0: do people who try this get value from it? A rule of thumb from early-stage operators is to aim for an activation rate you're not embarrassed by (often 30–50% of signups reaching first value, depending on how demanding the first-value moment is) before spending serious time on acquisition.

Make sure the visitor number is clean. On small sites, a single scraper run can double a week's “traffic” and halve your conversion rate; see bot traffic in analytics. And track signups as an event your backend confirms, not a button click, so a broken form can't hide behind a healthy-looking chart.

What should you track at $1k MRR?

At $1k MRR you have something like 20–50 customers. That's enough to see which channel brought them and too few for churn percentages to be stable — one customer leaving moves monthly churn by two to five points. So count churned customers and talk to each one, rather than staring at a rate. The MRR calculator and churn rate calculator are handy for sanity-checking what your billing tool reports.

This is the stage where revenue attribution starts paying for itself. With 30 customers, knowing that 14 came from comparison pages, 6 from one newsletter sponsorship and 3 from three months of posting on X is the difference between a focused next quarter and a scattered one. How to track revenue by traffic source covers the setup, and which marketing channels bring paying customers covers what to do with the result.

What should you track at $10k MRR?

With a few hundred customers, rates finally mean something. ChartMogul's benchmark data put median monthly customer churn at 6.5% for companies under $300k ARR, falling to around 3.7% in the $1–3M ARR band (ChartMogul). At 6.5% monthly churn you lose more than half your customers in a year, so at $10k MRR churn reduction often beats acquisition as the best use of a week. Use the LTV calculator and CAC calculator per channel; a common target is LTV at least three times CAC, with payback under 12 months for a bootstrapped business.

Which SaaS metrics formulas do you actually need?

MRR            = Σ monthly price of active subscriptions (annual ÷ 12)
Customer churn = customers lost in month ÷ customers at start of month
Gross MRR churn= (churned MRR + contraction MRR) ÷ MRR at start of month
NRR (12 mo)    = (start MRR + expansion − contraction − churned) ÷ start MRR
ARPU           = MRR ÷ active customers
LTV            ≈ ARPU × gross margin ÷ monthly customer churn
CAC            = acquisition cost in period ÷ new customers in period
Payback        = CAC ÷ (ARPU × gross margin)
RPV            = revenue ÷ unique human visitors

Worked example at $10k MRR:
  ARPU $40, 250 customers, 4% monthly churn, 85% gross margin
  LTV  ≈ 40 × 0.85 ÷ 0.04 = $850
  Newsletter channel: $1,200 spend, 8 customers → CAC $150
  Payback = 150 ÷ (40 × 0.85) ≈ 4.4 months  → scale it

How do you build a metrics dashboard as a solo founder, step by step?

1. 1.Write down your stage and the five or six metrics for it from the tables above. Nothing else goes on the dashboard.
2. 2.Install privacy-first web analytics with bot filtering so visitors and conversion rates are honest. One script tag; see the install guide.
3. 3.Send a signup event from your backend and, if you have a key activation action, an event for that too. See custom events.
4. 4.Connect your payment provider so payments are tied to visitors and sources. That gives you revenue by channel and revenue per visitor without a spreadsheet.
5. 5.Get MRR, churn and NRR from your billing system or a subscription analytics tool; web analytics shouldn't try to be your billing ledger.
6. 6.Pick one weekly slot — 30 minutes on Monday morning — and write three lines: what moved, why you think it moved, and what you'll do this week because of it.
7. 7.Revisit the metric list each time you cross a stage boundary. Retire what no longer drives decisions.

VisitTrack covers the web side of this: human-only visitors, signups by source and landing page, funnels, and revenue attribution from Stripe, Polar, Lemon Squeezy, Paddle and Razorpay with revenue per visitor on the Revenue view. It also has an API and MCP server, so you can ask Claude or ChatGPT “how did signups and revenue by source change this week?” instead of opening a dashboard at all — a surprisingly good fit for a 30-minute weekly review. The SaaS use case page shows what that setup looks like.

Which metrics should indie hackers ignore?

• Pageviews and total sessions. Visitors are the unit that matters; pageviews mostly measure how your site is structured.
• Time on page as a goal. Useful for diagnosing a page, useless as a target — longer can mean confused.
• Bounce rate on its own. A docs page that answers the question in 20 seconds “bounces” and did its job. See the bounce rate glossary entry for when it does matter.
• Social follower counts. Track signups and revenue from social as a channel instead.
• Vanity ARR. Annualizing a single good month or counting annual prepayments as run-rate makes the number bigger and your decisions worse.
• Anything you can't name a decision for. If no plausible value would change what you do this week, drop it.

What does a good weekly review look like?

An illustrative example, in the format we recommend, for a $2,400 MRR developer tool:

Visitors 3,150 (flat). Signups 61 (+18%) — the new comparison page converts at 6% vs 1.9% site-wide. 4 new customers, all first-touched on comparison or pricing pages. 1 churn (moved to an in-house script). This week: write the second comparison page, and email the 9 trial users who never created a project.

Five numbers, one insight, two actions. That's the whole job of a dashboard at this stage. If yours produces fewer actions than that, it's tracking the wrong things; if it takes more than 30 minutes, it's tracking too many. When you're ready to go deeper on any single area, the guides on SaaS conversion funnels and revenue per visitor pick up where this leaves off.