Revenue Can Rise 33% and Still Wipe Out $20 Million of Value

A SaaS company growing annual recurring revenue from $15 million to $20 million can still lose $20 million in enterprise value. That's the hypothetical Itay Sagie, strategic adviser and guest contributor to Crunchbase News, uses to make a point many founders miss: revenue can rise while enterprise value falls.

In his example, a company at $15 million ARR valued at 6x revenue carries an implied enterprise value of $90 million. Two years later, ARR reaches $20 million, but the multiple compresses to 3.5x. Enterprise value falls to $70 million. Revenue climbed 33%. Value dropped 22%.

The figures are illustrative, Sagie writes, but they demonstrate how multiple compression can overshadow operating growth. For a founder postponing a sale until the next revenue milestone, the practical implication is blunt: reaching that milestone may still produce a smaller exit.

When do revenue and value move in opposite directions?

Founders and boards routinely track revenue and profitability over time. Sagie argues another graph deserves equal attention: enterprise value. Its trajectory can turn downward while operating numbers keep improving, with significant implications for M&A timing.

The revenue multiplier reflects several dimensions that evolve differently. Sagie groups them into three categories:

• Qualitative factors: management quality, founder dependence, competitive intensity, product differentiation and strategic relevance to buyers.
• Absolute financial measures: revenue, EBITDA and cash flow.
• Relative performance measures: growth, margins, net revenue retention and gross revenue retention.

Retention metrics are expressed as percentages, but Sagie notes their importance lies in what they reveal about customer durability and expansion. Buyers assess these measures together and compare them against relevant peers. As companies mature, absolute results can improve while growth rates weaken.

The valuation math cuts both ways. Stronger profitability, better retention or deeper management capabilities may support a higher multiplier. The outcome depends on the combined effect. Sagie's recommendation for boards: ask which characteristics will improve over the next year, which could deteriorate, and how buyers might price those changes.

Why should M&A preparation start while you're winning?

A sale takes preparation, buyer engagement, negotiation and diligence. During that process, buyers continually reassess performance and forecasts.

Waiting until a slowdown becomes visible can weaken negotiating leverage and raise questions about management's projections, Sagie writes. Strategic buyer demand also runs on its own timetable. A buyer may place substantial value on a specific technology, customer base or geographic presence today. That interest can vanish after an internal product launch, a competing acquisition or a budget change.

Delay isn't always wrong. Waiting can create considerable value when additional scale attracts more buyers, profitability improves or concentration falls. Sagie suggests boards make that case tangible by reviewing estimated enterprise value alongside the operating plan, using scenarios in which revenue grows while the multiple holds, expands or contracts.

Deal structure matters too. Boards should weigh how debt, cash, dilution, liquidation preferences and transaction terms affect shareholder proceeds — a headline valuation doesn't equal shareholder payout.

Nobody can reliably identify the valuation peak in advance, Sagie concedes. But every decision to delay a sale embeds a view about future valuation. His closing argument: that view deserves its own graph.

Sagie, who lectures and advises startups and investors on strategy, growth and M&A, anchors the piece in a live situation: a potential client who declined to sell because the founder sees growth over the next couple of years worth materializing for a larger exit. That conversation, he writes, prompted the analysis — and it's exactly the bet more boards should be modeling explicitly.