A lost proposal: what to hear before deciding it was the price
Use a lost B2B proposal to understand the buyer’s comparison, evidence and next improvement.
Article language: English

In this article
“We lost on price” has one great advantage: it ends the discussion before anyone opens the proposal. The team can return to work, the competitor remains suspiciously cheap and the document needs no change. Sometimes price really is decisive. But you still need to hear what the buyer compared and why the chosen option suited the need.
A conversation after a decision can reveal the buying process, a moment of uncertainty or an explanation the company omitted. Its purpose is to understand the choice. If every answer makes the salesperson defend the offer, the buyer may switch to a polite account. Then you get a sentence to close the conversation, not material for improving the proposal.
First establish what actually ended
Imagine a website studio sent a proposal to an equipment manufacturer. Two weeks later it learns that the company chose another route. It does not yet know whether the buyer purchased a similar service, reduced the scope, postponed the project or decided to do part internally. This example is fictional. Each result needs a different interpretation.
Salesforce Revenue Insights documentation defines win rate as closed-won opportunities divided by closed opportunities, including wins and losses. That is a specific product's metric definition. The number describes results by category; it does not explain one buyer's decision. Keep the type of outcome in your record. No purchase differs from selection of a comparable supplier. Your own refusal to accept the scope is not an ordinary loss either. Connect the analysis with recognising a B2B assignment that does not fit (in Polish), so you do not improve sales of work the company does not intend to perform.
Before the conversation reconstruct your own process: which proposal version the buyer received, what questions were asked and what the company confirmed. You need not build an extensive dossier immediately. You do need a shared basis so questions do not rest on the memory of the most convinced person in the team.
Before selecting cases, check which offers enter the analysis. If you speak only to people who are easy to contact, different experiences may be missing. Keep a list of the types of cases invited and where no answer was obtained. A missing conversation remains missing knowledge rather than silently disappearing from the picture.
You can also compare selected wins of similar scope. This helps test whether a feature blamed for a loss was also present where the buyer purchased. It does not automatically establish that feature's effect. It can prevent one comment from becoming a ready explanation for every result.
Invite the buyer to a conversation with a clear purpose
Say you want to understand the choice and improve how the service is presented. The buyer may decline or share only part of the information. Do not make a calm end to the relationship conditional on a detailed explanation. The recipient is not obliged to conduct your internal sales review.
Clozd's win-loss interview guide, updated in September 2026, describes a flexible conversation with open questions and follow-up on what answers mean. It is a practice described by a provider of such research, not a guarantee of useful answers in every interview.
Choose someone able to listen without renegotiating the earlier proposal. Another person may help, but does not automatically make the interview neutral. A question about difficulty should not end with an explanation that the buyer misunderstood or should have chosen differently.
B2B customer-interview principles (in Polish) help keep the discussion tied to an event. Here the subject is a completed purchase decision about your own service, so there is an additional reference: the document actually received and the contact history. Ask about that material and actions rather than a general opinion of the company.
Reconstruct the comparison from need to choice
In the example ask: what problem was the project meant to solve? What options were considered? What mattered during comparison? When did uncertainty about our proposal arise? The answer may show that the buyer did not want a full rebuild, although that was what the studio proposed.
When someone says “too expensive”, ask for the point of comparison. Did they compare the same result and subsequent support? Did they need a smaller part? Was the reason for a particular stage unclear? The goal is not to prove the price right. It is to understand how cost was connected to the task.
A cheaper option may have included less work, which is exactly what the buyer needed. Or a necessary stage may not have been explained. Then the change concerns the construction of the offer (in Polish), not automatically lowering the price. If the buyer really chose a lower price for comparable scope, keep that finding too rather than inventing a more comfortable reason.
Do not request a competitor's confidential document. Ask about the kind of solution considered and the important criterion without collecting details the buyer should not disclose. Your analysis needs to understand the decision, not obtain the competitor's full terms. Keep missing detail visible as a limitation.
Ask when the choice took shape. A buyer may have assessed the main difference before receiving the formal proposal or only when discussing delivery. If uncertainty arose in the first conversation, a change only to the final PDF may arrive too late. If it arose in the detailed scope, a general website heading may not be the right place to clarify it.
Keep the order of criteria. A recipient may first compare the appearance of past work and later discover a need for data maintenance. Do not present the last argument as the sole need from the beginning. The change may reveal what the company should help buyers learn earlier.

The interviewee knows their part in the purchase
The contact may know the comparison but not every internal conversation. If they say “the team decided”, ask what was agreed and what their role was. You need not challenge their account. You do need to know whether it is their observation, a confirmed decision or an interpretation of others.
Keep the interviewee's words separate from your team's conclusion. “I did not understand who would change the data later” is specific. “Customers want full support” is a wider assumption. It may need comparison with other cases, particularly across different audiences.
Check whether questions about the same uncertainty appeared earlier. A customer returning with a similar question (in Polish) may leave a trace of an unexplained journey. If the buyer asked three times about website maintenance and the document still only named a general package, the contact history itself contains material for improvement.
Across several interviews look for a repeated sequence in comparable situations. Do not present three conversations as a representative map of the market. They may reveal a question worth testing or a problem visible in a particular segment. That is enough to prepare a small change and assess whether it helps.
After the conversation check notes against what was actually heard. Preserve context and agreed conditions when using a quotation. Do not present a paraphrase as a direct quotation. Readers of an internal report should see where the buyer's account ends and the team's inference begins.
If the buyer gave only a general reason, do not fill in detail from memory. Keep a hypothesis and identify material that needs another reading. An earlier question may contain important information, or it may remain unknown. An honest limitation is a better basis for improvement than a confident reason added afterwards.
Avoid embedding a diagnosis in the question. “Did we lose because the price was too high?” invites confirmation. Ask how the buyer compared options and what mattered about price or scope. It does not guarantee a complete answer, but leaves room for a reason the company had not considered.
If further questioning changes the buyer's own explanation, keep that path. The first sentence may have been shorthand and the detail may explain it. Do not select only the quotation most convenient for an internal presentation. A conclusion should reflect what could actually be established about the purchase.
Improve the explanation that mattered
In our studio, buyers may not recognise the difference between launching a site and ongoing data maintenance. The site can then identify the result, the company's contribution and handover conditions. A comparison of two services (in Polish) helps if it answers a real buyer question rather than comparing invented packages.
Aeneia Design helps organise an offer and its contact journey. A useful input is the actual passage the buyer did not understand and the question that arose during the purchase. The change can then explain scope or evidence where the recipient needs it before contact.
Use evidence for B2B claims (in Polish). If the buyer lacked proof of a specific capability, a stronger adjective is not enough. Material must answer the concern and describe its scope accurately. Sometimes the result is recognising that the company does not yet have the evidence.
Assess a content change against a specific question. The studio might show a revised description of data support to someone considering a similar service and check their understanding. This will not prove future sales growth. It can show whether the selected uncertainty from the described purchase has been reduced.
Do not turn conversations into another meaningless table
Reasons can be organised, but keep context. Two cases tagged “price” may need different actions: one compared equivalent scope, the other an unnecessarily broad proposal. If a tag replaces the description, the analysis returns to its starting point in a more colourful system.
This is a good time to examine metrics that begin to direct behaviour (in Polish). A count of interviews does not show whether the result affected an identified obstacle. A chosen change needs a reason, scope and a later way to assess it. Collecting quotations alone may not suffice for a decision.
Decide who will use the result. An unclear maintenance description may go to the proposal writer; a capacity problem to delivery planners. Not every finding calls for a website change. If the problem is the actual scope of work, editing must not conceal it. Identify the decision and the person with the knowledge needed for it.
After a change keep the reason and examine later similar cases. Buyers may still choose another offer while understanding yours better. That is a separate result and should not be confused with proven growth in wins. Analysis should distinguish clarified information from an unknown effect on purchase.
If a referral mattered, keep it as part of the buying journey. A B2B referral partnership (in Polish) can help explain how the recipient found the proposal and what expectation they already had. Do not attribute everything to the website or the last sales conversation. After a well-read loss, the company should know what it confirmed, what remains unknown and which single change is worth testing next.







