The Founder Dashboard: Metrics That Matter

What you actually need to know

• Vanity metrics (total users, total page views, total signups) feel good but do not tell you whether the business is viable. Track metrics that reveal health, not metrics that validate effort.
• Net revenue retention is the single most diagnostic metric for a SaaS business. Track it weekly even if the week-over-week signal is noisy -- the trend over a month reveals the business's retention quality.
• CAC must include the cost of your own time. If it does not, every CAC calculation is understated and every margin calculation is overstated.
• Deployment frequency belongs on the founder dashboard. It is an early warning signal for engineering process health.
• Eight metrics, reviewed weekly, take 30 minutes. A founder who cannot spend 30 minutes per week on these eight numbers is optimizing for comfort over visibility.

The core argument

Most founder dashboards are assembled from the metrics that are easiest to pull from existing tools, not from the metrics that are most revealing about the business's health. Google Analytics is already installed, so page views are on the dashboard. Stripe is already connected to a dashboard, so total revenue is visible. Total users are in the product database and easy to query. These metrics feel like information, but they answer the wrong questions.

A business with 10,000 total users, rising page views, and growing total revenue can still be dying if the active user rate is 10 percent, net revenue retention is 85 percent, and CAC has doubled in the past quarter. The vanity metrics are moving in the right direction; the health metrics are in crisis. The founder who only sees the vanity metrics believes the business is on track. The founder who sees both sees the crisis in time to address it.

The eight metrics I have described are not the only metrics that matter for every business. The right metrics depend on the business model, the stage, and the current risks. But these eight cover the questions that every SaaS founder needs to answer every week: Is revenue growing? Are existing customers staying and growing? Is acquiring customers efficient? Is the product engaging enough to retain customers? Is the engineering team shipping? Is the infrastructure cost sustainable?

MRR and the growth rate question

MRR growth rate is not the same as MRR. A business with $100,000 MRR growing at 3 percent per month is growing slower than a business with $10,000 MRR growing at 15 percent per month. The growth rate is the signal; the absolute number is context.

For early-stage SaaS (under $1M ARR), a healthy monthly MRR growth rate is 10-15 percent. For later-stage (over $10M ARR), 5-8 percent monthly is strong because the absolute additions are larger. The benchmark that matters is the comparison to the previous period: is the growth rate accelerating or decelerating?

Weekly MRR tracking is noisy because of billing cycles -- a week with several annual renewals will show a spike that is not real growth. The weekly number is useful as an early warning, not as a trend signal. The monthly rate is the trend.

NRR and the leaky bucket diagnosis

Net revenue retention below 100 percent is the most common overlooked crisis in early SaaS businesses. The business is growing because new customer acquisition is outpacing churn, so total revenue is increasing. But under the growth, existing customers are leaving or downgrading faster than the growth disguises. When new customer acquisition slows -- which it always eventually does -- the NRR below 100 percent becomes the primary driver of revenue direction, and that direction is down.

The NRR calculation: (MRR from existing customers at end of period) / (MRR from those same customers at start of period). If you had $100,000 MRR from 100 customers at the start of the month, and those same customers were paying $95,000 at the end of the month (some churned, some upgraded, some downgraded), NRR is 95 percent.

NRR above 110 percent is a strong signal that the product delivers compounding value -- customers expand their usage over time. Below 90 percent is a crisis. The diagnosis requires segmenting the number: are large customers churning, or small ones? Are churns concentrated in a particular cohort (customers who signed up in a particular month, customers who use a particular feature)? The segmentation reveals the root cause.

CAC and the channel efficiency question

CAC is most useful when it is broken down by acquisition channel. Total blended CAC obscures the efficiency differences between channels. A business with a blended CAC of $500 may have a Google Ads CAC of $1,200 (which is too high for the product's gross margin) and a content marketing CAC of $80 (which is excellent). The blended number masks the fact that one channel is destroying value and one is creating it.

Building per-channel CAC requires tagging leads and customers with their acquisition source at the moment of acquisition, not retroactively. The tracking infrastructure should be set up before the first dollar is spent on acquisition, not after. Retroactive attribution is inaccurate by design.

Active user rate and the engagement question

Total users is a vanity metric. Active users / total paid users is a health metric. A product with 500 paid customers and a 20 percent active user rate has 400 customers who are paying for something they are not using. Those 400 customers are churn risk -- they will cancel when they realize they are not using the product.

The definition of "active" depends on the product. A project management tool might define active as "created or updated a task in the past 7 days." A reporting tool might define active as "ran a report in the past 30 days." The definition should reflect the minimum engagement required for the product to be delivering value to the customer.

When the active user rate is below 40 percent for a SaaS product, the first investigation is whether the onboarding is getting customers to the product's core value quickly enough. Customers who never experience the core value do not become active users. The engagement problem is usually an onboarding problem.

Common mistakes founders make with their dashboards

1. Not separating new MRR from expansion MRR from churned MRR. Blended MRR growth hides whether the business is growing through acquisition or through expansion, and which type of growth is decelerating.
2. Not tracking CAC by channel. Blended CAC averages together the efficient and inefficient channels, preventing the decision to shift spend from inefficient channels to efficient ones.
3. Tracking support tickets as an absolute number rather than per customer. As the customer base grows, absolute ticket volume grows -- this is expected. Rising tickets per customer is the signal that product quality or documentation is degrading.
4. Not including infrastructure cost in the founder dashboard. Infrastructure cost surprises are common at scale. Tracking cost per customer monthly catches the drift before it becomes a crisis.
5. Reviewing the dashboard monthly instead of weekly. Monthly reviews miss the early signals. A weekly 30-minute review is the right cadence -- enough to catch trends early, not so often that noise dominates the signal.

Where to start: a 3-step dashboard setup

Step 1: Define the eight metrics and identify where each number comes from. MRR and NRR come from Stripe or your billing system. CAC by channel requires tagged acquisition data from marketing analytics. Active user rate requires a query against the product database. Support tickets per customer come from your support tool's API or export. Deployment frequency comes from your CI/CD system or GitHub.

Step 2: Build or configure a single view that shows all eight numbers. This does not need to be a custom dashboard -- a Google Sheet that pulls from Stripe, a simple query script, and a manually updated deployment log is enough to start. The goal is one place where you can see all eight numbers in 5 minutes.

Step 3: Schedule 30 minutes every Monday morning to review the dashboard. Write the eight numbers in a shared doc (a simple table with the date and the values). The act of writing them down over time creates the historical comparison that makes the weekly review meaningful. A month of weekly snapshots is more valuable than any real-time dashboard.

The Numbers That Tell the Truth

Yashveer Singh. Founder of Yashveer Labs. The dashboard I review for my own projects covers MRR, NRR, CAC by channel, and deployment frequency. When I work with clients, the first thing I ask to see is their metrics setup -- not the metrics themselves, but how they are tracking them. The businesses that can show me clean, weekly data on these eight numbers are the ones that are running with visibility. The businesses that have to pull numbers from four different tools and reconcile them manually are the ones where the surprises come from the blind spots.

Related reading

• The Engineering Dashboard Every Founder Should Have
• The Finance Stack for a SaaS Business
• The First Time a User Costs You Money: SaaS Unit Economics for Engineers
• The Business Metrics That Predict Churn Before It Happens