Why SaaS Companies Stall at $20M (And It's Not the Market)

Most of the SaaS leadership content written online is built around bold moves.

The breakout campaign. The hockey-stick quarter. The contrarian bet that paid off. The aggressive hiring sprint that broke the team but produced the number.

It’s good content. It’s also, by and large, not how the companies that actually scale to a unicorn outcome get there.

The companies that compound their way to $100M ARR — the ones that hit the T2D3 curve and then settle into the Rule of 40 — tend to win on much less glamorous work.

Quarterly pricing reviews. Renewal motions that actually function. Onboarding optimization. Cross-sell mechanics designed and operated, not just hoped for. Customer health scoring systems that catch churn before it happens.

None of that is press-release work. Almost none of it shows up in a keynote. But applied consistently to a real customer base over a five-year window, it produces a different company than the one acquisition-only growth would have built.

The cultural bias toward visible work

There’s a reason the quiet work gets neglected, and it’s not because anyone thinks it doesn’t matter.

Every operator I talk to agrees, in principle, that pricing matters. That retention matters. That expansion matters. That onboarding matters.

And then the calendar fills up with the work that’s easier to talk about.

Pipeline reviews. Campaign launches. Hiring decisions. Strategy offsites. Quarterly business reviews dominated by funnel metrics.

Pricing reviews don’t happen because they’re hard to scope, harder to model, and uncomfortable to discuss — nobody wants to be the person who suggests raising prices on existing customers. So they get pushed to next quarter, then next year, then the year after that.

Customer health systems don’t get built because they require cross-functional buy-in from product, customer success, and revenue operations — and nobody owns the integration.

Expansion motions don’t get designed because the team responsible for them is also responsible for renewal, support, onboarding, and a handful of other things — so expansion becomes the work that fits between the other work.

The cultural bias isn’t against the work. It’s against the kind of attention the work requires — slow, careful, unglamorous, and rarely rewarded with applause.

Five examples of work that compounds

Here are five specific examples of the kind of quiet work that produces outsized five-year outcomes. None of these are revolutionary. All of them are skipped by most teams.

Annual pricing reviews

Most B2B SaaS companies set their pricing at launch and then leave it alone, with the occasional discount or experiment around the edges. But buyer expectations evolve, competitor pricing shifts, and the product itself becomes more valuable over time. A formal annual review — looking at where buyers cluster, what they actually use, what they’d pay more for — reliably produces ARPU growth that costs nothing to acquire.

The work itself takes a quarter to do well. It produces returns for the next five years.

Packaging changes

The same product can be sold many different ways. Packaging — what’s included, what’s gated, what’s priced separately — determines who can buy, at what price point, and how easily they can expand.

Most SaaS companies stick with the packaging they launched with, because changing it feels disruptive. But a thoughtful packaging restructure can open new segments, raise the ceiling on existing accounts, and create natural expansion pathways that didn’t exist before.

It’s slow work. It also frequently moves ARPU by double-digit percentages.

Customer health scoring

Most churn is predictable. Usage drops. Login frequency declines. Key contacts disengage. The signals are there — they’re just scattered across product analytics, support tickets, and CRM activity.

A real health scoring system pulls those signals into one view, weights them, and alerts customer success early enough to intervene. It doesn’t prevent every churn. It catches the recoverable ones.

Building it is a cross-functional project that takes a few months. Operating it produces compounding retention improvements every quarter after.

Renewal forecasting and intervention

Most companies treat renewals as a customer success activity that happens in the last 30 days before the contract anniversary. By then it’s often too late.

A real renewal forecast starts 90 to 120 days out, identifies which accounts are at risk, and triggers a structured intervention motion — not just a renewal call, but an executive sponsor reach-out, a value review, a usage analysis.

The work isn’t complicated. It’s also rarely done well, which is why so many “surprise” churns happen.

Expansion motion design

Land-and-expand is talked about constantly in SaaS. It’s also rarely operationalized.

A real expansion motion has named owners (often shared between customer success and sales), defined expansion triggers (usage patterns, milestone moments, organizational changes at the customer), structured plays for each trigger, and measurable conversion rates from trigger to closed expansion.

Without that structure, expansion is just a hope. With it, expansion becomes a predictable revenue stream that doesn’t require new customer acquisition to grow.

What it looks like when leadership rebalances

When a SaaS leadership team actually rebalances toward this kind of work, a few things change.

The board update changes. New logos still get reported, but so do retention rates, expansion conversion, ARPU movement, and unit economics. The picture becomes three-dimensional instead of pipeline-shaped.

Customer success changes. The function moves from being a reactive support layer to being a proactive revenue layer. Health scores get reviewed weekly. Renewal forecasts get treated like sales pipeline.

Pricing changes. It stops being a thing that happens at launch and never again. It becomes a recurring discipline, with a named owner and a real cadence.

The cultural shift is the hardest part.

Acquisition culture rewards the launch. Retention culture rewards the discipline. They feel different, and they require different leadership instincts.

But the math says the retention culture wins. Quietly. Over time. Compounding.

The shift from launch to improvement

Maybe the simplest way to describe the cultural rebalance is this:

Acquisition-first companies ask, “what did we launch this quarter?”

Compounding companies ask, “what did we improve this quarter?”

Both questions matter. But the second one is the one that bends the five-year curve.

The teams that get to $100M ARR don’t just do bigger launches. They get systematically better at the parts of the business that already exist — pricing, packaging, retention, expansion — and they treat that improvement work as core operating discipline, not optional polish.

None of this is news to a thoughtful operator. But the gap between knowing it and actually building the leadership cadence around it is where most SaaS companies stall.

If you’d like to see how much this kind of work would actually move your own five-year curve, we recently hosted a session called The Economics Behind Scaling to $100M ARR. It walks through the math behind the three growth levers and shows the calculator that makes the picture visible — lever by lever, year by year, against the T2D3 benchmark. Watch the recording below: