# How to respond when a prospect asks you to read their posts
> Turn a prospect's request to read your posts into a booked call. Show you did the work, skip the flattery, and pivot back to the problem your product solves today.
- HTML: https://getkinlead.com/reply-prospect-says-check-out-my-content
- Markdown: https://getkinlead.com/reply-prospect-says-check-out-my-content.md

**Short answer:** When a prospect tells you to read their posts, treat it as a test of whether you looked before you typed. Quote one specific thing they wrote, say why it connects to the problem you solve, then ask for the call. Skip the praise and skip asking them to explain their own post.

## Why prospects ask you to read their posts

A reply like "take a look at my posts and see if this is a fit" reads like a brush-off. Sometimes it is one. It's also a cheap test, and it costs them nothing to run. They want to know whether you send the same paragraph to everyone or whether you looked before you typed.

Most people fail that test in one of two ways. They send three lines of praise that could apply to any human on the platform, or they go quiet and never follow up. Both confirm the suspicion that started the test.

There's a third option. Read one post properly, quote something specific from it, and tie that thing to the problem you solve. That reply takes four minutes and it sounds like a person wrote it.

## How to find the hook in their feed

You don't need to read everything they've written. One usable sentence is enough. Budget three minutes per prospect and stop when you find it.

Skip the announcements. Job changes, awards, conference photos and "honored to share" posts tell you nothing about how they think. Look for posts where they argue with something, describe a mess, or explain a decision they got wrong.

The shape of the post tells you what to quote. Use this as a shortcut.

1. **Open the activity tab.** Go to their profile, click Activity, then Posts. This filters out likes and comments on other people's content, which is most of what shows up in a feed.
2. **Read the last five posts.** You're looking for a complaint, a number, or an opinion. Words like "frustrating", "took us months", "we finally" or "I was wrong about" usually sit next to the useful part.
3. **Copy one phrase, not a summary.** Write down the exact sentence you'll reference. If you can't quote it, you didn't read closely enough and your reply will show it.
4. **Check the fit before you reply.** Ask whether that specific point touches the problem your product solves. If it doesn't, pick a different post or accept that this prospect isn't a fit right now.

| | Post type | What to quote | How to bridge |
| --- | --- | --- | --- |
| A complaint about a process | The step they said wastes time | Ask how much of that step is still manual |
| A lesson from a mistake | The decision they'd make differently | Say what your product changes about that decision |
| A number or result they shared | The metric and the timeframe | Ask what they'd need to move that number next quarter |
| An opinion on how the industry works | The claim you agree with | Name the part of your product that assumes the same thing |

## The acknowledge and pivot formula

The reply has three parts, in this order: proof you read it, a reason their point matters to you, and a question that moves toward a call. Skip the proof and you're selling to a stranger. Skip the pivot and you're a commenter with a LinkedIn account.

Keep it under five sentences. The prospect is busy, and a long reply about their own post reads like you have time to kill.

Here's what it looks like in practice.

- **them:** I'm slammed this week. Have a look at my recent posts, that'll tell you whether this is relevant.
- **you:** Read your post on attribution gaps. The line about marketing reporting numbers the sales team doesn't trust is the same thing we hear from every demand gen lead we work with.
- **you:** That gap is what our tool closes, by matching call outcomes back to the campaign that produced them. Worth 15 minutes on Thursday to see if it maps to how your team works?
- **them:** Thursday works. Send an invite.

## When their posts have nothing to do with your product

Plenty of prospects post about hiring, culture, or their kid's football team. None of that connects to your product, and pretending it does sounds worse than saying nothing.

You have two honest moves. Find an older post that does connect, or acknowledge the gap and go straight to the reason you reached out. Prospects respect the second one more than a forced bridge.

The difference is easy to spot once you've seen both.

**Forced bridge**

- I saw you're passionate about marathon running. That discipline is exactly what we see in teams that implement our software.
- Your post about your daughter's graduation reminds me of how we help companies grow.
- Love the hiking photos. Our platform helps teams reach the summit too.

**Honest redirect**

- Your posts are mostly about hiring, so I'll skip the content review. I reached out because your team posted three SDR roles in a month, and that usually means pipeline is the bottleneck.
- Nothing in your feed touches what we do, so I won't pretend otherwise. The reason I messaged is the new Leeds office, which usually comes with a territory to fill.
- I read your conference recap. It's not related to us, but the panel you mentioned on retention is the problem our customers bring up most.

## Mistakes that get you ignored

The fastest way to lose the room is to sound like a template with a name dropped in. Templates use adjectives. People use nouns, dates and specifics. If your reply could go to anyone else in their industry, it isn't personal, it's decorated.

The second mistake is asking them to explain the post. "What did you mean by that?" hands the work back to them, and you're the one who wants the meeting.

The third is waiting. If you say you'll read their posts, the clock starts. Replying three days later tells them you weren't curious, you were busy.

> Never ask a prospect to explain their own post. You're the one asking for the meeting, so the reading is your job.

```
Lines that get you ignored:
- I found your content very inspiring
- Thanks for sharing your insights
- I'd love to hear more about your thoughts
- Your posts really resonate with me
- I'm a big fan of your work

What to write instead:
- Your post on [topic] said [specific claim]. That's the same problem [role] bring to us.
- You wrote that [quote]. We built [thing] because of that exact gap.
- The [number] you mentioned in [post] is what [product] moves. Worth a look?
```

## How fast to reply and what happens after

Reply the same day, ideally within a couple of hours. The prospect is at their desk, they just sent the message, and the conversation is still open in their head. Tomorrow is a colder room.

If they don't answer your pivot, one follow-up is enough. Reference the same post, add one new piece of information, and ask again. After two follow-ups, stop. Three messages about a post they half-remember reads as pressure.

When they do reply, don't reopen the content discussion. Move to the calendar. The post did its job.

One more thing worth knowing: if you quote a post and get the point slightly wrong, say so in the next message. "I reread it, you were arguing the opposite" costs you nothing and buys more credibility than a clean pivot would have.

## Doing this with Kinlead

Reading posts by hand works, and it stops scaling somewhere around a few dozen prospects a week. The [Steal Customers](/features/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 the person actually commented, so the hook is in front of you before you write anything. Leads land in a lead group, and any campaign can point at that group. Connection notes can be AI-written under 200 characters and open with why that person became a lead.

1. **Point the agent at a competitor.** Add the company page, plus any founder or employee profiles whose commenters look like your buyers.
2. **Open the lead and read the comment.** The post URL and comment text sit with the lead, so you can quote a real sentence without opening LinkedIn.
3. **Let the campaign write the first line.** The connection note opens with why they became a lead. Edit it on the Actions page before it sends if you want a different hook.

## Related

- [Steal Customers agent](https://getkinlead.com/features/steal-customers.md)
- [Book LinkedIn demos](https://getkinlead.com/use-cases/book-linkedin-demos.md)
- [AI LinkedIn outreach](https://getkinlead.com/features/ai-linkedin-outreach.md)

## Common questions

**What if they haven't posted in months?**

Don't claim you read their posts. Say what you actually looked at, whether that's company news, a job posting or a product launch, and connect that to your reason for reaching out.

**Should I like or comment on their posts before replying?**

It can help, but it isn't a substitute for the reply. One comment and a direct message beats five likes and no conversation.

**What if their content has nothing to do with my product?**

Say so and move to the real reason you messaged. A forced bridge between marathon running and your software damages your credibility more than skipping the content review.

**How specific does the reference need to be?**

Specific enough that no other prospect could receive it. A quoted phrase or a named number works. "Great insights on leadership" doesn't.

**Do I need to read their comments too, or just their posts?**

Posts are enough for a first reply. Comments are useful when the person rarely posts but shows up under other people's content, which is where their real opinions tend to land.

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