TL;DR
- Five signals a proposal was dead on arrival: single-thread send, no mutual action plan, pricing/scope surprise, vague CTA, no "why now" in the doc.
- Deals with a mutual action plan close 2× more often than deals without one (GTMnow). 6–20 completed steps is the sweet spot.
- 80% of ghost rate is upstream. The 15-minute pre-send meeting fixes more of the silence than 10 post-send follow-ups ever will.
- Follow-up cadence: 5–7 touches over 14 days. Fewer than 5 leaves replies on the table; more than 7 becomes nagging.
- The day-14 breakup email converts ~30% of cold proposals. "Want me to pause and check back in 90 days?" is the highest-leverage line a rep can write.
Direct answer
Proposals get no response for five specific reasons: only one person saw the document, no mutual action plan existed when it went out, the proposal contained a pricing or scope surprise, the CTA was vague ("let me know if you have questions"), or the document did not name a "why now" reason to act this quarter. Most ghosted proposals trigger two or three of these at once, and the fix is almost always upstream — in the 15-minute pre-send meeting — not in the follow-up emails after.
What "no response to a proposal" actually means
If your proposals keep landing in inboxes and going silent, the issue usually isn't the document — it's what happened in the last discovery call and the fifteen minutes before send. Most reps assume the fix is a better-looking proposal or a more persistent follow-up, but the pattern across the deals we've reviewed is that proposal ghost rate is almost always set before the document goes out, in one of five upstream signals. This guide covers the five signals in order, the seven-block proposal anatomy that gets replied to, the fifteen-minute pre-send meeting that prevents most of the silence, and the 14-day follow-up cadence plus recovery moves for proposals that have already gone cold. By the end, you'll have a pre-send checklist you can run on tomorrow's proposal and a cadence template you can queue up for the deals that are already silent.
"No response" is not a mystery. It is a diagnosis. A proposal that goes cold almost always fails on one of five specific signals. Read the table against the last proposal that never came back — the signal will usually jump out.
| # | Signal | Tell | Primary fix |
|---|---|---|---|
| 1 | Only one person ever saw it | Email open count never climbed past 2 | Before sending, name 3 stakeholders and cc all of them |
| 2 | No mutual action plan existed | No date for the signed contract was ever agreed | Co-author a 6–12-step MAP in the meeting before send |
| 3 | The proposal landed with surprises | Champion goes quiet the day they open it | Walk the pricing + scope page-by-page on the pre-send call |
| 4 | Your CTA was "let me know" | You are the one chasing every follow-up | Replace with “can we get 20 minutes Thu to review together?” |
| 5 | No "why now" in the document | The deal has slipped 2+ quarters already | Add a ‘cost of inaction’ block tied to a specific event on their calendar |
Three patterns stand out. First, four of the five signals can be detected before the proposal ever goes out — which is why the pre-send meeting matters more than the follow-up sequence. Second, signal 1 (single-thread) is the most common and most fixable, but reps skip the cc list because it feels pushy. Third, signal 5 (no why-now) is the easiest to miss — the proposal reads fine on the day of send, and then every subsequent quarter it becomes easier for the prospect to defer.
Signal 1: only one person ever saw it
The most common reason a proposal gets no response is that nobody except the champion ever read it. The rep ran discovery with one person, built rapport with one person, sent the proposal to one person — and then that one person is too busy to forward it, too uncertain to sell it internally, or too junior to champion it past their VP. The deal was single-threaded the whole time; the proposal just made the bottleneck visible.
The tell is clean. Email-tracking shows 1 open. Maybe 2 if the champion forwarded it to one peer. The proposal sat in their inbox for 3 days, got skimmed once on a phone, and quietly aged out. Ninety percent of "no response" proposals trace back to a 1-open event that the rep only noticed on day 7 when following up felt awkward.
The fix is upstream. Before the proposal goes out, the rep should name 3 stakeholders and cc them on the send email. Champion (who ran the evaluation). Economic buyer (who signs the contract). One technical or functional counterweight (who would raise questions anyway — better to pull them in than let them object later). Per multi-threading research, proposals sent to 3+ stakeholders close at ~40%; single-thread sends close at 15% or lower. That gap is not a delta in rep quality — it is a delta in who was in the room.
Reps skip the cc because it feels presumptuous — cc-ing the VP when the champion is the point of contact can look like going over their head. The fix is a pre-send conversation: "For the proposal I want to make sure it lands with the right people. Usually I cc [finance + economic buyer + one other champion]. Does that match your team?" Asked that way, the champion usually nods and adds two more names — and the deal gets read by 4 people on day one instead of 1.
Signal 2: there was no mutual action plan
A mutual action plan is a co-authored list of every step from proposal-sent to contract-signed — owner, date, deliverable — visible to both sides. Its absence is the second most common cause of a ghosted proposal, and the easiest to fix. When a prospect reads a proposal without a MAP, they do not know what is expected of them next. The rep is hoping for "reply soon." The prospect is thinking "I'll get back to this when I have time." Both sides are waiting on each other; the deal stalls in that gap.
The data on this is concrete. Per GTMnow research, deals with a mutual action plan close roughly 2× more often than deals without one. The win-rate sweet spot is 6–20 completed steps — enough granularity to feel real, not so much it feels bureaucratic. Most reps skip the MAP entirely. The ones who build it on the pre-send call out-earn their peers by a margin wider than any coaching intervention can add.
A working 8-step MAP for a B2B SaaS deal: (1) proposal reviewed by champion + economic buyer; (2) security review kickoff with buyer IT; (3) technical validation call with SE; (4) pricing + scope sign-off meeting; (5) legal redlines exchanged; (6) procurement sign-off; (7) contract countersigned; (8) kickoff scheduled. Every step has an owner on both sides and a target date. The rep and the prospect co-author the document. It sits in the proposal or in a shared link, visible whenever either side wants to check status.
The reason MAPs work is removal of ambiguity. The prospect does not have to guess what is expected — it is written. The rep does not have to guess what is blocking the deal — when a step slips, it slips visibly, and the conversation is "this step is blocked, what do you need?" instead of "did you get a chance to look at it?" Deals with visible next steps stall 40% less often than deals without them.
Signal 3: the proposal landed with surprises
A proposal should never contain a surprise. Pricing, scope, implementation time, contract length, integration complexity — every material term should have been named and confirmed on a call before it appears in the document. When the proposal arrives with a number or scope detail the prospect has not seen, the call goes quiet — usually forever, because the champion now has to explain to their team why the rep quoted a different number than they thought.
Pricing is the most common surprise. The rep said "starts around $X" on the call; the proposal lands at $X + $Y + $Z in add-ons. The champion, who was pitching "around $X" internally, suddenly cannot defend the number. They go quiet. The proposal dies. The rep, a week later, wonders why a deal that felt warm went cold — without realizing pricing surprise was the quiet drag on the deal.
Scope surprise is the second flavor. The rep assumed "we will start with phase 1" means one thing; the prospect had a different phase 1 in mind. The proposal scope section does not match what the champion had been selling internally. Same outcome: silence, then death. Implementation timelines are the third flavor — a proposal that says "go-live in 12 weeks" when the prospect expected 4 weeks triggers an internal renegotiation the rep never sees.
The fix is the pre-send call, specifically the walkthrough of the pricing page and the scope page. Not "I will send the proposal, let me know if you have questions." Instead: "I want to walk the pricing and scope pages together before I send so there are no surprises for your team." Fifteen minutes. Every surprise gets caught and renegotiated on the call, not in the dead silence of a week-long non-reply. The proposal then arrives as a document the champion can already defend internally, because they already saw and approved it.
Signal 4: your CTA was “let me know if you have questions”
"Let me know if you have questions" is the worst CTA in B2B sales. It is a polite way of saying "I have no idea what happens next." Vague asks get vague replies — or no replies at all. The prospect is busy. "Let me know if you have questions" asks them to do the work of scheduling the next step; they almost never will.
A good proposal CTA is specific on three dimensions: who, when, and what. Who: the specific stakeholders. When: a specific date with two options. What: a specific agenda for that time. The template is "Can we hold a 30-minute review with [champion + economic buyer + technical eval] on [Tuesday 3pm or Thursday 11am] to walk the proposal together?" Reps who replace "let me know" with that exact template see their proposal reply rate jump 2× in the first 30 days.
Two variations by deal stage. If the prospect has not seen any pricing yet, the CTA is "Can we hold 20 minutes on [date] to walk pricing live together?" — a small ask that drives a specific outcome. If pricing has been seen and the deal is ready for signature, the CTA is "Can we hold 30 minutes on [date] for contract redlines with legal on your side?" — an explicit move toward close. A specific CTA does two things: it tells the prospect what the rep expects, and it reduces their cognitive load by offering date options instead of asking them to figure one out.
The common rebuttal: "What if they are not ready for that? I do not want to pressure them." The reality is the opposite — a vague CTA leaves the prospect adrift and they mark the email as "later." A specific CTA gives them a reason to reply, even if the reply is "not that date, how about next week?" Any reply beats silence; a specific CTA produces specific replies.
Signal 5: no "why now" inside the document
The quietest ghost driver is the missing "why now." A proposal that describes what the product does and how much it costs, without naming why this quarter matters, is a proposal that reads fine today and gets easier to defer every week. No urgency means the prospect rank-orders it behind whatever is in front of them that afternoon — which is usually not a $50K B2B SaaS decision.
"Why now" is not a manufactured deadline or a fake discount clock. It is a specific event on the prospect's own calendar that makes this quarter different. Examples that work: "You are hiring 3 AEs in Q3 — the cost of onboarding them without a workflow tool is roughly $60K in ramp time." "Your enterprise contract renews in 90 days — the analytics gap you described will cost you one multi-year expansion if unaddressed." "The RevOps lead you hired last month starts Q2 looking for tooling to own — this is the first tool decision on their roadmap."
A "cost of inaction" block in the proposal makes why-now visible. Three lines, under the scope section: "If this is deferred by 90 days, [specific cost]. If deferred by 180 days, [larger cost]. If solved in the next 30 days, [specific opportunity]." The numbers come from the discovery call, in the prospect's own words. A proposal with a cost-of-inaction block extends deals 30 days less than one without, on average, because the prospect's own math is sitting in front of them every time they open the doc.
The test: read the proposal out loud and ask "why should they sign this quarter instead of next?" If the answer is only "because we quoted this price this quarter" — it is a weak why-now, and the deal will slip. A real why-now has to pass a 10-second smell test from the prospect's finance team; it ties to something already on their calendar or budget. For more on building urgency upstream, see why 'not a priority right now' keeps shelving deals.
The proposal anatomy that gets replied to
A proposal that gets replied to is not a longer proposal or a prettier one. It is a proposal with 7 specific blocks in a specific order, each doing one job. Top reps use this anatomy across deal sizes; the only thing that changes between SMB and Enterprise is the length of each block, not the structure.
| Block | Purpose | What goes in it |
|---|---|---|
| 01 · Why you | Anchor the proposal in the specific pain you heard. 3–5 sentences. | Rephrase the pain in the prospect’s own words. Name the 2 specific quotes from discovery. Skip the company boilerplate. |
| 02 · What changes | State the outcome, not the feature. | A 2-column before/after grid. Current state, post-implementation state. 6 rows max, measurable outcomes only. |
| 03 · Scope | What you will deliver, in what order. | Phased scope. 3–5 phases with dates. Each phase names the buyer output, not the rep output. |
| 04 · Investment | The price, with context. | One number per plan. Show ROI math one level up from the number — "this pays back in Q2 at current close rate." Never bury pricing on page 12. |
| 05 · Timeline | Walk the deal from signature to first value. | Kickoff → integration → onboarding → first value. Dates. Owners on both sides. 7–14 day steps max. |
| 06 · Mutual action plan | What both sides do next. | The MAP. 6–12 steps with dates, owners, and checkboxes. The single most underrated part of a proposal. |
| 07 · Specific ask | One concrete next step. | "Can we hold a 30-minute review with [champion + economic buyer + technical eval] on [date + 2 options]?" |
Three things separate a strong proposal from a weak one. First, length discipline — under 8 pages for SMB, under 16 for Enterprise. Every extra page dilutes attention; most ghosted proposals are longer, not shorter, than they should be. Second, pricing on page 2, not page 12 — burying pricing looks evasive and signals the rep does not trust the number. Third, a specific next step on every final page, not a generic signature block. "Can we hold 30 minutes [date] to review" beats a PandaDoc signature request every time.
The proposal is a document the champion has to sell internally. Its job is to be easy to defend in a 10-minute conversation the rep will never be in. Every block should answer the question the champion's VP will ask: "why this, why now, why this price, what happens if we wait?" If the champion can copy-paste three sentences from the proposal into a Slack message and it reads as a compelling case — the proposal is doing its job.
The 15-minute pre-send meeting that removes most ghost rate
The single highest-leverage meeting in the whole sales process is the 15 minutes before the proposal goes out. Most reps skip it because it feels redundant — "I'll just send the doc, it is all there." That redundancy is exactly what makes it work. Walking the pricing and scope pages live removes a large share of the ghost rate in our experience, because every surprise that would have stalled the deal gets caught on the call instead of in silence.
| Time | Goal | Script |
|---|---|---|
| Minute 0–3 | Re-frame the pain | "Before I send the proposal — just to lock the framing: when we last spoke you said [specific quote]. Is that still the top priority this quarter?" |
| Minute 3–7 | Walk the scope page | "On the scope page — I have us starting with [phase 1] in week 1. Does that match what you had in mind, or should we front-load [phase 2]?" |
| Minute 7–11 | Walk pricing + ROI math | "Plan is $X per month. Your current spend on [problem] is $Y. The ROI math as I read it is [Z months payback]. Does that math hold up on your side?" |
| Minute 11–14 | Lock the MAP | "I have 8 steps from here to signed contract — owners on both sides. Can we agree to these dates now so the proposal lands with the plan baked in?" |
| Minute 14–15 | Confirm the distribution | "Who else should I cc when this goes out? Usually [finance + economic buyer + one extra champion] — does that match your team?" |
The pre-send meeting does five things in 15 minutes: re-confirms the pain is still the pain, catches pricing surprises, catches scope mismatches, co-authors the MAP, and locks the distribution list. Each of those kills one of the five signals in the diagnostic. Run this meeting on every proposal worth more than the cost of 15 minutes of the rep's time — which, for any deal over $15K ACV, is every proposal.
