The operator scorecard I wish I'd had on day one. Lessons from $0 to $7M to exit.

The metrics that mattered most weren't the glamorous ones

The numbers that actually told me how the business was doing were unglamorous. Revenue churn and net revenue retention, because the leaky bucket is what quietly kills durable companies — you can acquire efficiently and still go nowhere if the bucket leaks. CAC Payback, because as a bootstrapped company I was spending my own money to acquire, and "I spent $2,500 and get it back in X months" is a sentence you can act on. And cash — survival months off the bank balance — because for a self-funded business, running out of money is the only way to truly lose.

The deepest lesson across all of them: manage the leading inputs, and the lagging outputs follow. You don't move LTV by staring at LTV — you move it by managing the churn and lifetime underneath it. You don't fix churn by watching churn — you watch adoption and activation, the early signals that predict it.

The metrics that didn't matter as much as everyone says

A whole class of celebrated numbers turned out to be board theater for us. Burn Multiple never applied — we were profitable, so we had negative burn, and that was the goal, not a gap. Magic Number we computed for the deck, but it was the same signal CAC Payback already gave us in a more usable form; it never drove a decision. We ran ~25 on Rule of 40, mostly from the profit half, and never cleared 40 as our growth flattened — and the business is still operating today. A 40 isn't a 40; how you got there matters more than that you got there, and a durable, profitable slow-grower beats an unproven sprinter.

The pattern: most "best practice" SaaS metrics are calibrated for venture-backed companies deliberately burning capital to grow. If you're profitable and bootstrapped, you've opted out of the game those numbers score — so don't let them tell you you're losing it.

The mistakes I'd warn my earlier self about

Three stand out. First, the new-versus-polish trap — we built a feature called Goals that nobody used and let it sit in the product for twelve years; I'd have been far more disciplined about killing dead features and investing in polishing what worked. Second, not closing the loop between support and product — your ticket volume by feature is the most honest bug map you have, and for too long we heard the pain without routing it to the roadmap. Third, not formalizing the leading signals early — we knew our customers were stalling, but without a defined activation number we intervened too late, after they'd already gone quiet.

What I'd do right: support as differentiation, raise from strength, watch the trajectory

And the things I'd keep exactly as they were. We treated support as a differentiation strategy, not a cost center — a human answered the phone, no IVR, the number on the homepage — and in a low-bar field that was a genuine edge. We took investment once, from opportunity rather than need, which is the only good reason to raise. And we watched cash and burn on a trajectory, not just a level, because a widening loss is the warning long before the number looks scary.

The scorecard, from $1M ARR onward

If I were starting again, here's what I'd put in front of the leadership team every week from $1M ARR: the leading signals where you can still act — activation, feature adoption, first response time, ticket volume, net new MRR — read weekly, as trends. And the company-level health numbers — LTV:CAC, CAC payback, Rule of 40, runway, retention — read quarterly, against the trend, knowing they're the outputs of the weekly work.

But more than any specific list, I'd build the habit — the same numbers, the same rhythm, the same leadership team, every week. The health of a SaaS business doesn't come from knowing these metrics; plenty of founders know them. It comes from looking at the right ones together, consistently, early enough to act. That's the scorecard I wish I'd had on day one — and it's exactly what we built Upbeat to be.