# How to connect with leads after a company announcement
> Use a press release, funding round or product launch as the reason for a LinkedIn connection request, then follow up without pitching too early.
- HTML: https://getkinlead.com/connecting-with-leads-after-company-news
- Markdown: https://getkinlead.com/connecting-with-leads-after-company-news.md

**Short answer:** A company announcement gives you a dated, specific reason to send a connection request, which is why it gets accepted more often than a blank invite. Pick news the person was involved in, mention one detail from it, and keep the note short. Then wait for the accept before you ask for anything.

## Find an announcement worth mentioning

Company pages post plenty of things that are useless as a hook. Job ads, reposts of customer testimonials and holiday greetings tell you nothing you can build a conversation on. What you want is a dated event that changed something for the person you plan to message: a funding round, a product launch, a new market, a senior hire, an award, an acquisition.

The announcement matters less than the person's connection to it. A press release about a new office in Rotterdam is a strong hook for the ops lead who has to staff it and a weak one for a designer in another country. Read the post, then read the profile, and check that the two actually touch.

1. **Start on the company page, not your feed.** Open the company page and click Posts. Read the last month of original posts and skip anything that is a reposted job ad or a customer quote. You are looking for something that happened on a date.
2. **Check the press page for what never got posted.** Most announcements live on the company's News or Press page before or instead of LinkedIn. A short paragraph there often carries a detail the social post left out, like a city, a name or a number you can quote back.
3. **Find the person's fingerprint on the news.** Look for the post the lead wrote, commented on or shared. If they said something in the comments, use their idea rather than the headline. That is a stronger hook than the announcement itself.
4. **Write the hook down before you write the note.** One line: what happened, when, and why this person cares. If you cannot fill that line, the announcement is not a hook for this lead. Move to the next one.

## Write a connection note that doesn't read like a pitch

The note has one job: give them a reason to click accept that isn't curiosity about what you sell. Two sentences is enough. One names the thing you saw, the other says why you are writing to them and not to someone else at the company.

Skip the congratulations-only note. Everyone sends those and they read as filler. Add a small observation or a question that shows you read past the headline. If you cannot think of one, send the request without a note and put the observation in your first message after they accept.

Keep it short enough to read on a phone without scrolling. Long notes get skimmed, and a skimmed note is a rejected note.

**Reads like a template**

- Hi Sarah, I saw your company announcement and wanted to connect. I help companies like yours with operations.
- Congratulations on the funding round! Would love to connect and explore how we could work together.
- I noticed Northwind opened a new office. I work with ops leaders on scaling. Open to a quick chat?

**Reads like a person**

- Saw the Rotterdam warehouse post. Curious whether you're hiring locally or moving people across. Would like to follow along.
- Your comment on the funding post about hiring in ops stuck with me. I watched two agencies handle that same jump last year. Happy to connect.
- Congrats on the acquisition. The part about keeping the Bristol team intact was the interesting bit. How's that going down?

> If the note would still make sense with a different company name pasted in, it isn't specific enough to send.

## Match the angle to the news

Different announcements carry different emotions, and the note should land on the right one. A funding round is about what happens next. A launch is about a problem they now own. An award is about the work behind it. Decide the angle before you type, because the angle is what makes the note sound like a person who read the thing.

| | News type | What the person is thinking about | Opening line that fits |
| --- | --- | --- | --- |
| Funding round | Hiring, new targets, pressure to spend it well | The bit about doubling the sales team is the part I'd want to hear more about. |
| Product launch | Adoption, support load, whether the market gets it | Saw the launch. Curious how the first month of support tickets is going. |
| New market or office | Staffing, local hiring, logistics | Rotterdam is a real jump from Leeds. Are you hiring there or sending people over? |
| Senior hire | What the new person is expected to change | Saw you brought in a new head of revenue. What's the first thing you're handing over? |
| Award or ranking | The work that earned it, and the team behind it | The ranking makes sense given the work you posted about in January. |
| Acquisition | Integration, retention, who reports to whom | Keeping the Bristol team intact is the hard part. How's the integration going? |

## What to send after they accept

Don't pitch on the accept. The request already told them you are paying attention. The first message should keep that going with one question they can answer in a sentence.

Send it the same day or the next morning if you can. A message that lands three weeks after the accept reads like a sequence, because it is one. If they don't reply, one follow-up about a week later is enough. Two is the limit before it starts costing you something.

- **you:** Thanks for connecting, Sarah. The Rotterdam line caught my eye because I've watched two agencies open a first site abroad and both got stuck on the same thing: hiring locally versus relocating people. Which way are you leaning?
- **them:** Relocating for the first six months, then hiring locally. The visa side is the bit nobody warned me about.
- **you:** That tracks. Both of the ones I watched ended up bringing in a local payroll partner earlier than planned for exactly that reason. Want me to send over what they ran into?
- **them:** Yes please, that would help.

## Time it right and keep a record

Reach out while the news is still news. A week or two after the post is the sweet spot: the team has had time to react internally, and the announcement is still near the top of their page. Past a month, mentioning it sounds like you are working through a list.

Keep a log. A plain file with one line per lead is enough. You want to know what you said, when they accepted and what you promised to send. This is also how you avoid mentioning the same announcement to two people at the same company, which happens more often than you would think.

```
Lead: Dana Whitfield, Head of Ops, Northwind
Hook: 12 March post, Rotterdam warehouse opening
Note sent: 14 March
Accepted: 16 March
First message: asked about local hiring vs relocation
Promised: the payroll notes from the Leeds agency
Follow-up due: 23 March
```

## Doing this with Kinlead

The Steal Customers agent watches competitor company pages and, if you want, founder or employee profiles. It reads the comments on their recent posts and turns commenters who look like buyers into leads, keeping the post URL, what the post was about and what they commented. That is the same hook you would find by hand, minus the scrolling.

Connection requests can carry an AI-written note under 200 characters that opens with why that person became a lead. Queued messages can be read and edited on the Actions page before they send, and a send window keeps outreach inside the lead's working hours. Leads sit in [lead groups](/features/lead-groups-and-scoring) that any campaign can point at, and you can book a [demo](/demo) to see the watch list set up on a competitor you already track.

## Related

- [Steal Customers agent](https://getkinlead.com/features/steal-customers.md)
- [AI LinkedIn outreach](https://getkinlead.com/features/ai-linkedin-outreach.md)
- [Booking demos](https://getkinlead.com/use-cases/book-linkedin-demos.md)

## Common questions

**Should I always send a note with the request?**

Only when you have something specific to say. A note that repeats the announcement back to them is worse than no note, because it looks like a mail merge. If you cannot add an observation, send the request bare and put the detail in your first message.

**How old is too old for an announcement?**

About a month. After that the news is background and referencing it makes it obvious you are working from a list. If you find something older that is genuinely relevant, mention it as context rather than as the reason you are writing.

**What if the news is bad, like layoffs or a recall?**

Leave it. Reaching out during a hard week reads as opportunistic, and people remember that longer than they would remember a good note. Wait for something neutral or positive.

**Can I mention the same announcement to more than one person at the company?**

One person per announcement is the safe rule. Two colleagues comparing notes on the same opening line is an awkward conversation you don't want to be the subject of.

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