The Proposal Follow-Up Sprint: Running a 60-Minute Team Working Session Where Every Rep Audits Every Delivered-But-Undecided Proposal, Diagnoses Why It Stalled, and Builds a Specific Next Move That Forces a Yes or a No — a 60-Minute Sales Training

Format: 60-minute live team working session. Manager-led. Every rep leaves with a written, dated next move for every proposal they have sitting in limbo.

Who runs it: Sales manager or team lead. Who attends: The full sales team (account executives and senior reps). 4-12 people is ideal. What reps bring: A laptop with CRM access and a printed or on-screen list of every proposal, quote, or formal pricing document they have sent in the last 90 days that has not yet been won or lost.

Why This Session Exists

A delivered proposal that has gone quiet is the most dangerous thing in a pipeline, because it does not look dangerous. It is still in the forecast. It still has a close date.

The rep still says "they're reviewing it." But a proposal a buyer received three weeks ago and has not responded to is not "in review" — it is stalled, and every day it sits there it gets colder, the champion gets busier, a competitor gets a turn, and the original compelling event quietly expires.

Reps let this happen for an understandable reason: chasing a proposal feels like begging. So the rep sends one limp "just checking in" email, gets nothing back, sends another, gets nothing back, and then simply stops — leaving the deal to rot in the pipeline because killing it feels worse than ignoring it.

The forecast slowly fills with proposals nobody is actually working.

This session ends that. In the next 60 minutes the team will pull every open proposal into the light, give each one an honest diagnosis of *why* it stalled, and build a specific, dated next move designed to force a real answer — a yes or a no — instead of more silence. A clean no is worth more than a hopeful maybe, because a no frees the rep's time and a maybe quietly steals it.

The one rule for today: every next move must be *specific, dated, and designed to get a decision*. "I'll follow up with them" is not a move. "I will call the CFO Thursday at 9 a.m., reference the Q3 budget deadline she named, and ask for a verbal yes or a clear no by Friday" is a move. Specific, dated, decision-forcing — or it does not count.

The Agenda (60 Minutes, 0:00 -> 1:00)

The agenda below sums to exactly 60 minutes. Keep time strictly — the diagnose and build blocks are where the value is, so protect them.

Total: 60 minutes, running clean from 0:00 to 1:00.

Block 1 — Frame the Session (0:00 - 0:05)

Open with the number. Before the meeting, the manager pulls the total dollar value of every proposal on the team that is more than seven days old with no movement. Put that number on the screen.

Then say plainly: "This is money we already did the work to earn. We ran the discovery, we built the proposal, we sent it. And right now it is sitting in the dark doing nothing.

Today we are going to drag every one of these into the light, figure out honestly why it stalled, and give it one real shove — toward a yes or toward a no. Both of those are wins. The only loss is the silence we have now."

Set the one rule (specific, dated, decision-forcing) and the mindset: a fast no is a gift. It returns your time. The enemy is not rejection — the enemy is the hopeful maybe that lives in the forecast for two quarters and closes for zero.

Block 2 — Audit: Surface Every Open Proposal (0:05 - 0:13)

Eight minutes, individual work. Each rep makes a single list. One row per proposal. For each one they capture only four things, fast:

1. Account and deal name.
2. Dollar value.
3. Days since the proposal was delivered.
4. Date and nature of the last real two-way contact — not a one-way "checking in" email the buyer ignored, but the last time the buyer actually responded.

No storytelling yet, no excuses, just the list. The goal is to make the invisible visible. Most reps are quietly shocked at how many proposals they find and how old the oldest one is. That shock is the point.

Manager move: walk the room. The rep who says "I only have one" usually has five they forgot about. Push them to check sent items and CRM, not just memory.

Block 3 — Diagnose: Assign Each Proposal a Stall Reason (0:13 - 0:25)

Twelve minutes. This is the analytical core of the session. For every proposal on their list, each rep assigns exactly one primary stall reason from the menu below. One reason — the dominant one — because the diagnosis determines the move.

The six stall reasons:

• No compelling event. Nothing forces the buyer to act by a date. The proposal is "nice to have" with no deadline. This is the most common and most fatal.
• Wrong or incomplete buying committee. The proposal is sitting with a champion who cannot sign and may not have shown it to the people who can. The economic buyer and other stakeholders were never engaged.
• Unspoken objection. The buyer has a real concern — price, a competitor, a risk, internal politics — that they have not voiced, so the rep never handled it. Silence here is an objection wearing a disguise.
• No agreed next step. The proposal was sent into a vacuum. There was never a calendar invite, a decision date, or a mutually agreed plan-to-close. It simply ended with "let me know."
• Priority displaced. The buyer's attention got pulled to something more urgent. The deal is not dead, it is buried under a reorg, a fire drill, or a fiscal-year crunch.
• Genuinely losing or lost. Honest assessment: a competitor is winning, or the budget evaporated. The rep just has not admitted it.

Reps write the reason next to each proposal. Then each rep shares their oldest or largest stalled proposal and its diagnosis with the group in one sentence. The manager pressure-tests: "You said no compelling event — is that true, or is it actually an unspoken price objection?

What did they say the last time you talked?" The diagnosis must be honest, because the next block builds directly on it.

Block 4 — Build: Write a Specific Next Move for Each Proposal (0:25 - 0:40)

Fifteen minutes, individual work. This is the largest block and the heart of the session. For every proposal, the rep writes a next move matched to its diagnosed stall reason. The move must satisfy the one rule: specific, dated, decision-forcing.

Match the move to the diagnosis:

• No compelling event -> Re-anchor on a real deadline or create one. "Call the buyer, ask what changes for them if this is not solved by [date], and quantify the cost of waiting. Offer an implementation slot or terms that expire to give the timeline teeth."
• Wrong buying committee -> Go get the missing person. "Ask the champion directly: who else has to bless this, and can we get 20 minutes with them together this week? Frame it as helping the champion sell internally, not going around them."
• Unspoken objection -> Surface it. "Call and say: 'When we last spoke this felt like a strong fit, and it's gone quiet. In my experience that usually means a real concern came up. What is it — price, timing, a competing option? I'd rather hear it straight.'"
• No agreed next step -> Install one. "Propose a specific decision call with a date and a clear agenda, and ask the buyer to confirm who will be on it and when they can give a final answer."
• Priority displaced -> Reconnect to urgency or park honestly. "Acknowledge the buyer's bigger fire, then ask one question: should we pick this back up on a specific date, or has it genuinely fallen off the list for the year? Get a real date or a real no."
• Genuinely losing/lost -> Force the close. "Send the takeaway-style message: 'It looks like this isn't moving forward — I'm going to close it out unless I'm wrong. If there's still a path, tell me what it is.' Then accept the answer either way."

Every move needs an owner (the rep), a channel (call beats email for anything that matters), a date, and a defined outcome that counts as success. The manager circulates and kills every vague move on sight. "Follow up next week" gets sent back until it is "Call Tuesday 10 a.m., ask for a decision by Friday."

Block 5 — Rehearse: Role-Play the Three Hardest Follow-Ups (0:40 - 0:52)

Twelve minutes, in pairs. Reps pick the single hardest follow-up on their list — usually the unspoken-objection call or the takeaway "force the close" message, because both feel uncomfortable.

One rep plays themselves, the other plays the buyer and is instructed to be realistically evasive: "We're still looking at it," "Can you send that over email," "Now's not a great time." The selling rep has to hold the line, ask the decision-forcing question, and not retreat into "no problem, I'll check back later."

Run it twice so each person practices. The partner gives one piece of specific feedback: where did the rep flinch, soften the ask, or let the buyer off the hook? Then the pair fixes the wording.

The point of the rehearsal is that decision-forcing follow-ups die in the throat. Saying the words once in a safe room makes the rep far more likely to actually say them to the buyer.

Block 6 — Commit: Lock Dates and Accountability (0:52 - 0:58)

Six minutes. Every rep states out loud, to the team:

• How many stalled proposals they audited and their total value.
• Their top three moves, each with its date.
• The date by which the team will know the outcome of all three — yes, no, or a concrete advance.

The manager records each rep's commitment in a shared doc or the CRM. The standing follow-up: at the next pipeline meeting, every one of these proposals must have changed status. Won, lost, or genuinely advanced with a new agreed next step. Still-silent is not an acceptable status. The forecast gets honest because the proposals get resolved.

Block 7 — Close (0:58 - 1:00)

Two minutes. The manager restates the core idea: a delivered proposal is the most expensive asset in the pipeline and the easiest one to abandon. The job is never finished when the proposal is sent — it is finished when the buyer says yes or says no. Silence is not an answer the team accepts.

Reinforce the win condition: by the next pipeline review, zero proposals in this group are still sitting in the dark. Then close the session.

What Good Looks Like After This Session

• Every rep has a written, dated next move for every proposal they had sitting in limbo.
• The forecast is more honest within a week, because hopeful maybes have been converted into real yeses and clean nos.
• Reps stop sending limp "just checking in" emails and start making decision-forcing calls.
• The team adopts a standing rule: no proposal goes more than seven days without an agreed next step, and "still reviewing" is a stall reason to diagnose, not a status to accept.

Manager's Follow-Through Checklist

1. Inspect within seven days. Pull the audited proposals at the next pipeline meeting; every one must have moved.
2. Reward the nos. Publicly credit reps who turned a stalled maybe into a clean no — it protects the culture that silence is the enemy, not rejection.
3. Make it a habit, not an event. Add a proposal-age column to the weekly pipeline review so stalls get caught at day seven, not day thirty.
4. Coach the flinch. The reps who could not hold the line in the role-play need one-on-one reps before their real calls.
5. Run this sprint quarterly. Stalled proposals accumulate continuously; a recurring sprint keeps the pipeline clean.

Frequently Asked Questions

How is this different from a general stalled-deal review? This session is narrowly about *delivered proposals* — deals where the rep has already done the discovery and quoting work and the buyer simply has not decided. That specificity matters: the diagnosis menu and the moves are tuned to the post-proposal stall, which behaves differently from an early-stage deal that went quiet.

Isn't aggressively chasing a proposal just begging? No. Begging is repeating "just checking in" with no value and no ask. This session does the opposite: every move is built to force a real decision and to make a clean no as acceptable an outcome as a yes. Asking a buyer to make the decision they already owe you is professional, not desperate.

What if a rep has twenty stalled proposals and only time for three moves? Prioritize by value and recoverability — the largest deals and the ones with the most recent real contact go first. But the deeper signal is that twenty stalled proposals means proposals are being sent without agreed next steps.

Fix that upstream so this backlog stops rebuilding.

How often should we run the Proposal Follow-Up Sprint? Quarterly as a full session, with a lightweight proposal-age check built into every weekly pipeline review. Stalled proposals accumulate continuously, so the discipline has to be continuous.