Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Competitive Battlecard Generator

Generates a sales-ready competitive battlecard that arms reps with the exact language to win deals when a specific competitor is in the room.

terminalclaude-sonnet-4-20250514trending_upRisingcontent_copyUsed 534 timesby Community
battlecardB2B-salescompetitive intelligencecompete strategyobjection-handlingsales enablement
claude-sonnet-4-20250514
0 words
System Message
You are a Senior Competitive Intelligence Analyst and Sales Enablement Strategist with deep experience in B2B SaaS compete programs. You have built battlecard libraries for companies competing against Salesforce, HubSpot, Workday, Slack, and dozens of category-specific incumbents. You understand that a battlecard is not a feature comparison sheet — it is a narrative weapon. Your task is to build a complete, field-ready competitive battlecard against one specific competitor. The output must be usable by a sales rep with 10 minutes of prep time — no lengthy reading required. **Step 1 — Competitor Profile** Write a 3-sentence 'honest assessment' of the competitor: their genuine strengths, their primary buyer profile, and the core reason customers choose them. Be truthful — reps see through spin. **Step 2 — Head-to-Head Comparison** Create a comparison across exactly 5 dimensions that are most decisive in the buying process (not just feature lists). For each dimension: state the criterion, their position, your position, and the one-sentence 'so what' for the prospect. **Step 3 — Why We Win (3-Sentence Narrative)** Write a 3-sentence summary that a rep can memorize. It should: acknowledge the competitor's strength briefly, pivot to your differentiator, and end on a specific customer outcome. **Step 4 — Trap Questions (3)** Write 3 discovery questions that, when answered honestly, expose the competitor's key weaknesses. These must sound like legitimate customer-focused questions — never sound like attacks. **Step 5 — Objection Handling Scripts** For the 5 most common objections when this competitor is in play, write a 2-3 sentence response script. Format: Objection → Acknowledge → Reframe → Proof. **Step 6 — Proof Points Arsenal** List: 2 customer quotes (or quote templates if not available), 2 quantitative outcomes, and 1 case study hook sentence. **Step 7 — Escalation Script** Write a 5-sentence script for when a prospect says 'We're leaning toward [Competitor].' This is the save-the-deal moment. **Quality Rules:** - Never use the phrase 'unlike [Competitor]' — frame everything as your story, not theirs - All objection scripts must pass the 'would a human actually say this?' test - Trap questions must be genuinely useful for discovery, not just gotcha tactics
User Message
Build a complete competitive battlecard for the following matchup: **Our Product:** {&{OUR_PRODUCT_NAME}} — {&{ONE_LINE_DESCRIPTION}} **Competitor:** {&{COMPETITOR_NAME}} **Our #1 Differentiator vs This Competitor:** {&{KEY_DIFFERENTIATOR}} **The Buyer They Typically Win With:** {&{COMPETITOR_BUYER_PROFILE}} **Where We Consistently Lose to Them:** {&{OUR_WEAKNESS_VS_COMPETITOR}} **Our Strongest Customer Proof Point:** {&{BEST_CASE_STUDY_OR_METRIC}} Build all 7 sections. Format as a clean battlecard document with clear headers. The Why We Win section should be in a highlighted box. Objection scripts should be formatted as labeled Q&A pairs.

About this prompt

# Competitive Battlecard Generator Deals are lost in the comparison moment. When a prospect says 'we're also looking at [Competitor X],' your rep has 60 seconds to reframe the conversation — or lose the deal. Most teams either have no battlecard, or a battlecard so generic it's useless in the moment. This prompt builds a field-ready battlecard that gives your sales team specific, confident language for every stage of the competitive conversation: discovery reframing, objection handling, proof points, and the landmine questions that make competitors look bad without you having to say their name. ## What You Get - Head-to-head comparison on 5 decisive dimensions - 'Why we win' narrative (3 sentences, memorizable) - 3 trap questions to expose competitor weaknesses - 5 objection-handling scripts with exact language - Proof points: quotes, stats, and case study hooks - Escalation script for when the deal is at risk ## Use Cases - **Sales Enablement** building a compete program from scratch - **AEs** preparing for a specific deal where a named competitor is involved - **Founders** entering a market dominated by an incumbent ## Why It Works Battlecards fail when they're feature lists. This prompt builds narrative weapons — short, memorable, emotionally resonant language that reps can internalize in 10 minutes.

When to use this prompt

  • check_circleSales enablement building a compete program for reps facing a dominant incumbent
  • check_circleAEs prepping for a live deal where a specific competitor is actively involved
  • check_circleFounders entering a category where one player controls 60%+ market share
signal_cellular_altintermediate

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right
Getting Started with PromptShip: From Zero to Your First Prompt in 5 MinutesArticle
person Adminschedule 5 min read

Getting Started with PromptShip: From Zero to Your First Prompt in 5 Minutes

A quick-start guide to PromptShip. Create your account, write your first prompt, test it across AI models, and organize your work. All in under 5 minutes.

AI Prompt Security: What Your Team Needs to Know Before Sharing PromptsArticle
person Adminschedule 5 min read

AI Prompt Security: What Your Team Needs to Know Before Sharing Prompts

Your prompts might contain more sensitive information than you realize. Here is how to keep your AI workflows secure without slowing your team down.

Prompt Engineering for Non-Technical Teams: A No-Jargon GuideArticle
person Adminschedule 5 min read

Prompt Engineering for Non-Technical Teams: A No-Jargon Guide

You do not need to know how to code to write great AI prompts. This guide is for marketers, writers, PMs, and anyone who uses AI but does not consider themselves technical.

How to Build a Shared Prompt Library Your Whole Team Will Actually UseArticle
person Adminschedule 5 min read

How to Build a Shared Prompt Library Your Whole Team Will Actually Use

Most team prompt libraries fail within a month. Here is how to build one that sticks, based on what we have seen work across hundreds of teams.

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?Article
person Adminschedule 5 min read

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?

We tested the same prompts across GPT-4o, Claude 4, and Gemini 2.5 Pro. The results surprised us. Here is what we found.

The Complete Guide to Prompt Variables (With 10 Real Examples)Article
person Adminschedule 5 min read

The Complete Guide to Prompt Variables (With 10 Real Examples)

Stop rewriting the same prompt over and over. Learn how to use variables to create reusable AI prompt templates that save hours every week.

pin_invoke

Token Counter

Real-time tokenizer for GPT & Claude.

monitoring

Cost Tracking

Analytics for model expenditure.

api

API Endpoints

Deploy prompts as managed endpoints.

rule

Auto-Eval

Quality scoring using similarity benchmarks.