Handling "We need to see ROI proof" as BDRs
Acknowledge the need for ROI validation, then ask about their success metrics so the conversation moves from "we need to see roi proof" to the business outcome they actually care about.
Why this hits harder for BDRs
BDRs hear objections from champions and blockers inside the same account, so the same objection can mean five different things depending on who said it.
The tactical move
Log the objection against the persona who raised it and pattern-match across the account before crafting a response — a CTO's 'too expensive' rarely means the same thing as a procurement lead's.
The common trap
Treating every objection as one to overcome, instead of using it as free intel about the buying committee.
What the objection really means
Almost always a value or risk problem in disguise — they don't yet see the return that justifies the spend. For "we need to see roi proof" specifically, the underlying job is to acknowledge the need for roi validation before you say anything else — that one move usually reveals whether this is a genuine blocker or a reflex response.
Frequently Asked Questions
- What does "We need to see ROI proof before spending this much." really mean?
- Almost always a value or risk problem in disguise — they don't yet see the return that justifies the spend. In this specific case, the signal you're looking for is whether you've done step one: acknowledge the need for roi validation. If that's missing, the objection will keep resurfacing.
- What's the best framework for handling this objection?
- Use the Price & Budget framework: Acknowledge → Anchor on value → Quantify the cost of doing nothing → Re-confirm fit. For "we need to see roi proof" specifically, the move that matters most is to ask about their success metrics before you share relevant case studies with data.
- Should I respond immediately or ask a question first?
- Ask first. A useful opener here is: "When you say 'we need to see roi proof', what's the specific thing driving that?" — it earns you the right to respond and prevents you from solving the wrong version of the objection.
- What's the single most common mistake reps make here?
- Discounting before you've established value — it permanently lowers the anchor. Specifically on "we need to see roi proof", reps tend to skip "acknowledge the need for roi validation" — which is the one move that turns the objection from a wall into a conversation.
- How should I follow up if the call ends with "we need to see roi proof"?
- Send a short recap that mirrors their exact language, references one piece of proof (case study, benchmark, or customer quote), and proposes one specific, low-commitment next step with a date attached.
- Can I practice this objection with an AI buyer?
- Yes — LemCoach scenarios let you run a live roleplay where the AI prospect uses "We need to see ROI proof before spending this much." verbatim, then scores your response against the key points: Acknowledge the need for ROI validation; Ask about their success metrics; Share relevant case studies with data.