playbooks

home / skills / gtmagents / gtm-agents / battlecard-system

battlecard-system skill

/plugins/sales-enablement/skills/battlecard-system

This skill standardizes competitive positioning, objection handling, and talk tracks to accelerate enablement across teams.

npx playbooks add skill gtmagents/gtm-agents --skill battlecard-system

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
1.2 KB
---
name: battlecard-system
description: Use to standardize competitive positioning, objection handling, and talk
  tracks across teams.
---

# Battlecard System Skill

## When to Use
- Launching new competitive programs or product updates.
- Training teams ahead of major deals or campaigns.
- Refreshing differentiators based on win/loss analysis.

## Framework
1. **Competitive Intel** – capture strengths, weaknesses, proof, and trigger signals per competitor.
2. **Messaging Pillars** – align headline, supporting proof, and objection responses.
3. **Delivery Format** – deck, one-pager, LMS module, and short-form scripts.
4. **Distribution & Access** – tag assets, set expiration dates, and embed in enablement tools.
5. **Feedback Loop** – collect field feedback, update win/loss data, and refresh quarterly.

## Templates
- Battlecard layout (overview, talk track, objections, proof points).
- Objection handling matrix.
- Competitive win/loss capture form.

## Tips
- Keep “permission to win” statements crisp; avoid feature dumping.
- Include audio/video snippets from top performers.
- Align with legal/product teams before publishing sensitive data.

---

Overview

This skill standardizes competitive positioning, objection handling, and talk tracks across go-to-market teams. It packages templates, frameworks, and distribution patterns so sales, marketing, and CS speak consistently about competitors and product differentiators. Use it to speed up enablement and keep messaging current with field feedback.

How this skill works

The skill captures competitor intelligence, messaging pillars, and delivery formats into repeatable battlecards and objection matrices. It enforces tags, expirations, and distribution paths so assets reach the right teams via decks, one-pagers, LMS modules, or short-form scripts. A built-in feedback loop collects win/loss signals and field input to drive scheduled refreshes.

When to use it

  • Launching a new product or major update and aligning GTM messaging
  • Preparing reps and customer-facing teams ahead of key deals or campaigns
  • Refreshing differentiators after win/loss analysis or competitor changes
  • Rolling out a competitive program with standardized templates
  • Embedding objection handling and proof points into enablement content

Best practices

  • Capture competitor strengths, weaknesses, proof, and trigger signals in a single view
  • Keep permission-to-win statements crisp; avoid feature dumping
  • Map headline pillars to supporting proof and clear objection responses
  • Tag assets, set expiration dates, and embed in enablement tools for discoverability
  • Collect field feedback and update battlecards on a regular cadence

Example use cases

  • Create a one-page battlecard for a high-priority competitor before a product launch
  • Build an objection handling matrix for AE training sessions and roleplays
  • Generate short talk-track scripts for SDR outreach aligned to messaging pillars
  • Compile win/loss captures into quarterly updates that refresh sales assets
  • Distribute video/audio snippets from top performers alongside written playbooks

FAQ

How often should battlecards be refreshed?

Refresh quarterly or sooner after major competitor moves or product changes; use field feedback to trigger interim updates.

Who should approve sensitive competitive claims?

Align with legal and product teams before publishing any sensitive assertions or proof points.