# Using AI to announce product updates to leads
> Learn how to re-engage LinkedIn leads by using AI to connect product features to specific buyer problems and job roles instead of sending generic messages.
- HTML: https://getkinlead.com/ai-sdr-outreach-for-product-updates
- Markdown: https://getkinlead.com/ai-sdr-outreach-for-product-updates.md

**Short answer:** To tell LinkedIn leads about new features, don't send a generic announcement. Group your leads by the specific problem the update solves, then use AI to write messages that connect the new feature to the lead's specific job title or previous conversation.

## Segment your leads by problem

Most founders message their entire lead list when a new feature drops. This feels like a newsletter and people ignore it. To get a response, you have to separate your leads based on which specific problem the update actually solves for them.

A CTO cares about a different part of your update than a Head of Operations. If you send the same message to both, they'll likely mute you. Create small groups of leads based on their job title or the pain points they mentioned in previous conversations.

Start with the leads who already described the problem your update fixes. If a lead told you last quarter that manual reporting eats their Fridays, they belong in the first group. If you have no previous conversation, use the job title and the language in their LinkedIn headline. A 40-person agency owner who lists 'ops' in their headline is a better fit for a reporting update than a designer who lists 'brand.'

Keep groups small. A group of 20 leads who share a problem is easier to write for than a list of 500. You can write one message per group and still sound specific. If you have a large list, start with the smallest group. Twenty leads who share a clear problem will teach you more than a hundred leads who don't. You can always expand the group after you see what gets replies.

| | New feature | Target lead | Problem solved |
| --- | --- | --- | --- |
| Automated reporting | Ops managers | Manual data entry and spreadsheet errors |
| API integration | CTOs | Fragmented tool stack and data silos |
| New dashboard | Project leads | Poor visibility into team progress |

## Build a feature-to-value map

AI can write the messages, but you have to provide the logic. A feature is what the product does. Value is what the customer gets. When you announce an update, focus on the shift from the old way of doing things to the new way.

Avoid company-centric language. Phrases like 'we are proud to announce' or 'we've worked hard on' don't matter to the lead. They only care if the update makes their day easier or their boss happier.

Write the map before you open the AI tool. List the feature, the person who cares, and the sentence you would say to that person at a conference. If you can't say it out loud without sounding like a press release, the AI will make it worse. The map doesn't need to be fancy. A three-column spreadsheet with feature, person, and sentence is enough.

For example, 'automated reporting' is a feature. 'You stop copying numbers into a spreadsheet every Friday' is the value. The second one gives the AI something to work with.

**Company-centric**

- We just launched a new reporting tool. Check it out here.
- Our team is excited to share that we now have API integrations.

**Problem-centric**

- I remember you mentioned manual reporting takes your team four hours a week. We built a tool that does this in one click.
- Since you're managing a fragmented tool stack, I thought you'd want to see the new API that connects your data automatically.

## Draft your AI prompt for personalized outreach

To get a human-sounding message from AI, you need to constrain it. If you give it a vague prompt, it uses corporate jargon and adjectives that signal 'bot' immediately.

Your prompt should define the role of the sender, the profile of the recipient, and the exact outcome you want. Tell the AI to be direct and to avoid the 'excited' tone that AI defaults to.

Give the AI the lead's own words when you have them. Paste a line from your last conversation or from their LinkedIn post. The message will sound like you remembered them, because the AI is using their language, not yours.

1. **Input the context.** Provide the lead's current role and the specific feature update you're announcing.
2. **Ban the fluff.** Instruct the AI to avoid launch-day adjectives and corporate enthusiasm.
3. **Set the opening.** Tell the AI to open with the specific reason they are receiving the update, such as a previous conversation or their job responsibility.
4. **Limit the length.** Set a strict length so the message is readable on mobile without tapping 'see more'.

```
Write a LinkedIn message to a [Job Title] about [Feature]. Use a professional but casual tone. Do not use launch-day adjectives or corporate enthusiasm. Start by mentioning [Specific Pain Point]. Keep it short enough to read on a phone without tapping 'see more'. End with a low-friction question.
```

## The re-engagement sequence

A single message often gets lost. Instead, use a short sequence that builds value over a few days. The first message introduces the solution, the second provides proof, and the third offers a low-stakes way to see it in action.

Don't push for a 30-minute demo in the first message. That's a high-friction ask for someone who hasn't spoken to you in months. Start by asking for their opinion or offering a short video.

If they reply, stop the sequence. The worst thing you can do is keep sending scheduled messages after someone has answered. Move the conversation to a real thread and answer their question.

The sequence should feel like three separate thoughts, not three reminders. If the first message gets no reply, the second should add a new detail, not repeat the first one.

- **you:** Hi Sarah, remember when you mentioned that tracking team hours was a nightmare? We just released a one-click export that handles that. Thought it might save you some time.
- **them:** That sounds interesting. How does it handle different time zones?
- **you:** It normalizes everything to your primary office zone. I actually have a 2-minute Loom showing exactly how it works. Want me to send it over?

> Avoid sending the scheduling link in the first message. It feels like a sales pitch rather than a helpful update.

## Use the lead's own words

The best product update message sounds like a follow-up to a conversation you already had. That means you need to keep notes on what leads told you. Even a single line in a spreadsheet is enough. This is also why generic AI messages fail. The AI has nothing specific to use, so it fills the space with adjectives.

When you write the prompt, include the exact phrase the lead used. If they said 'our reporting is a mess,' use that phrase. If they said 'I spend too much time in spreadsheets,' use that. The AI will mirror it, and the lead will notice.

If you don't have notes, look at their recent LinkedIn activity. A post about hiring an ops person or a comment about a messy tool stack gives you the same signal. Use that public language in the message.

## Doing this with Kinlead

You can automate this by using [lead groups and scoring](/features/lead-groups-and-scoring) to organize leads by the problem they face. Instead of manual prompting for every lead, use a sales playbook to guide the AI's tone and positioning.

Kinlead writes messages from the campaign's goal, tone and your playbook. You can read and edit queued messages on the Actions page before they send, and set the campaign to hand the conversation to you at the first reply or once real interest is shown. You can pause any campaign if the replies show the message is off.

1. **Group your leads.** Organize your leads into lead groups based on the specific feature they need.
2. **Upload your playbook.** Import your sales script as a playbook so the AI knows how to position the update and which pain points to mention.
3. **Launch the campaign.** Create a campaign where AI writes messages based on that playbook and the lead's LinkedIn profile.
4. **Manage the hand-off.** Set the campaign to hand the conversation to you at the first reply or once real interest is shown.

## Related

- [AI LinkedIn outreach](https://getkinlead.com/features/ai-linkedin-outreach.md)
- [Unified inbox](https://getkinlead.com/features/unified-inbox.md)
- [Outbound for founders](https://getkinlead.com/use-cases/outbound-for-founders.md)

## Common questions

**Should I use a LinkedIn post or a DM for updates?**

Use posts for general awareness and DMs for leads who already described the problem your update solves. A DM lets you tie the feature to a specific conversation.

**How often can I update leads without being annoying?**

Only message leads when the update solves a problem they actually have. If you have three updates in a month, group them into one message.

**What if the lead never replied to my first connection request?**

A new feature is a good reason to try again. Send a new request or message that focuses on the new solution rather than asking why they didn't reply before.

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