We’re seeing a common pattern at the moment, companies selling embedded finance, infrastructure, enablement, components and tools getting stuck on the same idea “how do we tie our proposition to revenue uplift?” . Falling into this ‘revenue trap’ is something we occasionally feel too given ‘strategy’ and ‘proposition’ advisory is a driver of revenue but rarely directly attributable to.
[Before continuing, we’re going to be talking about back-end and middleware solutions here, fantastic products that transform how enterprises operate, but don’t necessarily bring in direct revenue themselves. Without them there’s no revenue, but it’s harder to attribute revenue to their implementation. If your service does provide direct revenue then of course, lead with that.]
Conventionally, leading with revenue a great idea, because “that’s what buyers care about, especially the C-Suite”
The only problem is that the buyers evaluating your solution, the Heads of X, the Directors of Y and the VPs of Z, sometimes even some of the C-Suite themselves, don’t own revenue. They own the systems, processes, people and capabilities that enable revenue and they understand that one technology is unlikely to drive top-line growth on its own.
When you lead with revenue claims to these buyers, you’re hoping to sound ambitious but might come off sounding like you don’t understand their job.
This creates four risks that could undermine your offer’s credibility:
1 – You sound like everyone else (which means you sound like no one).
Walk into many categories, process automation, people training, data platforms, finance, professional services, etc. and you’ll often hear the same claim about “driving revenue growth.”
The pattern is there to see; promises of “revenue uplift through better productivity”, “revenue retention through reduced churn”, “revenue efficiency through process optimisation”, “new revenue opportunities mapped and sized”, etc
When your value proposition is indistinguishable from the other 7 key competitors, you’ve commoditised yourself before the conversation’s started.
The logic: Differentiation comes from specificity, not how aspirational you might be. It’s likely your client has heard “revenue uplift” from every cold approach they’ve had this year. What they haven’t heard is a credible explanation of how your solution uniquely solves their actual problems, the specific workflow bottlenecks, adoption challenges, or KPI gaps that keep them up at night.
The cost: You won’t stand out because everyone else will be talking up the revenue benefits too.
2 – You risk looking disingenuous to the people who know better.
Operational buyers understand their business well enough to know that revenue is influenced by market conditions and competitive dynamics, by product-market fit and pricing strategy, sales execution and even the macro-economic headwinds or a hundred other factors outside their control.
When a VP evaluates a new platform, they’re thinking about adoption rates, time-to-value for customers, support ticket volume, and renewal workflows, enablers of but not directly providing, revenue. When you claim your tool will “drive revenue retention,” you’re implicitly asking them to believe that you understand their ‘churn problems’, that they’re solved by your solution and they should ignore product, pricing, service issues, or the dozen other factors actually driving their retention metrics.
The logic: Credibility with B2B buyers is built on demonstrating you understand the problem and how to solve it. When your claims don’t match what they’re seeing, they start to question whether you can really achieve the things you’ve said you can.
The cost: Once you’re tagged as another “overselling vendor,” recovering trust is much harder than earning it in the first place. This is especially damaging in tight-knit sectors where reputation travels fast.
3 – You can’t answer the obvious follow-up (and they will ask).
Enterprise buyers are trained to probe claims. It’s not scepticism, it’s their job and their reputation on the line if they make the wrong choice. When you say, “we drive revenue uplift,” expect these questions:
- “Show me how. Walk me through exactly how it achieves that.”
- “Which client achieved this? What was their baseline?”
- “How did you isolate your impact from everything else that changed?”
- “How long did it take to get results?”
- “Can I speak to a reference who saw this outcome?”
If your revenue claim is aspirational rather than attributable (even when you fully believe the outcome you claim), you now have three bad options:
- Deflect (“Every customer’s situation is different…”), this only looks evasive.
- Share a vague case study (“One client saw significant improvements…”), looks weak or could potentially come off as misleading.
- Double down with more assertions, which only looks desperate.
The logic: A value proposition that can’t survive a 10-minute interrogation on methodology isn’t a value proposition; it’s just marketing copy. Operational buyers make their living connecting initiatives to outcomes. If you can’t articulate the chain of causation, and show the metric uplift, they’ll assume there isn’t one.
The cost: You lose the deal not because your solution doesn’t work, but because your narrative couldn’t withstand scrutiny. Added to that, you’ve now trained them to distrust everything else you say from then on.
4 – You demonstrate you don’t actually understand their job.
This is the most damaging one, because it signals broader misalignment. Consider what your actual buyers are measured on:
Head of Banking Operations: Processing cycle time, error/rework rates, operational cost per transaction, SLA adherence, straight-through processing. Efficiency, accuracy, and compliance are their scorecard, not top-line growth.
Risk Director: Exposure reduction, compliance audit scores, coverage & exclusions, claims handling times, claims approval rates. Their mandate is protection, not growth; revenue claims can sound tone-deaf.
Director of Operations: Process cycle time, error rates, capacity utilisation, cost per transaction. Efficiency is their mandate, not turnover.
CTO: System reliability/uptime, technical debt reduction, security posture, delivery velocity, infrastructure TCO. Revenue is a business outcome, not a technology metric.
All of these roles will think about revenue at some point and some will even be incentivised with overall company growth metrics, but when you lead with revenue, you’re signalling that you haven’t bothered to understand what success looks like for them. You’ve done the quick research, you’ve shown that you know what the CEO, CFO or CRO cares about, but not what your actual buyer cares about.
The logic: People buy from vendors who make their job easier, not from those who make their job sound irrelevant. If your value proposition speaks to a stakeholder who isn’t in the room (or who doesn’t control the budget), you’ve missed the buyer.
The cost: You’re not just losing a sale, you’re signalling that implementation will be equally misaligned with their actual needs. If you don’t understand their KPIs now, why would you understand their integration requirements, change management needs, or adoption barriers later?
The better approach: credibility before aspiration, avoiding the revenue trap.
This isn’t an argument against ambitious outcomes, nor is this an argument to say you should never include revenue messaging in your offer. There are a few times when revenue messaging should be a strong part of your positioning;
- If you can show, and evidence revenue gain directly due to adoption of your solution, then you should, but make sure you also have arguments for the contributing metrics you’ll be improving for them as well.
- If your buyer is in control of some, or all, of the revenue in their business, but again, be clear on what they are and are not in control of.
- If you’ve already convinced your main buyer and are now helping them make the case internally to adopt your solution.
In most other cases, it’s about earning the right to talk about revenue by first proving you understand the operational reality that makes revenue possible.
The sequence that works across sectors:
Start with what they control: What can they actually change? It might be operational efficiency, process speed, team productivity, system reliability, adoption rates and as we say in some cases revenue
Connect to what they’re accountable for: What are they incentivised on? System reliability and uptime, reduced risk, cost optimisation, improved NPS
Frame revenue as an enabled possibility, not a guaranteed outcome: “This is what clients have been able to pursue once they had this capability”
The logic: You’re not avoiding revenue, you’re building a credible pathway to it. You’re showing you understand their business well enough to know that revenue is a lagging indicator of operational excellence, not a leading one.
The real differentiator
In a market where everyone is promising revenue, you’ll be the vendor who demonstrates genuine understanding of their reality. You’ll be the one who stands out, not because you’re more ambitious, but because you’re more credible.
Regardless of who you’re selling to, the dynamic is the same, they’re evaluating you on how you make their part of the machine work better. Help them do that, and you’ll earn the right to talk about what that enables for their business.
Revenue is likely what your buyer’s boss cares about. Operational performance is what your direct buyer cares about. Convince them, and then work together to convince the internal stakeholders who’ll form the buying committee, best done with a champion on your side.
As we mentioned at the beginning, not only do we see this in clients but we also see this ourselves, when engaging different leaders in our client organisations we have to frame the right benefits to ensure we’re resonating with everyone.
If you’re wrestling with how to articulate value without overpromising, let’s talk. we work with B2B companies to build value propositions that resonate with buyers, without the credibility tax of revenue claims that can’t be substantiated.
