playbook

The objection battle-cards

Turn your hardest recurring objections — price, a named competitor, "not now" — into honest, non-defensive responses that reframe around value, as a doc the whole team reuses.

medium ~45 min

when to reach for this

The same objections come up every week — "you're too expensive," "we're already looking at [competitor]," "call us next quarter" — and they get handled differently (and often defensively) by every rep, in the moment, under pressure. This system builds a reusable battle-card doc: each hard objection turned into an honest, non-defensive response that reframes around value, with the real concern named and the follow-up question ready. Build it once and the whole team handles the hard moments the same strong way — not a one-off save you forget by next call.

gather this first

Your top 6–10 recurring objections — pull them from call transcripts (see *The post-call follow-up system*) or just list the ones you dread, in objections.md.
Your value-prop.md and proof points (cases, ROI numbers, references) — the honest material every reframe has to be grounded in.
2–3 responses that have actually worked for you, and 1–2 that fell flat — so Claude learns your real register and what to avoid.

the workflow

01
Find the real concern under each objection

A defensive answer fights the surface objection; a strong one addresses what's underneath. Have Claude diagnose the true concern before writing a single response.
you ask
```
Read objections.md and value-prop.md. For each objection, tell me the REAL concern likely underneath it (e.g. "too expensive" often means "I'm not convinced of the ROI" or "I don't have budget authority"), and what question would confirm which one it is. Don't write responses yet.
```
what you get back A diagnosis table — "'Not now' → usually no urgency or a competing priority; confirm with: 'What would need to change for this to be a this-quarter problem?'" — so every response targets the real blocker, not the words.

Diagnosing before answering is the whole game — most weak objection handling answers the literal words instead of the concern underneath them.
02
Draft honest, non-defensive responses

Now write the responses, with a hard rule: no defensiveness, no bad-mouthing competitors, no claims you can't back. Reframe around value the prospect actually cares about.
you ask
```
For each objection, write a response that: acknowledges it genuinely (no "but"), reframes around the value in value-prop.md, and ends with a question that re-opens the conversation. Rules: never disparage [competitor], never make a claim we can't prove, no defensiveness. Match the register of the responses I pasted. Keep each under 60 words.
```
what you get back One battle-card per objection — for "too expensive": acknowledge the budget reality, reframe to cost-of-the-status-quo with a real proof point, and ask "what would the right ROI need to look like for this to be worth it?" — honest, not slippery.
03
Stress-test the hard ones

Have Claude play a tough prospect and push back on your responses, so you find the ones that crumble before a real prospect does.
you ask
```
Play a skeptical prospect. For the 3 hardest objections, push back twice on each of my responses — find where they sound scripted, evasive, or make a claim I can't defend. Then tighten those 3 cards.
```
what you get back A back-and-forth that exposes the weak spots ("this still sounds like you're dodging the price question") and three tightened cards that hold up under a second and third push.
04
Assemble the reusable battle-card doc

Pull it into one clean, scannable artifact the team can actually use mid-call — the format matters as much as the content.
you ask
```
Assemble everything into a clean battlecards.md: one card per objection with Objection / Real concern / Response / Follow-up question / Proof point to cite. Add a one-line index at the top so a rep can jump to the right card mid-call. Keep each card scannable in 10 seconds.
```
what you get back A single, paste-ready battlecards.md — indexed, one tight card per objection — that a rep can open during a call and use in seconds, and that onboards new reps faster than shadowing.

Save this file. It becomes a living team asset — add a new card every time a fresh objection shows up in *The post-call follow-up system*.

make it your own

**Competitor-specific cards:** when a named competitor keeps coming up, build a dedicated section grounded in honest, verifiable differences — never claims you can't back or can't say to their face.
**Feed it from real calls:** mine recurring objections out of *The post-call follow-up system* extractions so the doc reflects what prospects actually say, not what you imagine they'll say.
**Make it always-loaded:** advanced teams can turn battlecards.md into a reusable skill or /objection command so it's available in any sales conversation (see the *Features* tab).

watch out for

Every proof point and competitor claim on a card must be true and current — a battle-card spreads a wrong number or an unfair claim to the whole team at once. Fact-check each card against real evidence before it ships, and never put a disparaging or unverifiable claim about a competitor in writing.
Pull objections from transcripts and notes, but scrub the source — keep customer names and deal details out of the battle-card doc itself; it's a team reference, not a place for [prospect]'s private data.
Claude drafts the cards; reps still read the room and decide what to say. A battle-card is a starting point a human adapts live, not a script to recite — and you own that the responses are honest, not just persuasive.

you'll end up with A reusable, indexed `battlecards.md` — each hard objection turned into an honest, non-defensive, value-reframing response the whole team uses the same strong way.

Find the real concern under each objection

Draft honest, non-defensive responses

Stress-test the hard ones

Assemble the reusable battle-card doc