When they say send me some information

"Send me some information" is a soft no that leaves a crack in the door. Send a brochure and the door closes. Send one sharp thing and it might open.

Every seller has gotten this reply. It feels like progress. The buyer engaged. They want to learn more. So the seller attaches a capabilities deck and three case studies and waits.

Nothing comes back.

What it usually means

There are three common reasons a senior buyer writes this.

The first is politeness. They don't want to say no outright, so they ask for something that ends the conversation gracefully. You send it, they don't read it, everyone moves on.

The second is real but light interest. Something in your note landed, but not enough to give you time on their calendar. They want to see if you're worth a meeting.

The third is a filter. They're busy, they get a lot of pitches, and asking for information sorts the serious sellers from the rest. The ones who send a generic deck lose. The ones who send something thoughtful earn a second look.

In all three cases, a brochure is the wrong answer.

Why the deck fails

A capabilities deck is about your firm. It lists services, logos and generic outcomes. The buyer asked for information, but they meant information that helps them, not your marketing.

And nobody reads a twenty-slide deck from a stranger. It sits in the inbox, then in the archive. You've confirmed that you're like every other vendor.

The reply to send

Answer with a question that narrows what's useful, plus one small thing worth reading. Keep it short.

Say you'd written to a COO at a regional distributor about warehouse labor costs, and they replied asking for information.

Happy to. So I don't bury you in slides, which part is most useful right now, the labor planning side or the systems underneath it? In the meantime, here's a one-page note on how two distributors cut overtime during peak without adding headcount. It's a short read.

That reply does a few things. It respects their time. It shows you're not going to spam them. It gives them a binary choice that's easy to answer. And it hands over one useful thing, not ten.

Their answer tells you where the problem lives. If they say systems, you know who the technical lead is likely to be. If they say labor planning, you know the operational pain is the hook.

What to send, if you send anything

If you attach something, make it short, specific and about their problem. A one-page point of view. A short summary of how a similar company handled the same issue, without naming the client if you can't. A list of questions they should be asking. Anything they'd find useful whether or not they ever hire you.

Never send the full deck on the first exchange. Save it for when they ask for it by name or when you're preparing for a real meeting.

What to avoid

Don't reply with "Sure, what's the best way to send it?" You'll waste a turn.

Don't send everything you have to prove you're serious. Volume reads as desperation.

Don't follow up three days later asking if they had a chance to look. They didn't. Follow up with something new instead, a fresh observation about their company or a reaction to something they posted.

And don't treat it as a dead end. A buyer who asked for information is more open than one who didn't reply at all. A sharp misery hypothesis with an easy binary in your next note is your best tool for turning that opening into a real conversation.

The goal of the next note

You're not trying to inform the buyer. You're trying to learn which problem matters to them, in their words. Every reply should move toward that.

Send less. Ask better. Give them one useful thing. That's how "send me some information" turns into a meeting.