A daily LinkedIn outreach routine for founders

A daily LinkedIn outreach routine for founders who build product all day: what to check first, how to sort replies, and where to spend fifteen minutes.

Get started

Short answer

A daily LinkedIn outreach routine for founders works best in a fixed order: answer the replies you already have, check what's queued to send tomorrow, then spend fifteen minutes finding a few people worth a message. Sourcing comes last because replies are the only part that turns into calls.

Check replies before you do anything else

The first ten minutes of your outreach day belong to people who already wrote back. They replied while you were shipping, and every hour the reply sits there makes the conversation colder. Open the inbox, answer everything, close it.

Founders who skip this and go straight to sourcing end up with a pile of half-finished conversations and a queue of new messages nobody asked for. New messages are cheap to produce. Replies are the ones that turn into calls.

Do this before you open your editor, your email or Slack. The moment you start on product, the reply block stops happening, and a message that arrives at 8am and gets answered at 6pm reads very differently to the person waiting.

  1. 1

    Clear the inbox first

    Answer every reply, including the noes. A short thanks-and-no closes the loop and gets the person out of your head.

  2. 2

    Move interested people to a time

    If someone asks a question or shows interest, answer it and put your scheduling link in the same message. Asking whether they'd like a call and waiting for a yes burns a day.

  3. 3

    Pull back stale invitations

    Withdraw connection requests that have been pending for a couple of weeks. A pending pile that never moves tells you your requests aren't landing.

  4. 4

    Only then open the sourcing tab

    Set a timer. When it rings you stop, even if you found fewer people than you planned.

Sort every reply by what it actually says

Most inboxes are a flat list, so you read messages in the order they arrived. That's the wrong order. Sort by what the person actually said: interested first, questions second, everything else after.

Four kinds of reply cover almost everything. Each has one action and one place it should end.

The reply that costs founders the most is the polite maybe. Someone says it sounds interesting and you leave it sitting because you don't want to push. Ask a direct question instead: is this a this-quarter problem or a next-year problem? Either answer tells you what to do next.

Interested

Reply
Answer the question, then send the scheduling link in the same message
What to do
A booked call

Curious but not ready

Reply
Answer, ask one thing back, no pitch
What to do
A follow-up you set for two weeks

Wrong fit

Reply
Say thanks, name who you do help, stop
What to do
Closed

Not now

Reply
Ask when to come back and write the date down
What to do
A reminder in your calendar

Find a handful of people worth a message today

You don't need a big list. You need five people you can say something true to. Searching by job title gives you strangers who have read forty identical messages this month.

Look for activity instead. Someone who commented on a competitor's launch post, asked a question in a group, or wrote about hiring for the role your product supports is already thinking about the problem. That comment is your reason for writing and your first line.

Save the profile URL and one note about why you picked them. If you can't write the note in a single sentence, skip the person. That filter saves an hour a week on its own.

Five a day is plenty. A handful of conversations you can keep up with beats a big list you never get to.

Sourcing that wastes the day

  • Searching 'founder' in a city and working down the list
  • Adding anyone with a relevant title
  • Picking people you can't say anything specific about

Sourcing that gives you a first line

  • Reading comments on a competitor's product post from this week
  • Noting the exact sentence that made you pick them
  • Skipping anyone whose reason you can't write in one line

Write the first line from something real

The first line decides whether the rest gets read. It should name the thing that made you pick this person, in their words or close to them. A compliment about their profile doesn't count.

Keep the whole message short. One line on why you're writing, one on what you do, one question that's easy to answer.

Don't open with hope-you're-well or a line about their impressive background. Both tell the reader you send the same thing to everyone. If you can't find anything specific, that's a sourcing problem, not a writing problem. The connection request message templates here are a decent starting shape.

Example

  1. You

    Saw your comment on Northwind's post about the reporting export. You said the CSV drops custom fields whenever a client adds one. We fixed that for a 30-person agency last quarter. Worth a look?

  2. Prospect

    Ha, yes. It's been on the list for months. What did you change?

  3. Suggested reply

    Mostly how the export maps fields, so custom ones stop getting dropped. I can walk you through it in 15 minutes Thursday or Friday. Which is easier?

Paste this job

Line 1: the thing they said or did, in their words
Line 2: what you do about it, one sentence
Line 3: one question that costs them nothing to answer

Example:
You wrote that your team rebuilds the same onboarding doc for every client.
We turn that doc into a template the client fills in themselves.
Is that still a problem this quarter?

Put the routine on your calendar

Outreach loses to product every time it's a when-I-get-to-it task. Give it two slots and protect them like a standup.

The morning slot is for replies, because that part needs your brain. The afternoon slot is for sourcing and reading tomorrow's queue, which you can do tired.

Batch the queue review. Reading messages one at a time as they're written is the slowest way to do it, and you'll rewrite the same sentence five times.

If a day gets eaten, do the reply block and skip sourcing. A day without new leads costs you nothing. A week without replies costs you the pipeline you already built.

Paste this job

09:00 to 09:15  replies only, nothing else open
09:15 to 09:25  read tomorrow's queued messages, fix the weak ones
13:00 to 13:05  check for new replies
17:30 to 17:50  source five people, write the reason for each

What to skip when the week gets busy

Some weeks the routine falls apart. Decide now what gets cut, so you don't cut all of it.

Treat the routine as a floor. Two reply blocks and one sourcing block a week will keep a small pipeline moving. What kills it is stopping for a month and then trying to catch up in one sitting. Keep a note of where you stopped, because coming back to a half-finished list of names is much easier than starting from a blank search.

  • Skip sourcing before you skip replies. New leads are replaceable, a reply that goes cold is not.
  • Skip personalising a follow-up before you skip sending it. A plain second message beats silence.
  • Skip the metrics review. Acceptance rate and pending invites matter, but not as much as answering the person who wrote back.
  • Skip the new experiment. Testing a different opener can wait until the week is calm.

Doing this with Kinlead

Kinlead handles the repeating parts of this routine. You describe the customer you want, and it finds matching people on LinkedIn, scores each lead from 0 to 100 against that profile and doesn't keep the ones below the fit line. Leads sit in lead groups, and any campaign can point at any group.

The Steal Customers agent watches competitor company pages and the founder or employee profiles you add, 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 your first line is already written.

Outreach sends from your own LinkedIn account through Unipile. Each account sends at most one action every five minutes, inside the daily limits and send window you set. Queued messages can be read and edited on the Actions page before they send, replies from every campaign land in one inbox sorted by intent, and you get an email when someone answers. Pro is $49 a month after a 7-day free trial, with a minimum booking guarantee if you want the terms in writing.

Frequently asked questions

Related

Get started with Kinlead

Prefer markdown? A daily LinkedIn outreach routine for founders.md