Founder Dashboards: What to Track Weekly

A founder dashboard is the one screen that tells a bootstrapped operator whether the business is healthy this week: revenue, growth, churn, conversion, and cash. The useful version is small. It holds six numbers you can read in thirty seconds, not forty metrics you scroll past. Fewer numbers, checked weekly, beat a wall of charts nobody reads.

I am a solo founder, pre-revenue, building several products at once from Bharatpur, Nepal. So I am writing this from the build phase, not from a victory lap. I do not have a churn number to brag about yet. What I do have is a strong opinion, formed across PDF9to5, TYPEMUSE, and a mobile portfolio, about which numbers will matter the day money starts moving and which ones will quietly waste my attention.

This is a dev-tools and operations question as much as a metrics one, because the dashboard you can actually maintain is the one that fits your stack. Mine is deliberately light: Stripe plus a spreadsheet, not Notion, not a CRM, not an analytics suite. Below I define the six numbers, how to pick a north star metric, how to build the dashboard cheaply, and what I would do differently. It connects to the break-even MRR you are aiming at, the weekly review where you read it, and the solo founder operating system it plugs into, all part of the broader Dev Tools pillar. A public status page turns your uptime numbers into a trust signal customers can see. Roll every metric into the bootstrapped founder metrics dashboard. And the infrastructure those numbers run on can stay just as small — the single-VPS SaaS playbook shows how far one server goes before you need to split it.

Key takeaways

• A useful founder dashboard is one screen with about six numbers, not forty.
• Check it weekly, not daily. Most SaaS metrics move in weekly and monthly cycles.
• The six that matter: MRR, net new MRR, gross churn, trial-to-paid, cash and runway, and one acquisition metric.
• Pick one north star metric that captures delivered value, and let it anchor the rest.
• Build it cheaply: Stripe plus a spreadsheet first, a tool like Baremetrics later when manual export becomes a chore.

Why a weekly dashboard beats a daily one

The instinct, especially for a technical founder, is to build a real-time dashboard and check it constantly. Resist it. Daily checking adds noise without adding signal, because the numbers that decide whether a SaaS lives or dies do not move on a daily clock. They move on weekly and monthly cycles tied to billing, trials, and renewals.

Look at MRR daily and you will see a flat line punctuated by random jumps when a payment clears. That randomness invites two failure modes. You either celebrate noise as a trend, or you panic at noise as a decline. Both waste the one resource a solo founder cannot refill: focused attention. A weekly cadence smooths the noise into something you can actually read.

There is a second reason to keep it weekly. A daily ritual that requires you to interpret numbers will get skipped the first busy week and never come back. A weekly review is sustainable. It earns a fixed slot, it becomes a habit, and a habit you keep beats a perfect dashboard you abandon.

The same logic kills the forty-metric dashboard. Every metric you add is a metric you have to interpret, and attention does not scale. A dashboard with six numbers gets read every week. A dashboard with forty gets glanced at, then ignored, then quietly abandoned. The constraint is not data. The constraint is how many numbers a tired founder will actually look at on a Friday.

Keep operational alerts separate from the weekly dashboard. A failed payment, a spike in errors, or downtime needs to reach you in minutes, not at the weekly review. That is a different system, an alert that pages you. The dashboard is for judgment, not for emergencies. Mixing the two ruins both.

What metrics should a solo founder track?

A solo founder should track six numbers weekly: MRR, net new MRR, gross churn, trial-to-paid conversion, cash and runway, and one acquisition or pipeline metric. Together they answer whether revenue is growing, whether the bucket leaks, whether new signups convert to money, and how long the cash lasts. Six is enough.

The reason it is exactly these six, and not the twenty a metrics tool will offer you, is that each one maps to a decision. MRR and net new MRR tell you about growth. Gross churn tells you about retention. Trial-to-paid tells you whether your funnel converts. Cash and runway tell you how much time you have. The acquisition metric tells you whether the top of the funnel is moving. Anything else is detail you can pull when a specific question comes up, not something you stare at every week.

Here is each number, defined crisply.

MRR (monthly recurring revenue). The normalized monthly value of all your active subscriptions. An annual plan at $120 counts as $10 of MRR, not $120 in the month it was paid. MRR is the base level of the business, the floor you are standing on this month. Stripe reports a version of this directly if your billing runs through it.

Net new MRR. The change in MRR over the period: new MRR plus expansion MRR, minus churned and contraction MRR. This is the single most honest growth number you have, because it nets your wins against your losses. MRR can rise while net new MRR shrinks, which is the early warning that growth is slowing even though the top-line still looks fine.

Gross churn (gross MRR churn rate). The percentage of recurring revenue you lost to cancellations and downgrades in the period, before counting any expansion. Measure the gross version, not net, because net churn can hide a leaky product behind a few big upgrades. Gross churn tells you the truth about how well you keep what you win. Reported SaaS benchmarks vary widely by segment; Paddle ProfitWell publishes ranges worth reading rather than guessing.

Trial-to-paid conversion. Of the people who started a trial (or hit your activation point), the percentage that became paying customers. This is the hinge of your funnel. A small move here changes everything downstream, because it multiplies against every signup you ever get. If only one number is broken, this is usually where the leak is.

Cash and runway. Cash is what is in the bank. Runway is how many months that cash lasts at your current burn, which for a bootstrapped founder includes your own living costs. For a pre-revenue or thin-revenue solo operator, this is the number that decides whether you keep going. It is uncomfortable, which is exactly why it belongs on the screen where you cannot avoid it.

One acquisition or pipeline metric. Pick the single leading indicator for how new people reach you. For a content-and-SEO business that might be weekly organic signups. For an outbound business it might be qualified conversations in the pipeline. You only need one, and it should be the input you can actually influence this week, not a lagging total.

The One-Screen Founder Dashboard

Here is the framework, named so you can reuse it. Six rows, one screen, each tied to a question and a source. If a metric does not answer a question or have a clear source, it does not belong on the screen.

Metric	What it answers	Where it comes from
MRR	What is the business worth per month right now?	Stripe billing data
Net new MRR	Did the business grow or shrink this month, after losses?	Stripe (new + expansion − churn − contraction)
Gross churn	How well do I keep the revenue I win?	Stripe cancellation and downgrade events
Trial-to-paid	Does my funnel turn signups into money?	Trial starts vs. first paid charge
Cash and runway	How many months do I have left?	Bank balance ÷ monthly burn
Acquisition metric	Is the top of the funnel moving this week?	Analytics, signups, or pipeline count

The discipline of the framework is the column on the right. Every number has a source you can point to. If you cannot name where a metric comes from, you cannot trust it, and an untrustworthy number on a dashboard is worse than no number, because it invites confident wrong decisions.

What is a north star metric?

A north star metric is the single number that best captures the value your product delivers to customers, the one that predicts long-term revenue better than any other. Amplitude popularized the framing. It is not revenue itself. It is the leading behavior that revenue follows, the thing customers do when the product is actually working for them.

The point of a north star is focus. A founder juggling six dashboard numbers still needs one metric that wins ties, the number that decides which feature ships and which gets cut. Revenue is too lagging to play that role day to day. The north star sits upstream of revenue and moves first, so steering by it lets you correct before the money shows the problem.

For most SaaS products, a good north star is some version of weekly active accounts performing the core action, not signups and not page views. For a PDF tool it might be documents successfully processed by a returning user. For a typing platform it might be completed practice sessions per active player. The test is simple: if this number goes up, does the customer get more value and is revenue more likely to follow? If yes, it is a candidate.

One warning. The north star is a focusing tool, not a substitute for the dashboard. Teams that obsess over a single number can optimize it into a corner, juicing the metric while churn quietly climbs. Keep the north star as the tiebreaker and the dashboard as the guardrails. The dashboard catches you when the north star starts lying.

How to build it cheaply without buying an analytics suite

Start with what you already pay for. If your billing runs through Stripe, most of the six numbers are derivable from Stripe data alone: MRR, net new MRR, churn, and the inputs to trial-to-paid all live in subscription and charge events. You do not need a metrics suite to read them. You need a place to write them down once a week.

That place, at the start, is a spreadsheet. One row per week, one column per metric. Each Friday you open Stripe, read the numbers, type them into the row, and look at the trend across the last several rows. That is the entire system. It takes fifteen minutes, it costs nothing beyond Stripe, and it forces you to actually look at each number rather than letting a chart blur past.

I run this stack deliberately: Stripe plus a spreadsheet, on Arch Linux, edited in Neovim, hosted on Cloudflare and Hetzner. No Notion, no Slack, no CRM. The lighter the tooling, the lower the chance the dashboard becomes a project of its own. A founder who spends a weekend building the perfect dashboard has spent a weekend not building the product.

The manual approach has a real cost, which is your time, and that cost grows. Once the weekly export becomes a chore, or once you want cohort and segment views the spreadsheet cannot give you cheaply, that is the signal to buy a tool. Baremetrics and Paddle ProfitWell both connect to Stripe and compute MRR, churn, and net new MRR automatically. Buy one to remove friction, not to feel like a real company. The spreadsheet was already a real dashboard.

A note on the acquisition metric, since it is the one that usually lives outside Stripe. For an SEO-driven business, a privacy-friendly analytics tool or Cloudflare’s own analytics will give you weekly visitor and signup counts without a heavy suite. Pull one number from it into the same weekly row. The goal is one spreadsheet, one screen, not a second dashboard you have to reconcile.

Vanity metrics to ignore

A vanity metric is a number that looks impressive and changes no decision. The tell is that it only goes up. Total signups, total downloads, page views, registered users, social followers: all of them climb forever and none of them tell you whether the business is healthy. A real metric can go down, and when it does it forces an action.

Total signups is the most seductive one for a founder, because it feels like progress and the number is always growing. But total signups says nothing about whether those people pay or stay. The honest version is active paying customers, or trial-to-paid conversion, both of which can fall and both of which make you do something when they do. Replace every cumulative total on your dashboard with a rate or a current level.

Page views and traffic deserve a specific caution for content-driven businesses, because they sit so close to the work that you mistake them for the goal. Traffic is an input to the acquisition metric, not the metric itself. The number that matters is how much of that traffic converts to a signup, and then to a paid customer. A traffic spike that converts nothing is a vanity event dressed up as a win.

The simplest filter: for every number on your screen, ask what you would do if it dropped. If the answer is a concrete action, keep it. If the answer is nothing, it is a vanity metric and it is stealing attention from the six numbers that would have told you what to do.

What I would do differently

Since I am pre-revenue, the honest framing here is not a postmortem but a set of decisions I am locking in before the numbers exist, so I do not have to unlearn bad habits later. The first one: build the dashboard before there is revenue to put in it. An empty spreadsheet with the right six headers is a commitment to measure the right things. Filling it after the fact means you never have the early baseline.

Second, I would resist the urge to instrument everything just because I can build it. As a technical founder the temptation is to wire up a full analytics pipeline on day one, because it is a fun engineering problem. It is also a trap. The spreadsheet is enough until it provably is not, and “I could build it” is not the same as “I should build it now.”

Third, I would put cash and runway on the screen from the very first week, not bury it. It is the least pleasant number for a bootstrapped founder, which is exactly why it tends to slide off the dashboard. Keeping it visible is the difference between running out of money as a surprise and running out of money as a decision you saw coming and chose to manage. The point of the weekly review is to make that number impossible to avoid.

If you take one thing from this: a founder dashboard is a tool for deciding, not for feeling productive. Six numbers, one screen, every week. Build it cheap, keep it small, and let it tell you the truth even when the truth is uncomfortable.

Want the system, not just the article?

This dashboard is one module of a larger operating system I am putting together for bootstrapped founders: The Bootstrapped Founder Operating System ($29). It includes the one-screen dashboard template, the weekly review checklist, and the worksheets behind the metrics in this post, set up so you fill them in rather than build from scratch.

Get the workbook →