Lost quotes: understand rejections without cutting prices

Before analysing the reasons, check what actually happened. A prospect who writes “we have chosen another agency” has communicated a decision. Someone who says “the project is waiting for the next budget” is describing a postponement, although its date may remain uncertain. Someone who does not reply has given you no explanation. Putting all three situations into a single “too expensive” column creates information you do not have.

For a small agency, start with four statuses: won, confirmed loss, postponed, and no known decision. Add the date of the last verified fact and a sentence explaining the classification. You can remove an old opportunity from your forecast without knowing why it did not progress. Your management rule and your knowledge of the reason are two different things. Keep that distinction visible in your table.

Define the scope of the review as well. You might examine proposals sent for the same service over a particular period, rather than every sales conversation. An enquiry that never led to a quote should not become a lost sale simply because its label changes. Equally, a proposal sent to several locations within one group does not necessarily represent several independent decisions.

Your first action is to reread the correspondence around each case, not to send a new campaign. Correct duplicates, identify superseded quotes, and keep the last version that was actually considered. If the decision is unknown, write “unknown”. An incomplete but honest table is more useful than an apparently tidy list built on assumptions.

The central worksheet for this method uses one row per decision, with a little room for notes. It replaces neither your invoicing tool nor your contract records. It answers a specific question: what have we understood well enough to improve our next proposal? The following fields can sit in a private spreadsheet or a tool you already use, without another subscription.

Add an owner and a review date only where an action exists. A review of rejections does not need to become a second, cumbersome CRM to maintain. Keep personal information to the minimum needed, within your authorised professional environment. For team discussions, use internal references and anonymised examples rather than screenshots containing a prospect’s contact details.

Finally, separate a short quotation from your interpretation. “We chose someone who could start on Monday” is a reported fact. “We must recruit immediately” is one possible conclusion, but far from the only one. Better planning, a partner, or accepting that a project is not a fit could address the same problem. The worksheet should preserve that freedom to decide.

If the prospect has announced a decision and further discussion remains appropriate, you can invite brief, optional feedback. Make the purpose clear: understanding, not negotiating under the cover of research. Do not make the quality of your response depend on whether they accept an interview. Thank the person for communicating their decision even when they have nothing to add, and respect a refusal to continue the conversation.

Here is wording to adapt to an existing professional relationship: “Thank you for letting us know. To improve our future proposals, would you be willing to tell us which factor mattered most in your choice? A short answer is enough, and there is no problem if you would rather not go into detail.” This template is not permission to message any address. Use it thoughtfully, in the context of the particular case and the rules that apply to your relationship.

If the person replies, start with what they explain. You can ask which part of the proposal was difficult to assess, what should have been clarified earlier, or whether the schedule had changed. Avoid a list of answers that suggests your own theory: “It was the budget, wasn’t it?” A leading question often produces polite agreement rather than additional information.

Take notes after the exchange rather than automatically recording the conversation. Do not ask for a competitor’s confidential quote. A general description may be enough: included support, starting date, or number of deliverables. If you receive no feedback, keep the reason unknown. Do not organise repeated follow-ups simply to complete your spreadsheet: the prospect’s right to end the discussion comes before your analysis.

A reference to price does not yet tell you what decision to make. The prospect may have a firm spending limit, may not understand part of the service, or may be comparing your proposal with a different solution. Bpifrance Création explains that price objections can cover several situations. This resource, checked on 31 October 2026, encourages clarification rather than treating every objection in the same way. It cannot tell you why your own proposals were rejected.

Return to your document and check the elements the client could actually compare: delivered outcome, content they must supply, number of revisions, training, follow-up, responsibilities and availability. Two prices are not comparable if one includes copywriting, migration and support while the other covers layout alone. But a more comprehensive service is not automatically better: the client may need less.

Then ask a separate internal question: can you deliver this service properly at the price being considered? Count production time, discussions, checks and costs directly associated with the work. Include your own constraints rather than importing a margin presented as universally appropriate. A discount that makes the work unsustainable does not become sensible because it improves your acceptance rate.

You might simplify the scope, explain it better, or target a different type of client. You might also change nothing when a need does not fit your business model. The aim is not to win every quote. It is to avoid rejections that your process causes unnecessarily, while retaining a service you can actually deliver.

Group decisions by sufficiently similar services and circumstances. A website build, a one-off consultation and a maintenance subscription involve different purchases and different decision-making efforts. A personal recommendation and an approach without an existing relationship also start from different levels of trust. Mixing everything together can lead you to blame the quote for a targeting problem or a project that was not ready.

For each group, display raw counts before percentages: proposals considered, confirmed decisions, wins, rejections, postponements and unknown outcomes. If you calculate a rate using known decisions, explicitly name that denominator. Do not present it as the success rate of all your proposals. A case with an unknown decision should not quietly disappear from the commentary.

In a purely fictional example, an agency has ten comparable proposals: three won, two rejected, three postponed and two with no usable response. Of the five firm decisions, three are wins. That fraction does not describe the outcome of all ten proposals. The postponed projects might proceed or not, and the silence remains unexplained. Publishing a flattering percentage without these counts would make the review less useful.

A small number of cases mainly helps you identify questions to investigate. A single comment can reveal a concrete error, such as a broken link in a quote. It is not enough to prove that your entire market wants a different offer. Read directly observable defects separately from supposed trends. Fix the former where appropriate; test the latter cautiously.

A drop-down menu makes classification easier, but it does not verify the reasons. In documentation checked on 31 October 2026, HubSpot describes a loss-reasons report based on closed-lost deals and the corresponding property. That describes how a report works, not the reliability of every recorded answer. Your tool can produce an accurate chart from poorly completed categories.

Keep your list of reasons to understandable categories, supported by a source and a short comment. Examples include an incompatible schedule, unsuitable scope, a stated budget shortfall, another solution chosen, an abandoned project, or an unknown reason. Allow a main reason and a qualification rather than ten boxes ticked for one case. The label “another solution” does not authorise you to invent a competitor or their prices.

During the review, choose a few cases and check whether two people would classify them in the same way using the same correspondence. A disagreement often reveals a vague field. Clarify its definition before comparing results between salespeople. The exercise must not become a search for someone to blame: if every rejection feels like a personal failure, recorded reasons may serve self-defence rather than understanding.

If your forecast contains cases whose outcomes are unconfirmed, distinguish this work from our method for making sales forecasts more reliable in your CRM. Forecasting helps you decide what may plausibly happen next; reviewing rejections helps you learn from past decisions. The two approaches complement each other without requiring the same evidence.

A useful review ends with a testable decision, not a long list of recommendations. Describe the observed problem, the proposed change, the cases it applies to, and the sign that will help you assess it. Keep a point of comparison: the previous document version, a reference period, or similar examples. You do not need to describe a small trial as a perfectly controlled scientific experiment.

If several prospects say they cannot understand the difference between two packages, your trial could be a clearer comparison page. If they mention an incompatible date, you could communicate availability earlier. If a proposal arrives before anyone has discussed the budget, change the initial scoping before changing the price. Each action should address the problem actually observed, not the easiest symptom to measure.

Also write down what will stay unchanged during the trial. If you simultaneously cut the price, add a guarantee, change your target market and replace the document, you will not know what mattered. In a small business, low volumes already make comparisons fragile. Reducing the number of changes at least helps you maintain a readable account of what happened.

Choose a review point suited to your sales cycle: after a few comparable proposals and their decisions, rather than an arbitrary date that comes too soon. Examine understanding, questions received, preparation effort and known outcomes. Improved clarity can be useful even without an immediate increase in signed contracts. Conversely, more contracts are not enough if you have sold work that is impossible to deliver.

Imagine a small agency proposing website redesigns to local businesses. This case is entirely fictional; it represents neither a SprintLead customer nor a measured result. The team rereads three confirmed rejections concerning the same package. In two exchanges, the prospect explains that they did not know who was supposed to write the copy. The third chose a provider who could start sooner. None of these comments proves that the price was too high.

The worksheet separates the decisions. In the first two cases, the observed problem is a responsibility that was insufficiently understood. In the third, it is a schedule incompatible with the stated need. The agency does not group all three rows under “lack of value”: that label would be too broad to guide action. It also keeps silent cases in a separate category.

Its first trial is to add a short section to the next proposals: content supplied by the client, content produced by the agency, approval required, and the consequence of a delay in providing material. It discusses these points before sending the document. It keeps the same price and target audience during this test rather than changing every condition at once.

The review is not limited to signatures. The team notes whether the prospect can explain who prepares the copy, whether questions remain, and how long the explanation takes. If the document is understood but the actual need is for a lighter service, a second experiment could explore a different package. The initial rejection thus becomes a question about offer design, without an immediate discount or a promise of conversion.

The first mistake is looking only for rejections that confirm your intuition. If you believe prospects always want a lower price, you will mainly notice comments about budget. Reread won proposals and positive feedback about clarity or support as well. The same feature may be useful to one audience and unnecessary for another. Your decision may concern the segment, not the overall quality of your service.

The second mistake is confusing an absence of evidence with evidence of absence. A prospect does not necessarily mention everything that influenced their choice. A friendly answer can still be incomplete. Record this limitation without routinely suspecting the person of lying. You are looking for information useful enough to act on, not complete access to a decision that belongs to someone else.

The third mistake is turning the review into another sales funnel. Requested feedback must remain optional; a refusal or objection to further contact should not become a follow-up task. Do not publish recognisable details of a lost project to defend your work. Discuss methods internally using minimal data, and obtain the necessary permissions before publicly reusing a testimonial.

Finally, do not let rejections consume all your sales time. A short, regular review is enough if it produces a precise change or a deliberate decision to change nothing. Your goal remains serving clients who fit your offer. Learning from a lost sale is useful; rebuilding your business after every “no” can make it inconsistent.

Before returning to new opportunities, summarise the review in a decision sheet: what we observed, what remains unknown, what we will change, what we will keep, and when we will reconsider the choice. Someone should be able to understand it without attending the whole discussion. Keep useful examples but remove details that do not clarify the action.

This analysis starts after a commercial decision. It does not replace earlier checks of the client’s identity, the people involved and the scope. For that preliminary work, use our guide to checking a new B2B client before preparing a quote. A process can be sound before sending a proposal and still produce normal rejections: no proposal suits everyone.

When the review mainly reveals a mismatch in targeting, return to your criteria for researching the next accounts. SprintLead’s Search and Qualification page describes selection and interpretation of signals upstream. Do not expect it to guess why a buyer declined: that knowledge comes from your exchanges and the available facts. No tool automatically turns a sales assumption into a certain explanation.

To start today, take a small set of comparable proposals, classify their outcomes, complete the worksheet and choose one improvement. If no reason is sufficiently established, your conclusion can be “document future cases better”. That is a valid decision. It protects your price and time from rushed corrections while creating the conditions for more reliable learning.