How to Respond to "We Tried Something Like This and It Didn't Work"

1. Acknowledge

Take the failure seriously. "That's frustrating, and I understand why you'd be cautious" acknowledges both the experience and the reasonable conclusion they drew from it. Do not jump in with "we're different" before you know what they tried. Every vendor says they are different, and this buyer has heard it from the one that failed.

2. Clarify

Get the whole story. What did they buy, who drove it, how was it rolled out, when did it start to go wrong, and what do they think the real cause was? Listen for the difference between "the product was bad" and "nobody used it", because those lead to completely different conversations. Finish by asking whether the original problem is still there. If it is, the failure did not solve anything, and the cost of leaving it is still being paid.

3. Reframe

Reframe from "this category doesn't work" to "that specific thing went wrong, and here is how we'd handle it". Be precise: if the last tool failed because nobody adopted it, talk about your onboarding and the first thirty days. If the integration never finished, talk about who owns it and what happens if it stalls. If your approach is not actually different on the point that failed, say so and move on; this buyer will know.

4. Ask

Propose a next step that directly addresses the failure mode. If adoption was the problem, offer a pilot with the people who would use it, judged on usage. If delivery was the problem, offer to put milestones in the contract. Ask what would make them confident this time, and build the next step around the answer. Do not ask for a leap of faith; this buyer has none left.

On a cold call

That's useful to know, and honestly it's better than hearing you've never thought about it. Can I ask what you tried and what went wrong? [Listen.] I hear that a lot: in most cases it's [common failure mode] rather than the idea itself. I'm not going to claim we're different in a cold call. But if the problem it was meant to fix is still there, it might be worth twenty minutes to see whether we'd fail the same way.

On a discovery call

I'd like to understand that properly before I say anything, because "we're different" is what the last vendor said too. What did you try, who drove it, and when did it start to go wrong? [Listen.] So if I've got it right, it was [their diagnosis] rather than the product itself. Is that fair? And is the original problem still costing you what it was then?

After a demo

You said earlier the last one failed because [specific reason]. Now that you've seen ours, let me be direct about where we'd handle that differently: [specific difference], and where we wouldn't: [honest limitation]. The thing I'd want to prove to you is [the failure mode], so I'd suggest a pilot judged on exactly that, with [their team] involved from day one. Would that give you what you'd need to trust it this time?

Late in the deal

I know the last attempt is on your mind, and it should be. So let's put the thing you're worried about into the agreement. If [failure mode] happened last time, we'll set [specific milestone] as a condition in the first [period], with a clear exit if we miss it. That means the risk sits with us, not with you. What else would you want written down so that this time is not a repeat?

By email

Thanks for telling me, that's more useful than a polite no. I'd like to understand what happened before I claim anything. Would you be willing to tell me in a couple of lines what you tried and what the real reason was that it didn't stick? If it was [likely failure mode], I can show you specifically how we handle that and you can judge whether it's different. If it was something else, I'll tell you honestly whether we'd be any better.