# How to use AI SDRs for a product launch
> A step by step guide to launching a product with LinkedIn outreach: pick high intent leads, write a short script, set safe limits, and handle replies.
- HTML: https://getkinlead.com/ai-sdr-outreach-for-product-launches
- Markdown: https://getkinlead.com/ai-sdr-outreach-for-product-launches.md

**Short answer:** To use AI SDRs for a product launch, start with a short list of people who already have the problem your product fixes. Write one message that names that problem and asks for a specific next step. Then send at a pace close to how you would work by hand and sort replies by intent.

## Define your launch target list

Most founders message their whole network on launch day. That gets a few likes and a lot of silence. The people who buy are usually the ones who told you about the problem before you built the product.

Build the list before you write the message. If you're launching a reporting tool for agencies, don't message every agency owner. Start with the ones who complained about manual reporting, asked for a feature you now have, or left for a tool that did this one thing well.

Sort the list by why they are on it. The reason becomes the first line of the message, and it tells you what to ask for. A list of 40 people with a real reason beats a list of 400 with a job title.

If you don't have a list yet, build one from behavior. People who commented on a competitor's launch post, asked a question in a group, or downloaded a related guide are better than a cold filter by job title. Save the post URL or the comment so the first line has a real reference.

- Former customers who left over a gap you closed
- People who asked for this feature in a call or comment
- Leads who went quiet when the old product could not do this
- Users of a tool that solves this problem now

**Broad approach**

- Messaging every connection you have
- Opening with 'We are excited to announce'
- Picking anyone with the right job title

**Targeted approach**

- Messaging a short list of people who mentioned the problem
- Referring to a call where they asked for this feature
- Targeting users of a tool that already solves this

## Write a launch script that asks for one thing

Your first message is not a press release. It is a question about the work they do. The ask is a short call or a feedback session, not a congratulations reply.

Open with the reason they are on your list. Say what the product does in one sentence. Then ask for a specific time or a specific next step. Vague interest dies in the second message.

Skip adjectives that could describe any product. Say what changes on Monday. 'It turns client approvals into one thread' tells the reader more than a paragraph about speed.

Keep a connection note short. It has to fit in the request box and read on a phone. Put the full story in the message that follows, not in the request.

- **you:** Hi Sarah, you mentioned last month that client approvals get lost in email threads. We built a tool that keeps every version and approval in one place. Would you be open to a 15 minute demo next Tuesday?
- **them:** That sounds interesting. We struggle with that right now. How does it handle version control?
- **you:** It keeps every version in one thread and timestamps approvals so there's no confusion. You can see it here: [your demo link]. Does Wednesday at 10 a.m. work for a quick walkthrough?

## Set sending limits you can live with

LinkedIn does not publish exact limits for invites, messages or profile views. Any number you see online is a guess based on someone else's account. Work within what your account has done before.

Space your actions. A burst of invites in a minute looks like a bot. A steady pace with gaps between actions looks like a person working through a list.

Match the send window to the lead's time zone. A request at 3 a.m. their time reads as automated even if you wrote every word.

If you sell to several regions, run one region at a time. A single campaign that fires in every time zone will either send at odd hours or sit idle for half the day.

1. **Audit pending invites.** Open your sent invitations and withdraw the ones that have sat for weeks. A pile of pending invites makes new requests riskier.
2. **Set a daily cap below your normal manual activity.** If you usually send a handful of invites in a work session, set the cap around that. Raise it after two quiet weeks, not before.
3. **Map time zones.** Group the list by region and send inside local business hours. Split the campaign by region rather than sending around the clock.
4. **Write a stop rule.** Decide now what you will do if LinkedIn shows a warning: pause the campaign, lower the cap, and check pending invites before restarting.

## Handle replies without losing the thread

The inbox is where launches get messy. You get real interest, feature questions, and polite 'not now' replies in the same hour.

Sort by intent before you answer. Interested people get a scheduling link. Feature questions get one clear answer and a demo ask. 'Not now' gets a month and a reason to come back.

Don't debate people who are only being polite. If there is no meeting and no qualifying question after two replies, move them to a later list and keep going.

Write your replies before the launch: one for interest, one for a feature question, one for 'not now'. You will send them many times. Having them ready keeps the tone even and stops you from writing a long answer at 11 p.m.

| | Reply type | Goal | Action |
| --- | --- | --- | --- |
| Direct interest | Book meeting | Send scheduling link immediately |
| Feature question | Check fit | Answer briefly and ask for a demo |
| Not right now | Keep the relationship | Ask for a better time to check back |

> Once a lead agrees to a meeting, stop all automated sequences for that person immediately to avoid sending a generic follow-up after they've already booked.

## Doing this with Kinlead

Kinlead finds people who match the customer you describe or your website, scores each lead from 0 to 100, and keeps only leads above the fit line. The Steal Customers agent can watch competitor company pages and founder profiles, read comments on recent posts, and turn commenters who look like buyers into leads with the post URL, topic and comment attached. You can point a campaign at any lead group. See [how Steal Customers works](/features/steal-customers).

Outreach runs from your own LinkedIn account through Unipile, a third-party LinkedIn provider. Kinlead never stores your LinkedIn password. Each account sends at most one action every 5 minutes, inside daily invite and message limits you set and inside a send window in the lead's time zone. Connection notes are under 200 characters and open with why that person became a lead. Queued messages can be read and edited on the Actions page before they send, and any campaign can be paused.

Replies from every campaign land in one inbox, sorted by intent. Choose hand-off at the first reply, AI replies until real interest, or AI replies until a meeting is booked with your scheduling link. You get an email when someone replies.

1. **Build the launch group.** Import a CSV of LinkedIn profile URLs or describe the customer. Keep the group separate from your everyday leads so the launch has its own numbers.
2. **Set the campaign goal and script.** Add your goal, tone and sales playbook. The AI writes messages and follow-ups from those inputs.
3. **Choose reply handling.** For a launch with high value leads, hand-off mode keeps you in every conversation. For volume, let the AI reply until there is real interest.
4. **Watch the inbox and settings.** Interested replies come first. Settings shows pending invitations and acceptance rate with warnings, and Kinlead pauses invites on an account and emails you when LinkedIn pushes back.

## Related

- [View pricing](https://getkinlead.com/pricing.md)
- [Book a demo](https://getkinlead.com/demo.md)
- [AI outreach features](https://getkinlead.com/features/ai-linkedin-outreach.md)

## Common questions

**Should I use InMail for a launch?**

InMail is a separate paid LinkedIn feature. For most launches, a connection request that names a real problem starts a better conversation than a long pitch. Use InMail only when you cannot reach the person any other way.

**How many people should I message on launch day?**

There is no published number that fits every account. Start below what you have done by hand, keep gaps between actions, and watch pending invites before you raise the volume.

**What if someone replies 'not right now'?**

Ask what would need to change and when to check back. Put them on a later list instead of sending another launch message.

**Can I run a launch campaign and my normal outreach at the same time?**

Yes, if both fit inside the same daily limits and send windows. Two campaigns sending at once can push an account past what it normally does, so set the caps for the total, not per campaign.

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