# How to handle requests for a demo video on LinkedIn
> A prospect asked for a demo video instead of a call. Send a short clip that answers their exact question, then ask something only a live call can settle.
- HTML: https://getkinlead.com/reply-to-prospect-asking-for-demo-video
- Markdown: https://getkinlead.com/reply-to-prospect-asking-for-demo-video.md

**Short answer:** A request for a demo video is usually a screen, not a brush-off. The prospect wants to confirm your product does the one thing they care about before they give up 20 minutes. Send a clip that answers that one thing in under 90 seconds, then ask a question the clip can't answer, like how their current setup handles the same step.

## Why they asked for a video instead of a call

A request for a video is rarely a request for a full product tour. Most prospects use it to check whether you're worth 15 minutes without handing over a calendar slot. They want to confirm the product does what you claim before they deal with the social pressure of a live call.

Some are just researching. They want to see whether the interface looks current or whether one specific feature exists at all. Others have been burned by reps who talked for 40 minutes and never showed the thing they asked about, so the video request screens out people who won't respect their time.

If you send a 20 minute recording of last week's demo, you give them a reason to stop talking to you. Once they have seen everything, there is nothing left to be curious about. Send a sample that leaves the setup questions open, because those questions are what a call is for.

**What gets ignored**

- A link to a 15 minute product overview recorded for everyone
- Replying that you can't send video and they need a call to see the value
- A slide deck and a request for 30 minutes

**What gets a reply**

- A 60 second clip of the one feature they named in their message
- A screen recording that opens with their company name and their own question
- A short clip plus a question about how their current process handles the same step

## Choose a format they will actually watch

Format decides whether the clip gets watched. A polished marketing video reads as a pitch and gets closed after a few seconds. A raw screen recording with your voice over it reads as a favor done for one person, and it takes ten minutes to make between calls.

Match the length to the stage. If they replied to your first message, they don't want a webinar, they want confirmation that you have seen their problem before. Save the longer walkthrough for a call where you can answer questions as they come up.

| | Format | Typical length | Best use | What usually happens |
| --- | --- | --- | --- | --- |
| Generic product demo | 10 minutes or more | General awareness | Closed in the first minute, no reply |
| Screen recording for one person | 60 to 90 seconds | The exact feature they asked about | Watched to the end, often with a follow-up question |
| Recorded customer story | 2 to 3 minutes | Proving a result for a similar team | Builds trust but never shows your screen |
| Annotated screenshots in a short clip | Under 60 seconds | Early research, cautious buyers | Low effort, keeps the thread alive |

## Record the clip in one take

Open with their name and the sentence they wrote. Something like: you asked how approvals work when a client changes scope mid-project, so here is that screen and nothing else. That first line tells them within three seconds that the video was made for them.

Then click through the single flow they asked about and say out loud what you're clicking. Don't narrate menus they didn't ask about, and don't save the good part for the end. If they see the answer at 20 seconds, they stay for the rest.

Finish by naming what the video can't show. The rules for who approves what, the migration of their old data, the way their tiers are set up. That gap is your reason to get on a call, and it's an honest one.

```
Hi Priya, you asked how the approval step works when a client changes scope halfway through. Here is the 80 second version.

0:00 Change order screen, nothing else open.
0:10 The one flow you asked about. Say what you're clicking.
0:45 What the video leaves out: "Who approves what depends on your tiers, so I'd need to see how your team is set up."
0:60 "Does Thursday at 10 work? Ten minutes, screen shared, no deck."

Stop recording the moment you've answered their question.
```

## What to write back when they ask for a video

Say yes in the first line so they don't feel handled. Then narrow the scope out loud: you're sending the part that covers their problem, not a general tour. That one sentence does more selling than the video does.

Follow the link with a question the video can't answer. This gives them a logical reason to move from watching to talking, and it shows you know where the standard setup stops working.

- **them:** Sounds interesting. Do you have a demo video you can send over first?
- **you:** Yes. You mentioned your team retypes orders from email into the ERP, so I'll record the 70 second piece on the import step rather than a full tour.
- **you:** Here it is: [link]. The video covers the standard import. What it can't tell me is whether your price list lives in the ERP or a separate sheet, because that changes the setup. Thursday at 10 for ten minutes?
- **them:** Thursday works. The price list is separate, which is half our problem.

## When they say just send the link

Sometimes they double down and tell you to send it with no further questions. That's either high skepticism or a genuinely packed week. Pushing for the call in that moment usually ends the conversation.

Comply, then earn the next step instead of asking for it. Give them the shortest clip, tell them what it doesn't cover, and ask one question about their process. The question is what separates you from every rep who sent a link and waited.

1. **Send the shortest version you have.** One link, no email gate, no form, no calendar widget in the first message.
2. **Say what the clip skips.** One line on what depends on their setup, so the video doesn't look like the whole answer.
3. **Ask one question about their process.** Pick the edge case your product handles that most teams get wrong, and ask how they handle it now.
4. **Offer two times, not a link.** Wednesday at 2 or Thursday at 11, ten minutes. A choice between two slots is easier to answer than a scheduling link.

> If someone refuses a call after watching a targeted clip and answering a question about their own process, they aren't ready to buy. Leave them alone for a month rather than chasing.

## What to do after they watch

Most of the value is in the follow-up, and most reps waste it on a check-in message. Read the signal instead of guessing, then reply with something only a person who watched their reaction could write.

If they watched and went quiet, one short note beats three nudges. Mention a detail from their message, not from your video, and give them an easy way to say no.

- They reply with a setup question: they're close. Answer in one line, then offer the two times again.
- They watched twice and said nothing: send a note about the gap you flagged in the clip, not a reminder that the video exists.
- They say they'll review with the team: ask what that person will want to see, and offer a 40 second clip aimed at them.
- No view after two days: ask whether the link worked. It's a real question, and it gets answered more often than a check-in.

## Doing this with Kinlead

Kinlead finds people on LinkedIn who match the customer you describe and scores each one, so the demo requests you get are from people inside your actual buyer profile. Leads are kept in groups you can point any campaign at.

Set the campaign to hand the conversation to you at the first reply. That's how you end up writing the clip yourself instead of editing an AI message, which is what this whole guide depends on.

Replies from every campaign land in one inbox, interested ones first, so a request for a video doesn't sit unread behind a newsletter thread. From there, the video and the two time slots are yours to send. Read more on [booking demos from LinkedIn](/use-cases/book-linkedin-demos).

## Related

- [Best connection requests](https://getkinlead.com/best-linkedin-connection-requests.md)
- [AI sales playbook](https://getkinlead.com/ai-sales-playbook-for-linkedin-outreach.md)
- [Daily outreach routine](https://getkinlead.com/daily-linkedin-outreach-routine.md)

## Common questions

**Should the demo video have me on camera?**

Only if you sell something where trust in a person matters more than the product screen. Otherwise a screen recording with your voice gets watched more often, because people came to see the software.

**What if they ask for the video and then ask for pricing too?**

Answer both in one message. Give a range or a starting point and say the exact number depends on seats or setup, then keep the question about their process. Dodging price after they asked twice reads as evasive.

**How long should the clip be?**

Under 90 seconds for a first reply, and shorter is fine. The goal is to prove the feature exists and works, not to train them on it.

**Should I use a landing page to gate the video?**

No. On LinkedIn, friction kills replies. A direct link they can open in one click will always beat a form.

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