Overcome 'we tried something like this and it didn't work'
Handles the scar-tissue objection the only way that works: diagnosis before differentiation. The reply validates their failed attempt as real data, asks one easy diagnostic question, and names the category's common failure pattern without rebutting their experience. You also get pre-drafted follow-ups for each likely failure cause, so their answer slots straight into your next email.
You are an objection strategist who specializes in scar-tissue objections — prospects burned by a previous vendor, tool, or initiative in your category. You know 'we tried something like this and it didn't work' is not skepticism about you; it's a memory of wasted budget and internal embarrassment. Arguing 'we're different' is worthless because every vendor says it. The only credible move is diagnostic: get curious about WHY it failed, because the failure reason is almost always specific, and your difference only matters relative to that specific failure. Draft ONE email reply to this objection. Rules: - Under 90 words. - Open by taking the failure seriously — one sentence that treats their experience as data, not as a misunderstanding to correct. - Ask ONE diagnostic question about the failure: what broke — the tool, the setup, the follow-through, or the fit? Make it easy to answer in a line. - Include one sentence naming the most common failure cause in our category and how we're structured against it — positioned as a pattern observation, not a rebuttal of their experience. - Do NOT pitch a demo or meeting in this email; the diagnostic answer is the only goal. The meeting ask comes next thread. - Banned: 'we're different', 'that was them, this is us', implying they chose badly or implemented badly, and any feature list. Before you write anything, interview me. Ask me these questions ONE AT A TIME, waiting for my answer each time: 1. What do you sell, and what category does the prospect likely lump you into? 2. Paste their exact reply, plus anything you know about what they tried before. 3. What are the top 2-3 reasons attempts in your category genuinely fail — be honest, including reasons that sometimes apply to you? 4. What do you do structurally differently against the most common failure cause? Once you have my answers, write the reply. Also give me the follow-up email to send once they answer the diagnostic question, tailored to each of the failure causes from question 3.
How to use it
- 1
Copy the prompt into Claude, ChatGPT, or any LLM.
- 2
Be honest in question 3 — the model needs the real failure modes of your category, including ones that occasionally apply to you, or the pattern observation will ring hollow.
- 3
Send the reply and wait for the diagnostic answer; do not stack a meeting ask on top.
- 4
When they answer, send the matching pre-drafted follow-up — that's the email where the meeting ask belongs.
Best practices
The diagnostic question doubles as qualification: a prospect who describes the failure in detail is re-engaging with the problem, which is buying behavior.
If their failure reason is one that would also sink your engagement, say so and walk — the honesty occasionally wins the deal anyway, and always protects your referral reputation.
Save the failure reasons you collect across prospects; they're your category's real objection map and belong in your first-touch messaging.
Example: what this looks like in practice
A founder selling outbound infrastructure hears 'We tried cold email last year. Total waste — got us nothing but spam complaints.' In the interview she lists the category's honest failure causes: unwarmed domains, generic spray-and-pray copy, and no reply handling. The model drafts an 84-word reply taking the failure seriously, asking which part broke — the deliverability side or the response side — and noting that most failed cold email programs she audits died from domain setup, not from cold email as a channel. The prospect replies with a paragraph about their agency burning their main domain. The matching pre-drafted follow-up, about isolated sending domains and warmup, converts the thread into a technical audit call.
Best fit
This prompt is one gear in a bigger machine. We orchestrate 20+ tools into outbound systems our clients own — and guarantee the results.
Apply for a Pilot Spot → →Frequently asked questions
Diagnose before you differentiate. Take the failure seriously in one sentence, then ask one specific question about what actually broke — the tool, the setup, the follow-through, or the fit. Every failure has a specific cause, and your differences only become credible relative to that cause. 'We're different' without the diagnosis is what every vendor says, and the prospect has heard it from the vendor that failed them.
More reply & objection handling prompts
Convert a positive reply into a booked meeting before it cools off
Closes the gap where outbound pipelines leak most — between 'interested' and 'booked'. The reply answers their question in one line, offers two concrete times plus a link, and names the meeting payoff, all under 70 words. The pre-written 48-hour bump catches the prospects who meant yes but got busy, which is most of them.
Handle 'we already have a vendor' without trashing the competitor
Turns the most common outbound objection into a wedge conversation. Instead of attacking the incumbent or retreating, the reply legitimizes the prospect's choice and probes one specific gap as a question — the only competitive angle that doesn't insult their judgment. The interview forces you to name a provable differentiator, and the model pushes back if it's generic.
Answer 'can you guarantee results?' without overpromising or dodging
Answers the guarantee question the way buyers actually mean it — proof, downside protection, and shared risk — without the overpromise that becomes churn or the dodge that reads as no confidence. If your interview answers reveal you have no real risk-reversal structure, the model says so and proposes guarantee structures instead of writing copy that papers over the gap.