LinkedIn follow-ups after an unsuccessful demo
Recover leads after a bad product demo. Use these LinkedIn templates to handle technical glitches, poor fit, and bad delivery without losing the deal.
Get startedShort answer
Move the conversation from the failed product experience back to the business problem. Acknowledge the specific friction point and offer a path forward that does not require another live call.
Diagnose why the demo failed
Before you send a message, decide if the lead is saveable. Not every bad call is a lost cause, but some are a sign that the customer isn't a fit for your product. Write down what actually went wrong: the software, the fit, or your delivery. The fix is different for each one. If you skip this step, you will send an apology that sounds generic and makes the lead less likely to reply.
Technical failures are the easiest to fix because they aren't about your value proposition. Feature gaps are harder because you have to change how you position the product. Poor delivery is a rapport issue you can fix with honesty and a shorter follow-up. Pick one problem and address it. Do not try to fix all three in one message.
Ask yourself one question: would this person still have the same business problem if the demo had gone perfectly? If yes, the deal is probably saveable. If no, treat the follow-up as a relationship message, not a sales message. That means you offer help without asking for another meeting.
The ghostable lead
- They need a core feature you will never build
- They are in a different industry than your target market
- They told you the price is impossible for their budget
The saveable lead
- The screen share froze or the API timed out
- They were confused by the UI but the value is there
- You rambled and missed the main point
The technical glitch recovery
If the software crashed or the internet lagged, the lead is questioning your reliability. You can't fix this by saying sorry. Fix it by showing the product working in a controlled environment. Record a short clip of the exact feature that failed. Keep it under two minutes and narrate what you are doing. Show the same steps you tried on the call so they can compare.
Don't ask for another 30 minute call. That feels like a risk to them. Send the clip with one question that ties the feature back to their problem. For example, 'Does this cover the approval step you described?' That gives them an easy way to say yes or no. If they say yes, you can ask for a short call only if the next step needs one.
If they reply with a no, ask what is missing. Do not defend the software. The goal is to get the conversation back to the business problem. If the glitch was on your side, say what you changed so it does not happen again. A specific fix is more convincing than a promise.
Example
- You
I'm sorry about the lag on that call. It's frustrating when the tech gets in the way of the conversation.
- You
I recorded a 60 second clip of the specific feature we missed so you can see it working without the glitches.
- You
Does that solve the problem we talked about, or should we look at a different approach?
- Prospect
Thanks for the clip. It looks like it does what we need, the call was just a bit choppy.
The poor fit pivot
When a lead realizes you aren't a match during the call, the relationship usually dies. You can save the relationship and get referrals by being the person who tells them you aren't the right fit. This builds trust. If you are honest about where you fail, they'll believe you when you talk about where you succeed. That trust can turn into an introduction later.
Use a short message that names the gap, offers a useful next step, and asks nothing in return. Do not send a deck. Do not ask for another call. If you know a tool or a person who can help, make the introduction. That is the whole message. The lead will remember that you did not waste their time.
If the gap is temporary, say what would need to change before you could help. For example, 'When you hit 50 seats, our reporting layer will make more sense.' That gives them a reason to come back without pressuring them. If the gap is permanent, say that too. A clean no is better than a slow maybe.
Missing feature
- Scenario
- It's clear we aren't a fit for X right now. I'm happy to point you toward a tool that does.
Wrong company size
- Scenario
- I realized during the call that our current setup is better for teams of 20. I don't want to waste your time with a tool that won't scale.
Low value perception
- Scenario
- I think I overcomplicated the demo. The only thing that actually matters for your goal is [Benefit].
The bad delivery apology
If you stumbled through the presentation or forgot the main value prop, avoid over-apologizing. When you spend three paragraphs saying you're sorry, the lead feels like they have to comfort you. That is an awkward dynamic for a buyer. Call out the mess quickly and move the focus back to their business problem.
Use one sentence to own the mistake. Then ask a question about their current process. The question does two things: it shows you are still interested in them, and it gets them talking about themselves instead of your performance. Keep your tone even. Do not joke about how bad you are.
Send a written summary or a one page PDF instead of asking for another meeting. A written asset lets them review the details on their own time. It also gives you a reason to follow up in a few days without asking for a call. Make the summary about their problem, not about your features.
- 1
Acknowledge the elephant
Use a direct line like 'That demo was a bit of a mess' or 'I didn't do a great job explaining the flow.'
- 2
Shift to their pain
Ask one specific question about their current problem to get them talking about themselves instead of your performance.
- 3
Offer a low friction asset
Send a written summary or a one page PDF instead of asking for another meeting.
Stop apologizing for your performance. It makes you look like a junior and makes the lead feel like they are doing you a favor by staying on the line.
Write the first message within two hours
Send the follow-up while the call is still fresh. Two hours is enough time to calm down and write something useful. If you wait until the next day, the lead has already told the story to a colleague and moved on. A fast reply also shows that you noticed the problem and care about fixing it.
Keep the message short. Name the problem, say what you are doing about it, and ask one question. Do not write a long apology. Do not attach a deck. The first message should make it easy for them to reply with one sentence. If they have to read three paragraphs, they will put it off.
If the call went badly because of your delivery, say that. If it went badly because of the product, say that too. The lead already knows what happened. Pretending the call went well makes you look worse. A direct note is easier to trust than a polished excuse.
Paste this job
Subject: About our call Hi [First name], That demo did not go the way I wanted. The [feature] did not load, and I spent too much time on [wrong topic]. I recorded a short clip of [feature] working here: [link]. It covers the [specific step] you asked about. Does that answer the question, or is there another part of the workflow I should show? [Your name]
What to do when they go quiet
Send one follow-up three days later with a useful resource. Do not ask if they got your last message. That puts the burden on them and makes you sound needy. Share a short note about their problem, a relevant article, or a comparison that helps them decide. Keep it under four sentences.
If they still don't reply, move them to a long term nurture list. Keep the door open with a final message that says you are closing the loop. For example, 'I'll stop here so I don't clutter your inbox. If the [problem] comes back, I'm happy to help.' That is a clean exit. It also gives them a reason to reach out later.
Do not send a discount after a bad demo. A discount looks like a bribe for a mistake. Fix the value perception first, then discuss pricing once they actually want the product. If they never reply, accept it and spend your time on leads who are still engaged.
Doing this with Kinlead
You can manage these recovery sequences without manual tracking. Import a CSV of LinkedIn profile URLs for leads who had a bad demo into a lead group to keep them separate from your standard pipeline. Any campaign can point at that group.
Create a campaign with a sales playbook that defines the tone for recovery messages. The AI drafts follow-ups from the campaign goal, and you can read and edit queued messages on the Actions page before they send. Set the campaign to hand-off mode so you can jump into the conversation the moment they reply.
Frequently asked questions
Related
Get started with Kinlead
Prefer markdown? LinkedIn follow-ups after an unsuccessful demo.md