# How to do customer interviews on LinkedIn
> How to find B2B interview subjects on LinkedIn for product discovery and beta testing, and how to write a short request that gets a real reply.
- HTML: https://getkinlead.com/linkedin-outreach-for-product-managers
- Markdown: https://getkinlead.com/linkedin-outreach-for-product-managers.md

**Short answer:** To get customer interviews on LinkedIn, stop selling and start asking for expertise. Find people who are stuck in the problem you're researching and ask for 15 minutes of their time. A tight persona and a short, specific request do most of the work.

## Define your interview persona

Most discovery outreach fails because the target is too broad. Ask any product manager for 15 minutes and you'll get ignored, because the request reads like the last twenty they got.

A tight persona lets you name a specific problem in the first line. The person you want is someone who is stuck in the workflow you're researching right now. Job title matters less than whether they touched the problem this week.

Write the persona as one sentence you could say out loud: role, company size, and the thing they're responsible for this quarter. If you can't fill in the third part, you don't know enough to message anyone yet.

| | Role | Too broad | Specific persona |
| --- | --- | --- | --- |
| Product management | any PM in B2B | PMs at Series A fintechs who own the payments flow |
| Operations | people who hate their CRM | sales ops leads who spent more than five hours last week on manual data entry |
| Marketing | anyone in marketing | demand gen managers at companies with 50 to 200 employees |

## Find the right people

You don't need a large network. You need a few dozen people who match the persona and are active enough to notice a message.

Search for the language of the problem, not just the job title. People post about the mess they're in: a migration that broke, a report that takes a day to build. Those posts are your shortlist, because the person has already told you the problem is real.

Filter by company size and location before you open anyone's profile. A good post from someone at the wrong kind of company is still the wrong person.

1. **Search the problem, not the title.** Use the LinkedIn search bar with the words people use when they describe the problem, then filter by People, location and company size.
2. **Read recent activity.** Open the profiles that survive the filter and check the last three posts or comments. Someone who wrote about the problem this month is worth ten people with the right title and no activity.
3. **Check competitor employees.** The People tab on a competitor's page lists everyone in the roles you care about. Run that list through the same persona sentence.
4. **Confirm the pain before you write.** Write down the one line that made you pick this person. If you can't, they're not a fit and your message will read as generic.

> Check the date on the post before you message. A complaint from two years ago tells you nothing about this quarter.

## Write the request

The word 'demo' ends the conversation before it starts. So does 'solution', 'platform' and 'quick chat'. The recipient assumes you're a salesperson in disguise, and they're usually right.

Say what you're doing, why you picked them, and how long it takes. Three sentences. If it doesn't fit in three, cut the part about your company.

Ask for their expertise, not their opinion on your idea. People will give you 15 minutes to talk about their own work. Almost nobody will give you 15 minutes to react to your pitch deck.

**The sales approach**

- I see you're a PM at Acme. We have a tool that solves Y. Do you have 15 minutes for a demo?
- I'd love to show you how our platform can help you scale your operations. Are you free Thursday?

**The discovery approach**

- I'm researching how PMs at fintechs handle reconciliation and I'm not selling anything. Would you be open to 15 minutes next week?
- I saw your comment on the post about Z. I'm looking into that exact problem for a new project. Could I get your take on it for 10 minutes?

```
Hi {{first_name}}, I'm researching how {{role}} handle {{specific problem}} at the moment. I'm not pitching anything, I'm trying to find out whether the problem is as bad as it looks from the outside. Would you be open to 15 minutes next week? Happy to share what I learn from the other calls.
```

## Manage the conversation

Once someone says yes, send a calendar invite in the next message. Every extra round of 'what about Thursday' is a chance to lose them.

Offer two specific times. Asking 'when works for you?' pushes the scheduling work back onto them, and that's where people go quiet.

If they ask what the call is about, send the two or three questions you plan to ask. That turns a vague chat into a structured 15 minutes and gives them a reason to show up.

- **them:** Sure, I can help. What do you want to know?
- **you:** I'm curious about how you handle X today. I'll keep it to 15 minutes. Does Tuesday at 10am or Wednesday at 2pm work better?
- **them:** Wednesday works.
- **you:** Booked. I'll send the invite now with a couple of questions so you know what's coming.

> If someone goes quiet after agreeing, send one follow-up with the same two time options. Don't ask an open question the second time.

## Run the interview without pitching

The call is where founders lose the plot. Someone asks what you're building, you talk for eight minutes, and the rest of the call is them being polite.

Ask about the last time they hit the problem. Past behaviour beats opinions about the future. If they say they'd 'probably' use something, you've learned nothing you can build on.

- Walk me through the last time this happened.
- What did you do instead?
- What made it bad enough to notice that day?
- Who else gets pulled in when it goes wrong?
- Have you tried to fix it? What happened?

> If they ask what you're building, answer in one sentence and hand the question back. 'It's a tool for X, but I'm more interested in how you handle it now.'

## Follow up and keep them warm

Send a thank you within a day. Not a template, one or two lines about what you took from the call.

Then tell them what changed. When you rewrite the onboarding because of something they said, email them. That's the moment they stop being an interview and start being a beta tester.

Most people skip this and then wonder why nobody from the research will try the product. The follow-up is what turns a 15 minute call into a relationship you can ask another favour from.

- One line on the thing you're changing because of them.
- A short note when the beta is ready, with the specific ask.
- A check-in eight weeks later if you haven't shipped, so they know you didn't disappear.

## Doing this with Kinlead

Searching by hand works for the first ten interviews. After that you're spending hours on the same filters, and the list goes stale while you're on calls.

Kinlead finds people who match the persona you describe and scores each one from 0 to 100 against it. Leads below the fit line aren't kept, so the list stays short. The [Steal Customers agent](/features/steal-customers) watches competitor company pages and their founders' posts, reads the comments, and turns commenters who look like your persona into leads. Each lead keeps the post URL, what the post was about and what they commented.

1. **Describe the persona.** Write the same persona sentence you used for manual search. Lead search finds people who match it and scores each one from 0 to 100.
2. **Set the fit line.** Leads below the fit line aren't kept, so the list stays short enough to actually message.
3. **Watch competitor pages.** The Steal Customers agent reads comments on competitor posts and optional founder or employee profiles, then turns the commenters who fit into leads.
4. **Write the note.** Connection requests can carry an AI-written note under 200 characters that opens with why that person became a lead.
5. **Book the call.** Set the campaign to let the AI reply until a meeting is booked on your scheduling link, or hand the conversation to you at the first reply.

## Related

- [Finding leads on LinkedIn](https://getkinlead.com/tools/find-leads.md)
- [Steal Customers agent](https://getkinlead.com/features/steal-customers.md)
- [Connection request templates](https://getkinlead.com/ai-linkedin-connection-request-templates.md)

## Common questions

**Should I offer a gift card for the interview?**

Usually not. People in senior roles are more likely to say yes to shaping a product than to a small card, and offering money makes the call feel like a transaction. If you're interviewing people who lose income by talking to you, pay them.

**How many people do I need to message to get one call?**

There's no reliable number, and anyone quoting one is guessing. A tight persona with a specific problem in the first line gets replies; a generic request to a broad title doesn't. Track your own reply rate over the first 50 messages and adjust the persona, not the wording.

**What if they ask for a demo during the discovery call?**

Acknowledge the interest and go back to the problem. Say you'd rather show them once it's ready, and right now you want to make sure you're solving the right thing.

**How do I handle people who accept the invite but don't reply to the message?**

Send one polite follow-up 48 hours later. Mention you're still interested in their perspective and offer two specific time slots instead of an open question.

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