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

"Send me a proposal" is not a buy signal. It's a stall, a handoff, or — at best — a request for ammunition to compare you against two other vendors. A proposal that lands in an inbox without a calendar invite already attached has roughly the win rate of a cold email: per Gong's analysis of 67,149 B2B sales calls (gong.io/labs), deals where pricing is discussed without a scheduled follow-up close at less than half the rate of those with a locked next step. Your job in the next 90 seconds is to convert the request into a working session — not to comply with it.

The Response Script (Memorize This)

"Happy to. To make sure it's actually useful and not a generic template, I need 3 things: (1) seat count and ramp timing, (2) integration target — Salesforce or HubSpot, (3) who signs and what your procurement cycle looks like. Give me those and I'll have something tight in your inbox by Thursday EOD — and let's hold 15 minutes Friday at 10am to walk through it together. Calendar invite incoming."

That's the entire move. You did four things in one breath: qualified BANT, set a delivery date, locked a walkthrough, and signaled the proposal will be tailored — not boilerplate. In MEDDPICC terms you just stress-tested Metrics, Economic Buyer, Decision Process, and Identified Pain in 30 seconds. See [q12](/knowledge/q12) for the full discovery teardown.

The Mechanics, Step by Step

1. Never send blind. A generic proposal is marketing collateral, not a closing document. The Bridge Group's 2024 SaaS AE Metrics Report (bridgegroupinc.com/blog/sales-development-report) shows median enterprise SaaS sales cycles of 84 days; deals that skip discovery before pricing add a documented 30%+ to that cycle. Salesforce's FY24 10-K (sec.gov DEF14A annex) reports an average enterprise sales cycle of 6–9 months — every shortcut on day one extends the back end.
2. Send with the calendar already locked. "Proposal lands Wednesday EOD. Walkthrough Thursday 2pm — 15 minutes." Non-negotiable; it's on their calendar before they open the PDF. The forcing function isn't your discipline — it's their inability to politely decline a meeting they already accepted. Send the invite *before* the proposal email lands; the order matters. See [q88](/knowledge/q88) on calendar-as-commitment.
3. Lead the walkthrough, don't narrate it. Three sections only: scope, timeline, investment. When pricing pushback comes (it will), reframe live with exact math: "That $42K ACV is all-in with onboarding ($8K equivalent), 90-day CSM coverage ($6K equivalent), and integration setup ($4K equivalent). Strip those and the platform itself is $24K — Pavilion's 2024 GTM Benchmarks (joinpavilion.com/compensation-report) put comparable platforms at $38–48K stripped. We're at the floor." See [q34](/knowledge/q34) on objection reframing.
4. Use the proposal as a trial close. "Does this scope match what your team needs, or should we structure a 60-day pilot on the core SKU first?" You're offering the pilot path *inside* the proposal conversation, not as a desperate save 30 days later. See [q41](/knowledge/q41) on pilot structures and [q72](/knowledge/q72) on landing motions.
5. Keep it 2–3 pages, max. SaaStr's 2024 founder survey of 410 SaaS CEOs (saastr.com/2024-saas-survey) found buyers spend a median of 4 minutes on a proposal before forwarding to procurement. A 12-page deck gets skinned by procurement into a price-comparison spreadsheet. Scope, timeline, price, signature block. See [q19](/knowledge/q19) on proposal density.

Why Blind Proposals Fail

A proposal emailed without a follow-up call says "here's what we quoted." It doesn't say *why* the price makes sense, what success looks like in *their* business, or what month one feels like. Buyers read it once, line it up against two other quotes, and hand it to procurement. RepVue's 2024 quota attainment data (repvue.com/insights) shows AEs who close above 80% of quota run 2.3x more proposal walkthroughs per quarter than peers who attain below 50% — the walkthrough *is* the close moment, not the email.

The comp implication matters too: levels.fyi 2024 data on enterprise SaaS AE roles (levels.fyi/companies?role=Account+Executive) shows median OTE of $245K with ~50/50 base/variable split, meaning a single missed walkthrough on a $42K ACV deal costs the rep roughly $4,200 in commission at a 10% commission rate. Reps who treat the walkthrough as optional are leaving five figures per quarter on the table.

BVP's State of the Cloud 2024 report (bvp.com/atlas/state-of-the-cloud-2026) adds the macro lens: median enterprise SaaS gross retention has compressed to 89% as procurement teams sharpen pencils on renewals — meaning the *original* proposal motion now has to embed expansion logic from day one, or you're underwriting next year's churn. A walkthrough lets you plant that expansion seed live; an emailed PDF cannot.

Bear Case (Genuinely Adversarial)

"This is theater. Real Fortune 500 procurement teams *require* written proposals submitted via Coupa, Ariba, or Workday Strategic Sourcing, often with an explicit no-contact rule during evaluation. Your 'walkthrough demand' will get you disqualified from RFPs at any company over $1B in revenue. Carta's 2024 State of Private Markets (carta.com/state-of-private-markets) shows roughly 38% of Series C+ deals run through formal procurement portals — your charming Friday-10am script is irrelevant there. Worse: pushing for a walkthrough against an experienced procurement lead reads as desperation and *lowers* your perceived BATNA, which is why your final price gets cut another 8–12%. Second-order: the walkthrough script also assumes the buyer has 15 free minutes in a calendar that, per Microsoft's 2024 Work Trend Index, is 252% more meeting-saturated than 2020 — you're competing for a slot that doesn't exist. Third-order: experienced procurement leads are now trained to *say yes* to a walkthrough specifically to extract more concessions live, then ghost the close. Your 'forcing function' just became their leverage-extraction tool."

That critique is partially correct, and worth taking seriously. For true RFPs with procurement gatekeepers, follow the rules: submit clean, comply with the no-contact window, route through the portal. The script in this entry applies to the 60–70% of mid-market and SMB deals where "send me a proposal" is being said by the *economic buyer themselves* — the person who can override procurement. Read the room. If they say "send it to procurement," you're in RFP land — see [q58](/knowledge/q58) on RFP response strategy. If they say "send it to me," you're in walkthrough land. On the procurement-counter-tactic: the defense is to walk into the meeting with a pre-set price floor and a written one-page ROI summary, so that any concession requests get parked to a follow-up call rather than negotiated live. Misreading which game you're in is the actual unforced error.

When This Script Fails (Diagnostic)

• They won't give you the 3 answers. That's not a buyer; that's a tire-kicker. Send a one-pager with public pricing and disqualify. See [q47](/knowledge/q47) on disqualification discipline.
• They accept the calendar invite then no-show. Champion is weak or you're talking to a coach, not the EB. Reset and ask: "Who else needs to be in the room for this to move?"
• They demand the proposal in 24 hours, no walkthrough. They have a competitor's proposal and want yours for price-comparison. Either compress and walk away with low odds, or refuse and ask: "What's driving the timeline?" Their answer reveals the real game.

Bottom line: A proposal is a meeting agenda, not a deliverable. If you can't get 15 minutes on the calendar to walk through it, you don't have a deal — you have a price-shopping exercise wearing your logo. Treat the request as the start of the close, not the end of discovery.

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