“Send Me Some Information”: Turn the Request Into a Useful Next Step

• “Send me information” may be genuine, exploratory or a polite ending. Clarify before treating it as progress or rejection.
• Ask what question the material should answer, who will use it and what evaluation comes next.
• Use a concise diagnostic recap: buyer-owned destination and gap, relevant mechanism, evidence, requirements and open questions.
• Offer a follow-up with a clear purpose; do not make information conditional on booking another call.

“This looks useful. Can you send me some information?” The seller sends the full product deck. A week later, they are checking in without knowing what the buyer intended to review.

The mistake is not sending a document. It is treating a broad request as a defined next step. The buyer may need a technical detail, a summary for a colleague, a way to compare options or simply time away from the conversation. Ask what the information needs to do.

Clarify the request with one useful question

“Happy to. What is the main question you want the material to answer?” This turns a vague request into a possible evaluation. If the buyer says, “The integration,” ask which requirement or workflow matters. If they say, “Something I can show finance,” learn what finance needs to judge.

A buyer who remains broad may still be genuinely exploring. Offer a short overview and leave room for later questions. Do not turn clarification into an interrogation designed to prove that the buyer is serious.

Three details make the material easier to use

Question: what uncertainty should the document resolve? “How migration works” is still broad; “whether historical attachments can be preserved” is actionable.

Audience: who will evaluate it? The person on the call, an operations lead, finance and security may need different material. Ask the buyer rather than assuming what those people care about.

Next evaluation: what happens after review? It may be an internal discussion, a technical test, another conversation or no planned action. Agree what is known. A scheduled call is useful when it serves a real question, not as a toll for receiving the information.

Question

The exact uncertainty the buyer named.

Audience

The person or group who needs to understand it.

Evidence

The relevant document, example or verified capability.

Open items

Assumptions, limitations and facts still to check.

Next step

The action both people actually agreed to.

A worked conversation: the deck request is really an operations test

This example is fictional.

Buyer: Send me some information and I will take a look.

Seller: What is the main question you want it to answer?

Buyer: How much work it is to switch. Our operations lead will want to know.

Seller: Which part of switching is most difficult for your team?

Buyer: We cannot stop processing orders. We need both systems running during a transition.

Seller: Then a general product deck will leave the important question open. What would operations need to see to judge a parallel transition?

Buyer: The steps, who does each one and what happens if something fails.

Seller: I can send our current transition outline and identify the parts that depend on your systems. We have not verified the parallel requirement yet.

Buyer: Include that. I do not want them thinking it is already solved.

Seller: Would a technical review after they read it help, or do you need to discuss internally first?

Buyer: Internally first. I will speak with them Friday and let you know whether a review is useful.

Read the method: the Clarifying question locates implementation effort. A Direct question identifies the operational dependency. The buyer defines the evidence standard: steps, ownership and failure handling. The seller states what remains unverified. The next step supports the buyer's process rather than treating a document request as permission to keep selling.

Use a diagnostic recap instead of an indiscriminate packet

A diagnostic recap helps the buyer reconstruct the reasoning accurately. Use their words for the destination and gap, then connect the relevant mechanism and evidence. Include the commercial and implementation requirements necessary for a fair evaluation. Keep facts separate from estimates.

For the fictional conversation above, a useful recap might read:

Priority: You want to evaluate a switch while keeping order processing live.

Key requirement: Operations needs to assess a parallel transition, including step ownership and fallback behavior.

Attached: Our current transition outline. The highlighted dependencies require review against your systems; parallel operation is not yet confirmed.

Next: You plan to discuss this internally Friday and let me know whether a technical review would help. Please correct anything I have summarized inaccurately.

This format is useful because it records the actual evaluation. It does not guarantee the email will be read, forwarded or outperform a brochure. If the buyer requests a specific document, supply it through the appropriate channel rather than replacing it with your preferred recap.

Handle evidence requests directly

A security reviewer asking for current compliance documentation needs the actual authorized material, not a sales story about trust. A buyer requesting terms needs the terms. If a document is unavailable or cannot establish what they ask, explain the limit and offer the next way to verify the point.

Use Consultative GP for the organizational evaluation and Proxy GP when the person on the call must carry the case to an absent approver. The buyer needs material that survives independent scrutiny, including unresolved questions. An emotional high from the meeting cannot do that job.

If the request is an ending, let it be an ending

When the buyer says, “Just a general overview; I do not want a follow-up,” send the agreed overview and honor the boundary. A refusal to schedule does not prove deception. They may be researching without an active project.

If an actual concern emerges, use the five-step dissolution flow: Absorb, Diagnose, Validate, Dissolve and Confirm. Diagnose Money, Trust, Timing or Identity from the explanation. Do not classify the request itself as a fixed Trust objection or an exit based on tone.

Practice writing the smallest useful follow-up

Take your last three information requests. Write the buyer's question, audience and intended evaluation. Leave missing details blank. For each blank, write one question you could have asked during the conversation.

Role-play two versions of the dialogue: an urgent technical review and a person doing early research who wants no next meeting. Practice sending accurate, appropriately sized material for both. Then write a four-part recap for a real, confirmed request and remove every paragraph that does not serve its question.

Continue with buying signals and objections and Consultative and Proxy GP to match the follow-up to the decision structure.

Common questions

Is “send me information” usually a brush-off?

No prevalence claim is established here. The request can have several purposes. Ask what the buyer wants to evaluate.

Should I insist on a meeting before sending material?

No. Offer a follow-up with a clear purpose, and send appropriate requested information without making a meeting a condition.

What makes a diagnostic recap useful?

It captures the buyer’s destination, gap, relevant mechanism, evidence, requirements, open questions and agreed next step in concise, correctable language.

Put it into practice

Choose a conversation to practise.

Explore the framework and put this idea to work on your next call.

Explore VIVID Layer 6: Objection Dissolution →