Back to blog
Ask a leadership team why a customer should pay a premium for their product, and the answer almost always starts the same way: a list of specifications. Better materials. A longer warranty. Tighter tolerances. None of that is wrong. None of it answers the question either. We've put that same question to enough manufacturing and product leadership teams to expect the same shape of answer every time: a product description with a price attached, not a reason a specific customer would choose to pay it. That answer is usually the clearest sign that the value proposition for product companies in the room describes the product, not the buyer.
That's the pattern worth naming directly. Most companies with a genuinely differentiated product still pitch it the same way to every buyer who walks through the door, and then wonder why the conversation keeps drifting toward a spec sheet and a discount. The value proposition wasn't wrong. It was never built to hold up under that kind of scrutiny in the first place.
The tell: when the pitch turns into a comparison table
Here's a simple test. Sit in on three sales conversations for the same product line and ask what the buyer is actually being asked to compare. If the answer is a features list, a spec sheet, or a price point against a named competitor, the value proposition has already failed. Not because the product lost the comparison. Because the comparison is happening at all.
A value proposition built from product features invites exactly this kind of scrutiny. It hands the buyer a checklist and lets them run it against every alternative in the category. Once that checklist exists, the differentiated product and the commodity product are competing on the same terms, and the terms almost always end at price. Getting the commercial agenda built in the right order helps, since a proposition sequenced after the segment decision starts from firmer ground than one designed in parallel with it. But sequence alone doesn't rescue a proposition that was never built to survive a head-to-head comparison.
"If the buyer conversation can be settled with a comparison table, the value proposition was never really one."
One pitch, three very different buyers
The deeper issue shows up once you look at who's actually receiving the pitch. Most product ranges serve genuinely different buyer types under one commercial roof: a procurement lead evaluating on total cost, a specifier caring about integration and reliability, an end user caring about how the product performs day to day. Each of these buyers has a different decision timeline, a different tolerance for risk, and a different reason to pay a premium, if they'll pay one at all.
Treat them all to the same pitch and you're not being efficient. You're forcing three different value questions into one answer, and the answer that satisfies none of them defaults to whatever's easiest to compare: price. We've watched sales teams get frustrated that a genuinely strong product keeps losing on cost, without noticing that the pitch handed to a specifier last week was word-for-word the one handed to procurement the week before.
This is where the product strategy conversation and the value proposition conversation start to pull apart. A product can be built with real differentiation and still get sold as if none of it exists, because nobody rebuilt the pitch for the buyer actually receiving it.
What a segment-built proposition actually requires
Fixing this isn't a matter of sharper language. Three things need to be true at once, and most companies fix one of them without touching the other two.
The proof points need to differ. What convinces a procurement lead (total lifetime cost, warranty terms, supply reliability) is not what convinces a specifier (integration ease, technical support, a track record on complex jobs). Use the same proof point for both and one of them is being unpersuaded by evidence that was never meant for them.
The language needs to differ too. Not the brand voice. The specific claim being made, and what it's being measured against.
The sales motion needs to differ, and this is the one companies most often skip. A specifier needs a longer, more technical conversation earlier in the process. A procurement-led buyer needs the value case made before the RFP stage, not during it, because once the RFP is written the comparison has already been reduced to a spec sheet. Get this sequencing wrong and even a well-built segment-level proposition ends up presented at the wrong moment to do any good.
"The price point should be a consequence of the positioning, not the opening move in a negotiation."
Where this leads next
Once the value proposition genuinely holds at segment level, two things tend to get easier almost immediately. Portfolio decisions stop being about which products to keep and start being about which ones a specific segment will actually pay for. And the go-to-market question, which channel or route reaches which buyer, becomes a design decision rather than a default.
The place to start isn't a rebrand. It's an audit. Pull the last three pitches your team gave to three genuinely different buyer types for the same product line. Line them up next to each other. If they read the same, the value proposition isn't failing because the product is weak. It's failing because nobody built three propositions where the market needed three.
Key takeaways
A value proposition built from product features invites a spec-sheet comparison, and that comparison ends in price almost every time, regardless of how differentiated the product actually is.
Serving genuinely different buyer types with one identical pitch isn't efficiency. It collapses three different value questions into one answer that satisfies none of them.
Proof points, language, and sales motion all need to differ by buyer type. Fixing only one of the three still leaves the pitch too thin to hold price.
The RFP stage is usually too late to make the value case. By the time procurement writes the spec, the comparison has already been reduced to a checklist.
Auditing the last three pitches given to three different buyer types is a faster diagnostic than any positioning workshop. If they read the same, that's the problem.
FAQ
What does it mean to build a value proposition at segment level? It means starting from how a specific buyer type experiences value, rather than from a single description of the product meant to serve every buyer at once. Different buyer types weigh cost, risk, and performance differently, so the proposition that holds price for one will often fail to hold it for another.
Why does a feature-based value proposition lead to price competition? Because it hands the buyer a checklist. Once a product is described in terms of its features, it can be compared line by line against any competitor, and that comparison almost always defaults to price, even when real differentiation exists elsewhere.
How many different value propositions does a company actually need? As many as there are genuinely different buyer types with different decision drivers, not as many as there are products. A single product range can require two or three distinct propositions if it serves buyers who evaluate it on fundamentally different terms.
What's the difference between a value proposition and a sales pitch? The proposition is the underlying claim about why a specific buyer should pay what's being asked. The pitch is how that claim gets delivered, and it needs to change by buyer type even when the underlying proposition doesn't.
When should the value case be made to a buyer? Before the formal comparison starts, not during it. Once an RFP or a spec sheet exists, the conversation has already been reduced to a checklist. The value case needs to shape how the buyer defines what they're comparing, not just respond to it after the fact.
