The "Just Send Me a Proposal" Trap: Running a 60-Minute Team Working Session Where Reps Build the Exact Words to Refuse a Premature Proposal and Convert the Brush-Off Into a Real Discovery Meeting — a 60-Minute Sales Training

Format: 60-minute live team working session. Manager-led. Every rep leaves with a written, rehearsed response to "just send me a proposal" and a re-qualification plan for one real deal where a proposal was requested too early.

Who runs it: Sales manager or team lead. Who attends: The full sales team (account executives, SDRs who book demos, senior reps). 4–12 people is ideal. What reps bring: A laptop with CRM access and one real, currently open deal where a prospect has asked for a proposal, quote, or pricing before the rep has run real discovery.

Why This Session Exists

"Just send me a proposal" is one of the most expensive sentences in B2B sales, and most reps treat it as a win. It feels like progress — the prospect is asking for something, the rep has something to do, the deal moves to a later stage in the CRM. So the rep goes back to their desk, builds a polished proposal, sends it, and waits.

And waits. The deal goes quiet, gets marked "proposal sent," and slowly rots in the pipeline as a forecast number nobody actually believes.

The brush-off works because it is polite. The prospect is not being hostile. Often they genuinely do not want to invest an hour in discovery with a vendor they have not decided to take seriously — so they ask for a document instead, because reading a PDF is cheaper than a meeting.

Sometimes "send me a proposal" is a soft no the prospect is too courteous to say out loud. Either way, a proposal written before discovery is a guess: it guesses the problem, guesses the scope, guesses the budget, and guesses who is even involved in the decision. A guess loses to a competitor who actually did the diagnosis.

The skill is not refusing to ever send a proposal. It is refusing to send a *premature* one — and doing it in a way that makes the prospect *want* the discovery conversation instead of feeling stonewalled. That is a specific set of words, and words can be built and rehearsed. In the next 60 minutes, every rep builds and pressure-tests theirs.

The one rule for today: every response a rep writes must do two things at once — decline to send the blind proposal *and* give the prospect a concrete reason the discovery conversation is in *their* interest. A flat "I can't do that" is not allowed. The answer must trade up to a meeting, not just block the request.

The Agenda (60 Minutes, 0:00 → 1:00)

The agenda below sums to exactly 60 minutes. Keep time strictly — the build and rehearsal blocks create the value, so protect them and cut discussion, not work.

Total: 5 + 8 + 10 + 15 + 12 + 7 + 3 = 60 minutes.

Block 1 — Frame the Session (0:00 – 0:05, 5 min)

Manager opens. Keep it to five minutes and say something close to this:

"Every one of us has a deal sitting in 'proposal sent' that we know in our gut is dead. It died the day we agreed to write a proposal before we understood the problem. Today we are going to fix the moment that kills those deals — the moment a prospect says 'just send me a proposal' and we say 'sure.' By the end of this hour you will have written and rehearsed the exact words you'll use next time, and a plan to re-open one real deal where you already fell into the trap.

Pick that deal now and open it in the CRM."

State the one rule: the response must decline the blind proposal *and* sell the discovery conversation as something the prospect wants. Blocking without trading up is not allowed.

Block 2 — Why the Premature Proposal Kills Deals (0:05 – 0:13, 8 min)

Manager-led discussion. The goal is to make the team feel the cost before they fix it.

Ask the room three questions and take fast, honest answers:

1. "Pull up your 'proposal sent' deals. How many of them have actually moved in the last three weeks?" The honest answer is usually: very few. Let that silence land.
2. "When you wrote your last early proposal, how many of these did you actually know — the real problem, the dollar cost of that problem, the budget, the full list of decision-makers, the timeline?" Most reps will admit they were guessing on at least three of the five.
3. "A competitor ran a full discovery call and you sent a blind quote. Whose proposal looks more credible to the buyer?" The answer is obvious, and it stings.

Land the teaching points:

• A proposal is a diagnosis, not a brochure. Sending one before discovery is a doctor writing a prescription before the exam. Buyers can feel the difference.
• "Send me a proposal" is often a polite exit. It lets the prospect end the conversation without saying no. Accepting it at face value means you never find out, and you forecast a dead deal as live.
• The proposal you send too early sets an anchor you cannot undo. If you guessed the scope and price wrong, you now have to negotiate against your own document.

The point is not "never send proposals." It is: a proposal earns its place *after* discovery, and the request for one early is a signal to diagnose, not to comply.

Block 3 — Diagnose: Which Kind of Brush-Off Is It? (0:13 – 0:23, 10 min)

There is no single right answer to "send me a proposal," because the sentence means different things. The rep's first job is to diagnose which one they are facing. Manager walks the three types, then reps classify their own deal in solo work.

The three kinds of "just send me a proposal":

1. The genuine shortcut. The prospect is interested and busy. They believe a document is faster than a meeting and simply do not yet see why discovery is worth their hour. *Tell:* they are responsive, engaged, and the request comes early in the relationship. This one is winnable — they just need a reason to meet.
2. The polite no. The prospect has mentally checked out — wrong fit, wrong timing, a competitor already chosen — and "send me a proposal" is a courteous way to end things without conflict. *Tell:* low engagement, vague answers, the request arrives right as the conversation loses energy. This one needs you to surface the real objection, not write a document.
3. The procurement screen. The request is real but mechanical — they are collecting bids and want a number to put in a spreadsheet. *Tell:* they reference a formal process, multiple vendors, a deadline. This one needs you to get into the requirements *behind* the bid before you price.

Solo work (last 4 minutes of the block): every rep writes one or two sentences for their chosen deal answering: *Which of the three is this, and what is the specific evidence?* If a rep cannot tell, that uncertainty is itself the finding — their next move is a diagnostic question, not a proposal.

Block 4 — Build Block: The Trade-Up Response (0:23 – 0:38, 15 min)

Solo work. This is the core build. Every rep writes their full response for their chosen deal, structured in four moves. Keep it tight — this should be sayable on a live call or readable as a short email reply, not a speech.

Move 1 — Agree and validate (one sentence). Never fight the request. Start by agreeing you want them to have a proposal. "Absolutely, I want to get you a proposal — and I want it to be one you can actually take to your team." This removes the friction; you are not refusing, you are upgrading.

**Move 2 — Make the cost of a blind proposal *their* problem (one or two sentences).** Explain, in the prospect's interest, why a guessed proposal wastes *their* time: "If I send you something before I understand [their situation], I'll either over-scope it and you'll think we're expensive, or under-scope it and the price changes later — both waste your time." The reframe: discovery protects the buyer from a bad number, not just the rep from a lost deal.

Move 3 — Make a small, specific, easy ask (one sentence). Trade the blind proposal for a *short, concrete* commitment — not "a meeting" in the abstract. "Give me 20 minutes — three or four questions — and I'll send you a proposal built around your actual situation, with real numbers, by [day]." Small, time-boxed, and tied to a deliverable they want.

Move 4 — Name the deliverable and the date (one sentence). Close the loop with exactly what they get and when, so the discovery call has an obvious payoff: "After that call you'll have an accurate proposal in your inbox within 48 hours." The prospect now sees the meeting as the fastest path to the document, not a detour from it.

For the "polite no" case: the response shifts. Instead of trading up to discovery, the rep writes a permission-based question that surfaces the real objection: "Happy to send something — but I'd rather not waste your time. Be straight with me: is this a real priority for this quarter, or has something changed?" Naming the exit gracefully often re-opens an honest conversation.

Reps write the full four-move response (or the permission question) into a CRM note or a draft reply they could actually send.

Block 5 — Live-Fire Rehearsal in Pairs (0:38 – 0:50, 12 min)

Pairs. This is where written words become spoken words. Reps pair up. In each pair:

• Rep A is the seller and delivers their response out loud, exactly as written, as if on a live call.
• Rep B is the prospect and pushes back twice — the two most realistic pushbacks: "I really don't have time for a call, just send me what you've got," and "We're talking to three vendors, I just need a number." Rep B does *not* go easy.
• Rep A must hold the line — agree, reframe, trade up — without caving and without sounding like they are stonewalling. If Rep A folds and promises the blind proposal, Rep B calls it, and they run it again.
• Swap. Repeat so both reps rehearse. Roughly six minutes each.

The rehearsal exposes the most common failure: a response that reads fine on the page but comes out apologetic or rigid out loud. Reps edit their wording on the spot until it sounds natural, confident, and genuinely helpful — not defensive.

Block 6 — Hot-Seat: Pressure-Test Two Responses (0:50 – 0:57, 7 min)

Manager-led. Pick two reps — ideally one with a clean response and one wrestling with a hard "procurement screen" or "polite no" deal — to run their response in front of the team.

For each (about three minutes):

1. Rep states the deal and which of the three brush-off types it is, in one sentence.
2. Rep delivers their trade-up response out loud.
3. The manager plays the toughest version of the prospect and pushes back once, hard.
4. The team offers one concrete improvement and the rep edits the response live.

The point is not to grade. It is to show the whole team the difference between a response that converts the brush-off into a meeting and one that just delays the loss — and to surface strong wording the rest of the team can borrow.

Block 7 — Commitments & Next Step (0:57 – 1:00, 3 min)

Manager closes. Go around the room fast. Every rep states out loud:

1. The deal their response is built for, and which brush-off type it is.
2. When they will send the trade-up response — a real calendar date, this week. Re-opening a stalled "proposal sent" deal is the entire point; the words are worthless unsent.
3. The specific small ask they are trading the blind proposal for — the time-boxed call or the permission question.

Manager records every commitment and states the follow-up: at next week's pipeline review, every rep reports whether they sent the response, what the prospect said, and whether the deal converted into a real discovery conversation. Inspected commitments get done; uninspected ones do not.

What "Good" Looks Like After This Session

A successful session does not end with reps agreeing that early proposals are bad. It ends with every rep having a written, rehearsed response and a scheduled send to re-open one real deal. The measurable outcome over the following weeks: fewer deals stranded in "proposal sent," more proposals that go out *after* a real discovery call, higher proposal-to-close conversion, and a forecast that contains real opportunities instead of polite brush-offs dressed up as pipeline.

Manager's Pre-Session Checklist

• [ ] The day before, ask every rep to pick one real open deal where a proposal was requested before discovery — send a reminder so nobody arrives empty-handed.
• [ ] Pull the team's aggregate count of deals stuck in "proposal sent" with no recent activity — use the real number to open Block 2.
• [ ] Have one strong example trade-up response ready to show if the team stalls in Block 4.
• [ ] Pre-select your two hot-seat reps so Block 6 starts instantly.
• [ ] Block next week's pipeline review to inspect the Block 7 commitments — uninspected commitments do not happen.
• [ ] Keep the build and rehearsal blocks (4 and 5) sacred — if the session runs long, cut discussion in Block 2, never the build.