# AI SDR playbook for reaching out to former colleagues
> Reconnect with former colleagues on LinkedIn without a pitch: pick the right people, write a first message that gets a reply, and follow up once.
- HTML: https://getkinlead.com/ai-sdr-playbook-for-former-colleagues
- Markdown: https://getkinlead.com/ai-sdr-playbook-for-former-colleagues.md

**Short answer:** Reconnecting with former colleagues works when the first message asks for nothing. Pick the people you could still hold a five minute conversation with, open with a detail only someone who was there would know, and ask about their current work before you mention yours.

## Decide which former colleagues are worth a message

Your connections list is mostly people you would struggle to describe in one sentence now. That is fine. Keep the ones you could still talk to for five minutes without checking their profile first, and leave the rest alone.

The mistake is treating every former colleague the same way. A message to the person at the next desk reads badly if you write it like a job application. A message to the director who signed off your budget reads badly if you write it like a text to a mate. Sort the list before you write anything.

Two things decide where someone lands: how often you actually spoke, and whether they had power over your work. Frequent plus peer means lead with a memory. Rare plus senior means lead with a result you delivered under them, then one specific question.

| | Tier | Who they are | What to lead with | What to ask for |
| --- | --- | --- | --- | --- |
| Peer | People at your level you spoke to most weeks | A shared project or a running joke | A catch-up with no agenda |
| Former manager | Someone who reviewed your work and knows what you can do | A specific thing you learned from them | Their read on a problem you are stuck on |
| Skip-level or exec | People two levels up who knew your name | A result you delivered while they were there | One short question, not a meeting |
| Adjacent team | People you worked with on one project and never closely | The project that connected you | Permission to send one useful link |

## Write a first message that gets a reply

The first message has one job: get a reply. Not a meeting, not a demo. If your opening line is a pitch, they read it as a pitch, and the years you worked together stop counting for anything.

It should also show you remember them specifically. That means a detail only someone who was there would know. Not the company name, which anyone can look up in ten seconds. Something about how the work actually went.

1. **Open with the detail, not the greeting.** Skip 'I hope this finds you well'. Start with the thing that made you think of them: a launch they posted about, a piece of news about the old team, a project you both survived. One sentence.
2. **Say how long it has been, briefly.** 'It's been a while' or 'I've been meaning to send this for ages' handles the silence in five words. Don't apologise for it at length.
3. **Ask about them first.** One question about their current work. Not 'how are you', which is easy to answer badly. Something they will enjoy answering, like what changed after the reorganisation or how the new team is set up.
4. **Stop before the ask.** The first message can end with no request at all. A reply is the win. If you need an ask, make it one easy question they can answer in two lines.

## Scripts that don't read like a template

A conversation that paused years ago should pick up where it stopped. If you never used words like synergy or optimisation with this person, don't start now.

Here is what a peer catch-up looks like when it works. The first message carries a memory, the reply carries warmth, and the question arrives only after both.

- **you:** Marcus, saw you moved to Acme as head of ops. That Q4 at Northwind when we rebuilt the shipping schedule still comes up whenever I have to explain bad planning to someone. How's the new team?
- **them:** Ha, I still remember the spreadsheet you built at 2am. Team is good, smaller than Northwind but we ship faster. What are you up to now?
- **you:** Running my own agency for e-commerce ops, mostly cleaning up the kind of mess we used to inherit. Can I ask you one thing about how Acme handles carrier contracts? I'd rather hear it from you than guess.
- **them:** Sure, fire away.

## Follow up once, with something useful

Most former colleagues mean to reply and then don't. That isn't rejection, it's a normal week. One follow-up after about a week is expected and nobody minds it.

Skip 'just checking in'. It tells them nothing and hands them a task. The follow-up should carry something: an update on the thing you asked about, a link that helps their current job, or news from the old team they would actually want.

- Wait roughly a week. Same day feels pushy, a month later they have forgotten the first message.
- Reference the first message in one clause so they don't have to scroll back.
- Give them an easy exit. 'If now is a bad time, say so and I'll leave it' gets more replies than silence.
- Do not send a third message.

> One follow-up, then stop. A third message to someone who already knows you costs more than the conversation was worth.

## Turn the catch-up into a work conversation

Once they reply, you have a short window. They are warm and they are thinking about you. Don't spend it on small talk for four messages and then spring a demo.

The move is to ask about the problem your product solves without naming your product. If they describe the problem, your work comes up on its own. If they don't have the problem, you find out early and nobody is embarrassed.

**Pitch in the second message**

- Great to reconnect! I've just launched a platform that could transform how your team handles vendor management. Can I book 30 minutes?
- Let me know if you'd be open to a quick call to explore how our organisations could work together.

**Ask about the problem first**

- Since you're running vendor ops now, how are you handling supplier onboarding? Everyone I talk to says it's the part nobody has time for.
- One thing I'm curious about: does Acme still do the quarterly contract review, or did that die with us at Northwind?

```
Hi {first name}, {specific detail from their work or a project you shared}. {One line on how long it has been.} Quick question: {something about their current work that touches the problem you solve}? No agenda either way, I'm mostly curious.
```

## What to do when they say no or go quiet

Some will say no. Some will say nothing and stay silent permanently. Both are fine and neither means you delete the contact.

A no today is often a maybe in nine months. The people who get value from an old network are the ones who stay in loose touch without asking for anything: a comment on their post, a useful link twice a year, remembering what they actually do.

- If they say not right now, ask whether you can check back in a quarter, then put it in your calendar and do it.
- If they point you to a colleague, thank them and use their name in the first line to that person.
- If they never reply, leave the connection quiet for at least six months.
- If a conversation fizzles after a few messages, don't send a bump.

## Doing this with Kinlead

Kinlead helps when the list grows past the point where you can track it in your head. Leads live in lead groups, and you can import a CSV of LinkedIn profile URLs into one group per tier, so the peer list and the exec list never get mixed. Every lead gets a score from 0 to 100 against the customer profile you describe, and leads under the fit line are dropped, which is useful when you are deciding who gets a personal message and who waits.

Connection requests can carry an AI-written note under 200 characters that opens with why that person became a lead, and queued messages can be read and edited on the Actions page before they send. Set the campaign to hand the conversation to you at the first reply. You want to be the person typing back to someone you used to work with. Details are on [lead groups and scoring](/features/lead-groups-and-scoring).

## Related

- [AI outreach for founder led sales](https://getkinlead.com/ai-outreach-for-founder-led-sales.md)
- [Import leads from a CSV of profile URLs](https://getkinlead.com/ai-sdr-csv-import-workflow.md)
- [Lead groups and fit scoring](https://getkinlead.com/features/lead-groups-and-scoring.md)

## Common questions

**Should I send a connection request or a message first?**

If you're already connected, send a direct message. If you aren't, send a connection request with a short note that mentions where you worked together, then message once it's accepted.

**Is it strange to pitch an old boss?**

It's only strange if the pitch arrives before the relationship does. Reopen with a memory, ask about their current work, and let your product come up as the answer to a problem they've described.

**How long should I wait before following up?**

About a week. One follow-up that carries something useful is normal. After that, leave it and stay in loose touch instead of messaging again.

**What if they reply but the conversation goes nowhere?**

Let it end politely and keep the person in your loose network. A dead conversation today is still a live contact next year, and pushing turns it into an awkward one.

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