“Send me a proposal.” Those four words kill more deals than any competitor ever will. They sound like progress — the customer is asking for something specific, something formal, something that looks like a buying step. Often they’re the opposite: they’re the polite exit ramp.
Knowing the difference is a craft.
What “Send Me a Proposal” Often Means
Before you race back to the office to draft a document, consider what the phrase often actually signals:
“I need to look busy.”
The customer is evaluating three vendors to satisfy an internal process. You’re one of them. A proposal from you becomes file material, not a decision input. The customer has already decided — probably for internal build, or for the vendor they worked with before.
“I want to end this meeting politely.”
The conversation wasn’t going anywhere useful. Asking for a proposal is a soft way to give you something to do without committing to next steps.
“I need to justify this upward.”
The customer likes what you’re offering but can’t justify it without documentation. The proposal is real, but the request came before the conversation fully surfaced the objections you’d need to handle in the document.
“I want to compare pricing.”
The customer is using your proposal to pressure an incumbent vendor or to benchmark another option. You’re the stalking horse.
All four of these are more common than “I want to evaluate your offering seriously and move to close.” Treating every proposal request as the last one is how sellers end up writing twelve proposals to get one close.
The Qualifying Move
Before accepting the request at face value, run a qualifying sequence:
1. “What specifically would you want to see in the proposal?”
If the customer says “standard stuff — pricing, timeline, scope,” you’re in a commoditized bake-off. If they say “specifically how you’d address X and how the implementation would go for Y team,” you have a real proposal request.
2. “Who else will be reviewing this document?”
If the customer names specific stakeholders (“my CFO, our ops lead, and procurement”), the proposal is real. If they say “just me” or “I’ll pass it around,” the proposal is probably not going to a real committee.
3. “What’s the decision timeline after you review it?”
A real proposal has a decision attached. “We’ll make a decision by [specific date]” is a good sign. “We’ll take some time to think about it” is a warning. “I’m not sure” often means the request was tactical rather than strategic.
The Counter-Move
When the qualifying sequence suggests the proposal request is a soft deflection, the right move is often not to write the proposal. Instead:
“Happy to put something together. Before I do, it would help me make the proposal more useful if we could do a 20-minute working session with [specific stakeholder] to walk through how it would actually fit their situation. Without that, the proposal ends up generic — and I don’t think a generic proposal serves either of us. Can we schedule that for next week?”
This move does three things: it qualifies the seriousness of the request, it engineers another stakeholder conversation, and it repositions you from “vendor sending paper” to “thoughtful partner who’s trying to help.” Customers who are serious will find the time. Customers who weren’t serious will reveal themselves.
When to Send the Proposal Anyway
Sometimes the proposal is the right move even when the signals are mixed:
- Strategic account where being in the consideration set is worth the cost
- Customer with a history of slow but real buying cycles
- Situation where your proposal itself can reframe the conversation
In those cases, write the proposal — but write it as a strategic document, not a commodity quote. Include discovery findings, the problem framing, a recommendation, a proposed structure, a pricing approach. Make it something the customer couldn’t get from a competitor, because it reflects specifically what was surfaced in your conversation.
The Cost of Getting This Wrong
Every generic proposal written for a soft-signal request is lost time. A typical enterprise proposal is 10 to 20 hours of work — legal, pricing, SE, rep time. If 70% of proposals go to deals that were never real, the cost compounds fast.
The seller who writes 30 proposals per year and closes six of them has the same result as the seller who writes 10 proposals per year and closes six — except the first seller spent 400 hours on paper that went nowhere.
The proposal is a tool, not an automatic response. Use it when it’s going to move a real deal forward. Qualify before writing. Sometimes the best response to “send me a proposal” is a working session that produces a real deal, instead of paper that produces silence.
“Send me a proposal” is the phrase sellers want to hear and should investigate before trusting. Most of the time, what sounds like the last step is actually the last-but-polite exit.