# How to Create Competitive Battlecards with Effective Objection Handling: A Complete Guide

> Master competitive battlecards with effective objection handling. Use the PM Skills marketplace /battlecard command to structure competitor intelligence and responses into a markdown template.

- Repository: [Pawel Huryn/pm-skills](https://github.com/phuryn/pm-skills)
- Tags: how-to-guide
- Published: 2026-06-13

---

**To create competitive battlecards with effective objection handling, use the `/battlecard` command in the PM Skills marketplace, which structures competitor intelligence into a markdown template with dedicated "Common Objections & Responses" matrices.**

The **phuryn/pm-skills** repository provides an end-to-end solution for sales teams and product marketers to generate competitive battlecards. By leveraging the `competitive-battlecard` skill and corresponding `/battlecard` command, you can transform raw competitive intelligence into sales-ready assets that include structured objection handling frameworks.

## Understanding the Competitive Battlecard Architecture

The PM Skills marketplace implements a **skill → command** pattern that separates knowledge from workflow execution. This architecture ensures battlecard logic remains reusable across different AI assistants and commands.

### The Skill Definition

The core framework resides in [`pm-go-to-market/skills/competitive-battlecard/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/pm-go-to-market/skills/competitive-battlecard/SKILL.md). This file defines the canonical battlecard structure, including:

- **Research prompts** that guide web searches for competitor features, pricing, positioning, and customer sentiment
- **Section templates** for company overviews, quick comparison tables, and win-loss patterns
- **Objection handling matrices** that use the format `| Prospect Says | Respond With |` to preload responses to common push-backs

The skill file acts as the knowledge base, containing the specific markdown layouts and checklists that ensure consistent output quality.

### The Command Implementation

The executable workflow lives in [`pm-go-to-market/commands/battlecard.md`](https://github.com/phuryn/pm-skills/blob/main/pm-go-to-market/commands/battlecard.md). This file orchestrates the skill by:

- Defining the invocation syntax: `/battlecard <product> vs <competitor>`
- Adding UI-level guidance for step-by-step execution
- Specifying input handling for uploaded files like competitor PDFs or win/loss CSVs
- Rendering the final output using the templates defined in the skill

When invoked, Claude (or compatible AI assistants) loads the skill, executes the research steps, and populates the objection handling tables with contextual data.

## How to Create a Competitive Battlecard

The `/battlecard` command accepts various input formats to accommodate different research scenarios. Below are practical implementations you can execute directly.

### Basic Competitive Analysis

Invoke the command with your product and primary competitor:

```text
/battlecard Our CRM vs Salesforce

```

The AI solicits follow-up details—such as target buyer persona and available win/loss data—then generates a complete battlecard using the research checklist defined in [`SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/SKILL.md).

### Enriching with Primary Source Materials

Upload competitor collateral to ground the analysis in factual data:

```text
/battlecard ProjectFlow vs Monday.com for mid-market teams
[upload] competitor_feature_list.pdf
[upload] win_loss_data.csv

```

The command parses the uploaded files, merges them with web-search findings, and populates the "Common Objections & Responses" table with data-backed proof points rather than generic responses.

### Exporting for Team Collaboration

Generate battlecards formatted for your knowledge base:

```text
/battlecard Our AI-writer vs Jasper
--format markdown
--output ./battlecard.md

```

This outputs a self-contained markdown file ready for import into Notion, Confluence, or conversion to PDF for sales enablement distribution.

### Chaining with Market Analysis

Combine strategic and tactical competitive intelligence:

```text
/competitive-analysis Figma competitors
/battlecard Our Design Tool vs Figma

```

The first command gathers broad market insights; the second focuses those findings into a concise battlecard with specific objection handling for sales conversations.

## Structuring Effective Objection Handling

The PM Skills battlecard framework emphasizes **objection handling** through structured matrices that prepare sales reps for typical buyer resistance.

### The Objection Matrix Format

The skill implements two complementary table structures:

**Prospect-Focused Matrix** (from [`SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/SKILL.md)):

```

| Prospect Says | Respond With |
|---------------|--------------|
| "Your competitor is cheaper" | "While their base price is lower, our total cost of ownership includes..." |

```

**Response-Proof Matrix** (from command context):

```

| Objection | Response | Proof Point |
|-----------|----------|-------------|
| Security concerns | SOC 2 Type II certification | "We completed audit in Q2 2024" |

```

These matrices ensure reps never face objections without prepared responses and supporting evidence.

### Research-Backed Proof Points

The battlecard skill specifically prompts the AI to gather:

- **Customer sentiment** from review sites and forums
- **Recent product launches** that might shift competitive positioning
- **Strengths/weaknesses** relative to your specific feature set

This intelligence feeds directly into the proof point column, ensuring responses cite specific competitor limitations or verified customer outcomes rather than vague claims.

## Summary

- **Use the `/battlecard` command** to invoke the competitive battlecard workflow in the PM Skills marketplace.
- **Reference [`pm-go-to-market/skills/competitive-battlecard/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/pm-go-to-market/skills/competitive-battlecard/SKILL.md)** for the underlying framework that structures research and objection handling.
- **Upload competitor files** to enrich the battlecard with primary source data and specific proof points.
- **Leverage the matrix formats** (`| Prospect Says | Respond With |` and `| Objection | Response | Proof Point |`) to create sales-ready objection responses.
- **Export to markdown** for easy integration into Notion, Confluence, or PDF distribution tools.

## Frequently Asked Questions

### What file types can I upload to the `/battlecard` command?

The command accepts PDFs containing competitor feature lists, CSV files with win/loss data, and text-based collateral. According to the implementation in [`pm-go-to-market/commands/battlecard.md`](https://github.com/phuryn/pm-skills/blob/main/pm-go-to-market/commands/battlecard.md), these uploads merge with web-search findings to populate the objection handling tables with specific proof points.

### How does the skill ensure objection responses are accurate?

The `competitive-battlecard` skill in [`SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/SKILL.md) defines specific research prompts that gather customer sentiment, recent competitor launches, and verified strengths/weaknesses. The command then maps these findings to the proof point column in the objection matrix, ensuring responses cite concrete data rather than generic marketing claims.

### Can I customize the battlecard sections for my industry?

Yes. Because the skill definition uses standard markdown templates stored in [`SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/SKILL.md), you can modify the research checklist and table structures to include industry-specific comparison criteria or regulatory objections. The skill → command architecture allows these customizations to persist across all future `/battlecard` invocations.

### Is the battlecard output compatible with other AI assistants?

The markdown skill format is portable. While the `/battlecard` command is optimized for Claude, the underlying [`SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/SKILL.md) file can be consumed by other AI assistants that support markdown skill definitions, such as Gemini CLI or OpenCode, making the battlecard framework reusable across your AI tool stack.