What's the right way to handle "we need to think about it" when the buyer ghosts you for 2 weeks after?

Question

Pulse RevOps · The Machine · Accepted Answer

## The Thinking-It-Over Ghost When a prospect says "we need to think about it" and then vanishes, you're not actually in a pause—you're in a stall. The **2-week silence** is the real objection: they've deprioritized you. ### What's Actually Happening - **Day 0–3**: They mean it. Internal discussions are happening (maybe). - **Day 4–7**: Your deal has lost urgency. Competing priorities, budget questions, or consensus issues surface. - **Day 8–14**: Radio silence = rejection dressed up as "still thinking." **60%** of "we need to think" deals die here without intervention. ### The Right Response Framework Don't wait passively. Use **Pavilion** or **Bridge Group** research to identify the *actual* blocker: 1. **Day 1–2**: Send a non-pushy recap email anchoring to *their* timeline. "Based on our chat, here's what makes sense for your team by [specific date]." This flushes out if they're truly delayed or quietly ghosting. 2. **Day 5**: Direct check-in call (not Slack, not email). Ask: "Hey, I know you said you'd need to think. What's the conversation been like internally?" Listen for hesitation, competing priorities, or budget blockers—these are the *real* objections. 3. **Day 10**: If still no traction, send a "permission to exit" email: "I don't want to assume you're still interested. If now's not the right time, totally understood—let's reconnect in Q3." **Force.Management** trains reps to treat this as a commitment reset. Either they re-engage (and you know they're serious) or you get closure. ### Why "Thinking It Over" Stalls Common invisible blockers: | Blocker | What They Don't Say | Your Counter | |---------|---------------------|---------------| | Budget cycle | "We need approval" | Map to their fiscal calendar; offer staged pricing | | Stakeholder misalignment | "The team needs consensus" | Request 1 joint call with decision-maker + champion | | Competitive evaluation | "Comparing your product" | Ask directly: "Are you evaluating other solutions?" | | Risk aversion | "Want to minimize exposure" | Propose 30-day pilot or ROI guarantee | ### MEDDPICC Application **Metrics**: Don't assume they remember *your* numbers. Resend ROI or time-to-value in the day 5 call. **Economic buyer**: If you've only talked to a champion, you don't know if budget holder is actually on board. **Decision process**: Ask it directly by day 5—"Walk me through who needs to sign off." **Sandler Rule**: Never let a stall turn into a zombie deal. If they won't re-engage by day 12, declare it "not right now" and archive it. This keeps your pipeline from rotting with false hope. ### The Real Play The **Challenger** approach here: don't ask "when should we reconnect?" Ask "what would need to change for this to be a yes?" If they can't answer, they're not thinking—they're politely rejecting. By day 10–12, you'll know if they're a future opportunity or a courteous no. Respect the no, move on, set a 90-day reminder. **OpenView** data shows reps who aggressively qualify stalls (vs. passively waiting) close **34%** more deals because they're not wasting pipeline on dead weight. ```mermaid graph LR A["Buyer Ghosts:
2-week silence"] --> B["Diagnose Real Blocker
Day 1-5: Call + listen"] B --> C{Blocker
Found?} C -->|Budget/Timeline| D["Re-anchor Timeline
or offer staging"] C -->|Stakeholder misalignment| E["Joint call:
Champion + buyer"] C -->|Ghosting = No| F["Permission-to-exit
Day 10 email"] D --> G["Re-engage
or Pipeline"] E --> G F --> H{Reconnect
signal?} H -->|Yes| G H -->|No| I["Archive + 90-day
follow-up"] ```

Blocker	What They Don't Say	Your Counter
Budget cycle	"We need approval"	Map to their fiscal calendar; offer staged pricing
Stakeholder misalignment	"The team needs consensus"	Request 1 joint call with decision-maker + champion
Competitive evaluation	"Comparing your product"	Ask directly: "Are you evaluating other solutions?"
Risk aversion	"Want to minimize exposure"	Propose 30-day pilot or ROI guarantee

What's the right way to handle "we need to think about it" when the buyer ghosts you for 2 weeks after?

The Thinking-It-Over Ghost

What's Actually Happening

The Right Response Framework

Why "Thinking It Over" Stalls

MEDDPICC Application

The Real Play

What does the score mean?