"Sounds interesting. Send me the datasheet."
Every security seller has heard it. Most of them send it. That's where the deal ends.
Not because the datasheet is bad. Because once a technical buyer has the PDF, the demo has nothing left to show. They compare it to the two other PDFs on their desk, pick the cheapest, and the rep never hears back.
We watched this happen on a live account. Meetings were converting to demos at a rate nobody was happy with. The pattern in the call notes: datasheet sent, silence.
The fix wasn't a better datasheet.
The reply we trained the team on:
"Happy to. Which part of the stack are you evaluating it against? I'll send the two pages that matter for that and we'll skip the other twelve."
Three things happen. The buyer tells you what they're comparing. You send something they'll read. And you've earned a second conversation without asking for one.
Same account, two weeks later: two meetings, two demos booked.
"Send me the datasheet" isn't a request for a document. It's a request to stop talking to you politely. Answer the second one.
Why does sending the datasheet end the deal?
- Once a technical buyer has the PDF, the demo has nothing left to show.
- They compare it to the two other PDFs on their desk.
- They pick the cheapest, and the rep never hears back.
We saw this on a live account. Meetings converted to demos at a rate nobody liked. The pattern in the call notes: datasheet sent, silence.
What should you reply instead?
"Happy to. Which part of the stack are you evaluating it against? I'll send the two pages that matter for that and we'll skip the other twelve."
What does that reply get you?
- The buyer tells you what they're comparing. You learn the real evaluation.
- You send something they'll read. Two pages, not fourteen.
- You earn a second conversation without asking for one.
Did it work?
Same account, two weeks later: two meetings, two demos booked.