Priya just finished a 35-minute discovery call with Daniel, VP of Operations at a logistics company evaluating her SaaS platform. The deal is worth $54,000 in annual recurring revenue. Daniel nodded through the whole demo, asked good questions, and at the end said: "This looks solid. Can you just send me some information I can review?" Priya said sure, sent a 12-page product PDF that afternoon, and never heard from Daniel again. Three follow-up emails later, silence.
Priya did not lose that deal on the call. She lost it in the four words that came after it. Most sellers hear "send me some information" and treat it as a logistical request. It is almost never a logistical request. It is a brush-off borrowing the shape of a next step, and treating it as a real ask is what kills deals that were otherwise winnable.
This post covers how to tell the rare genuine information request apart from the far more common exit, what sending a generic PDF actually does to a deal's momentum, and the two responses that reveal whether real interest exists at all, plus the one alternative to a generic info-dump that actually gets read.
Classifying the Request: Signal or Exit
The buying signals vs. objections three-test diagnostic applies directly here. Run "send me some information" through all three tests and the pattern repeats.
Energy direction. A genuine request comes with continued engagement: follow-up questions, a stated reason, forward motion. A brush-off arrives with a tone shift: the prospect's voice flattens, the conversation winds down immediately after, and there's no follow-up question about what the information will actually contain.
Specificity. "Can you send me the security and compliance one-pager so I can forward it to our IT team?" is specific: it names an audience, a purpose, a document. "Just send me some information" is vague on all three counts. Vague requests create distance. They don't gather data.
Future orientation. A real request imagines a next step after reviewing the material: "so we can regroup next week" or "before our Friday budget meeting." A brush-off has no next step attached. It's the conversational equivalent of "I'll think about it," polite, non-committal, and designed to end the call without confrontation.
Daniel's version ("can you just send me some information I can review") fails all three tests. No specificity about what he needs. No stated audience or purpose. No proposed next step. That's an exit, not information-gathering.
What a Generic PDF Actually Does to the Deal
Sending a brochure feels like progress. It rarely is. Four things happen the moment a generic information packet lands in a prospect's inbox instead of a real next conversation.
- The deal exits your control. While the prospect has your call, you can diagnose, clarify, and handle whatever comes up in real time. Once the PDF is sent, the deal is now happening entirely inside the prospect's head, on their timeline, with zero ability for you to catch a misunderstanding before it hardens into a "no."
- It breaks momentum. Deals move on emotional continuity: the felt sense of "this is happening" carries a prospect from call to decision. A generic PDF sitting in an inbox for four days lets that momentum go completely cold, and re-igniting cold momentum is far harder than sustaining warm momentum.
- It becomes shopping material. A polished PDF with your pricing and positioning is easy to forward to a competitor as a comparison point: "this is what Priya's company quoted, can you beat it?" You've just handed a negotiating tool to whoever the prospect talks to next.
- It has no urgency mechanism. Nothing about a static document creates a reason to act this week instead of next quarter. Silence after you send information is a dead deal that hasn't told you yet, not a busy prospect.
The Two Responses That Reveal Real Interest
Response A: The Clarifying Redirect
Priya: "Happy to send something over. So I get you the right thing instead of a generic deck. What's the one thing you and the team need to agree on before this moves forward?"
This question does the diagnostic work the original request skipped. If Daniel has a real answer ("we need to see the integration docs for our warehouse system"), that's a genuine request, and you now know exactly what to send and why. If Daniel hesitates or gives another vague answer, you've just learned the request was never really about information at all.
Response B: The Conditional Close
Priya: "Let's do this. I'll get that over to you today. And rather than you reading it cold, let's grab 15 minutes Thursday so I can walk you through the parts most relevant to your setup and answer whatever comes up. Does 2pm work, or is mornings better for you?"
This response tests real intent by proposing a return loop instead of a one-way document drop. A prospect with genuine interest schedules the 15 minutes without hesitation. A prospect who was exiting the conversation declines the follow-up, or goes vague on timing. Cleanly, without confrontation, you now know the deal needs a different approach. Or isn't real at all.
The Diagnostic-Recap-Email Alternative
When a real information need does exist, the material you send matters as much as the response you give. A generic product PDF gets skimmed once and forgotten. The diagnostic recap email format (mirroring the prospect's own words, naming the gap, the priority, the decision, and a specific next step) gets read, replied to, and forwarded internally at multiples of the rate a generic PDF ever manages, because it's built to be re-read, forwarded, and acted on.
For Daniel's deal, that means the follow-up isn't a brochure. It's three paragraphs reflecting exactly what he said about his warehouse bottleneck, the cost he named for it, the priority he ranked first, and a specific proposed next step. That document is useful to Daniel whether he forwards it to his own boss or reads it alone at 9pm, which a generic PDF never is.
When It's Genuinely Real
The three-test diagnostic isn't a trick to catch prospects lying. (Nobody needs a polygraph for a VP asking about SOC 2 documentation. If Daniel wanted to disappear, "send me some information" is a strange amount of effort to put into it.) Some information requests are completely legitimate, and treating a real request as a brush-off is its own mistake. A VP who says "I need the SOC 2 documentation to forward to our security team before Thursday's review" has passed all three tests: specific document, named audience, a real deadline attached. Send that immediately, and send it well. The point of the diagnostic is precision. It was never about catching someone in a lie.
The mistake to avoid in the other direction is treating every vague request as automatically fake and interrogating a prospect who's simply tired at the end of a long day and genuinely does want to look something over before committing further. The clarifying redirect and the conditional close both work precisely because they're gentle enough to not feel like an accusation. They create a small amount of friction. Real intent survives friction. A polite exit doesn't.
Where This Fits in the Framework
"Send me some information" sits at Layer 6 in the VIVID framework, but the real fix is upstream: a deal that produces this brush-off usually skipped a piece of Layer 3 diagnostic work that would have surfaced the real hesitation before the call ended. If the deal seems to be stalling for a different, quieter reason entirely, the let me think about it post covers the four real meanings behind sales' other most common stall, and the same diagnostic instinct applies to both lines.
