# Finding product gaps through competitor comments
> Find product gaps in competitor LinkedIn comments, qualify the people who mention them, and send a first message that points to a fix you can deliver.
- HTML: https://getkinlead.com/using-linkedin-to-find-product-gaps
- Markdown: https://getkinlead.com/using-linkedin-to-find-product-gaps.md

**Short answer:** Read the comments on competitor company pages and founder posts for specific missing features, broken workflows or manual steps. Those comments name a gap you can fill. Then check that the commenter can buy, and send a first message that refers to the exact problem they described.

## Where competitors' customers complain

Most unhappy customers don't leave a public review. They leave a short comment under a feature announcement, a pricing post or a founder's update. That comment is often more specific than a review because the person is writing to the company, not to a review site.

Start with the company page, but don't stop there. Founders, heads of product and support leads often post updates that get franker replies than the polished brand account. A post about a new integration will collect comments from people asking whether it works with their stack. A post about a change in pricing will collect comments from people who say the change breaks their budget or their workflow.

Look at posts that ask for feedback, announce a change or explain a workflow. Those posts attract people who are already trying to use the product and hitting a wall. Save the post URL and the comment text as soon as you see it. Comments get edited or deleted.

1. **Check the company posts.** Open the competitor's company page, click Posts and sort by recent. You want posts from the last few weeks, not the greatest hits from last year.
2. **Read the leadership posts.** Find the founder, head of product or support lead. Read their posts and the replies. A founder asking what to build next is a useful place to start.
3. **Skip praise and look for questions.** Ignore the 'great post' replies. Read the questions, the workaround stories and the 'does this work with X' comments.

## Spotting a real product gap in the comments

A complaint is not automatically a gap. A gap is a missing capability or a workflow that forces the customer to do extra manual work. If the comment names a task they cannot finish, a system they cannot connect or a step they have to repeat, that is worth writing down.

Pricing complaints are usually not product gaps. They tell you the buyer thinks the current price is wrong for their size, which is hard to solve with a feature. Login failures and one-off bugs are support issues. They may create a moment of frustration, but they don't tell you what to build or sell.

Read the replies under the comment too. If three people ask the same follow-up question, the gap is broader than one account. If the original commenter is the only person who cares, you can still reach out, but treat it as a one-off conversation, not a market signal.

**Noise**

- Great post, thanks for sharing.
- The pricing is too high for a small team.
- I can't log in this morning, is the site down?

**Product gap**

- I need this to connect with our support desk without a manual export.
- Is there a way to set different permissions per client? I can't find it.
- We're switching, but I'm worried about losing the custom fields we built.

> Write the gap as a sentence a customer would say: 'I need this tool to sync with Salesforce without a CSV export.' If you can't write it that plainly, you don't have a gap yet.

## Qualifying the commenter before you reach out

A comment can come from anyone. Before you add the person to a list, open their profile and check role, company and whether the complaint matches your product.

You want someone who feels the problem and can influence the purchase. A solo founder can switch tools in a day. A VP of sales can sponsor a change. An intern who is venting about a login screen is not a buyer, even if the complaint is real.

Check whether they already use the competitor or were just comparing options. A person who says 'we're evaluating Acme' is earlier in the process than someone who says 'we've used Acme for two years and this still doesn't work.' The second person has a live workflow and a reason to move.

| | Check | What to look for | Skip if |
| --- | --- | --- | --- |
| Role | Director, VP, head of function or founder | Student, recruiter or unrelated role |
| Company fit | Matches your customer profile by size and sector | A company you cannot serve |
| Current tool | Says they use the competitor or are switching | Asking for a friend or researching for a blog |
| Comment detail | Names a task, integration or missing feature | Only says the post is great or the price is high |

## Writing the first message without sounding like a vulture

Open with the thing they wrote, not with your product. Mention the post and the specific question or complaint in one sentence. Then say what you do about it. Keep the first note short and easy to answer.

Don't tell them their current tool is bad. They chose it. If you attack it, you make them defend it. Say what you built for the problem they described and ask if they want to compare notes.

Use the same words they used. If they wrote 'manual export', don't call it 'data orchestration'. If they asked about a Salesforce sync, say Salesforce sync. A short note that repeats their own phrase is easier to trust than a polished pitch.

- **you:** Hi Sarah, I saw your comment on Acme's post about the missing Salesforce sync. The Friday CSV export is a common workaround for teams sending a lot of messages. We built Northwind to sync records without the export. Would you be open to a 15-minute look at how it handles duplicates?
- **them:** Exactly. We spend hours exporting CSVs every Friday. It's a pain. Does it handle custom fields?
- **you:** It does. I can show you the field mapping on a short call. If it doesn't fit, I'll tell you and you can keep the export.

> If the comment is more than two weeks old, say so. 'I saw your comment from last month' is honest and still works. Pretending it's fresh is worse.

```
Hi {first_name}, you commented on {competitor}'s post about {missing_feature}. That's the exact problem we built {product} to fix. Open to a quick compare this week?
```

## Keeping a gap log your team will actually use

You will forget which post had the best complaint. Keep a simple log with five columns: date, competitor, post URL, what the person asked for, and the person's profile URL. Add one line for the gap in your own words.

Review the log once a week. Look for the same gap showing up across different competitors. Two or three people asking for the same integration is a stronger signal than one loud complaint. If the same gap appears in your own comment section, you have a product roadmap item and a sales pitch.

Don't log every comment. Log the ones where the person fits your customer profile and the gap is something you can solve today. Keep the log small enough to review in one sitting. Ten useful rows are enough to start.

1. **Capture the post and the profile.** Put the post URL and the profile URL in the same row. The post gives you the context. The profile gives you the person.
2. **Write the gap in the customer's words.** 'Needs a Salesforce sync without a CSV' is useful. 'Needs better integrations' is not.
3. **Tag the row with a simple status.** Use new, messaged, replied or not a fit. Review the new rows every Monday and delete rows that went nowhere after a month.

## Doing this with Kinlead

The manual version works, but it takes a daily scroll through several competitor pages. 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 the commenter wrote.

Leads go into a lead group. A campaign can point at that group, and the connection request can carry an AI-written note under 200 characters that opens with why that person became a lead. Messages and follow-ups are written from the campaign goal, tone and your sales playbook. You can read and edit queued messages on the Actions page before they send, and pause any campaign.

Lead search uses LinkedIn's standard search, so a Sales Navigator seat is not required. Pro costs $49 a month after a 7-day free trial. A card is needed to start the trial, nothing is charged that day, and you can cancel in Settings. Extra LinkedIn accounts cost $40 a month each. If you want to see the agent on your own competitor list, [book a demo](/demo).

1. **Point the agent at competitors.** Add the competitor pages and the founder or employee profiles you already watch.
2. **Read the evidence on each lead.** Open each lead and read the saved post and comment before you send anything.
3. **Send with a note that names the gap.** Put the leads in a group, point a campaign at that group and write the note around the gap they mentioned.

## Related

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

## Common questions

**Is it allowed to message people who comment on competitor posts?**

LinkedIn allows direct messages, but it does not publish exact daily limits. Keep each note specific, stay inside the limits your account shows and watch your pending invites and acceptance rate. If LinkedIn pushes back, stop and fix the list before sending more.

**How often should I check competitor posts?**

Once a day is enough for most teams. Sort by recent and work the comments from the last week first. If daily is too much, set a weekly block and accept that you will be late to some conversations.

**What if the competitor replies and says the feature is coming?**

That reply is useful. You can tell the lead you have the feature today without promising a roadmap. If they need it now, they will ask. If they can wait, they were not ready to switch.

**What if the commenter is not a decision maker?**

Ask who owns the workflow. A junior person can introduce you to the manager who feels the same pain. Don't pitch them as if they can sign a contract.

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