Building Competitive Battlecards

• Source: Report research library
• Frameworks applied: Corporate Visions Unconsidered Needs and Why Change / Why You stories, Corporate Visions 5-step renewal messaging framework, status quo bias, evidence tiering from win/loss buyer interviews, Gong multithreading and question-volume benchmarks, weighted objection-handling criteria

The four-tier source hierarchy plus the ban on unsourced disparagement makes the card falsifiable, and the renewal-versus-displacement inversion is a real footgun most battlecard guidance misses.

Known weakness, published as found: Add a filled example card (one competitor, 4-5 populated rows) rather than an empty template, since 'speakable on a live call' cannot be judged from column headers. Cut the description to ~800 chars; at 999 the 'even if the word battlecard is never used' clause invites over-triggering.

1. 1.Copy the SKILL.md text below, or download the raw file.
2. 2.Create a folder named exactly building-competitive-battlecards in your agent's skills directory.
3. 3.Save the file inside that folder as SKILL.md.
4. 4.Ask the agent one of the trigger requests below.
5. 5.Check the output against what you already know before it leaves your desk.

• Build a battlecard for Competitor X with trap-setting questions and objection handling
• Our reps keep losing head-to-head to Acme — give me a one-pager they can use on calls
• Turn these win/loss findings into competitive positioning our AEs can actually use live

• Design the buyer interview guide and sampling plan for our win/loss program
• Score this recorded demo against our coaching rubric

---
name: building-competitive-battlecards
description: >-
  Builds one-page, field-usable competitive battlecards containing
  trap-setting questions, sourced objection handling, unconsidered-needs
  framing, and an owner and review date. Use when the user says "battlecard",
  "battle card", "competitive one-pager", "how do we position against
  a competitor", "our reps keep losing to X", "objection handling doc",
  "competitive positioning for sales", "trap setting questions", or
  "displacement play", or hands over competitor pricing pages, feature
  comparisons, or win/loss findings to turn into sales enablement. Use this skill whenever
  the task is packaging competitive intelligence into something a seller uses
  live in a call, even if the word "battlecard" is never used. Do NOT use for
  running the buyer interview program that generates the intelligence (see
  running-win-loss-analysis), for scoring a rep's call (see
  scoring-sales-calls), for new hire ramp design (see
  building-onboarding-ramp-plans), or for public-facing comparison pages and
  analyst briefs.
metadata:
  version: "1.0"
---

# Building competitive battlecards

Produce one battlecard per competitor that a seller can use mid-call, plus the maintenance mechanism that keeps it true. Market landscape analysis, public comparison pages, analyst briefings, and pricing strategy are out of scope.

## Source hierarchy

Rank evidence in this order and label every claim with its tier, because a battlecard that mixes buyer-verified fact with rep folklore gets abandoned after the first time a claim is contradicted on a call.

1. **Buyer-verified** — win/loss interview quotes from deals against this competitor. Highest weight: only 15% of CRM loss reasons match what buyers say in first-hand interviews, per Clozd's comparison of 1,000 closed-lost deals, reported in [Unkover](https://unkover.com/blog/win-loss-analysis/).
2. **Primary artifact** — the competitor's own pricing page, docs, contract terms, security portal, release notes.
3. **Field-reported** — rep or SE observation from a live deal, dated and attributed.
4. **Inferred** — anything else. Do not put tier 4 claims on the card.

Never write a disparaging claim you cannot source to tier 1 or 2. A single unverifiable jab handed to a buyer who knows better costs the deal and the card's credibility.

## Workflow

Copy this checklist and tick as you complete each item:

```
- [ ] 1. Scope the card to one competitor and one motion
- [ ] 2. Assemble evidence and tier every claim
- [ ] 3. Derive unconsidered needs and the differentiated change scenario
- [ ] 4. Write 3-5 trap-setting questions
- [ ] 5. Write objection responses with the pause-and-reframe structure
- [ ] 6. Write the displacement or defense play
- [ ] 7. Validate against the field-usability checks, fix, re-validate
- [ ] 8. Set owner, review date, and distribution
```

**1. Scope.** One card per competitor per motion (new-logo displacement versus renewal defense). Judgment step: you decide whether a competitor warrants its own card. Decision criterion — a card is justified when the competitor appeared in enough evaluated deals to produce a pattern rather than a story; below that, add them as a line on a landscape table. Start with the top two competitors and expand outward as the win/loss program widens ([Unkover](https://unkover.com/blog/win-loss-analysis/)).

**2. Assemble and tier evidence.** Pull competitive losses and wins against this competitor, the buyer-stated decision factors, competitor artifacts, and pricing observations. Mark each claim with its tier and the date observed. Undated competitive claims are the primary decay mechanism, because nobody can tell a stale claim from a current one without a date.

**3. Derive unconsidered needs.** Unconsidered Needs are challenges, shortcomings, or missed opportunities the prospect does not yet know about but that hold them back from important business goals, and they are by definition not discoverable through voice-of-the-customer research or by asking about stated needs ([Corporate Visions](https://corporatevisions.com/blog/unconsidered-needs/)). Run the sequence in order (same source): introduce the unconsidered need; align your unique strengths to it; establish the differentiated change scenario at the intersection of the two, where you are singularly qualified; use that as step one of a Why Change story; reinforce with a Why You story.

This is the highest-leverage section of the card. In a 400-participant B2B simulation run with Dr. Zakary Tormala, leading with an Unconsidered Need beat traditional stated-need and value-added messaging on presentation quality by 11%, uniqueness by 41%, and attitude and purchase intent by 10% ([Corporate Visions](https://corporatevisions.com/blog/unconsidered-needs/)). The mechanism it defeats is Status Quo Bias, and roughly 40% of pipeline deals end in no decision (same source) — so on a new-logo card, the primary opponent is inaction, not the named competitor.

Write it as: *unconsidered need → why it costs them → the capability only we bring → the change scenario*. Each unconsidered need must be one the competitor structurally cannot serve, not merely one they market less; an unconsidered need the competitor can also satisfy hands them your discovery work.

**4. Write trap-setting questions.** Produce three to five. A trap-setting question is asked of the buyer, is answerable honestly by them without any claim from you, and surfaces a limitation the competitor cannot resolve. Construction rules:

- Ask about the buyer's requirement or process, never about the competitor's product. "How do you plan to handle X when Y happens?" beats "Did you know they can't do X?", because the second is a claim you must defend and the first is a question they must answer.
- Ground each question in a documented tier-1 or tier-2 limitation, and note that limitation on the card next to the question so the rep knows what the trap is for.
- Phrase open-ended, not yes/no — "How does your team currently handle automation?" rather than "Do you use automation?" ([Gong](https://www.gong.io/blog/talk-to-listen-conversion-ratio)).
- Keep the total question load in range: 11–14 targeted questions is the discovery band with the greatest chance of success across 519,000 analyzed calls, and sellers who lost asked ~20 questions per call against 15–16 for winners ([Gong discovery](https://www.gong.io/blog/nailing-your-sales-discovery-calls), [Gong talk ratio](https://www.gong.io/blog/talk-to-listen-conversion-ratio)). Five traps plus a normal discovery flow exceeds the band, so cap traps at five and tell the rep to pick two.

**5. Write objection responses.** Objection handling carries the heaviest weight in call scoring at 30% ([MuchBetter.ai](https://muchbetter.ai/blog/sales-call-coaching-scorecard-a-25-point-rubric-for-managers)), so give each objection a rehearsable structure rather than a paragraph of talking points. Use four fields per objection: the objection in the buyer's words; the pause instruction, because pausing after an objection to let the customer speak is a rated coaching criterion (same source); the reframe that ties the objection back to the buyer's stated urgency (same source); and the proof point with its evidence tier. Cover at minimum: price, the competitor's single strongest feature, incumbent switching cost, and the "we're happy with what we have" status-quo objection.

**6. Write the play.** For new-logo displacement, the play is the Why Change story built on the unconsidered need, plus a multithreading instruction — multithreading lifts win rate by 130% on deals over $50K and successful deals carry 2x the buyer contacts, with strategic enterprise deals averaging 17 contacts ([Gong](https://www.gong.io/blog/the-best-sales-insights-of-2025)) — and, for technical evaluations, a note to bring a sales engineer to the demo, associated with up to +30% win rate (same source).

For renewal defense against a competitor circling your installed base, invert the messaging. Acquisition messaging disrupts status quo bias; renewal messaging must reinforce it ([Corporate Visions renewal framework](https://corporatevisions.com/blog/a-framework-for-winning-renewal-messaging/)). Run five steps in order (same source): document results with explicit progress detail; stabilize preferences by recalling the long original decision process; anticipate regret and blame by naming the ramp-up and change-management investment already made; mention the perceived cost of change; and reinforce selection difficulty by admitting competitors offer similar capabilities while showing you have kept them current. In the tested study, documenting results first with more explicit progress detail produced a statistically significant advantage on switching intentions, willingness to pay, trust, and perceived quality; no effect sizes are published, so cite the direction only (same source). Using acquisition-style disruption messaging on your own renewal base is the specific error that research warns against (same source).

**7. Validate, fix, re-validate.** Run all checks. If one fails, fix it and re-run the whole list; only publish once every check passes, because an unusable or unsourced card trains reps to ignore the whole library.

```
- [ ] Fits on one page at readable size; the rep can find any section in under 10 seconds
- [ ] Every factual claim about the competitor carries an evidence tier and an observed date
- [ ] No tier-4 (inferred) claims and no unverifiable disparagement
- [ ] 3-5 trap-setting questions, each tied to a named documented limitation
- [ ] Every objection has pause, reframe, and a sourced proof point
- [ ] At least one unconsidered need the competitor structurally cannot serve
- [ ] Named owner and next review date are on the card itself
- [ ] Read aloud: every line is speakable on a live call, not written prose
```

**8. Set the maintenance mechanism.** Put the owner name and review date on the card face. Re-review on the quarterly win/loss cadence and rebuild the card whenever loss reasons against that competitor shift, since closing the loop means updating battlecards and then measuring whether win rate against that competitor moves the following quarter ([Unkover](https://unkover.com/blog/win-loss-analysis/)).

## Output format

Use this exact section order — reps learn one card's geometry and navigate every other card by muscle memory, so reordering costs more than any wording improvement gains.

```markdown
# <Competitor> Battlecard — <motion: displacement | renewal defense>
Owner: <name> | Last verified: <date> | Next review: <date> | Our win rate vs them: X% (n=)

## When you hear they are in the deal
<2-3 line read: their typical entry point, buyer type, and where they win>

## Unconsidered needs -> our differentiated change scenario
| Unconsidered need | Why it costs them | Only we do this | Change scenario line to say |

## Trap-setting questions (ask 2, not all)
| Question to ask the buyer | Limitation it exposes | Evidence tier |

## Objection handling
| They say | Pause | Reframe to their urgency | Proof point | Tier |

## Where they legitimately win
<Honest list. Reps who know this stop over-claiming and get trusted.>

## Do not say
<Claims that are unverifiable, out of date, or legally risky>

## Deal mechanics
Multithread to: <roles> | Bring SE at: <stage> | Pricing posture: <line>
```

## Gotchas

- A battlecard written from CRM loss reasons encodes rep narrative, not buyer reality: only 15% of CRM loss reasons match first-hand buyer interviews across 1,000 closed-lost deals (Clozd, in [Unkover](https://unkover.com/blog/win-loss-analysis/)). Source the card from interviews or the competitor's own artifacts.
- The "Where they legitimately win" section is what makes the rest of the card believable. Cards with no honest concession read as marketing, and reps stop opening them after the first buyer pushback they were not prepared for.
- Unconsidered needs cannot be harvested from customer research or discovery calls, by definition ([Corporate Visions](https://corporatevisions.com/blog/unconsidered-needs/)). If the card's "unconsidered need" is something buyers already told you in interviews, it is a stated need and will produce no uniqueness lift.
- Do not reuse a displacement card for renewals. Disruption messaging aimed at your own installed base attacks the status quo bias that is currently keeping the customer, which is the specific failure the renewal research documents ([Corporate Visions](https://corporatevisions.com/blog/a-framework-for-winning-renewal-messaging/)).
- Cap trap-setting questions at five and instruct the rep to ask two. Question volume already correlates with losing — ~20 questions on lost calls versus 15–16 on won ones ([Gong](https://www.gong.io/blog/talk-to-listen-conversion-ratio)) — so a card that adds five obligatory questions on top of standard discovery converts a conversation into an interrogation.
- Competitive claims decay silently. Put the observed date next to each claim rather than only a single card-level review date, because a stale gotcha sends a rep chasing a limitation the competitor shipped a fix for two quarters ago.
- 84% of businesses say markets are increasingly crowded (Crayon, State of Competitive Intelligence, cited in [Unkover](https://unkover.com/blog/win-loss-analysis/)). Resist covering every named competitor: build for the top two, and keep the rest as a one-line landscape table until win/loss volume justifies a card.
- Distribution beats depth. Deliver the card as a one-page cheat sheet plus a 60-second video, and review it in week 2 of onboarding ([Prospeo](https://prospeo.io/s/sales-onboarding-training)); a five-page competitive brief that no seller opens mid-call has zero field value regardless of its accuracy.

What does the Building Competitive Battlecards skill do?

Builds one-page competitive battlecards with trap-setting questions, tiered objection handling, and unconsidered-needs framing

Where does the Building Competitive Battlecards skill come from?

Report research library. It was written by The Revenue AI Report against a 12 criterion quality rubric and graded in an independent scoring pass.

Why was the Building Competitive Battlecards skill chosen for this library?

The four-tier source hierarchy plus the ban on unsourced disparagement makes the card falsifiable, and the renewal-versus-displacement inversion is a real footgun most battlecard guidance misses.

When should the Building Competitive Battlecards skill not be used?

Do not use it for: Design the buyer interview guide and sampling plan for our win/loss program Or: Score this recorded demo against our coaching rubric

How do I install the Building Competitive Battlecards SKILL.md file?

Download the file, create a folder named exactly building-competitive-battlecards inside your agent's skills directory, and save the file inside it as SKILL.md. The agent loads it when a request matches the description.