LinkedIn outreach playbook for early stage founders
A practical system for founders: pick a narrow fit profile, find leads through behavioral triggers, and run a low volume sequence that gets replies.
Get startedShort answer
Founders get replies on LinkedIn by narrowing the target to one sentence they can defend, finding people who have already described the problem in public, and sending a short note that references it. Then run a slow follow up that asks for the call only after the buyer has explained their situation.
Define your high fit profile
Most founders start with a job title and a company size, then wonder why replies dry up. A title tells you where someone sits, not what they're dealing with this quarter. Two heads of demand gen at similar companies can be in completely different situations, and the same message lands differently on each.
Write the profile as one sentence you could say out loud: the role, a company attribute that changes how they buy, and something that happened recently. "Head of demand gen at a Series A fintech that just hired a VP of Sales" is a profile. "Marketing managers at B2B companies" is a mailing list.
Keep the list small enough to open every profile before you message it. If you can't read the last ten profiles in an afternoon, the list is too big for someone who is also running the company. A short list you actually read beats a long one you scrape and forget.
Broad targeting
- Every marketing manager at B2B companies.
- Note: I help marketing teams grow pipeline with our platform.
- Nothing in that message could only be true for this person, so it reads like a blast.
High fit targeting
- Head of demand gen at Series A fintechs that just hired a VP of Sales.
- Note: Saw you brought on a new VP of Sales last month. That usually shifts the focus from lead volume to lead quality.
- The note references a change the buyer is living through right now, which is hard to fake at scale.
Find leads through behavioral triggers
The best moment to reach someone is when they've already said something in public about the problem. You're not guessing who has the pain. You're reading it.
Competitor pages are the easiest place to start. When a competitor posts a feature update, the comments fill with people asking whether it handles a specific case, or saying the workflow still breaks for them. That comment thread is a list of people with the problem your product addresses, written in their own words.
The same works on posts from people in your space and on your own posts. Anyone who comments on a topic you sell into has raised their hand in public. You don't need a Sales Navigator seat for this. LinkedIn's standard search and a competitor's page will get you there.
- 1
Pick a trigger post
Open a competitor's company page and read the last few weeks of posts. Choose one that touches the pain you solve, not their funding announcement.
- 2
Read the comments, not the likes
Look for questions, workarounds and complaints. "Does this work if you have two CRMs?" is a better lead than a thumbs up.
- 3
Check the profile before you save it
Open the commenter's profile. Confirm the role, the company and the rough size. If they don't match your sentence from the first section, skip them.
- 4
Save them with the context
Put the profile in a group named after the post topic and paste the comment next to it. When you write the note a week later, you'll still know why they're on the list.
Write a connection note that doesn't read like a pitch
The note has one job: get the accept. If it pitches, it reads like the other requests in their inbox and gets ignored.
Keep it under 200 characters, open with the thing you noticed, and say what you're building in plain words. No adjectives about your product and no calendar link.
If they don't accept within a couple of weeks, leave it. Withdrawing and resending the same note rarely changes the outcome, and it burns the one introduction you get.
Example
- You
Hi Sarah, saw your comment on Northwind's post about API syncing. I'm building a tool that handles that sync differently and would like your read on it. Open to connecting?
- Prospect
Hey, yeah. The sync has been a mess for months. Happy to connect.
- You
Thanks. What does your current setup do when a record changes on both sides at once?
Write the note in the lead's words, not yours. If they said the sync is a mess, don't call it a data integrity challenge.
Run a low volume follow up sequence
After the accept, most founders send a calendar link in the first message. That ends the conversation before it starts, because the buyer hasn't told you yet whether the problem is worth a meeting.
Move in three beats: acknowledge what they said, give them something small, then ask. Space them out. A sequence that runs over a week and a half reads like a person. Five messages in two days reads like a tool.
The first message after the accept should be a question, not a pitch. Ask what their current setup does, or what they tried before. The answer tells you whether a call is worth asking for.
Day 1
- When
- Acknowledge
- What you're doing
- Thank them for connecting and ask one question about the thing they described in their comment.
Day 4
- When
- Give something
- What you're doing
- Send a short observation or a two sentence tip that solves a piece of the problem. No ask.
Day 8
- When
- Ask for the call
- What you're doing
- Say what you'd cover in 15 minutes and include your scheduling link.
If they don't reply to the day 8 message, one more short follow up is fine. Then stop. A founder who keeps messaging after two silences is a founder the buyer avoids at events.
Handle replies without rushing to a calendar link
When someone replies, answer the question they actually asked. Founders lose more conversations by over-answering than by under-answering. A two line reply that asks something back keeps the thread alive. A five paragraph explanation of your architecture usually ends it.
Notice how the reply below doesn't pitch. It asks what they run, then offers the call once the buyer has described the mess themselves.
Example
- Prospect
How is this different from what we already use?
- You
Depends what you're running now. If it's Northwind, the difference is that we don't need a separate sync job. What are you on today?
- Prospect
Northwind plus a Zapier chain someone built two years ago.
- You
That chain is usually where it breaks. Worth 15 minutes to look at it together? I can send a link.
Answer the first reply yourself. Automating the opener is fine. Automating the answer to "how does this work with our stack" is how you lose a warm buyer.
Doing this with Kinlead
Kinlead runs this loop without the copy and paste. The 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, so the note writes itself.
You describe the customer once and each lead is scored from 0 to 100 against that profile. Leads below the fit line aren't kept, which keeps the list small enough to read. Leads sit in lead groups, and any campaign can point at any group.
- Connection notes are written by AI under 200 characters and open with why that person became a lead.
- Each LinkedIn account sends at most one action every 5 minutes, inside daily limits you set and a send window in the lead's time zone.
- Queued messages can be read and edited on the Actions page before they send, and any campaign can be paused.
- Pick hand-off mode and the conversation comes to you at the first reply. Replies from every campaign land in one inbox, classified by intent.
Kinlead connects through Unipile, a third party LinkedIn provider, and never stores your LinkedIn password. It can't promise LinkedIn won't restrict an account, so keep your limits conservative.
Frequently asked questions
Related
Get started with Kinlead
Prefer markdown? LinkedIn outreach playbook for early stage founders.md