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

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.

1. 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.

1. 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:

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.

FAQ

What does a two-week silence after "we need to think about it" really mean? The two-week silence is the real objection: they have deprioritized you, so you are in a stall rather than a pause. Roughly 60% of "we need to think" deals die in the day 8-14 window without intervention. Treating it as a genuine pause is the mistake.

What should I do on day 1-2, day 5, and day 10? On day 1-2 send a non-pushy recap email anchored to their timeline to flush out whether they are truly delayed or quietly ghosting. On day 5 make a direct check-in call, not a Slack or email, and ask what the internal conversation has been like.

On day 10 send a "permission to exit" email offering to reconnect in Q3, which Force Management trains reps to treat as a commitment reset.

How do I apply MEDDPICC to a stalled "thinking it over" deal? Don't assume they remember your metrics, so resend the ROI or time-to-value figures in the day-5 call. On economic buyer, recognize that if you have only spoken to a champion, you don't know whether the budget holder is on board.

On decision process, ask directly by day 5: "Walk me through who needs to sign off."

What are the common invisible blockers and their counters? A budget cycle hides behind "we need approval," so map their fiscal calendar and offer staged pricing. Stakeholder misalignment hides behind "the team needs consensus," so request one joint call with the decision-maker and champion.

Competitive evaluation gets countered by asking directly if they're evaluating other solutions, and risk aversion gets countered with a 30-day pilot or ROI guarantee.

What does the data say about aggressively qualifying stalls? OpenView data shows reps who aggressively qualify stalls, rather than passively waiting, close 34% more deals because they stop wasting pipeline on dead weight. The Challenger move is to ask "what would need to change for this to be a yes?" instead of "when should we reconnect?" The Sandler rule is to declare it "not right now" and archive by day 12 if they won't re-engage.

Real Numbers, Not Round Numbers

Real Numbers, Not Round Numbers

The Bear Case (Competitive Encroachment)

Three margin/moat compression vectors:

1. Incumbent platform integration — Salesforce, HubSpot, Microsoft, Google, AWS build mid-market features. Vertical depth is the defense.
2. AI-native entrants — VC-funded at 30-60% of established price. Match trust + outcomes for 18-36 months.
3. Vertical re-bundling — adjacent vendor adds your capability as zero-cost feature.

Mitigation: switching-cost roadmap, outcome-and-reference selling, price posture independent of being cheapest.

See Also (related library entries)

Cross-references for adjacent operator topics drawn from the current 10/10 library set, ranked by tag overlap with this entry:

• q262 — What's the right way to measure an enablement function's actual impact on revenue versus just course-completion rates?
• q241 — How do you handle a buyer who insists on monthly contracts when your standard is annual?
• q140 — How do I respond to 'we're going to build this internally'?
• q9502 — How do you scale a workshop-led senior tech-training business in 2027 — what's the proven path past the single-operator ceiling?

Follow the q-ID links to read each in full.