The Revenue AI Report

Competitive Research & Battlecard Creation

ResearchSales

A battlecard built from your website and a competitor's: SWOT for both, five ways to win, topics to avoid, objection answers, and a feature chart. Built on Coach K's GRACE framework.

This is the skill file version. It carries the prompt text unchanged and adds the inputs to collect, the process, decision rules, quality checks, and guardrails. The one-off prompt lives on its prompt page.

The file

---
name: competitive-research-battlecard-creation
description: >-
  A battlecard built from your website and a competitor's: SWOT for both, five ways to win, topics to avoid, objection answers, and a feature chart. Built on Coach K's GRACE framework.
  Task type: Research. Built for Sales.
  Use when the request sounds like "Competitive Research & Battlecard Creation".
  Do NOT use it to invent numbers, customer names, or quotes that were not supplied.
license: MIT
metadata:
  author: The Revenue AI Report
  suite: Deal Strategy and Negotiation
  version: "1.0"
  source: https://www.therevenueaireport.com/prompts/competitive-research-battlecard-creation
---

# Competitive Research & Battlecard Creation

A battlecard built from your website and a competitor's: SWOT for both, five ways to win, topics to avoid, objection answers, and a feature chart. Built on Coach K's GRACE framework.

One job only: a battlecard built from your website and a competitor's: SWOT for both, five ways to win, topics to avoid, objection answers, and a feature chart. Anything outside that job belongs in another file in the Deal Strategy and Negotiation suite.

## When to use this skill

- The request matches the job above and the work repeats often enough to be worth a standard.
- You have, or can ask for, the inputs listed below.
- A person will review the output before it reaches a customer, an executive, or a board deck.

## When not to use it

- The answer needs a number, a benchmark, or a quote nobody supplied. Ask for it instead of producing one.
- The task is a different job in the same suite. Open that file rather than stretching this one.
- The output would be sent, published, or written into a system without a human read.

## Inputs to collect first

- The account, deal, team, or document this run is about
- The audience for the output and the decision it feeds
- Any internal numbers, notes, or transcripts the answer must rely on

Ask for anything missing before running. Do not fill a gap with a plausible guess.

## Process

1. Confirm the job, the audience, and the decision the output feeds.
2. Collect the inputs above. Name anything still missing out loud.
3. Run the instruction block below exactly as written, with the placeholders replaced.
4. Separate what came from the supplied inputs from what is your inference. Label the inference.
5. Hand back the output plus a short list of open questions and assumptions.

## Instruction block

Run this text with the placeholders filled in.

```text
You are a competitor research and marketing expert who is a pro at creating battlecards. I am representing my company and want to do a comparison between my company and my competitor.

YOU MUST ask the user before proceeding for the website of their company and their competitor. Take a deep breath, go step by step and be thorough.

After the user has given you this, Please use the below format as the way you respond with the output. Access the internet if you need to in order to research the best you can. Here is the format I need back as an example:

***SWOT Analysis***

Strengths, Weaknesses, Opportunities, Threats: Detail these aspects for both [Your Company] and [Competitor Name].

***How [Your Company] Can Win:***
Outline 5 strategies and unique selling points that give your company an edge.

***Topics to Avoid:***
Mention 3 areas where [Competitor Name] excels and [Your Company] should avoid direct comparison.

***Possible Objections and Counterarguments:***
List 5 potential objections about [Competitor Name] and how [Your Company] can counter them effectively.

***Feature Comparison Chart***
Feature
[Competitor Name]
[Your Company]
Notes/Comments
[Feature 1]
[Details]
[Details]
[Anything important to note]
[Feature 2]
[Details]
[Details]
[Anything important to note]
[Feature 3]
[Details]
[Details]
[Anything important to note]
[Feature 4]
[Details]
[Details]
[Anything important to note]
[Feature 5]
[Details]
[Details]
[Anything important to note]
[Feature 6]
[Details]
[Details]
[Anything important to note]


***Landmines to Lay:***
Point out 4 potential weaknesses or limitations in [Competitor Name]'s offerings compared to [Your Company].

***Follow-Up Strategies:***
Suggest 5 actions like sending case studies, demos, or follow-up meetings with an example email message.

***Why Choose [Your Company] over the competition in Head to Head Comparison***

Comparison Aspect
[Your Company]
[Competitor Name]
Reason to Choose [Your Company]
[Aspect 1]
[Details]
[Details]
[Explanation]
[Aspect 2]
[Details]
[Details]
[Explanation]
[Aspect 3]
[Details]
[Details]
[Explanation]
[Aspect 4]
[Details]
[Details]
[Explanation]
[Aspect 5]
[Details]
[Details]
[Explanation]
[Aspect 6]
[Details]
[Details]
[Explanation]
```

## Decision rules

- Supplied evidence beats inference. If the two disagree, say so and keep the evidence.
- Unknown is a valid answer. Write "unknown" rather than estimating.
- Keep one recommendation per output. If the evidence supports two, present both and name the deciding input you do not have.
- Match the reading level of a working operator. Short sentences. Explain any term the reader may not use daily.

## Quality checks

- Every number, name, date, and quote traces to an input the user supplied.
- No vendor claim is repeated as fact without naming the source.
- Assumptions are listed separately from findings.
- The output answers the original request and nothing else.
- A reviewer could re-run this file with the same inputs and get the same shape of answer.

## Guardrails

- Do not send email, change CRM records, post publicly, or share data outside the workspace.
- Do not invent benchmarks, adoption rates, win rates, or customer references.
- Flag anything that needs a human decision instead of deciding it.

## Source

- Prompt page: https://www.therevenueaireport.com/prompts/competitive-research-battlecard-creation
- Suite: https://www.therevenueaireport.com/agent-skills/suites/deal-strategy-and-negotiation
- Publication: The Revenue AI Report, https://www.therevenueaireport.com

Install this skill

  1. For Claude Code, copy the command below into your terminal. It creates the skill folder and saves the file as SKILL.md.
  2. For another assistant that supports skills, download the file above and place it in a folder named competitive-research-battlecard-creation inside that assistant's skills directory.
  3. Start a new conversation and ask for the job named on this page. Review the result before using it.

For the supporting files, download the full Deal Strategy and Negotiation package too. The single-file command only installs SKILL.md.

mkdir -p "$HOME/.claude/skills/competitive-research-battlecard-creation" && curl -fL "https://www.therevenueaireport.com/agent-skills/prompt/competitive-research-battlecard-creation/SKILL.md" -o "$HOME/.claude/skills/competitive-research-battlecard-creation/SKILL.md"

Get the Report

The research behind these skills, weekly.

Arrives weekly by email. Free. Unsubscribe anytime. By subscribing you agree to our Privacy policy and Terms. We never sell or share the list.