Revenue is not proof of scalability.

There's a number that comes up in almost every board discussion about channel performance: revenue. It's the first slide in the QBR, the headline in the investor update, the metric that defines whether a channel strategy is "working."

And in many cases, it's the wrong number to look at.

The pattern from inside distribution

Having held P&L responsibility at distributor level, I've seen a pattern that repeats across vendors, product categories, and market segments: the vendors that generate the most top-line revenue are frequently not the ones that generate the most efficient margin.

In fact, the relationship is often inverted. A single hyperscaler might drive the vast majority of a distributor's cloud revenue — but with a lean team and low management overhead. Meanwhile, a portfolio of mid-sized SaaS vendors might contribute a fraction of the revenue but consume a disproportionate share of enablement resources, support capacity, and management attention.

The revenue line says one thing. The channel P&L says something very different.

Why this matters for PE-backed platforms

In Buy-&-Build contexts, this disconnect becomes acute. Every acquisition adds products. Every product needs partner enablement. Every enablement initiative needs governance, content, training, and follow-up. The portfolio grows — but the channel cost base grows with it, often faster than the revenue it produces.

The board sees revenue increasing and concludes that the channel strategy is working. What they don't see is the rising EBIT drag: more vendor managers, more partner programs, more SKU complexity, more support tickets, more onboarding cycles — all for incremental revenue that may not justify the operational cost.

This is not a failure of execution. It's a structural problem. The portfolio was designed for product addition, not for channel scalability.

Three signals that revenue is masking a scalability problem

From operating across vendor, distributor, and partner environments, there are recurring indicators that a channel model has a scalability problem hidden behind a healthy-looking revenue number:

1. Partners sell products, not solutions. If your top partners are selling individual SKUs rather than repeatable, bundled solutions, the portfolio isn't structured for scale. Every deal becomes a custom configuration. Enablement never compounds. The partner's sales team can't build muscle memory because there's nothing repeatable to learn.

2. Enablement effort rises faster than partner productivity. More training sessions. More certification tracks. More partner portal content. But the number of active, productive partners stays flat — or declines. This is the clearest sign that the channel model is consuming resources without creating leverage.

3. Renewals depend on vendor effort, not partner ownership. If your renewal rate is only healthy because your own team drives it — rather than the partner proactively managing the customer relationship — then your channel isn't a distribution model. It's an outsourced sales force with a margin attached. That's a fundamentally different cost structure.

What to measure instead

Revenue will always matter. But for channel scalability, three questions are more diagnostic:

What is the channel cost-to-revenue ratio — and is it improving? If every euro of channel revenue requires an increasing share of internal resources to generate, the model isn't scaling. It's just growing.

How many partners are independently productive? Not registered. Not certified. Productive — meaning they close deals without vendor hand-holding. If that number isn't growing proportionally with your partner base, your enablement model is leaking.

Can a partner explain your value proposition in one sentence? This sounds trivial. It isn't. If your top partners can't articulate what they're selling and why a customer should care — without referencing individual product names — then your portfolio isn't solution-structured. And if it's not solution-structured, it's not scalable through indirect channels.

The decision that follows

None of this means revenue is irrelevant. It means revenue alone is insufficient as a measure of channel health. And for PE-backed platforms with growing portfolios, the question isn't whether the channel is generating revenue — it almost certainly is. The question is whether the channel model can sustain that revenue at improving efficiency as the portfolio scales.

If it can't, the answer isn't more enablement. It's a structural review of how the portfolio is designed, how solutions are defined, and how channel economics actually work at the partner level.

That's the conversation that matters — and it usually starts before the next acquisition, not after.

Friedrich Wahnschaffe is the founder of ClearBearing Advisory — an independent advisory practice for PE-backed software platforms navigating channel and portfolio scalability. He has held channel P&L responsibility at vendor level (Microsoft, Oracle), distributor level (ALSO Group, KOMSA), and partner level (Henson Group).