# How to handle requests for a summary before a call
> Learn how to answer a prospect who asks for a summary on LinkedIn, with a short value proposition, a clear next step, and templates that keep the call.
- HTML: https://getkinlead.com/handle-prospect-asking-for-meeting-notes
- Markdown: https://getkinlead.com/handle-prospect-asking-for-meeting-notes.md

**Short answer:** When a prospect asks for a summary, they're deciding if you're worth 15 minutes. Give them a specific outcome, a brief explanation of how you get it, and a reason why a live conversation is the only way to see if it works for their setup.

## Why prospects ask for a summary

A request for a summary is usually a filter. The prospect wants to know you aren't a bot or a low-quality service before they commit their calendar. They're looking for a signal that you know what you're doing.

Often, the prospect is looking for a shortcut. They hope to find an answer in your text and say no without having to be polite on a call. If you send a full manual, you give them everything they need to disqualify you without ever speaking to you.

The request also changes the power dynamic. By asking for a summary, they become the judge and you become the applicant. You need to move the conversation back to a peer-to-peer discovery session. That starts with answering the question directly and then asking for a small amount of time.

Some prospects ask because they are comparing you to another vendor. They want a short version they can forward to a boss or a teammate. If your answer is clear and specific, it can travel inside their company and help you get the call.

**The applicant approach**

- Sending a 10-slide pitch deck immediately
- Writing a 300-word essay explaining every feature
- Saying 'I'm happy to send whatever you need, just let me know'

**The expert approach**

- Giving a high-level outcome and a mechanism
- Identifying a gap that requires a conversation
- Maintaining a boundary around your time and theirs

## The three-part response framework

To keep the meeting, your response should give them enough to judge fit and leave one detail for the call. Provide enough info to prove you can solve the problem, but leave a gap that can only be filled during a live demo.

Start with the specific outcome. Don't say you help people grow. Name the one big result you get for people in their role. If you sell a recruiting tool, say 'reducing time-to-hire for engineers' instead of 'better hiring'.

Use the prospect's words. If they wrote 'reporting takes too long', your outcome should mention reporting time. A summary that mirrors their language feels like an answer. A pitch feels generic.

Write the summary in three sentences. One sentence for the outcome, one for the mechanism, and one for the gap. That length is easy to read on a phone and gives you a natural place to ask for the call.

1. **State the specific outcome.** Lead with the primary result. Use a noun and a verb that describes a tangible business win.
2. **Explain the mechanism.** Describe the how in one sentence. Focus on the process and avoid vague adjectives.
3. **Identify the gap.** Mention one variable that depends on their internal data or workflow. This makes the call necessary to see if the solution fits.

## Templates for different scenarios

Your wording depends on how the prospect asked. A direct request needs a direct answer. A skeptical request needs more focus on ROI. Use these as starting points and swap the bracketed text for your offer.

Keep the reply under 75 words. Put the outcome first, the mechanism second, and the question last. That order gives the prospect a reason to keep reading and a clear next step.

If they ask for a deck, send a short summary first and offer the deck during the call. A deck without context is easy to skim and dismiss. A deck you walk through is a reason to meet.

- **them:** Can you just send over a summary of what you do first?
- **you:** I can do that. We help agency owners reclaim time on billing by automating their client reporting. Because every agency has a different reporting stack, a quick call is the only way to see if our approach fits your current workflow. Do you have 15 minutes Tuesday?
- **them:** Just email me the info.
- **you:** Happy to. We solve lead leakage using a shared inbox for SDRs. I've found that a PDF is usually too generic to be helpful, so I'd rather spend 10 minutes showing you how it works for a 40-person agency. Does Wednesday work?
- **them:** What exactly is the value prop here?
- **you:** The value is faster lead conversion. We do this by scoring leads based on their LinkedIn activity. I can't give a full summary because the ROI depends on your current lead volume, which is what we'd figure out on a brief call. Open to a chat?

## Common mistakes that kill the meeting

The biggest mistake is over-explaining. When you send a wall of text, you're telling the prospect your time is less valuable than theirs. You also give them a reason to say 'this doesn't fit' based on a sentence they skimmed and misunderstood.

Avoid vague language. Phrases like complete solutions, a full approach, or helping you grow are noise. They don't provide information. If a prospect can't visualize the result, they won't book.

Ask one question instead of sending a document. A question like 'Is reporting time the main issue, or is it the handoff between sales and delivery?' gives the prospect a reason to reply and gives you information for the call.

Don't send a calendar link without context. A bare link asks the prospect to do work before they understand why the call matters. Put the link after the outcome and the gap.

| | Dimension | Avoid this | Use this instead |
| --- | --- | --- | --- |
| Vague claims | We provide a platform that helps your sales team | We reduce manual data entry for sales reps |
| Over-sharing | Attaching a 15-page company overview | A 3-sentence summary and a calendar link |
| Tone | Sorry to bother you, but I'd love to show you | It's worth a 10-minute chat to see if this fits |

> Never apologize for not providing a full summary. Apologizing makes you sound like a vendor seeking permission rather than a partner providing a solution.

## What to do after you send the summary

Send the summary in the same thread where they asked. Don't start a new message or move to email unless they ask. Keeping the context makes it easier for them to reply.

End with a specific next step. A question like 'Does Tuesday at 10 or Thursday at 2 work for a 15-minute call?' is easier to answer than 'I'll get back to you'.

1. **Wait one business day.** Give them time to read it. If they don't reply, send one short follow-up that adds a new detail, such as a question about their current process.
2. **Ask about the gap.** Follow up with a question about the variable you mentioned in the summary. That gives them a reason to reply and gives you information for the call.
3. **Close the loop.** If they still don't reply, send a final note that says you'll stop following up. Keep it short and leave the door open.

## Doing this with Kinlead

Kinlead can hold the response logic in your sales playbook, so AI-written campaign messages use the same outcome and mechanism language. For a summary request, set the campaign to hand-off mode. The conversation moves to your [unified inbox](/features/unified-inbox) at the first reply, and you answer with the three-part framework yourself.

If you want to tune a first message before it goes out, you can read and edit queued campaign messages on the Actions page before they send. That keeps the first touch close to your voice without adding a review step to every reply.

## Related

- [Book LinkedIn demos](https://getkinlead.com/use-cases/book-linkedin-demos.md)
- [AI reply modes](https://getkinlead.com/ai-reply-modes-for-high-ticket-sales.md)
- [SDR templates](https://getkinlead.com/ai-sdr-templates-for-demo-requests.md)

## Common questions

**Should I attach a case study to the summary?**

Only if the case study is for a company exactly like theirs. A generic case study is just more text for them to dismiss. A specific one proves the outcome you claimed.

**What if they insist on a summary and refuse to book a call?**

Send a slightly more detailed version of the three-part framework. If they still refuse, they're likely not a buyer or aren't feeling the pain you solve.

**How short should the summary actually be?**

Keep it under 75 words. It should be readable in 10 seconds on a mobile screen without scrolling.

[Create a Kinlead account](https://getkinlead.com/signup) or [book a call](https://getkinlead.com/demo) to talk through pricing and setup.
