The few KPIs a solo founder should actually track
Ninety percent of startups fail. The usual explanation is a bad idea, bad timing, bad market. The more honest one, the one that shows up across founder postmortems again and again, is a bad signal caught too late. Not missing data. Too much of it, arriving in a shape nobody had time to read.
You don't have a data problem as a solo founder. You have a which-five-numbers problem.
Ninety percent of startups fail. The common thread isn't a bad idea. It's a bad signal, caught too late.
Founders don't usually miss the warning. They miss it inside forty other numbers that looked equally important at the time. Every dashboard defaults to showing everything it can measure, because measuring more feels like doing more. It isn't. A cockpit with sixty gauges doesn't make a pilot safer than one with six. It just means the six that matter take longer to find during the moment they actually matter.
Solo founders inherit this problem worse than anyone, because there's no second person to specialize in reading the sixty gauges while you fly the plane. Every hire in a bigger company eventually owns one part of the dashboard. When it's just you, the whole panel is your job, on top of every other job you already have.
A solo founder tracking 30 metrics is tracking none of them well.
The pattern that shows up across founder guides and postmortems is small and specific: MRR or revenue as the scoreboard, new paying customers as the leading indicator behind it, top-of-funnel signups behind that, and activation rate, the percentage of new signups who actually reach a real "aha" moment in their first session. One widely cited solo-founder playbook puts the warning line at 30%: below that, onboarding is broken, not marketing.
That's four numbers. Everything else, page views, follower counts, app downloads, is what every guide on this topic calls vanity, not because those numbers are fake, but because they don't reliably predict what happens next. A view is not a person deciding anything. It's just a person passing through.
Page views alone are vanity. Page views plus where people got stuck is diagnosis.
Here's the part that gets missed in the anti-vanity-metrics advice, though: the fix isn't to stop looking at page views. It's to stop looking at them alone. A page view tells you someone showed up. It doesn't tell you what they did next, where they came from, or where they gave up. Pair it with the actual path someone took through the site, and where that path breaks, and the same "vanity" number turns into the exact diagnosis you needed.
Same logic applies to where visitors are coming from geographically. Country and region data is meaningless as a vanity count of flags on a map. It's genuinely useful the moment you're deciding where to spend a marketing dollar, or noticing that a spike in signups from one region isn't converting the way your existing base does. Two hundred visitors from a country you've never marketed to isn't a number to celebrate on its own, it's a question: did something get shared there, and is it worth following.
And error tracking, quietly, is the metric solo founders skip most often, because it feels like an engineering concern instead of a growth one. A broken checkout page or a form that silently fails looks identical to low demand on a revenue chart. It isn't. It's a bug wearing a business problem's clothes, and it's usually cheaper and faster to fix than whatever marketing response you'd have reached for instead.
This is the actual shape of good analytics for someone running a company alone: not more metrics, the same handful of metrics connected to each other, so a number that's meaningless by itself becomes obvious the second it's next to the one it explains.
Twelve months of the wrong five numbers looks like this.
Same dashboard, twelve months out, still showing total visitors as the headline. You've made three product decisions off a chart that never separated new visitors from returning ones. Somewhere in month four, an error on your signup form quietly cost you two weeks of conversions, and it looked, from the outside, exactly like a bad marketing month. Nobody caught it because nobody was watching the number that would have caught it.
What to actually check weekly, no new tool required.
- Pick your one scoreboard number, MRR for most subscription businesses, and check it first, before anything else, every week.
- Track new paying customers separately from total revenue. It's the leading indicator that tells you tomorrow's number before the scoreboard does.
- Calculate your activation rate: the percentage of signups who reach the one moment that makes your product click for them. If it's under 30%, that's the actual fire to put out, not more traffic.
- Look at where visitors actually came from by country or region at least monthly. Not for vanity, to catch whether a channel is bringing in people who'll never convert.
- Check your error logs the same week you check revenue. A silent bug and a bad month look identical on a chart. They aren't the same problem, and they don't have the same fix.
The cockpit, not the data center
A solo founder doesn't need a data center's worth of dashboards. They need a cockpit: a handful of gauges, placed where you'll actually see them, each one telling you something the others don't already say.
That's the shape we built into Clerion by default: visitor and page-level numbers, country and region breakdowns, the actual path people take through a site, and error tracking, connected to each other instead of scattered across forty tabs, so the five numbers that matter are the five you're actually looking at.
Frequently asked questions
What KPIs should a solo founder track?
Start with four: MRR or revenue, new paying customers, top-of-funnel signups, and activation rate (the share of signups who reach a real 'aha' moment). Add error tracking and country data as diagnostic context.
What is a good activation rate?
Many founder playbooks treat 30% as a warning line. Below that, onboarding is usually the problem, not marketing.
Are pageviews a vanity metric?
On their own, mostly yes. Paired with the path visitors took and where they dropped off, the same number becomes a diagnosis of what to fix.
Why should founders track errors alongside revenue?
A broken checkout or silent form failure looks exactly like low demand on a revenue chart. Checking errors the same week as revenue stops you from fixing marketing when the real problem is a bug.