LinkedIn outreach for product-led growth
Convert trial users and active free users into paid customers by targeting specific product usage triggers and behaviors inside LinkedIn outreach.
Get startedShort answer
Product-led growth outreach on LinkedIn targets people who already use your product. You pick usage events that show a user is stuck or getting value, then send a short message that helps them reach the next step or see the paid feature that fits their work.
Identify your conversion triggers
Don't message every person who signs up for a trial. Most trial users are still deciding whether the problem is worth solving. A message that lands before they have a reason to care reads like a cold sales pitch with a creepy detail attached. The person wonders how you know what they clicked and why you care.
Start with product data you already have: onboarding steps completed, number of projects or documents created, invites sent, days since last login, and which features they use. Pick one or two events that usually come before a paid upgrade in your own account base. If you don't know which events matter, ask support and customer success what new users ask before they pay. Their answers are better than a guess from a dashboard.
LinkedIn is a secondary nudge, not the main onboarding experience. Use it when someone is stuck on a specific step or when a free user is getting real work done and hasn't seen the paid feature that fits that work. The message should feel like a useful note from someone who knows the product, not a check-in from a sales team. If the product can solve the issue with an in-app tooltip, do that first.
Write the trigger as a sentence before you write the message. 'Invited two teammates but has not connected a data source' is a trigger. 'Signed up last month' is not. A good trigger tells you what to say and what to leave out.
Trial users
- User segment
- Signed up but didn't finish onboarding
- The trigger
- Help them finish the first key action
Power users
- User segment
- High daily use on a free plan
- The trigger
- Show the paid feature that fits their work
Stalled users
- User segment
- Active for a few days, then stopped
- The trigger
- Find the friction point
Feature users
- User segment
- Using one tool heavily
- The trigger
- Show the full version of that tool
Champion users
- User segment
- Invited teammates but hasn't paid
- The trigger
- Help them make the case to a manager
Segment your lead lists
Sending the same message to a cold prospect and a trial user is a mistake. A cold prospect needs to be convinced the problem exists. A trial user already knows the problem and is testing your solution. Mixing them makes your note too aggressive for one person and too vague for the other.
Name lists by the action that put the person there: trial-stalled-import, free-team-invite, paid-feature-trial. Keep the list small enough that you can read the trigger before you write the message. If a list has more than one trigger, split it. The message only works when the first line proves you know what the person did.
Add one field for context: the feature or step that caused the trigger. A list called 'trial users' gives you nothing. A list called 'trial users who created a report but did not share it' tells you to ask about sharing. The same rule applies when you import a CSV of LinkedIn URLs. Put the reason for the import in the group name, not in a note you will forget.
Cold prospect approach
- I saw you manage a team, do you struggle with project visibility?
- Our tool helps teams spend less time on reporting.
- Would you be open to a demo to see how it works?
PLG user approach
- I noticed you set up a few projects in the app. Have you tried the automation feature yet?
- Since you're using the reporting tool, the custom dashboard might help with your weekly syncs.
- I can record a short walkthrough of how to automate those projects if that helps.
Write the PLG outreach sequence
Keep the first message about the user's work, not your calendar. A trial user can see your product already. They don't need a pitch about the category. They need one specific tip tied to something they did.
Use three beats: observation, useful next step, low-friction offer. The observation shows you looked at their account. The next step gives them a reason to reply. The offer asks for a small action such as a recorded walkthrough or a short setup review.
Don't ask for a demo in the first message. The user has not agreed that a call is worth their time. If they reply with a question, answer it before you mention a meeting. The thread below shows the shape.
Keep the note short enough to read on a phone. One observation, one suggestion, one question. If you need three sentences to explain the tip, record a video instead. The video also gives you something to send when they ask how.
Example
- You
Hi Sarah, saw you joined AcmeApp and started using the lead scraper. Most people find the CSV export helpful at this stage to clean their data.
- Prospect
Oh thanks. I actually struggled with the export yesterday.
- You
That's common. I noticed you haven't tried the auto-formatter yet. It saves users a chunk of time on manual cleanup.
- Prospect
I didn't see that option. Where is it?
- You
I can record a short screen recording showing how to set it up for your workflow. Want me to send it?
Paste this job
Hi {first}, I saw you started {action} in {product}. Most people at that point use {feature} to {outcome}. Want a short example?The hand-off to a meeting
Move to a call when the user signals that the product problem is real and your help is useful. Signals include a reply with a question about setup, a request for the feature you mentioned, or a sentence like 'that would save us time.' A polite 'thanks' is not a buying signal. Answer the question, then offer a next step.
Frame the call around their setup, not your feature list. A trial user wants to know whether the tool will work for their team. A generic demo invites them to postpone. A short working session gives them a reason to show up.
If they say no, leave the door open with a resource. Send the help doc or the video and stop. A trial user who ignores a meeting request may still upgrade on their own. The outreach should not make them avoid the product.
- 1
Wait for the value signal
Ask for a call only after the user says thanks, says that would help, or asks a technical question about a paid feature.
- 2
Offer a specific outcome
Instead of 'can we chat?', say 'Let's spend 15 minutes on your setup so the trial matches your actual workflow'.
- 3
Provide the link last
Send your scheduling link after they agree to the outcome. This keeps the link from looking like spam in the first message.
Keep the message from feeling like surveillance
A product trigger can sound like you watched the user through a window. 'I saw you clicked the export button three times' is too much. 'I saw you started exporting your first report' is enough. Mention the work, not the click trail.
Use language the user would use. If your app calls it a workspace, don't call it a tenant. If the user created a campaign, ask about the campaign. Product names and internal labels make the message feel automated.
Give the user an easy exit. 'If this isn't useful, ignore this note' works better than pretending to be a friend. The goal is to help a user who already raised a hand by signing up. Respect the hand.
Mention one product action in the first line, at most. More detail makes the message feel like a report, not a note.
Doing this with Kinlead
Export the LinkedIn URLs of the trial and free users you want to reach and import them into a lead group. Keep each trigger in its own group so a stalled trial user never gets the same note as a heavy free user.
Point one campaign at each group. Kinlead can write a connection note under 200 characters that opens with why the person became a lead, and it sends at most one action every 5 minutes inside the daily limits and send window you set.
Choose hand-off mode for product questions. The campaign stops and the reply lands in your inbox, so you can answer the setup question yourself. Pause a campaign when a product change makes your message wrong.
LinkedIn does not publish exact invite limits. Set daily limits you can live with and check pending invitations and acceptance rate in settings. Kinlead shows both with warnings so a stale pending pool doesn't sit unnoticed.
Frequently asked questions
Related
Get started with Kinlead
Prefer markdown? LinkedIn outreach for product-led growth.md