how to handle "i need to think about it" without losing the deal
"let me think about it" is never about thinking. not really. it is usually one of three things the prospect does not want to say to your face: the price is not working, the person you are talking to cannot say yes, or they do not trust the decision enough yet.
if you accept the stall, the deal cools the second the call ends. if you guess wrong, you discount too early, send proof nobody asked for, or chase a follow-up that goes nowhere.
the three blockers it usually hides
this stall is one of the few sales objections where the meaning really does collapse into three categories. each one needs a different next move, and guessing wrong burns the deal.
price
the number does not fit the value they already believe they need. they will not say that out loud at the end of a demo because it feels confrontational. they say "let me think about it" instead.
authority
they cannot say yes alone. they need a CFO, a partner, a board member, or a procurement cycle to weigh in. naming that directly feels like admitting they were never the buyer.
trust
they like the idea, but they have not seen enough proof to feel safe committing. usually a missing case study, a missing security review, or a missing reference call.
the corrected version
which sales habit is costing you margin?
take the Sales Rep DNA Test and see whether you stall too late, over-accept vague next steps, or miss the real blocker.
take the dna testwhy it happens
the end of a demo creates two pressures at once. saying yes creates commitment. saying no creates conflict. "let me think about it" releases both pressures and lets the prospect leave without choosing.
that feels harmless in the moment, but the deal loses heat fast.
counter-frames
price diagnostic
ask: "if we set price aside for a second, would the rest of this be a yes?"
authority diagnostic
ask: "is the thinking just on your end, or are there others who weigh in?"
trust diagnostic
ask: "what would you need to see to feel confident saying yes?"
common mistakes and fixes
- scheduling a vague follow-up and calling it next steps. fix: any follow-up needs a named blocker attached. "we will talk thursday" is not progress. "we will talk thursday after you walk this past the CFO" is.
- sending more case studies without knowing the missing proof. fix: ask which kind of proof would change their mind, then send only that. random social proof reads like filler.
- dropping the price before price has been named. fix: run the price diagnostic question first. discounting an objection nobody raised teaches the prospect your number was inflated.
- asking "is it the price?" first and signaling that you think it is. fix: ask the neutral version. "if we set price aside, would the rest of this be a yes?" lets price surface without you leading them to it.
- letting the prospect leave without naming the blocker. fix: end the call by either confirming a blocker and a next step, or honestly admitting you don't have one and asking for one. silence after the call is the signal you missed it.
- treating all three blockers like the same problem. fix: price gets a scope or value answer. authority gets a multi-thread answer. trust gets a proof answer. do not bring scope to a trust problem.
when to walk away
- the prospect names a specific stakeholder concern outside their control
- a real approval event will not happen for 90 days or more
- security, board, or CFO review has not started and nobody owns pushing it
what Brutus does live
Brutus listens for the polite-stall pattern at the end of a pitch: vague timing, positive language, and no specific concern named. the live cue is: "don't schedule a follow-up. ask which of the three blockers is in the way."
related objections
faq
what if they really do just need time?
that is fine, but still name the blocker before the call ends. time is the default exit; specificity is what keeps the deal alive.
how long should the diagnostic take?
about 10 seconds. you are not running discovery; you are identifying which of the three blockers is real.
should I ever just accept the stall?
yes, when the blocker is clear and the next step is specific. no, when the stall is vague and unowned.