# How to message prospects who share career advice
> Learn how to find people who post career advice on LinkedIn, ask about a specific post, and move the conversation to a business problem without a pitch.
- HTML: https://getkinlead.com/how-to-message-prospects-who-share-job-tips
- Markdown: https://getkinlead.com/how-to-message-prospects-who-share-job-tips.md

**Short answer:** Find people who post tactical career advice in your market, read a recent post, and open with a question about a specific detail. Treat them as a practitioner with a useful opinion, then use their answer to explain the business problem you solve.

## Identify the right advice-givers

Start with people who write about how they work, not people who only share quotes. A post that explains a hiring process, a way to handle a difficult client, or a mistake someone fixed gives you something concrete to ask about. Those writers usually answer comments, which is a good sign they will answer a direct message.

Look for people in the role or company type you sell to. A founder posting about cash flow can be a prospect for accounting software. A sales manager posting about pipeline reviews can be a prospect for a CRM. The advice itself does not need to mention your product. It needs to show how they think about the problem you solve.

1. **Search for the problem, not the job title.** Use LinkedIn search for phrases like 'pipeline review', 'client onboarding', or 'hiring a first rep' combined with your buyer's role. Generic terms like 'career tips' return too many people who only repost articles.
2. **Open the posts filter.** Switch the search filter to Posts. You want people who publish their own words, not people who only update a headline.
3. **Read the comments.** Check whether the author replies to comments. A writer who answers questions in public is more likely to answer one in a message.
4. **Save the post link.** Keep the URL and the line that caught your attention. You will need both when you write the note.

## Read the post before you write

The post is the reason you are allowed to message. If you cannot point to a sentence that changed your thinking, pick another person. A vague compliment about their 'great content' reads like a template and gets ignored.

Read the comments too. Sometimes the author adds a caveat in the comments that is more useful than the post. That caveat is a better hook because it shows you read past the first paragraph.

| | What you see | What it tells you | What to do |
| --- | --- | --- | --- |
| A tactical post with a specific example | They explain how they work | Ask about the constraint behind the example |
| A post that ends with a question | They want replies | Answer the question and add one detail from your own work |
| Only motivational quotes or reposts | Low chance of a useful reply | Skip the profile and keep searching |
| A strong post with no comments from the author | They may not be active | Comment once, wait a few days, then decide |

## The expert hook vs. the sales pitch

People who share advice get pitches every week. Job seekers ask for referrals. Vendors ask for fifteen minutes. If your note sounds like either one, you become noise. The way in is to ask about their experience with a problem. Describing your offer comes later.

The difference is in the ask. A pitch asks for time or a decision. An expert hook asks for an opinion they can give in two sentences. That is a small favor, and it gives them a reason to reply without committing to a call.

**The pitch in disguise**

- I saw your post on leadership and would love to show you how our platform helps teams scale.
- Your career advice is inspiring. Do you have 15 minutes this week to talk about a solution for your team?

**The expert hook**

- Your post on hiring first reps mentioned scorecards. I'm working through a scorecard for a 40-person agency and stuck on how to weigh coachability. Does your approach change when the candidate has no industry experience?
- Your note about client onboarding was useful. I'm curious whether you still batch kickoff calls when the client has a hard deadline. We keep running into that at Northwind.

## Writing the first message

Keep the connection note short. A note that takes more than a few seconds to read on a phone will be skimmed. Lead with the detail you noticed, then ask one question. Do not add a calendar link.

Use plain language. 'Your post on X made me think about Y' is enough. If you have a shared context, such as the same industry or a similar company size, add one line. Do not stack credentials. The goal is a reply. A resume can wait.

- **you:** Hi Sarah, your post on asynchronous stand-ups caught my eye. The part about written updates replacing a daily call is something I keep debating. Does that still work for a team of eight?
- **them:** Thanks for reading. Yes, it works better at that size. The trick is keeping the update short and making the blocker obvious.
- **you:** That helps. I'm trying to fix a similar handoff problem at Acme. Did you ever try it with a client-facing team, or only with engineers?
- **them:** Only engineers so far. Client teams tend to need a live check-in when a deadline moves.

> Keep the first ask to one question they can answer from experience. A request for a call is a different message.

```
Hi {first name}, your post on {topic} made me rethink {specific detail}. I'm working through {problem} at {company}. Does your approach still hold when {constraint}?
```

## Moving from advice to business

After they reply, thank them for the specific answer. Then connect their answer to the work you do. Do not jump to a demo. The bridge is the problem they just described. Your feature list comes later.

Use their words. If they said client teams need a live check-in when a deadline moves, say that. Then explain that you are building or selling something for that exact moment. Ask if they have seen other teams handle it differently. That keeps the conversation peer to peer.

1. **Acknowledge the answer.** Reply with the part that helped and why. One sentence is enough.
2. **Name the business context.** Explain the company or team where you see the same problem. Keep it concrete.
3. **Ask a wider question.** Ask whether they see that problem across their team or only in one situation.
4. **Offer a short exchange.** If they show interest, suggest a 15-minute call to compare notes. Do not send a calendar link before they agree.

## Keeping the conversation alive without pitching

Most replies will not turn into a meeting on the first exchange. That is normal. Your job is to keep the thread useful. Reply once with a follow-up thought, then leave it. A second message that adds a new detail is fine. A second message that asks for a call again is not.

Track who replied and what they said. If someone says they are too busy this week, note the date and come back later with a specific reason. If someone asks for a case study or a review, send one and ask a question about their situation. The conversation should still sound like two people talking about the work.

- They mentioned a deadline or a launch date. Ask how it went after the date.
- They asked a question you could not answer. Send the answer when you have it.
- They shared a post on a related topic. Reply to that post with a real comment, then message later.
- They said the timing was bad. Ask again after the date they named, with a new detail.

## Doing this with Kinlead

Kinlead can find people who comment on competitor posts. The [Steal Customers agent](/features/steal-customers) watches competitor company pages and optional founder or employee profiles, reads comments on 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 note can point to the exact line.

You can put those leads in a lead group and point a campaign at it. Connection notes can be AI-written under 200 characters and open with why the person became a lead. Set the campaign to hand the conversation to you at the first reply if you want to manage the shift from advice to business yourself.

## Related

- [Book a demo](https://getkinlead.com/demo.md)
- [Steal Customers agent](https://getkinlead.com/features/steal-customers.md)
- [Outbound for founders](https://getkinlead.com/use-cases/outbound-for-founders.md)

## Common questions

**What if they don't accept my connection request?**

Move on. Do not send a follow-up request. Some people only connect with people they know, and a second ask rarely changes that.

**Should I comment on their post before messaging them?**

Yes, if you have something useful to add. A comment that repeats the post or says 'great share' will not help. One specific comment a few days before the note makes your name familiar.

**How many of these people can I message per day?**

LinkedIn does not publish exact limits. Set a daily number you can handle, keep the notes specific, and stop when replies pile up. The limit matters less than the quality of each note.

**What if they ask what I sell?**

Answer plainly in one sentence, then return to their situation. Do not hide the product. Hiding it makes the earlier question feel like a trick.

**Can I ask for a call in the first message?**

No. Ask for an opinion first. If they reply with interest, suggest a short call in the next message.

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