How to reply when a prospect had a bad experience with a similar tool
Learn how to handle prospects who had bad experiences with similar tools on LinkedIn. Acknowledge their frustration and differentiate without badmouthing.
Get startedShort answer
Acknowledge the bad experience before you say anything about your product, then ask one question that names the likely failure. Once you know whether setup, support or results broke, answer that specific thing with proof, and keep the reply short enough to read on a phone.
Stop the instinct to defend
When a prospect says a similar tool was a nightmare, the first thing you feel is the urge to correct them. You want to list the features that make your product different. That reply reads as a pitch and ends the conversation.
The prospect is not attacking you. They are describing something that cost them time or money. If you answer with a feature list, you tell them their experience matters less than your sales deck.
Treat the complaint as information. Something specific broke for them. Your job in the next two messages is to find out what, then answer that thing and nothing else.
Defending the product
- Sorry to hear that, but our platform is much more reliable and the support team is always on call.
- That's unfortunate. We have a dedicated success manager who makes sure that never happens here.
Naming the likely failure
- That sounds rough. The people I hear this from usually got stuck in setup and never reached the part that saves time. Did it go that way for you?
- I've had this conversation a few times lately. Usually the tool needed someone to babysit it every week. Was yours like that?
Find out what actually broke
"It was bad" is not a diagnosis. You cannot answer a feeling, but you can answer a failure. Move the conversation from the verdict to the specific thing that went wrong.
Aim for one question with a few possible answers, so they can reply from their phone in a sentence. Open questions like "what happened?" often get a paragraph of frustration and nothing usable.
- 1
Ask where it broke, not what they thought of it
Ask whether the problem was setup, day to day use, support, or the results themselves. Offer the options. It makes the reply easy and tells you which part of your product to talk about.
- 2
Turn the answer into a gap
Setup that dragged on is a time to value gap. Wrong or missing data is a reliability gap. Nobody answering tickets is an accountability gap. Name the gap in your head so your reply stays focused.
- 3
Ask what it cost them
Ask how the failure changed their week: hours lost, a report they stopped trusting, a launch that slipped. That tells you which part of your answer matters most.
Never argue with the experience. You can disagree with a conclusion later. The experience is theirs and it already happened.
Answer the failure they described
Once you know the gap, answer it in one or two sentences. Skip the comparison. If they say the tool needed a full time admin, say how yours runs without one and why. If support ignored them, tell them who they message and when they hear back.
Don't call the other product bad. The prospect may still use it in another team, or a former colleague may have built it. Criticizing it makes you look small and gives them a reason to defend a choice they already regret.
Show the fix where you can. A 40 second screen recording of the exact thing they said was missing does more than three paragraphs about your architecture.
"Nobody could work out the interface"
- What they say
- Usability
- The gap
- Say how many steps setup takes and offer a short clip of a real account.
"Support stopped replying after we paid"
- What they say
- Accountability
- The gap
- Name the channel they use and the response window you commit to.
"It never produced the report we bought it for"
- What they say
- Results
- The gap
- Send a screenshot or clip of that report coming out of your tool.
"We spent more time fixing it than using it"
- What they say
- Maintenance
- The gap
- Explain what runs without them touching it each week.
Write the reply short and end with one question
LinkedIn threads get read between meetings. Two or three sentences is enough. End every reply with a question that moves the conversation one step, never with a summary of your product.
Don't ask for a 30 minute call in the first reply. Offer the smallest useful thing: a clip of the feature they said was broken elsewhere, or a link to one page that shows how it works. If they watch it and reply, the call gets easier.
Example
- Prospect
We tried something like this last year and it was a nightmare. Total waste of money.
- You
I've heard that before. Usually it's because the tool needed someone to manage it full time. Was that the issue for you?
- Prospect
Exactly. We spent more time fixing it than using it.
- You
That's the part we built around. Setup takes a few clicks and it runs without a weekly babysitter. Want a short clip of that bit in a real account?
- Prospect
Sure, send it over.
Paste this job
Hi {first name}, that matches what I hear from {role} teams who tried {category} tools. The part that usually breaks is {likely gap}. Was that your experience, or was it something else?
If it was {gap}, I can send a short clip of how we handle it. No call needed.When the bad experience was with your own product
Sometimes the complaint is about your tool's earlier version, a botched migration, or an account manager who left. Denying it makes you the second bad experience in a row.
Admit the specific thing that went wrong and say what changed. Not a general "we've improved a lot", but the actual change: a rewritten import step, a new support process, a person who now owns those accounts. If the change has a date, give it.
Then hand the decision back to them. Ask what would need to be true for them to look again. Some will say nothing, and that's a useful answer too.
One honest sentence about a past failure buys more trust than five about your roadmap. Keep it to one sentence and move on.
Doing this with Kinlead
Kinlead writes messages and follow ups from the campaign's goal, tone and an optional sales playbook, which is your own script. Put your best response to the "we tried something like this and it was awful" line in that playbook and the drafts start from your wording.
Queued messages can be read and edited on the Actions page before they send, and any campaign can be paused. For replies this sensitive, set the campaign to hand the conversation to you at the first reply, or let the AI reply only until there is real interest. Every reply from every campaign lands in one inbox, classified by intent, with interested replies first, and you get an email when someone answers.
Sending runs from your own LinkedIn account at a human pace: at most one action every 5 minutes, inside daily limits you set and a send window in the lead's time zone. You can see how that works on the LinkedIn account safety page, and if you want to see the playbook setup, book a call.
Frequently asked questions
Related
Get started with Kinlead
Prefer markdown? How to reply when a prospect had a bad experience with a similar tool.md