Most proposals don’t get rejected. They go quiet.
Run back through the deals you have lost. A few were clean: a decision against you, a budget that evaporated, a client who chose another path. The rest were quieter. The client was warm on the call, said send it over, and then the thread cooled and stayed cool. Nobody decided against you. The decision just never got made.
That pattern has a name in buyer research: indecision, not rejection. One analysis of B2B sales conversations, from Matthew Dixon and Ted McKenna at Harvard Business Review, put the share of deals “lost to customers who express their intent to purchase, but ultimately fail to act” at between 40% and 60%. The clock matters too, because the panic runs on a timeline that does not match how the work closes. Surveying mostly small and midsize agencies, RSW/US found sales cycles average between one and six months from first meeting to close; Promethean Research puts the average at 4.4 months. Two weeks of silence sits comfortably inside that window. Reading it as a “no” is reading noise as signal.
So sort every losing deal into one of three boxes. They feel identical from where you sit, because all three end with no signed proposal, but they are three different failures. The first is the stall: the client neither accepts nor declines, the internal conversation never happens, and the deal dies of neglect, often inside the client’s own organization. Karl Sakas, writing about ghosted proposals, lands on the same read: the prospect “wasn’t really ready to buy.” Live pushback on price, scope, timing, or authority is an objection; it is information, where silence is its absence. And then there is the explicit no: a qualified buyer chose another path or the project got killed. That one is over.
A win, by contrast, is an event you can point to: the client accepts and signs, and you have a locked record of the “yes.” A stall is the absence of any event at all, which is why it is so easy to misread. Collapse all three into “I lost the deal” and you respond wrong to at least two of them, re-pitching a client who needed internal ammunition or discounting one who never had a price problem.
| Loss type | What it looks like | Right response |
|---|---|---|
| Stall | Silence after a warm call. No event at all. | Re-engage. Arm your contact for the internal conversation. |
| Live objection | The client pushes back on price, scope, or timing. | Address what is underneath the objection, not the proposal. |
| Explicit no | An explicit decline from a qualified buyer. | Ask why. Keep the relationship warm. |
These patterns appear under different search terms. A lost proposal that ended without a word is usually a stall. Proposal rejection, where a qualified buyer chose against you, is the explicit no. Proposal objections mid-deal are the third box. Whether the question is why clients reject proposals, why clients go silent on a proposal, or what drives proposal decision making on the client’s side, the answer starts with the same sort: which of the three boxes does this deal fit?
The reason you can see is usually downstream of the cause that lost the deal
Price is the cause sellers reach for first. Blair Enns names what “too expensive” means: “Price objections are really value objections, and the formula for value is quality divided by price.” The person controlling the budget was not convinced the work is worth it, which is a value problem wearing a price costume. The number on the page did not lose; the case for the value did, or it never reached the person who needed convincing.
Length, design, and the executive summary are the same kind of scapegoat. They are the easiest things to blame because they are the only things you fully control. The causes that lose deals are the ones you cannot see from your desk.
Two failures are the hardest to see coming: you were talking to someone who could say “no” but not “yes,” and your contact either could not or would not carry the deal inside their own building. The fight that kills those is often one you never witness.
- Bad timing. The budget got pulled into a launch, a priority shifted, a quarter ended.
- Unqualified from the start. Brennan Dunn qualifies before a proposal exists, “making sure they’re serious about the project and have a budget that we’re willing to bite at.” Enns names the most common mistake in selling expertise as “the overallocation of resources against early-stage opportunities”: a full proposal for someone who was only browsing.
- Never opened. The emailed PDF sat unread. You cannot lose on price a document nobody scrolled to the pricing page of.
David Baker’s point about contracts applies here: the document confirms an agreement, it does not manufacture one. “The contract comes out once you have an agreement in principle.” If there was no agreement in principle, no amount of formatting was going to produce one. If your diagnosis lands on the artifact, that work lives elsewhere: sharpening the writing and scope is the subject of our guide on how to write a business proposal, and setting the number is the subject of our guide on proposal pricing.
How to tell which loss you have
The instrument that narrows the guess is the engagement signal: what the client did with the proposal after you sent it. A static emailed PDF or a Word attachment gives you none of that, which leaves you diagnosing blind and defaulting to the cheapest story on the shelf: “it was the price.”
Send the proposal from ProposalKit.io as a branded client link instead of an attachment, and the link records what happened on the other side: whether it was opened, how often, which sections held attention, and how long the reader spent before going quiet. You can see what that looks like on a live sample proposal. Read as interpretation rather than verdict, the signal sorts into a few patterns:
- Never opened (zero views, or only your own) points to delivery or targeting, not the proposal. The message went to spam, your contact got buried, or it reached the wrong person. The fix is getting the document in front of the right reader, not rewriting it; the branded link lets you regenerate and resend for exactly the “are you sure they got it” moment.
- Opened once, then silence is the lowest-confidence read. They are aware, and that is all you know. Treat it as a prompt to re-engage, not a finished diagnosis.
- Multiple return visits focused on scope and outcomes, with no time spent on pricing, suggest the opposite of what the silence looks like: someone is building an internal case and is not yet sold enough to fight for the budget. Same silence, opposite diagnosis, opposite next move.
A read-through that ends in an explicit no is the most considered signal of the four. It earns a debrief, not a re-pitch.
Be precise about the limit. The signal narrows the diagnosis; it does not read minds, and it never predicts the outcome. At small deal volume, one deal is one data point against a months-long close, per Promethean Research. It is the instrument that makes a human diagnosis possible, not the diagnosis itself. The metric-by-metric depth is a separate subject, covered in our guide on proposal analytics; whether your overall loss rate is even abnormal for your volume is handled in our post on proposal conversion rate. If you sent a static document and had none of this signal at all, our guide on online proposal software covers how the category works and what changes when the client opens a link instead of an attachment.
When the deal went quiet: working a stall
The stall is the most recoverable loss, which is why walking away early is the expensive habit. The move is re-engagement that references their actual behavior. “Just checking in” signals nervousness and tells the client nothing. A message keyed to what the signal showed (“you spent some time in the scope section last week; happy to walk through how the two phases split if that helps make the case internally”) lands differently, because it is about their situation, not your inbox.
What senders skip is the internal fight. The stall often is not your contact’s “no.” It is a “yes” they could not get made. Your contact may want this and still be unable to move it past a skeptical partner, a frozen budget line, or a louder competing priority. So the job is arming the champion: a one-paragraph internal summary they can forward without rewriting, a clear answer to the predictable objection (why now, why this much, why you), and a reason this is the right quarter. You are not re-selling your contact. You are equipping them to sell it to people you will never meet.
Wording, cadence, and timing for a proposal follow up belong to our guide on how to follow up on a proposal. You cannot write the right follow-up until you have decided this is the loss you are working.
When the client pushed back: working an objection
When the client pushes back, you are in a stronger position than silence, even though it rarely feels that way. They are still talking, and the objection points at the blocker. The mistake, per Chris Do, is defending the proposal instead of addressing the thing underneath it.
Price. Do not reach for the discount. A price objection is one of three things. When the client does not yet see why the work is worth it, you remake the case; discounting in that moment confirms the doubt instead of resolving it. If they want it but the number does not fit their envelope, re-scope to what the budget buys. Walking without resentment is the move when the money is not there at any version worth your time. Chris Do’s framing holds across all three: “When a client pushes back on price, they are asking you to absorb their risk.” Enns’s value formula is the test: is the problem the quality they perceive, or the price relative to it?
Scope. A scope objection is often the client telling you what they want, which is more useful than what you assumed in discovery. Re-scope to theirs instead of arguing them back to yours.
A “not now” from a qualified buyer is worth keeping warm. Agree on when “now” is and put a firm date on the calendar instead of a vague “circle back.” If the objection keeps deferring to someone not in the conversation, you are talking to the wrong person, and no amount of polishing fixes that. Get to whoever can say “yes,” ideally with your contact’s help rather than over their head.
The money depth, how to set and hold a number, lives in our guide on proposal pricing, and for project-based creative work in our guide on how to price a creative project proposal. Here the job stops at the deal: name the blocker, then hold, re-scope, or walk.
The explicit no: closing out a loss without wasting it
Some losses are final, and pretending otherwise wastes them. A qualified buyer made a considered decision, the budget got cut, or they chose another path. The worst response is a sales push that turns a clean “no” into a closed door you might have wanted open later.
Do two things instead. Ask the one question worth asking: “For my own learning, what tipped the decision?” Then take the answer at face value and do not litigate it. Sometimes it is useful (“the scope felt too big for a first project together” is feedback you can act on next time); sometimes it is polite cover, and that is fine. Second, keep the relationship warm without hovering. Cycles run for months, per RSW/US and Promethean Research; today’s “no” from a qualified buyer is sometimes next year’s “yes,” when the budget refills or the path they chose disappoints them. A short post-proposal analysis checklist, run after every deal won or lost, keeps that pattern visible instead of relearned from scratch.