"We Tried This Before" Sales Objection: Learn What Failed First

When a buyer says "we tried this before," acknowledge the earlier experience and ask whether they want to explain what failed. If they are open to it, separate the intended outcome, the actual result and the conditions of the attempt. Compare only a verified difference that matters to that failure. If nothing relevant changed, do not push another trial.

The wording below is a set of examples, not measured conversion advice. HubSpot's objection-handling guide, checked October 10, 2026, recommends empathy, listening and clarifying concerns instead of defensiveness, false claims or pressure. A past failure is useful context, not proof of hidden buying intent.

Acknowledge the earlier attempt

Try: "That experience matters. Are you open to telling me what did not work, or would you rather leave it there?"

If they want to continue, ask: "What were you hoping it would change, and what actually happened?"

Avoid saying the buyer used the product incorrectly. You do not yet know whether the problem was product fit, setup, adoption, cost, support or an unrealistic promise.

Find the failure that matters

Try: "Was the main issue the result, the effort needed to use it, or something else?"

Use their words when summarizing: "So the problem was [their stated issue], rather than [your earlier assumption]. Have I understood that correctly?"

A transcript or note can preserve the account, but it does not establish why the attempt failed. Let the buyer correct your interpretation before proposing a remedy.

Check what changed

Try: "The relevant difference I can verify is [current capability or condition]. Does that address the failure you described?"

Replace the placeholder with a current, source-backed fact. Do not claim that your product will succeed because it uses newer AI, or invent weaknesses in the earlier provider. A different brand is not necessarily a different outcome.

If the conditions have not changed, acknowledge that. If the buyer wants a comparison, define the narrow question it should answer. The happy with our provider guide covers factual comparisons without attacking the incumbent.

Make any evaluation optional

Try: "Would testing that one difference be useful, or is another evaluation not worth your time?"

An agreed evaluation should name the question, the input and the success criterion. Discuss cost and commitment before proposing a trial. Do not promise a free trial, refund or easy cancellation without verified terms and an approved offer.

If the buyer declines, stop. The not interested guide covers respecting a refusal. If they ask for a short overview, use the send me information guide.

Where Boxy can help

Boxy by Hintro provides live transcription, contextual suggestions and configurable prompt buttons. A rep can request help with an objection or a discovery question, then decide whether the proposed wording fits the buyer's account.

Its product page also describes post-call summaries, objections, follow-up actions and follow-up email content. These can help retain the stated concern, but they do not prove the cause of a prior failure or authorize a next step.

See Hintro's use cases, FAQ and pricing for current scope and limits. Check product facts before repeating a suggested comparison aloud.

FAQ

Should I say our product is different?

Only explain a verified difference relevant to the failure. A broad claim that your product is better does not answer the concern.

What if the buyer does not want to explain?

Respect that decision and end the discussion. They do not owe you a detailed account of the earlier attempt.

What if nothing important changed?

Do not force a repeat evaluation. Acknowledge that the earlier concern remains.

Can AI determine why the earlier attempt failed?

This article makes no such claim. A suggested response is assistance, not a verified diagnosis.