# How to message a prospect after they speak at an event
> Stop sending generic praise to event speakers. Use one specific point from their talk to open a real sales conversation on LinkedIn this week.
- HTML: https://getkinlead.com/linkedin-messages-for-event-speakers
- Markdown: https://getkinlead.com/linkedin-messages-for-event-speakers.md

**Short answer:** To message a speaker on LinkedIn, skip the generic praise. Quote one specific point they made, say why it matters to you or your clients, and ask a narrow question that connects their point to the problem you work on.

## Why generic praise fails

Speakers get a wave of messages in the hours after a talk. Most say some version of great session, loved the energy. The speaker reads two words, files it under polite noise, and moves on. Nothing in it asks them to think.

A message that quotes a specific argument does something different. It shows you were listening to the content and not just clapping at the end. That's the difference between a message that gets a reply and one that sits unread.

There's a practical reason to be specific. Most speakers give the same talk at three or four events in a year. If your message could have been sent to any of those rooms, it reads as a template, because it is one.

The bar is lower than it sounds. You don't need a brilliant insight. You need one sentence that could only have been written by someone who was in the room, and a reason to send it.

**Generic praise**

- Great talk at the summit today. I loved your energy. Let's connect.
- Amazing presentation on AI. Really inspiring stuff. Would love to add you to my network.

**Specific reference**

- Your point about the shift toward decentralized data caught my attention. I'm seeing the same friction with two clients right now. I'd like to connect.
- I appreciated your take on why traditional SDR pods break down. The handoff gap you described is the exact thing we're trying to fix.

## Pick the speakers worth a message

You don't need to message every speaker you saw. Pick two or three from the day and write to them properly. A short list you can quote accurately beats a long list of half-remembered sessions.

A useful filter: could you write the message without checking the agenda again? If you need the agenda to remember what they said, you don't have a detail worth quoting.

- They said something you disagreed with, or something you've been trying to say for months and couldn't.
- They described a problem your buyers have, in their language, on a stage your buyers were sitting in.
- They run a team that looks like your customer, or they advise companies that do.
- They gave a number or a timeline that surprised you. Numbers are easy to quote back and hard to fake.
- Skip anyone whose talk you can't summarise in one sentence. That's not a writing problem, it's a sign you don't have anything to say to them yet.

## The three-part message structure

Every message that works has the same three parts. None of them need to be long. The whole thing can be four sentences and still land.

If you can't fill in the anchor, don't send the message. Rewrite it later when you have something real, or leave this person alone.

1. **The anchor.** Name the event and one specific thing they said. A quote, a slide, a number, an anecdote. Not the topic. The topic is on the agenda; the detail is what proves you were in the room.
2. **The bridge.** Say how that point connects to something you or your clients are dealing with. One sentence. This is what gives the message a reason to exist beyond flattery.
3. **The ask.** Ask for an opinion or a short conversation about a narrow question. Not a demo, not a call to explore synergies. Something they can answer in two lines from their phone.

## Templates for different goals

The anchor stays the same. What changes is the bridge and the ask, because a networking message and a sales message are trying to do different things. Replace the bracketed text with real details from the talk.

Don't send the same template to three speakers from the same event. They talk to each other, and a copied message is worse than no message.

| | Goal | What to write |
| --- | --- | --- |
| Networking | I was in your session on [topic] at [event]. The point about [specific detail] changed how I think about [process]. I'd like to follow your work from here. |
| Sales discovery | You said [specific problem] is the biggest hurdle for [role] right now. We're building for that exact step. Curious whether [alternative approach] holds up in practice, or whether you've seen it fail. |
| Partnership | Your take on [detail] at [event] matches a project I'm running. We're stuck on [specific part of it]. Would you be open to a short exchange on how you got past it? |

## What to write in the first 48 hours

Send within two days. The talk is still fresh, they're still checking the event hashtag, and you're still a face in the room rather than a stranger from LinkedIn.

If the event runs multiple days, send after their session, not after the whole conference. The earlier you send, the less competition there is in their inbox.

Keep it short enough to read on a phone. Connection notes have a hard character limit, and even a full message after connecting should fit inside a notification preview.

Write the anchor first, then cut anything that isn't the anchor, the bridge or the ask.

```
Anchor: I was at [event] for your session on [topic]. The part about [specific detail] is the bit I wrote down.
Bridge: We hit [related problem] with [type of client], and your framing of [idea] gave me language for it.
Ask: How are you handling [narrow question] at [their company]?
```

## Common mistakes to avoid

Most people lose the reply by rushing the sale. Speakers are visible right after an event and get pitched constantly. If you look like a salesperson, they'll treat you like one.

Watch the ratio of I to you in the first two lines. If the opening paragraph is about your company, you've already lost them.

Don't attach anything. A deck or a one-pager in a first message tells the speaker you're running a sequence.

Follow-ups are where most of these messages die. If they don't reply, wait four or five days and send one more line with something new in it, like a link to their own talk or a related piece of work. If that gets nothing, stop.

- **you:** Hi Sarah, your talk at the SaaS Summit on churn was the one I stayed for. The slide about the 30-day window for customer success stuck with me. I'm seeing the same pattern at my agency. Would like to connect.
- **them:** Thanks for noticing that. It's a huge pain point right now. Happy to connect.
- **you:** Glad it resonated. Since you mentioned the 30-day window, are you finding automated triggers work better than manual outreach there, or does the human touch still matter?

> Never ask for a 30 minute demo in the connection request. It's too much commitment for someone who doesn't know you yet.

## Doing this with Kinlead

The slow part is finding the right people to write to, and having something specific to say when you do. The Steal Customers agent in Kinlead watches competitor company pages and optional founder or employee profiles, reads the comments on their recent posts, and turns commenters who look like buyers into leads.

Each lead keeps the post URL, what the post was about and what the person commented, so you have a detail to quote before you write anything.

Those details feed AI-written connection notes under 200 characters that open with why the person became a lead. Leads sit in lead groups, and any campaign can point at any group. If you have an attendee list, you can import a CSV of LinkedIn profile URLs into a group and work from there.

Kinlead sends from your own LinkedIn account through Unipile, and you can read and edit queued messages on the Actions page before they go out. The [Steal Customers](/features/steal-customers) page shows how the agent works.

## Related

- [Book LinkedIn demos](https://getkinlead.com/use-cases/book-linkedin-demos.md)
- [Connection request checklist](https://getkinlead.com/connection-request-checklist-for-founder-led-sales.md)
- [Connection requests for event attendees](https://getkinlead.com/connection-requests-for-industry-event-attendees.md)
- [Steal Customers feature](https://getkinlead.com/features/steal-customers.md)

## Common questions

**Should I send the message with the connection request or after they accept?**

Put the specific reference in the connection request. It gives them a reason to accept and proves you aren't a bot.

**What if I didn't attend the event but saw the recording?**

Say so. Mention you caught the recording and quote a specific line or moment. It shows you did the work.

**How long should I wait after the event to reach out?**

Two days at most. The content is still fresh in their mind and they're likely still checking notifications from the event.

**What if the talk was closed-door or under Chatham House rules?**

Don't quote specifics. Reference the theme and ask a question about it, or wait until they've spoken publicly on the same topic.

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