Tactical insights for first-time founders to outsmart the burn, the churn & the breakdown.

Hey Founder,

You know your ARR, burn, and runway, the dashboards are covered, but do you know if those numbers are actually healthy for a company at your stage?
Because metrics without context are misleading.

$5M ARR can signal strength in one model - and trouble in another. The same goes for margins, hiring pace, even runway.

The problem isn’t metrics. It’s unanchored metrics.

Most founders benchmark against their own past, not against what “good” looks like in their market, at their size, with their capital structure.

In this issue, we’ll build a simple benchmarking lens, so you can quickly see what metric is healthy, what’s off, and where to focus next.

ARR, churn, margins, and other metrics - they only matter once you ask: good for whom, at what stage, with what model?

Serious benchmark reports reflect that. OpenView, for example, doesn’t publish one “good” churn number. It breaks performance down by ARR band, growth stage, and go-to-market motion - because a $3M PLG SaaS and a $30M enterprise sales company operate on completely different physics.

Take churn.

When Lenny Rachitsky asked Patrick Campbell (ProfitWell) what “good churn” looks like for a SaaS business, the answer wasn’t one magic percentage. It was ranges broken out by segment and price point.

HubSpot, early on, sold mostly to SMBs. Churn was naturally higher than enterprise peers - shorter contracts, smaller deals, faster cycles. The question wasn’t “Is this enterprise-grade churn?” It was: does LTV justify CAC, and is NRR improving?

Salesforce, scaling into large enterprise accounts, played a different game. Renewal rates, expansion, and predictability mattered more than headline growth.

Same metric. Different context. Different interpretation.

That’s the point of real benchmarking: reading your numbers through the lens of your stage, your market, and your model - not someone else’s version of “good.”

Where founders go wrong is grabbing a top-quartile number and turning it into a target. Suddenly, you’re chasing “elite churn” or “best-in-class margins” without asking whether those numbers even make sense for your business context. That’s how you end up optimising for someone else’s business.

Used well, benchmarks are much simpler than people make them.
First, get clear on your context - stage, model, capital situation.
Then look at a small set of metrics that actually drive your economics - growth, retention, margins, efficiency.
Not to set heroic goals, but to understand what’s normal.
From there, you make conscious trade-offs.

Maybe you push growth harder - but you accept lower short-term efficiency.
Maybe you protect margins - and grow a bit slower.

Benchmarks don’t tell you what to aim for.
They tell you where you’re out of line with reality.

Without baselines, numbers become emotional.
You overreact to churn that’s standard for your segment.
You feel good about growth that’s quietly burning too much cash.
You hire because momentum feels good - not because the economics justify it.

Investors, buyers, and lenders are benchmarking you anyway.
They’re already placing you next to similar-stage companies and forming a view.
If you’ve done the work yourself, you walk into those conversations clear-eyed:

This is where we are.
This is why.
And this is what we’re improving.

That level of clarity is underrated - and it compounds.

If benchmarking is calibration, this is where it becomes operational.

Before you look at any metric, define three things clearly.

Once those three are clear, you’re no longer benchmarking “a SaaS company.”
You’re benchmarking this kind of company, at this stage, with this model.

Keep it simple.

The point isn’t to admire the table. It’s to use it.
Before hiring ahead of plan.
Before doubling paid acquisition.
Before launching a new product line.

Ask: Does this move push our weak metrics toward healthy for our stage - or does it just sound ambitious?

Source note: Benchmarks synthesized from public agency KPI guides and utilization studies for creative/marketing agencies at $2–5M revenue.

When you see multiple metrics sitting just below healthy bands (gross margin, utilization, profitability), that’s usually one root cause showing up in different ways. Fix that first.

Big decisions should look obvious on paper.
If they don’t improve the economics you’ve already defined as weak, they’re probably ego, not strategy.

An email from one of you:

Short answer: You’re already the ops person.
You just haven’t admitted it.

Here’s how to think about it properly.

1. Prove it to yourself.
For one week, log every time you touch: vendor emails, CRM glitches, billing issues, access requests, reporting fixes, “quick workflow” patches.
By Friday, you won’t see “small tasks.” You’ll see a job description.

2. Hire for an outcome, not a title.
Ask each lead: “What recurring ops/system issue do you escalate to me at least once a week?”
Strip out the true one-offs. What remains is the role.
Own CRM and billing.
Own vendor relationships.
Own onboarding → renewal handoffs.
Keep reporting functional without you exporting CSVs at midnight.
That’s not admin. That’s leverage.

3. Set a hard rule.
Within 90 days of this hire, you do not touch vendor emails, system access, or workflow firefighting unless it’s a true escalation.
If people still DM you first, you didn’t hand off ops.
You hired help - and kept the job.

Send it my way, just hit reply.

A few useful reads this week:

Before You Go…

Benchmarks don’t account for luck, timing, or market cycles.
Use them to understand where you’re different - not to force yourself into average.

Your job isn’t to look like everyone else.
It’s to know exactly why you don’t - and whether that difference strengthens or weakens the business.

That discipline is the moat.

See you next Thursday,

— Mariya

Hit reply and let me know. I read every single one (for real).

Hey, I’m Mariya, a startup CFO and founder of FounderFirst. After 10 years working alongside founders at early and growth-stage startups, I know how tough it is to make the right calls when resources are tight and the stakes are high. I started this newsletter to share the practical playbook I wish every founder had from day one, packed with lessons I’ve learned (and mistakes I’ve made) helping teams scale.

Mariya Valeva

Find me on LinkedIn