Why Buyers Understand Your Product but Cannot Explain Its Value
Buyers can describe a product yet fail to explain its value when one link is missing: what it replaces, what it does that the replaced option cannot, what that changes in a measure the approver already tracks, or proof from the buyer's own operation. This applies to founders near launch whose champions stall at the approver. Have buyers retell the pitch, find the first missing link and fix only that. A few retellings give a judgment, not a statistic.
The symptom and what it does not prove
The symptom is specific. In the call the buyer follows the demo, asks sensible questions and can say what the product does. Then the deal stalls at the person who approves the spend, or the buyer's own summary comes back as a list of features. The buyer understood the product. What failed is the explanation the buyer has to give to someone who was not in the room.
This guide is for founders before or around launch who already have interested buyers and keep seeing that pattern. Choosing the alternative to compare with is covered in How to Position a Startup Against the Customer Current Alternative, filling in a full positioning sheet in Positioning Worksheet: Category, Difference, and Buyer Value and testing a finished sentence in How to Test Positioning in Real Sales Conversations. This page diagnoses which part of an existing explanation breaks when the buyer retells it, and what to fix first.
The symptom does not prove that the product is unclear, that the buyer lacks the problem or that the pitch needs more features. It does not prove demand either. If nobody with a budget owns the problem, the stall comes earlier and has a different fix, described in When Customer Interviews Say Yes but Nobody Buys. Rule that out before working on the explanation.
Two research findings explain why founders miss the gap. Camerer, Loewenstein and Weber, in a 1989 paper in the Journal of Political Economy that names the curse of knowledge, write that 'better-informed agents are unable to ignore private information even when it is in their interest to do so'. Their introduction gives sellers as an example: 'sellers are better informed about the true value of their products than buyers'. A founder hears the value in every sentence of the pitch because the founder already knows it. The paper compares individual judgments with market experiments and does not study sales conversations, so read it as a direction, not a measurement.
Shafir, Simonson and Tversky propose in a 1993 paper on reason-based choice in Cognition that 'when faced with the need to choose, decision makers often seek and construct reasons in order to resolve the conflict and justify their choice, to themselves and to others.' A buyer who has to win over an approver needs a reason that survives being retold. A list of features is not one.
Check current customer alternative
Run the diagnosis on the buyers' words, not on your own reading of the pitch. After a call that went well, ask the buyer how they would explain the product to the person who approves the spend, and write the answer down as spoken. Digital.gov's guide to paraphrase testing says to ask participants 'to tell you in their own words what that section means' and warns that questions answerable with a yes or no give little usable information. The guide is written for documents and web pages, so using it on a sales explanation is an adaptation.
Read each retelling for four links, in order. The first is the comparison point: what the buyer says the product replaces. A retelling with no 'instead of' leaves the approver to choose the comparison, and nothing stops the approver from choosing the cheapest option already in sight. The comparison point is missing or wrong when the retelling:
- describes only what the product does and names nothing it replaces;
- names a rival or a free option the account does not actually use;
- names what the approver sees, such as a supplier's free service, instead of the work the team does today.
The fix is to name the alternative seen in use and the person who carries its cost, and to open the explanation with it. The buyer then has something concrete to compare against before hearing what is new.
Investigate meaningful product difference
The second link is the difference: one thing the product does that the alternative cannot. Buyers who understood the demo often retell a list of features instead. A feature list gives the approver no reason to choose, and a difference the alternative shares gives a false one. The difference is missing when the retelling lists several features with equal weight, or names something the current alternative also does.
The third link is value in the approver's measure: what the difference changes in a number the approver already tracks, such as crew days, staff hours, missed orders or write-offs. Retellings that miss this link stop at 'it saves time' or 'it is more efficient', or name a measure only the user cares about. Daniel's go-to-market page says, in a list headed 'Where founders get go-to-market wrong': 'Pricing from cost rather than from what the buyer's problem is worth.' The same gap shows up in explanations: a buyer who cannot say what the problem costs in the approver's measure cannot say what solving it is worth.
The value link is missing when the retelling has no measure, uses a measure the approver does not report on, or gives a number the buyer cannot explain. The fix is to find the measure the approver reports on and size the change in it, with every input written out and tagged as counted or assumed.
Fix the gap in proof the buyer understands the offer
The fourth link is proof the buyer can carry into the approver's office: something from the buyer's own operation, such as a count from the buyer's site, a dated record, a demo on the buyer's own data or a paid pilot. A retelling can contain the first three links and still stall because the buyer has nothing to show. Another customer's figures are weaker for this purpose, because the buyer cannot vouch for them.
Fix the first missing link and only that one. The order matters because each link depends on the one before it: a difference only means something against a named alternative, value is the size of that difference in the approver's measure, and proof backs the value. Changing all four at once leaves no way to tell which change worked.
The explain-back gap grid
Copy this grid into a document and code every retelling against it, link by link, as present or missing. Keep the buyer's words next to each code.
| Link | Present when the buyer says | Missing when the buyer says | Likely cause | Targeted fix | Signal the fix worked |
|---|---|---|---|---|---|
| Comparison point | Instead of what the team does today, named | Only what the product does, or a rival the account does not use | The pitch opens with the product | Open with the alternative seen in use and who carries its cost | Retellings name that alternative without prompting |
| Difference | One thing the alternative cannot do | A feature list, or something the alternative also does | Features listed in place of a difference | Cut to one attribute the alternative lacks that you can show today | Retellings name the same single difference |
| Value in the approver's measure | What changes in a number the approver tracks | 'Saves time', 'more efficient' or a measure only the user tracks | Value stated in the founder's or the user's terms | Size the change in the measure the approver reports on, with inputs written out | The approver's first question moves from why to how much or when |
| Proof the buyer can carry | Something from the buyer's own operation | Another customer's figures, or nothing | Proof chosen for the founder's deck, not for the approver | Collect a count, record or demo from the buyer's own operation | The buyer shows or forwards it to the approver unprompted |
Read the coded retellings before changing anything:
- One link missing in most retellings. Fix that link and keep the rest of the explanation as it is.
- Several links missing. Fix the earliest one in the order of the grid, because the later links depend on it.
- Retellings differ by role. The user and the approver may track different measures. Write the value link for the approver.
- All four links present and the deal still stalls. The explanation is probably not the problem. Look at price, timing and who owns the budget.
A hypothetical example: lumber for small home builders
The following is a hypothetical example with invented details. It illustrates the diagnosis and does not describe a real company, customer or measured result, and it is not guidance on construction, lumber handling or site safety.
A founder offers sequenced lumber delivery to small home builders. The founder's company collects a house's full order from the lumber yard, stores it and delivers each day's boards in the order the crew will use them, at an intended $1,200 a house. On visits to 8 building sites, the founder sees the lumber yard's whole order dropped at once beside the house, and at one site at 7 a.m. finds three framers bent over the stack in the wet yard, sliding boards apart to find the lengths for the day's first wall. Six of the 8 site leads say the service makes sense. None of their builders, who approve the spend, agrees to a trial.
The founder asks the 6 site leads to explain the service as they would to their builder and writes each answer down as spoken. All 6 can say what it does: the wood comes in batches. The founder codes the retellings against the grid:
| Link | Retellings with the link | What the site leads said |
|---|---|---|
| Comparison point | 1 of 6 | 5 compared it with the lumber yard's free delivery and 1 with the crew sorting the stack |
| Difference | 4 of 6 | 'It comes in the order the crew uses it' |
| Value in the builder's measure | 0 of 6 | 4 said it saves the crew time and 2 said nothing about value |
| Proof the buyer can carry | 0 of 6 | None had anything from their own site to show |
The first missing link is the comparison point. Five of the 6 site leads compared the service with the lumber yard's free delivery, so their builders heard a middleman charging for something they already get for nothing. The real alternative is the crew's morning at the stack, which the builder pays for and does not see.
The founder rewrites only the opening of the explanation around that alternative, then sizes the value in the measure builders track, crew days per house. At 2 sites the founder times the crew for a week: a crew of 4 spends about 50 minutes each morning at the stack before the first cut. Over a framing job of 15 working days, that is 4 people times 50 minutes times 15 days, or 3,000 minutes, which is 50 hours. With a crew day of 4 people for 8 hours, 50 hours is about a day and a half of the whole crew's time. At an assumed $35 an hour per person, the 50 hours cost $1,750 against the $1,200 price, a margin of $550 before any gain in schedule.
The new explanation reads: 'Instead of your crew sorting the stack each morning, each day's boards arrive in the order the crew frames, which on the 2 timed sites would free about a day and a half of crew time per house.' The founder asks 6 other site leads to retell it, with a pass line of 4 written in advance. Of the 6, 5 name the crew's morning at the stack as the comparison and 4 mention crew days, which meets the line. Two builders then ask what it costs per house, and 1 agrees a paid trial on one house with a start date. The proof link is still the founder's timing, not the builder's own, so the trial exists to count the crew's time on that builder's site.
The assumptions stay written down: that the morning at the stack takes similar time across a whole job, that the 2 timed sites are typical, that freed time turns into framing rather than waiting, that $35 an hour is the builder's real cost, and that 14 site leads say little about small builders in general.
Evidence that the targeted fix is working
Set the pass lines before the next batch of conversations and keep them with their date. Then look for these signals, roughly in this order:
- Retellings change. More buyers include the fixed link without prompting, in their own words.
- The approver's first question changes. It moves from why to how much, when or how.
- The buyer carries something. The sentence or the proof reaches the approver without the founder sending it.
- Someone with a budget takes a dated step. A nod from the user does not count. Running the calls themselves is covered in the guide to testing positioning in sales conversations linked above.
If retellings now contain the fixed link and nothing else moves, the next missing link in the grid is the one to work on. A correct retelling shows understanding, not demand, so keep counting dated steps separately.
Common mistakes and limits
- Rewriting the whole pitch. If one link is missing, a full rewrite hides which change mattered.
- Judging clarity from the founder's own reading. The founder already knows the value, so the pitch sounds complete to the founder.
- Asking whether it makes sense. A yes says little. Ask for the retelling.
- Value in the user's measure only. The person who approves the spend may track something else.
- Borrowed proof. Another customer's figures help, but the buyer cannot vouch for them in front of the approver.
The grid has limits. A handful of retellings gives a judgment, not a statistic. The research cited here comes from experiments on judgment and choice, not from business sales. The four links, codes and reading rules are an editorial framework, not a measured result.
Related guides and next step
- The wider sequence by stage: How to Build a Startup Go-to-Market Strategy by Stage
- Choosing the alternative to compare with: How to Position a Startup Against the Customer Current Alternative
- Filling in category, difference and value: Positioning Worksheet: Category, Difference, and Buyer Value
- Testing a finished sentence in calls: How to Test Positioning in Real Sales Conversations
Daniel's go-to-market page says the first session is free and takes 30 minutes. Book a startup mentoring session to review your startup positioning decision with your actual evidence and constraints, and bring the buyers' retellings written down as spoken.
Frequently asked questions
Why do buyers understand your product but cannot explain its value?
Because the explanation they would give someone else is missing a link: what the product replaces, the one thing it does that the replaced option cannot, what that changes in a measure the approver tracks, or proof from the buyer's own operation. Understanding what a product does is not the same as having a reason that survives being retold to an approver.
What evidence should a founder collect for startup positioning?
Retellings written down as spoken, from buyers asked to explain the product as they would to their approver; for each retelling, which of the four links it contains; the alternative seen in use and who carries its cost; the measure the approver reports on; and a count, record or demo from the buyer's own operation. Keep estimates labeled as estimates.
What are common mistakes in startup positioning?
Rewriting the whole pitch when one link is missing, judging clarity from the founder's own reading, asking whether the pitch makes sense instead of asking for a retelling, stating value in a measure only the user cares about, using another customer's figures as the only proof and treating a correct retelling as evidence of demand.
How can a founder tell whether a positioning fix is working?
Set a pass line before the next batch of conversations, then count how many retellings contain the fixed link without prompting. Also watch whether the approver's first question moves from why to how much or when, whether the buyer passes the explanation on unprompted and whether someone with a budget agrees to a dated next step.
Sources
- The Curse of Knowledge in Economic Settings: An Experimental Analysis (Camerer, Loewenstein and Weber, Journal of Political Economy)
- Reason-based choice (Shafir, Simonson and Tversky, Cognition)
- Paraphrase testing (Plain language guide series), Digital.gov
- Go-to-Market Mentor and GTM Strategy Advisor