# How to book customer discovery calls on LinkedIn
> Get the right people to agree to discovery interviews on LinkedIn by asking about their problem first instead of pitching your product in the first message.
- HTML: https://getkinlead.com/using-linkedin-for-customer-discovery-calls
- Markdown: https://getkinlead.com/using-linkedin-for-customer-discovery-calls.md

**Short answer:** Stop asking for a demo or 15 minutes to show what you're building. Ask for someone's read on a problem they already discussed in public, and keep your product out of the first two messages. Discovery works when the other person gets to talk about their own experience.

## The difference between a sales pitch and a discovery request

Most founders treat discovery as lead generation with softer wording. The person reading the message spots it in one sentence. Ask for feedback on something you're building and it reads as a pitch in disguise, so it gets ignored or answered with a polite 'looks great, good luck' that goes nowhere.

The ask that works is smaller. You want their read on a problem they already know well. People will talk about their own experience for free. They won't sit through a demo for free, and they won't fill in a survey about your roadmap.

Keep your product out of the first two messages. If they ask what you're building, answer in one line and steer back to their problem. The call is research, not a reveal.

**sales pitch**

- I have a tool that solves X, can I show it to you?
- I'm building something that helps with Y, would you be open to a quick demo?
- I'd love to get your feedback on my new platform.

**discovery request**

- I saw your post about X and I'm trying to work out whether Y is really the cause. Would you share how it played out for you?
- You mentioned the struggle with Z in that thread. I'm mapping how teams handle it by hand right now. Can I ask you one question about it?
- You've run a team of 50, so your take on the attribution problem is the one I actually want.

## How to find people who already care about the problem

You don't need a big list. You need people who said something about the problem in public this month. The conversation is easier because the topic is already in their head, and the message almost writes itself because you're quoting them back to themselves.

Public complaints and arguments are the richest source. Someone arguing in a comment thread about how a process breaks is a better interview than a job title match on a search page, because you can see they have an opinion and you know exactly what it is.

1. **Search for problem phrases.** Use the LinkedIn search bar for how-to language around your problem, for example 'how do you handle' or 'struggling with' plus your industry keyword.
2. **Filter the results to posts.** Switch the search filter to posts so you find current discussions rather than static profile text.
3. **Check that they're qualified.** Open the profile and confirm the job title or company size means they actually live with this problem. Skip anyone who only reposts news.
4. **Watch competitor commenters.** Open a competitor's company page and read the comments on recent posts. People naming a missing feature or a workaround are the most specific interview subjects you'll find.

## Writing the first message so it gets an answer

The first message has one job: get a reply about their experience. Once someone answers a specific question, the conversation has started. Asking for time after that feels natural instead of presumptuous.

Keep it short enough to read on a phone. Reference the exact post or comment, ask one question, and leave the call out of it until they've answered. Two sentences of context and one question beats a paragraph of background.

- **you:** Hi Sarah, saw your comment on the thread about churn in SaaS. You've run a team of 50, so I'm curious whether you think the usual cause is the tool or the handoff between teams?
- **them:** In my experience it's almost always the handoff. The tools are fine. It's the moment a deal moves from sales to success where it breaks.
- **you:** That matches about half of what I'm hearing and contradicts the other half. Would you be open to a 15 minute chat about how you fixed that handoff? I'm not selling anything, I'm trying to map the actual workflow.
- **them:** Sure, Thursday afternoon works. Send me a time.

```
Hi {first name}, your comment on {post topic} stuck with me, specifically the part about {detail}. I'm mapping how teams handle {problem} right now and I don't have a clean answer for {their situation}. How does that work at {company}? Happy to keep it to one question.
```

## What to ask once they agree to talk

Open the call by saying you're not selling today and you want their view, not a verdict on your idea. That one sentence changes the tone and stops them handing you the polite version.

Then ask about the last time the problem happened. Real events beat opinions. People are bad at describing what they usually do and good at describing what went wrong on Tuesday, including who got pulled in and what it cost them.

| | Stage | Ask this | Avoid this |
| --- | --- | --- | --- |
| Opening | Walk me through how you handle X today, step by step. | Would a tool like ours help you with X? |
| Pain | What happens when that step goes wrong? | How frustrated are you, on a scale of one to ten? |
| Workarounds | What have you tried that didn't stick, and why? | Have you looked at what competitors offer? |
| Decision | Who else gets pulled in when this changes? | What's your budget for solving this? |

> Ask about the last time it happened, not how they usually handle it. Recent events come with detail, names and costs. General habits come back as a summary you can't use.

## Following up without chasing

Most replies die from silence rather than rejection. Someone reads your message in a meeting, means to answer, and forgets. One short follow-up a few days later brings a fair number of those back, and a second one after that is where you stop.

Never send a follow-up that just says bumping this. Add something: a detail from another interview, a narrower question, or the specific thing you still can't work out. Make it easier to answer than the first message was.

If someone says no, ask whether they know anyone who deals with the same problem. That grows your list faster than any search, and people say yes more often when they don't have to do the call themselves.

```
Hi {first name}, one thing I still can't work out on {problem}: most people I've talked to say {pattern}, but a few say the opposite. Which is closer to how it works at {company}? One line is plenty, no call needed.
```

## Doing this with Kinlead

Finding people who commented on the problem last week, then writing a note that proves you read it, takes an hour a day by hand. Kinlead does the finding and the first note so your time goes into the calls.

1. **Turn commenters into leads.** The [Steal Customers agent](/features/steal-customers) watches competitor company pages and any founder or employee profiles you add, reads the comments on their recent posts, and keeps the post URL, the topic and what the person wrote.
2. **Bring in people you already know.** Import a CSV of LinkedIn profile URLs, or describe the customer you want and score each lead from 0 to 100 against that profile. Leads below the fit line aren't kept.
3. **Open with why they became a lead.** Connection notes are written by AI and stay under 200 characters, starting with the reason that person made the list. Queued messages can be read and edited on the Actions page before they send.
4. **Catch the reply yourself.** Choose hand-off mode if you want the conversation the moment someone answers. Replies from every campaign land in one inbox, sorted by intent with interested ones first, and you get an email when one arrives.

> Kinlead is $49 a month after a 7 day free trial, which covers 1 user and 1 LinkedIn account. If you want to see lead scoring run on your own targets first, [book a call](/demo).

```
Hi {first name}, your comment on {competitor post topic} was the clearest take in that thread. I'm researching how {industry} teams handle {problem} without {workaround}. Would you swap notes for 15 minutes? No pitch, I'm after your experience.
```

## Related

- [Booking demo calls on LinkedIn](https://getkinlead.com/use-cases/book-linkedin-demos.md)
- [The Steal Customers agent](https://getkinlead.com/features/steal-customers.md)
- [AI outreach templates for new job titles](https://getkinlead.com/ai-outreach-templates-for-new-job-titles.md)
- [Outbound for founders](https://getkinlead.com/use-cases/outbound-for-founders.md)

## Common questions

**Should I offer money for a discovery interview?**

Usually no. Payment attracts people who want the incentive rather than people who have the problem, and their answers show it. For very senior executives, a donation to a charity they pick is a better route than cash.

**How many people should I message each day?**

As many as you can personalise properly. Discovery depends on proving you read their post, so a handful of careful messages beats a large batch of templates. Stay inside whatever volume your LinkedIn account already handles comfortably.

**What if they ask for pricing during the call?**

Answer honestly, then go back to the problem. Something like: pricing is still moving while we work out what the solution is worth, and right now I'm more interested in whether it solves the thing you described.

**How long should a discovery interview last?**

Ask for 15 to 20 minutes. It's a low-friction request and easy to say yes to. If the conversation goes well they'll often stay longer, which tells you more than any answer they gave.

**What if they never reply at all?**

Send one follow-up that adds something new, then leave it. A third message to someone who ignored two is a waste of your daily sending capacity and a small risk to how your account is seen.

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