# How to connect with leads who moved to a new company
> Use a past relationship to reach a lead who changed jobs. Templates, timing and follow-up steps for small B2B sellers entering a new account.
- HTML: https://getkinlead.com/connecting-with-leads-who-changed-companies
- Markdown: https://getkinlead.com/connecting-with-leads-who-changed-companies.md

**Short answer:** Connecting with a lead who changed jobs works when you use the shared history to ask about their new environment. A short note that mentions the old project and asks one specific question about the new company gets a better response than a generic congratulations message.

## Why a job change is a useful opening

A lead who has been in the same role for years has already defended the current stack to their boss. They know how to explain the renewal, the budget and the risks. A new person has not built that defense yet. They are usually hired to fix a process, hit a new target or replace something that was not working. That gives you a reason to ask about their plans without sounding like every other vendor. The same account can be hard to enter when the old vendor has a contract and a happy sponsor. A job change gives you a second path into the account through a person who already knows your work.

Use the opening to ask a question about how the new company handles the problem you solved together before. If you helped them cut reporting time at Northwind, ask how Acme handles reporting now. If you helped them fix a messy handoff, ask whether the new team has the same handoff problem. The connection is the shared history. The question is the reason to keep talking. Do not make the old win sound bigger than it was. One clear detail about the work is enough.

**Generic outreach**

- Targeting a lead who has been in the role for three years
- Asking them to replace a tool they already defended to their boss
- Sending a congratulations note with no question

**Job change outreach**

- Targeting someone who started in the last few months
- Asking how their new team handles the problem you solved before
- Entering the account while they are still reviewing current tools

## Finding people who changed jobs

LinkedIn search lets you look for people who worked at a company you had a win with and now work somewhere on your target list. Start with a short list of accounts you want to enter. Then search for people who moved from a past customer into one of those accounts. The list does not need to be big. Ten accounts and five past customers can give you enough people to work through in a week.

Look for people who can approve budget. A manager who uses the tool can help, but a director or VP is more likely to have room to change vendors. Titles like VP, Director, Head of Revenue, Head of Operations or founder are worth checking. A broad department filter will give you too many people who cannot make a decision.

Keep the list small enough to check by hand. A job change search can return hundreds of people, and most of them will not fit. Ten to twenty profiles is enough for a first pass. Open each profile and decide if the person is worth a note. If you cannot answer why they became a lead in one sentence, skip them.

1. **Build a target company list.** Start with accounts you want to enter, not every company on LinkedIn. Put the companies in a simple list so you can search for people who moved there.
2. **Search for people who worked at a past customer.** Use LinkedIn search to find people with your past customer in their experience and one of your target companies in their current role.
3. **Filter for roles that can approve budget.** Look at title and function. VP, Director, Head of Revenue, Head of Operations and founder are better than a broad department filter.
4. **Check the start date and recent posts.** Open the profile. Confirm the start date. Read the last two posts to see what they are talking about and whether the new company has the problem you solve.

## Writing the connection request

Use the request to remind them of a specific project and ask a light question. The note should mention the old company, the thing you worked on, and one detail about the new role. A congratulations note is easy to ignore because every vendor sends one. A note that says 'we fixed the reporting problem together' is harder to ignore because it is about their actual work.

Write like a person who remembers the work, not like a vendor who scraped a job change. 'Saw you moved to Acme' is fine. 'I help companies like Acme...' is not. Keep the note short enough to read on a phone. Aim for a reply. The meeting can come later.

The note should sound like you wrote it for one person. Mention the old company by name, the project by name if it had one, and one thing about the new role. If you only have the job change, say that. 'I saw you moved to Acme. We worked on the Northwind migration together. How is the new team handling data flow?' is enough.

- **draft:** Hi Sarah, saw you moved to Acme. We worked together at Northwind on the API migration. How is the new team handling data flow?
- **them:** Hey, good to hear from you. It is different here. We are still mapping the data flow.
- **you:** That is the same mess we had at Northwind. Happy to compare notes if it helps.

> The connection request should remind them of the work. Leave the demo ask for the message after they accept.

## The first message after they accept

Once they accept, reference the old result and ask about the new company. Do not jump to a calendar link. A question about their current process gives them a reason to answer. If they ask what you do, answer in one sentence and return to their problem.

The first message should focus on their new job. Keep your product out of it until they ask. If they moved to a company that is opening a new office, ask how they are handling the expansion. If they moved to a company that just raised money, ask what they are prioritizing. The news gives you a reason to be specific.

If they reply with a short answer, ask one follow-up question. Do not switch to a pitch. If they say the new team is still figuring it out, ask what they are using in the meantime. If they say it is better than the old company, ask what changed. The goal is to keep them talking about the work.

| | Part | What it does | Example |
| --- | --- | --- | --- |
| The hook | Names a change at the new company | I saw Acme is opening a second office in Berlin, which usually makes reporting harder. |
| The proof | Reminds them of a result from the old company | At Northwind we fixed that by simplifying the data flow. |
| The ask | Makes a small request that is easy to answer | Would it be worth a 15 minute call to see if the same approach fits your new team? |

## When they don't remember the old project

People change jobs and meet a lot of vendors. They may not remember your name. That is normal. Do not pretend you had a closer relationship than you did. Give them one concrete detail: the project name, the team, the problem you worked on, or the month you worked together.

If they still don't remember, do not force it. Ask a question about the new company. The shared history is useful, but a useful question about their current problem can carry the conversation on its own. The relationship gets you the reply. The question gets you the next message.

A short recap helps. 'We worked on the API migration at Northwind in 2023. I remember the reporting problem. You may not remember me.' That gives them a way to place you without making them feel bad. If they reply with 'sorry, remind me', send one line and move on.

**Weak recovery**

- I'm sure you remember me from Northwind
- We had a great relationship, don't you remember?
- Sending a long recap of every project you worked on

**Strong recovery**

- We worked on the API migration at Northwind in 2023. You may not remember me.
- I remember the reporting problem we fixed. Is that still an issue at Acme?
- If the old project is fuzzy, I can send a one line summary.

## Doing this with Kinlead

You can use Kinlead to build a lead group of people who match the customer you describe, then point a campaign at that group. The [Steal Customers](/features/steal-customers) agent 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 they commented.

For this play, set the campaign to hand the conversation to you at the first reply so the old relationship stays personal. Kinlead sends from your own LinkedIn account through Unipile, at most one action every 5 minutes, inside the limits and send window you set. LinkedIn does not publish exact invite or message limits, so the limits you set need to match what your account can handle.

Connection requests can carry an AI-written note under 200 characters that opens with why that person became a lead. Replies land in one inbox, classified by intent, with interested replies first.

## Related

- [AI sales playbook setup](https://getkinlead.com/ai-sales-playbook-for-linkedin-outreach.md)
- [LinkedIn connection request templates](https://getkinlead.com/ai-linkedin-connection-request-templates.md)
- [Book a demo](https://getkinlead.com/demo.md)

## Common questions

**Should I congratulate them in the first message?**

Yes, but keep it short. Use the congratulations as a bridge to a question about the new company.

**When is the best time to reach out after they start?**

The first few months are useful because they are still reviewing current tools and setting priorities. If you miss that window, a specific question about their new process can still work.

**What if they don't remember me from the previous company?**

Give one concrete detail: the project, the team or the problem you worked on. If they still don't remember, ask about the new company instead of pushing the old relationship.

**Do I need Sales Navigator to find job changes?**

No. LinkedIn's standard search shows current and past roles. Open the profile to confirm the start date and check recent posts.

**How do I ask for the meeting without making it weird?**

Ask after they describe a problem. Use their words, not a calendar link. 'Would it help to compare notes on that?' is enough.

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