How to Find Out Why You Lost a Proposal

Ask, within a week of hearing no, in a short email that makes an honest answer easy: one or two questions, and no attempt to reopen the deal. Then record the outcome next to how the proposal was read. One explanation can mislead you, but the pattern across twenty losses will not.

Most people either never ask, because it feels awkward, or ask in a way that sounds like a second pitch. Both leave you guessing about the most expensive thing that happens in your business.

Why the reason you are given is rarely the whole reason

"We went with someone else on price" is the easiest thing for a client to say. It is impersonal, it ends the conversation, and it does not require them to criticise you. It is sometimes true. It is often a stand-in for something harder to say: the proposal did not address their real concern, the timing was wrong, or someone senior preferred another supplier.

A good loss email makes it easy to give the harder answer.

The loss email

Send it within a week, while they still remember the decision. Keep it short, thank them, and ask one or two specific questions.

Subject: Thanks, and one question

Hi Dana, thanks for letting me know, and for considering us. So I can improve, could I ask what made the difference? Was it mainly price, the approach, or something about timing? One line is plenty, and I will not try to change your mind.

The last sentence matters most. It tells the client the answer is safe to give.

Questions worth asking

If they are open to a longer answer, or a short call:

• What did the proposal you chose do better than ours?
• Was there a point where you started leaning the other way?
• If the price had been the same, would the decision have been different?
• Was there anything you expected to see in our proposal that was missing?

What not to do

Do not argue. "But our approach includes..." turns a learning conversation back into a pitch, and the client stops being honest.

Do not discount now. Offering a lower price after a loss tells the client your original number was padded, and it rarely changes a decision already made.

Do not ask for a call unless they offer one. An email is easy to answer. A meeting request is easy to ignore.

Proposals you lost without being told why

Many proposals are not lost with a no. They simply go quiet. For those, send a final email saying you will close the file unless the timing changes, and mark the proposal lost only if they confirm it. Otherwise file it without an outcome, so your record of real losses stays accurate.

For silent losses, the reading history is often the only explanation you will get: it was never opened, it was opened once and abandoned at the pricing page, or it was read closely and then stalled with no new reader. Each points at a different cause.

Find the pattern across the proposals you lost

One loss teaches you little. Twenty teach you a lot. Record every outcome, and look at what the lost proposals have in common:

• Never opened: a delivery or targeting problem, not a proposal problem.
• Abandoned at pricing: the price, or how it was presented, or the budget conversation you did not have.
• Read closely, never forwarded: it never reached the person who decides. See how to get your proposal in front of the real decision maker.
• Read closely and forwarded, then lost: a real contest you lost on substance. These are the ones worth a loss email every time.

Compare against the wins. If most of your wins were reread on a later day and most of your losses were not, you have learned something about when to follow up harder.

What this cannot tell you

Self-reported reasons are imperfect, and a small number of losses can mislead: three price losses in a row can be coincidence. Reading data shows behaviour, not reasons. Treat patterns as hypotheses to test on the next proposals, not conclusions.

Where Closewatch fits

In Closewatch you mark each proposal won or lost in one click, and the outcome sits next to its full reading history: whether it was opened, what was read, how long on pricing, whether it reached a new reader. A deal that went nowhere without a decision can be archived instead, so it never counts as a loss. Closewatch does not yet turn those outcomes into a report for you; the history is there when you look. It is $19 a month, flat.

For what to send before a proposal is lost, see the proposal follow-up email templates.

Frequently asked questions

How do I ask a client why they did not choose my proposal?

Send a short email within a week of the decision. Thank them, ask one or two specific questions, such as whether it was mainly price, approach or timing, and say you will not try to change their mind. That last line makes an honest answer far more likely.

Should I ask for feedback after losing a proposal?

Yes, every time the proposal was genuinely considered. The feedback is the cheapest way to improve your next proposal, and asking gracefully leaves a good impression. Some clients come back later, and they remember who handled the loss well.

Why do I keep losing proposals on price?

Sometimes you are priced above the market. More often, price is the easiest reason to give, and the real issue is that the value was not clear, the budget was never discussed before the proposal, or the decision maker never saw the case for it. Talking about budget before writing the proposal fixes more price losses than discounting does.

What should I do after losing a proposal?

Thank the client, ask what made the difference, record the outcome, and look at how the proposal was read. Then compare it with your recent wins. The pattern across several losses is more useful than any single explanation.

How do I track why proposals are won or lost?

Record the outcome of every proposal, won, lost, or closed without a decision, together with the reason given and how the proposal was read. A spreadsheet works. A tracking tool that stores the outcome next to the reading history saves you from reconstructing it later.

New to proposal tracking? Start with what proposal tracking is and how it works, or try the proposal tracking demo on yourself: read a sample proposal, then see the report your reading produced.