What's the right way to respond to 'send me a proposal'?

The Response Script That Converts the Request Into a Working Session

The moment someone says "send me a proposal," you have roughly ninety seconds to decide whether this becomes a controlled sales motion or a document that disappears. The instinct — especially for newer reps — is to say "absolutely, I'll get that right over," hang up, and spend two hours building a beautiful deck. That instinct loses deals. The buyer didn't ask for a proposal because they're ready to sign; they asked because it's the socially frictionless way to end a conversation, to create something they can forward, or to collect ammunition for a comparison you're not in the room to shape.

So don't refuse — *redirect*. Here is a script that works because it complies with the request while quietly re-taking control:

> "Happy to put that together. To make sure it's genuinely useful and not a generic template, I need three quick things: first, the rough scope — how many users or seats and by when; second, the ballpark budget you're working against so I size the right option and don't waste your time; and third, who else weighs in on a decision like this and what your buying process usually looks like. Give me those and I'll have something tight in your inbox by Thursday. And let's hold fifteen minutes Friday morning to walk through it together — I'll send the invite now so it's on the calendar."

In one breath you did four things. You qualified the deal (scope, budget, decision process — the practical core of both BANT and MEDDPICC). You set a concrete delivery date, which signals reliability and prevents the request from drifting. You locked a walkthrough, which is the single highest-leverage move available to you. And you framed the proposal as *tailored*, which pre-empts the "this is just boilerplate" dismissal that kills so many quotes.

Notice the psychology of the phrasing. "So I don't waste your time" reframes your qualifying questions as a *service to them*, not an interrogation of them. "So it's on the calendar" makes the meeting feel administratively inevitable rather than a favor you're begging for. And the delivery date — a specific day, not "soon" — creates a mutual commitment: they're now expecting something Thursday, which gives you a legitimate reason to follow up if they go quiet.

The reason this works maps to well-documented findings from sales-conversation research firms like Gong, whose analysis of large volumes of recorded B2B calls consistently shows that *explicitly setting a concrete next step* is one of the strongest correlates of deals that advance versus deals that stall. Discussing price or scope without a scheduled follow-up leaves the outcome to the buyer's inertia — and inertia almost always favors the status quo or the incumbent. The walkthrough is not a courtesy; it is the mechanism by which you keep a hand on the wheel.

If the buyer resists the meeting outright — "just email it, I'll look" — you have a soft version ready: "Totally fair. I'll send it over, and I'll include a two-minute Loom walking through the pricing logic so it doesn't raise more questions than it answers. If anything's off, grab fifteen minutes here." You've conceded the format while preserving the walkthrough in asynchronous form and still planting a calendar link. You almost never send a fully naked PDF into silence.

The Five-Step Mechanics, Start to Signature

Scripts get you through the moment; mechanics get you to signature. Here is the full operational sequence, with the trade-offs at each step.

1. Never send blind. A proposal built without discovery is marketing collateral, not a closing document — and buyers can smell the difference instantly. Enterprise software sales cycles routinely run anywhere from three to nine months, and the fastest way to *extend* a cycle is to quote before you understand the problem, because a mispriced or misscoped first proposal forces a re-scope, a re-approval, and a fresh loop through the buying committee. The discovery you do in the first ninety seconds is the cheapest time you'll ever spend on the deal. The trade-off: yes, insisting on three answers costs you a few deals with buyers who won't engage — but those were tire-kickers, and disqualifying them early is a feature, not a bug.

2. Send with the calendar already locked — invite first, proposal second. The order genuinely matters. Send the meeting invite *before* the proposal email lands. Once the buyer has accepted a fifteen-minute walkthrough, the forcing function isn't your follow-up discipline — it's their reluctance to politely cancel a meeting they already agreed to. If you send the PDF first and *then* ask for time, you've handed them the deliverable and removed their reason to meet. Reverse the sequence and the proposal becomes the reason the meeting exists.

3. Lead the walkthrough — don't narrate it. When you get the fifteen minutes, do not read the document aloud slide by slide; the buyer can read. Cover three things only: scope (what they're getting), timeline (what the first ninety days look like), and investment (what it costs and why). When pricing pushback arrives — and it will — reframe with concrete decomposition rather than a discount. "That number is all-in: it includes onboarding, the first quarter of dedicated support, and the integration setup. If we strip those out, the platform license alone is meaningfully lower — but you'd be buying the thing without the parts that make it succeed." You're teaching them how to read the price, not defending it.

4. Use the proposal as a trial close. Somewhere in the walkthrough, ask the question that reveals whether the deal is real: "Does this scope match what your team actually needs, or would it make more sense to start with a sixty-day pilot on the core capability and expand from there?" You've now surfaced the pilot path *inside* the live conversation, at full confidence — not as a desperate save thirty days later when the deal has gone cold. Their answer tells you whether you're talking to a buyer or a browser.

5. Keep it short — two to three pages. Busy buyers spend a few minutes on a proposal before deciding whether to champion it internally or forward it to procurement. A twelve-page deck doesn't impress procurement; it gets flattened into a price-comparison spreadsheet, and every extra page is another surface for objection. Scope, timeline, investment, and a signature block. Density is a courtesy and a conversion tactic at the same time.

The through-line across all five steps: every action either keeps you in the conversation or hands the buyer a reason to continue without you. Blind sends, silent follow-ups, and bloated decks all do the latter.

Why Blind Proposals Lose

Picture the two paths a proposal can take. In the first, you email a polished PDF with a warm note and wait. The buyer opens it once, reads it in isolation with no one to explain *why* the price makes sense or what success looks like in *their* business, lines it up next to two competitors' quotes, and forwards all three to procurement — whose entire job is to make you interchangeable and drive the number down. You are now competing on a spreadsheet, on a dimension (price) where you have no advantage and no voice.

In the second path, you walk the buyer through the same document live. You watch their face when you hit the number. You hear the objection in real time and answer it before it hardens into a reason to say no. You connect the investment to the specific pain they named in discovery — "you told me your ramp time on new reps is killing you; here's the line item that fixes that." You leave with either a signature, a clear next step, or an honest read that the deal isn't real. In every case you have *information and control* the emailer never gets.

The difference isn't effort — both reps built a proposal. The difference is that one treated the document as the finish line and the other treated it as the agenda for the meeting where the deal actually closes. Top-performing reps run dramatically more proposal walkthroughs than their struggling peers, not because they're sending more proposals, but because they refuse to let a proposal leave the building without a meeting attached to it. The walkthrough *is* the close moment. The email is a hope.

There's a strategic layer here too. Renewal and retention pressure across SaaS has intensified as buyers scrutinize spend harder than they did a few years ago, which means the first proposal increasingly has to carry expansion logic — the story of how this lands, proves value, and grows — rather than just a price for year one. You cannot embed that narrative in a static PDF the buyer reads alone. A live walkthrough lets you plant the expansion seed while you have their attention; an emailed document is a snapshot, not a story. If your first proposal doesn't set up year two, you're quietly underwriting next year's churn.

And the pure math favors the walkthrough for the rep personally. On a variable-comp plan, a single deal that stalls at the proposal stage because no one walked it through is real money out of your own pocket — and it compounds, because the stalled deal also consumes pipeline slots and forecast credibility. Treating the walkthrough as optional is one of the most expensive habits in the profession.

What Actually Goes in the Proposal

A tailored proposal is not a longer proposal — it's a *sharper* one. Here is the anatomy that converts, section by section, and what to leave on the cutting-room floor.

Restate their problem in their words. The first thing a buyer should see is evidence that you listened. Open with one or two sentences naming the specific pain they described in discovery — the ramp time, the data mess, the churn number, the manual reporting eating their team's Fridays. This is the single strongest differentiator against a boilerplate competitor, and it costs you nothing but attention. A buyer who reads their own words back to them is already halfway to trusting your solution.

Scope — bounded and concrete. Spell out exactly what's included and, just as important, what isn't. Ambiguous scope is where deals go to die in re-negotiation; a clear boundary protects both your margin and their expectations. Use plain nouns and verbs, not feature-list jargon.

Timeline — what the first 90 days feel like. Buyers don't buy features; they buy the future state. Give them a dated, phased path: kickoff, onboarding, first value milestone, full rollout. This is where you make month one feel real and low-risk, which is often what's actually blocking the signature.

Investment — with the logic exposed. Present the price *and* its composition. If there are options — good/better/best, or a pilot path — present at most three; more than three triggers analysis paralysis and pushes the decision to procurement. Anchor the recommended option and make the others reference points, not equals. Never bury the number on page nine; a buyer hunting for the price reads nothing else until they find it.

One clear next step. End with a single, unambiguous call to action and a signature block. Not "let me know your thoughts" — that's an invitation to silence. "Sign here to lock the Q3 start date" or "reply to confirm the pilot scope and I'll send the agreement" gives the buyer a rail to move on.

What to *cut*: your company history, your logo wall of unrelated customers, generic feature grids, and anything that reads as if it could have been sent to any prospect in your vertical. Every sentence that isn't about *their* problem, *their* timeline, or *their* outcome is a sentence procurement will use to commoditize you. Length signals insecurity; precision signals expertise.

The Procurement Exception and When the Script Fails

The walkthrough-first playbook is not universal, and pretending it is will get you disqualified from deals you could have won. There is a genuinely adversarial case worth taking seriously, and a good rep knows which game they're in before they make a move.

The procurement exception. At large enterprises, "send me a proposal" is often not the economic buyer speaking — it's a formal RFP or RFQ process routed through a procurement platform, sometimes with an explicit no-contact rule during evaluation. In that world, demanding a walkthrough doesn't read as confident; it reads as someone who can't follow instructions, and it can get you eliminated. If the request comes wrapped in a portal, a template, a submission deadline, or the phrase "send it to procurement," you are in RFP land. There, the correct moves are the opposite of the script: comply precisely, submit clean, respect the no-contact window, and do your influencing *before* the RFP opens (by helping shape the requirements) and *after* it's scored (in the shortlist stage). A meaningful share of larger, later-stage deals run through formal procurement, and the charming Friday-morning walkthrough is simply irrelevant to them.

There's a subtler risk too: an experienced procurement lead may *accept* your walkthrough specifically to extract live concessions, then go quiet. The defense is to walk in with a pre-set price floor and a one-page written ROI summary, and to park any concession request to a follow-up rather than negotiating on the spot. "Great question on price — let me take that back and come to you with options tomorrow" costs you nothing and denies them the live leverage they were fishing for.

So how do you tell the two games apart? Read who's asking. If the *economic buyer themselves* — the person who owns the budget and can override procurement — says "send it to me," you're in walkthrough land and the script applies. If a procurement contact, an assistant, or a committee coordinator says "submit it through the portal," you're in RFP land. Misreading which game you're in is the real unforced error, not the script itself.

When the script fails — and what each failure tells you. Even in walkthrough land, the playbook surfaces diagnostic signals worth reading:

• *They won't give you the three answers.* That's not a qualified buyer; that's someone gathering quotes. Send a one-pager with public pricing, note that you'd tailor it after a short call, and move your energy to a real opportunity. The refusal *is* the qualification.
• *They accept the invite, then no-show.* Your champion is weak, or you're talking to a coach rather than the decision-maker. Reset with the diagnostic question: "Who else needs to be in the room for this to actually move forward?"
• *They demand the proposal in 24 hours with no meeting.* Usually a sign they already have a competitor's quote and want yours for price comparison — you're the stalking horse. Either compress and accept low odds, or ask the honest question: "What's driving the timeline?" Their answer reveals whether there's a real deal underneath or you're being used to keep the incumbent sharp.

The unifying principle: the proposal request is a probe, and how the buyer responds to your redirect tells you more about the deal's health than the request itself ever did. Treat every friction point as data, not rejection.

FAQ

What exactly is wrong with just sending the proposal?

Sending a proposal with no confirmed next meeting turns your offer into a document that can be ignored, compared, and shopped without you in the room. You lose control of both the timeline and the narrative — the buyer reads your price in isolation, with no one to connect it to the outcome they care about, and then hands it to procurement to be commoditized. A proposal without a scheduled walkthrough is a hope, not a close. The document isn't the problem; the *silence around it* is.

How do I respond without sounding pushy or losing the deal?

Frame every ask as a service to the buyer, not a demand on them. Instead of "I need a call before I'll send anything," say "so I don't waste your time with a generic template, can I grab three quick details and hold fifteen minutes to walk you through it?" You're offering accuracy and respect for their time, which is genuinely helpful. Most buyers say yes because the framing makes agreeing feel like the efficient choice, not a concession.

What if the buyer insists they just want it emailed, no call?

Concede the format but keep the walkthrough alive asynchronously. Send the proposal and attach a short screen-recorded walkthrough of the pricing logic, plus a calendar link: "Here it is — I added a two-minute video so it doesn't raise more questions than it answers. If anything's off, grab time here." You've respected their preference while still shaping how they read the document and leaving an obvious low-friction path back to a conversation. Avoid sending a completely naked PDF into silence.

Does this approach work for every industry and deal size?

It works best for consultative B2B sales where the deal size justifies a conversation and differentiation matters. For small, commoditized, transactional purchases, an emailed proposal with public pricing is perfectly appropriate — forcing a meeting there just adds friction. And for large enterprise RFPs routed through procurement portals, you follow the RFP rules instead, doing your influencing before and after the formal window. Match the intensity of your process to the size and complexity of the deal.

What if I suspect the buyer is just gathering information and isn't serious?

That's precisely why you qualify before you build. Asking for three details and a short meeting is a low-cost filter: a serious buyer will engage, while a pure information-gatherer will decline — and their decline saves you hours of proposal work that would have gone nowhere. Don't treat the filter as a loss. Disqualifying early frees your time for opportunities that can actually close, and quota attainment is as much about *what you say no to* as what you chase.

How do I handle it when I'm talking to a gatekeeper, not the decision-maker?

Use the proposal request as leverage to reach the real buyer. Offer to include the decision-maker on the walkthrough: "I'd love to have [name] on the call so we align on priorities directly — would twenty minutes work for both of you?" This prevents your proposal from being forwarded and re-narrated by someone who can't sell it internally, and it gets your value story in front of the person who controls the budget. If the gatekeeper blocks all access to the decision-maker, treat that as a serious risk signal about the deal's real health.

Sources

• Gong Labs — data-driven research on what separates winning B2B sales conversations: https://www.gong.io/labs/
• Harvard Business Review — sales, negotiation, and buyer-psychology coverage: https://hbr.org/topic/sales
• HubSpot Sales Blog — practical guidance on proposals, discovery, and closing: https://blog.hubspot.com/sales
• MEDDIC Academy — the MEDDIC / MEDDPICC qualification framework: https://meddic.academy/
• SaaStr — SaaS go-to-market, sales-cycle, and pricing benchmarks and commentary: https://www.saastr.com/
• RAIN Group — research and training on consultative selling and win rates: https://www.rainsalestraining.com/

Related on PULSE

• [How do you coach reps to handle 'just send me some information'?](/knowledge/q13914)
• [What's the framework for handling 'send me pricing' on call one?](/knowledge/q58)
• [What question would you ask a rep who consistently loses deals at the proposal stage to diagnose the real issue?](/knowledge/q14392)
• [How is AI changing RFP and proposal automation in 2027?](/knowledge/q13049)
• [How can RevOps design a lead handoff process when AI qualifies leads faster than human reps can respond?](/knowledge/q16349)

TAGS: proposal-motion,closing-conversation,discovery-questions,deal-pacing,trial-close