How to handle requests for email demos

Learn how to respond when a LinkedIn prospect asks for an email demo. Use a teaser strategy to prove value and move them toward a live meeting.

Get started

Short answer

When a prospect asks for a demo by email, they are usually trying to avoid a live meeting. Send a short clip of the one screen they asked about, then ask for 15 minutes to cover the parts that depend on their setup.

Recognize the soft rejection

When a prospect replies to your LinkedIn message with a request to email a demo, read it as a soft no. They are not ready to give you 30 minutes, and they want to check whether your product is worth any time at all. Sending a link or a PDF hands the whole conversation to their assumptions.

Static material is easy to ignore. A feature list gets skimmed on a phone between meetings, and the prospect decides fit on their own terms. You never hear the question they mutter at the screen, and you never get to answer it.

The goal is to get them participating instead of watching. A short live walkthrough lets you aim at the problem they actually have, which is the only way to earn enough trust for a next step.

The request also tells you something useful. They are interested enough to reply, which puts them ahead of everyone who ignored the message. The job is to keep that interest alive without handing over a recording they will watch alone and forget.

The passive approach

  • Sending a 20-page PDF deck
  • Sending a link to a generic recorded demo
  • Asking them to start a trial and explore alone

The active approach

  • Sending a 60-second clip about one problem they mentioned
  • Showing the single screen that answers their question
  • Asking for 15 minutes to cover what the clip skipped

Decide if the request is real

Some requests are genuine. A prospect who names a feature, a workflow or a comparison is telling you what they need to see. Treat that as a buying signal and answer it directly.

Other requests are a way to close the conversation without saying no. The tell is vagueness: no product question, no timeline, no mention of what they would do with the information. Ask one clarifying question before you decide which one you are dealing with.

A prospect who answers that question in detail is worth a clip and a call. One who replies with a single word is not. Sort them early and spend your time on the first group.

Names a feature or workflow

Signal
They know what they need to see
What it usually means
Send a clip of that exact screen, then ask for 15 minutes

Asks about pricing in the same breath

Signal
They are comparing vendors now
What it usually means
Send a short clip and a range, then push for a call this week

No product question at all

Signal
Usually a polite exit
What it usually means
Send one clip, ask one question, then stop chasing

Replies with a template line

Signal
Low interest or a gatekeeper
What it usually means
Reply once with a specific question and wait

The teaser strategy

Give away enough to prove the product works, and keep the part that needs a conversation. A 60-second clip of the exact screen they asked about does that. It shows you listened, and it leaves the setup questions for the call.

Keep the clip boring on purpose. No intro music, no slides, no company history. Open the product, show the one thing, say what it changes for their team, and stop.

Record it in one take. A polished edit takes longer than the call you are trying to book, and the rough version reads as more honest anyway.

  1. 1

    Pick the one screen

    Record the feature that matches the problem they mentioned. If they mentioned nothing, pick the step where most new users get stuck and show how your product removes it.

  2. 2

    Keep it under 90 seconds

    Say what you are about to show, show it, say what it means for them. Anything longer gets abandoned halfway.

  3. 3

    Write two lines around it

    One line on why you picked that clip, one line asking for a short call to cover the parts that depend on their setup.

  4. 4

    Leave one gap

    Do not show permissions, integrations or pricing screens. Those are the questions that make a call worth having.

Drafting the response

Acknowledge the request before you redirect it. If the first line argues, the prospect stops reading. Say yes, deliver something useful, then explain why a short call covers the rest.

Keep the ask small and specific. A 15-minute slot with two times attached gets a faster answer than an open question about availability.

Example

  1. Prospect

    This looks interesting, but I'm slammed this month. Can you just email me a demo?

  2. You

    Sure. Here's a 60-second clip of the reporting lag you mentioned, recorded on a setup close to yours. The part that changes by team is how the data gets in, so 15 minutes would cover that better than another recording. Does Thursday at 10 or 2 work?

  3. Prospect

    Thursday 10 is fine.

  4. You

    Booked. I'll send an invite with the join link.

What to do after you send it

Send the clip in the same thread where they asked. A fresh email loses the context and they have to search for it later.

Follow up once with a question about the content. A nudge about the meeting gets ignored. If there is no reply after that, mark it and move on. Chasing a soft no burns the contact for later.

Keep a simple note of who asked for what. When a prospect resurfaces three months later, the clip they asked for is the fastest way back into the conversation.

  1. 1

    Wait two working days

    Long enough for them to watch, short enough that the conversation is still warm.

  2. 2

    Ask about the clip

    Reference the exact screen and ask whether that matches how their team works today. A calendar question at this point reads as pressure.

  3. 3

    Offer the exit

    Say you will close the loop if the timing is wrong. Some prospects come back a quarter later, and they remember who did not pester them.

  4. 4

    Log what they asked for

    If they named a feature or a competitor, that belongs in your notes for the next touch.

Doing this with Kinlead

Kinlead finds people on LinkedIn who match the customer you describe, or your website, and scores each lead from 0 to 100 against that profile. Leads below the fit line are not kept, so the inbox starts with people worth a clip.

Each campaign chooses how replies are handled: hand the conversation to you at the first reply, let the AI reply until there is real interest, or let the AI reply until a meeting is booked with your scheduling link. For a demo request, handing over at the first reply puts the message in front of you before anything else goes out.

Replies from every campaign land in one inbox, classified by intent, with interested replies first, and you get an email when someone replies. Queued messages can be read and edited on the Actions page before they send. More on booking LinkedIn demos.

Frequently asked questions

Related

Get started with Kinlead

Prefer markdown? How to handle requests for email demos.md