# How to reconnect with former clients on LinkedIn
> Reconnect with former clients on LinkedIn using low-pressure messages, real templates, and a schedule based on how long you have been out of touch.
- HTML: https://getkinlead.com/connecting-with-former-clients
- Markdown: https://getkinlead.com/connecting-with-former-clients.md

**Short answer:** Reconnect with former clients by sorting them by how long it has been since your last project, then sending a short message that names the work you did together and asks a question about them. Leave your availability out of the first note. The goal is a reply, not a meeting.

## Sort your old clients by how long it has been

Your tone with a client from last quarter should not match the one you use for someone you last invoiced in 2019. Recent contacts remember the work and need less context. Older contacts may have changed roles, companies or priorities. Sorting by the date of your last deliverable tells you how much background to include in the first line.

Put each person into one of three buckets. Do not overthink the exact dates. The point is to avoid sending a five-year reconnection note to a client you finished a project with in March.

| | Time since last project | What they remember | Opening move |
| --- | --- | --- | --- |
| 6 to 12 months | The project and the people involved | Reply to a recent company update or ask how the project has held up since launch. |
| 1 to 3 years | The work, but not your current focus | Name the project, then ask what changed in their role or team. |
| 3+ years | Maybe the project, almost certainly not your last message | Introduce yourself again in one line and mention the specific work you did together. |

## Write a first message that doesn't ask for work

A reconnection message has one job: get a reply from someone who remembers you. Asking for availability, a call or a proposal in the first note turns a warm memory into a sales pitch. Leave the ask out.

Use a hook that exists outside your calendar. A new job, a product launch, a post they wrote, a shared client, or a plain acknowledgement that time has passed. Specific beats clever. If you cannot find a hook, say why you are writing now.

Include the project. Former clients talk to a lot of people. Two or three words about the work you did together bring the relationship back faster than a compliment about their career. If you are not connected, the request note is the only place to explain why you are appearing in their notifications.

**Asks for work too early**

- Hi Dana, it has been a while. I have some capacity next month and wanted to see if you need help with the same kind of work we did before.
- Hey Marcus, long time. Let me know if you want to jump on a call to catch up and explore synergies.

**Gives them a reason to reply**

- Hi Dana, I saw Northwind launched the self-serve plan last week. It made me think of the onboarding flow we rebuilt in 2022. Is that still the team you work with?
- Hi Marcus, I am going through old project notes and realized we never compared results after the Acme rollout. I am curious how the support queue looks now. No agenda, just cleaning up my records.

> Do not mention your availability in the first message. A reply is the only goal.

## Run the reconnection one client at a time

Bulk messages fail here because the hook is the whole message. If you skip the profile check, you end up referencing a job they left or a product that never shipped. Set aside twenty minutes and work through ten people, not a hundred.

If you are already connected, send a direct message. If you are not, the connection request carries the note. Keep it under two sentences and make the shared work the reason for the request.

1. **Find the person and confirm the basics.** Search by name and old company. Check their current title and company before you write anything.
2. **Pick one detail you can mention.** A recent post, a promotion, a launch, or the project you worked on together. Copy the exact name of the product or team so you do not guess.
3. **Send the first touch.** Direct message if connected. Connection request with a short note if not.
4. **Log the date and the hook.** Put the person, the hook and the date in a simple list. You will need it if they reply next month or not at all.

## Handle the reply without rushing to a pitch

When someone answers, you have permission to talk. That does not mean you should send a calendar link in the next sentence. Read what they wrote and respond to the thing they actually said.

Bridge to work only if they describe a problem you solve. A former client saying they are busy with a launch is not a buying signal. A former client saying the launch broke their onboarding flow is. Ask one question about the problem before you offer help.

Keep the same thread. Moving to email too fast feels like a handoff to a newsletter.

- **them:** Good to hear from you. We are heads down on the new billing page right now.
- **you:** That makes sense. The billing page is where most of the support tickets landed last time. Are you seeing the same thing or is it too early to tell?
- **them:** Too early, but I am worried about the upgrade path. We had a mess with proration before.
- **you:** I remember. I have been working on upgrade flows with two other teams this year. Happy to send the checklist I use if that is useful.
- **them:** Yes, send it over.
- **you:** Will do. I will keep it short.

## Follow up once, then leave it

Most reconnection notes get one reply or none. If they do not answer, wait two weeks and send one follow-up with something useful. A relevant article, a short observation about their market, or a note that you are closing your old project files. Do not ask whether they saw your last message.

After that, stop. A third message to someone who has not replied in years reads as pressure. Keep them on a list for a genuine trigger: a new role, a funding round, a product launch, or a post where they ask for help.

If they reply and then go quiet, treat that as a normal conversation. One check-in after a week is fine. Two is not. The same rule applies to former clients who were friendly but never bought again.

## Doing this with Kinlead

If your list is already in a spreadsheet, import it as a CSV of LinkedIn profile URLs into a [lead group](/features/lead-groups-and-scoring). You can then point a campaign at that group and write the outreach in your own voice.

Kinlead sends from your LinkedIn account through Unipile and never stores your password. Each account sends at most one action every five minutes, inside the invite and message limits you set and the [send windows](/features/campaigns-and-send-windows) you choose. That pace matters when you are messaging people who remember working with you.

Use hand-off mode for former clients. The first reply goes to you and lands in the [unified inbox](/features/unified-inbox) with an email alert, so you can answer as yourself instead of letting a template carry the relationship.

- Connection notes can be AI-written under 200 characters and open with why the person is a lead, which for this list is the project you worked on together.
- Queued messages can be read and edited on the Actions page before they send.
- Paused campaigns stop sending, and stale pending invitations are withdrawn automatically.

## Related

- [AI LinkedIn outreach](https://getkinlead.com/features/ai-linkedin-outreach.md)
- [Lead groups and scoring](https://getkinlead.com/features/lead-groups-and-scoring.md)
- [Unified inbox](https://getkinlead.com/features/unified-inbox.md)

## Common questions

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

If you are already connected, send a direct message. If you are not, send a connection request with a short note that names the project you worked on together. Do not use the request to ask for a call.

**What if they do not reply to my reconnection message?**

Wait two weeks, then send one follow-up with something useful. If that gets no response, stop and watch for a real trigger such as a new role or a launch.

**Is it strange to reach out after five years?**

Only if the first message asks for a favor. Say plainly that time has passed, name the work you did together, and ask a question about them. Most people answer a short, specific note.

**Can I reconnect with someone who left the company we worked with?**

Yes. Use their new company as the hook and mention the project from the old one. The shared work is the reason you are writing, not their current employer.

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