What Send Me Information Can Mean
A request for information can signal genuine evaluation, a need to brief a colleague, or a polite way to end a call. You cannot tell which from the phrase alone.
Read the signal
Sending a deck immediately feels responsive, but it often transfers the burden of finding relevance to the buyer. The missing piece is the question the material must answer. A brief clarification can make the response useful without turning the request into an interrogation.
Make the next move
Ask what the buyer is trying to assess, who else will read the material, and when they expect to discuss it. Offer two or three artifact types, such as a workflow summary, technical overview, or pricing outline. Then send the smallest asset that answers the stated question.
Language you can adapt
Illustrative wording:
Happy to send something useful. Are you looking to understand the workflow, evaluate technical fit, or brief another person on the business case?
The wording is a starting point. Replace the problem, evidence, and request with details the buyer actually gave you. If those details are missing, ask a question before sending a polished message. Specificity makes it easier for the buyer to correct your understanding and easier for you to see whether the opportunity is moving.
Decide what happens next
If the buyer names a question, send the matching asset and propose a review. If they will not name one, send a short overview and a low-pressure invitation to reconnect. Do not infer a committed evaluation from the request alone.
Write the result in your deal notes as an observable fact: who responded, what they agreed to do, and when. A friendly reply is useful, but a decision, a named owner, or a scheduled review tells you more. If the next step remains vague, treat that as information about the deal rather than a reason to send the same follow-up again.
Use these examples responsibly. Describe your product, pricing, and customer results accurately, and adapt every suggestion to the buyer’s stated process.