The tried it before objection is the one rep training skips, because it sounds like a no and is actually a story. Someone at this company bought a tool in your category, ran a rollout, and watched it die: the champion left, adoption stalled at a third of the team, or the data never matched the CRM. When the prospect says 'we tried something like this before,' they are handing you that history, and most reps respond by explaining why their product is different, which is the one thing the prospect cannot yet evaluate. The better move is to get the failure story out in full before you say a word about your product. The script below does that in five beats. The three openers give you a tone for a cold call, a demo, and a late-stage deal. The smokescreen test tells you when 'we tried it' is a polite way of saying 'go away.'
What "We tried something like this before" is really telling you
Underneath 'we tried something like this before' there are usually two things. The first is a scar: the last rollout cost someone credibility, and the person on the phone may be that someone, so agreeing to look again feels like admitting they picked wrong the first time. The second is a category verdict: they have decided the whole approach does not work for a company like theirs, and your logo is irrelevant to that conclusion. The mistake reps make is to treat it as a competitor objection and launch into differentiation. Every feature you list is a feature the dead tool also claimed. You cannot be different from a failure you have not heard described, so the work is to get the specifics: what they bought, who owned it, when adoption stopped, and what they are doing instead now.
Tried it before objection script: five beats, spoken
Read it once aloud, then put the paper away. The beats matter more than the words: get the failure story before you make a single claim about your product.
ACKNOWLEDGE: That is useful to know, and honestly it makes this an easier conversation, because you already know what the category is supposed to do and where it fell short.
CLARIFY: Can I ask what you ran, roughly when, and what the moment was when you knew it was not going to stick? Was it adoption, the data, the person who owned it leaving, something else?
REFRAME: Almost every failed rollout I hear about in this space comes down to one of two things: the tool needed reps to change how they work and nobody enforced it, or the data feeding it was wrong from day one so people stopped trusting the output. If either sounds familiar, the question is whether that cause is still true here, because it decides whether anything in this category works for you, mine included.
PROOF: Northwind Freight had shelved a similar tool eighteen months before we talked. The difference the second time was that we wired it to the CRM fields their managers already inspected on Monday, so usage was checked without adding a meeting. They were at full team adoption by week six.
ASK: Would it be worth twenty minutes with whoever owned the last rollout, so we can find out whether the reason it died is still in the building?Direct: 'Good. Then you already know what a failed rollout looks like, which puts you ahead of most people I talk to. What killed it?'
Curious: 'Tell me about that. I would rather learn from your last attempt than pretend mine is the first.'
Dry: 'So did most of my customers. The interesting question is what they did differently the second time.'The test: ask 'What did you buy, and who owned it?' A real scar comes with a vendor name, a year, and a person. A smokescreen comes with 'oh, something a few years back' and no detail.
If it is not real, drop the script: 'Fair enough, sounds like this is more of a not-right-now than a tried-and-failed. What would need to be true for it to be worth a look later this year?' Then log the date and leave.Never name the failed vendor first; let them say it, or you will spend the call defending a competitor's rollout instead of learning from it.
Rewrite the script for your product and this account
The script assumes a generic failure. The version that wins is specific to what this prospect actually bought and why it stalled, and that is a five-minute rewrite you will not do at 8:55. Paste the script with the prompt below and whatever you know about their last attempt.
You are helping me handle the objection 'we tried something like this before' on a call with {{prospect title}} at {{company}} ({{company URL}}).
What I sell: {{one-line product description}}.
What I know about their previous attempt: {{vendor or category they tried, when, and anything I know about why it stalled}}.
Rewrite the five-beat script below so that CLARIFY asks about the specific failure mode most likely given what they bought, REFRAME names the root cause in their language rather than mine, and PROOF uses this customer story: {{one sentence on a customer who had a failed prior rollout and what changed}}. Keep it under 200 words, spoken not written, no jargon. Then give me the two questions I should ask if the prospect goes vague, and flag anything you inferred rather than read.
SCRIPT:
{{paste the script above}}Handle any objection with Claude
- Objection handling script prompt →The copy-paste prompt that drafts a response to any objection in your voice, with the proof point pulled from your own wins.
- Competitive battlecard skill →For the competitor-shaped objections: a rep-ready battlecard built from live competitor intel.
- Discovery call prep skill →Most objections are discovery you skipped. The skill preps the questions that surface them before the pitch.
Frequently asked questions
How do you handle the tried it before objection?
Get the story before you get to your product. Ask what they bought, when, who owned it, and the moment they knew it had stalled. Most failed rollouts come down to unenforced behavior change or bad data feeding the tool, and once the prospect names which one it was, you can ask whether that cause is still true today. If it is, be honest that no vendor in the category fixes it. If it is gone, the door is open. Reps who skip the story and start differentiating are arguing against a tool they have never seen.
What if the prospect was the person who bought the failed tool?
Then the objection is partly about their credibility, and you handle that first. Say plainly that picking a tool that stalls is normal, that rollouts in this category fail for reasons that have little to do with the buyer's judgment, and mean it. Then ask what they would do differently with hindsight. That question puts them in the expert seat and gives you the exact list of things your rollout plan needs to address. Never imply the first choice was wrong; you were not there.
Should you ask which competitor they tried?
Ask, but let them volunteer the name rather than guessing. Guess right and you look like you were waiting to attack a competitor; guess wrong and you look like you do not know the market. Once they name it, resist the comparison. Ask instead what the tool was supposed to change in the team's week and whether it did, even briefly. That answer tells you the real bar for success at this company, which is worth more than any feature gap.