Knowledge
The language of benefits in B2B sales is not enough to make the client buy
A sales conversation with the CEO of a sizeable company. We are trying to find out what return the implementation of our custom software will bring him. We want to get to hard numbers, to ROI. The standard approach: show the client the benefit and you will justify the price more easily.
The CEO interrupts and says bluntly: “If I told you what benefits I would get, you would jack up the price on me right here.”
That answer stuck in my head for years. Because the CEO was right: benefits are what he will get out of the investment. That is his business, not ours. We were asking about benefits, and we should have been talking about something completely different.
What is wrong with the “feature, advantage, benefit” model
“Don’t sell features, sell benefits”: this formula has been circulating in companies for decades. It sounds sensible. Except it was born in times when products were simpler, one person made the decision, and the salesperson’s job was to convince the client that this product was better than that one.
In complex B2B sales, implementations, integrations, systems built to order, this model assumes something that is rarely true: that the client already wants to buy and only needs to be shown why it is worth it. In reality most clients are not yet ready to make a decision. They usually believe they are still managing somehow and do not need any additional benefits.
I see this all the time in my work with technology companies. The company has a great product, a competent team, solid references, but sales conversations end with “we still need to think it over”. The website describes features. The sales presentation describes modules. The proposal describes the scope of work. Sometimes someone told them “you have to speak the language of benefits!”, so the team starts tacking “thanks to which” onto every sentence. And still nothing changes.
Because the problem never lay in a lack of benefits. It lay in not understanding where to start the conversation.
What really triggers a buying decision
People do not make decisions because something sounds attractive. They make decisions when they feel that the current situation is no longer acceptable. When they know they are losing money, time, people, control. The motivator for change is not a vision of something better. The motivator is the feeling that things cannot go on as they are.
I can tell a client: “Thanks to our solution you will gain full real-time visibility of project status”. True. A benefit. And the client will reply: “Interesting”, and go back to their spreadsheets. Because they do not feel they have a problem that needs solving.
But if instead I ask what the situation looks like now, when two project managers work on the same data from different versions of a file and the client receives contradictory information, that is something the CEO reacts to differently. Because that is his reality and his pain, not my promise.
That is why I start the conversation with diagnosing problems.
Problem, Result, Solution: in that order
In my work with B2B technology companies I use a framework I call the Value Triangle. Three elements, a strictly defined order.
First the Problem. Not a generality like “they want to be more efficient”, but a specific situation: what is not working, what slows them down, what causes the company to lose clients or be unable to scale. A well-named problem is one the client hears and thinks: “That is exactly how it looks at our place”.
Then the Result. Not a benefit, not ROI, but a picture of what the situation should look like after the change. What specifically should work differently. The result is neutral and shared; both sides can agree on it, because it says nothing about who will earn how much from it.
And here the story with that CEO comes back. The result is a shared point of reference: what is to change after the implementation, which processes are to look different, which problems are to disappear. A benefit is already an interpretation: how much I will earn, how much I will save, what advantage I will gain. And that is something the client often prefers to calculate for themselves. When you talk about results, you build a shared understanding of the goal. When you ask about benefits, you enter the territory of negotiation.
Usually we will not manage to build such a deep understanding of the client’s situation that we could precisely define all the benefits they may have. Both the direct and the indirect ones, those that are named and conscious, and those that will only reveal themselves later.
Only at the end the Solution. The product, the service, the implementation. But at this point the solution is no longer a list of features with benefits tacked on. It is the answer to a specific problem and the road to a specific result.
The “feature, advantage, benefit” model starts from the end, from the solution, and tries to build a justification onto it. The Value Triangle starts from what the client actually knows and what troubles them.
Why technology companies fall into this trap especially easily
The people who create and sell advanced technology solutions are usually deeply technical. They know their product inside out: what it can do, what sets it apart, how it works under the hood. And that is exactly why they so easily slip into the mode of “we have something good, let’s show how good it is, then the client will surely buy”.
Except the client does not buy what is good. They buy what solves their problem and leads to the result they care about. No number of tacked-on “thanks to which” will change that if the conversation did not start from the right place.
The change is not about throwing out the word “benefit”
Benefits are real and the client thinks about them. But they think about them on their own, on their side, in their context. Your job is not to formulate them for the client, but to give them the material from which they will derive the benefits themselves. And that material is a precisely named problem and a clearly defined result.
And one more thing: sales communication does not exist in a vacuum. How you talk to the client follows from the strategy, from the process, from whether you measure what works. You can send salespeople to benefit-language training, rewrite the proposal, change the scripts, but if there is no system underneath, over time everyone will gravitate back to old habits and methods.
People do not buy because they saw a benefit. They buy because they care about specific results, and they usually associate achieving them with removing the problems that block them.
