OperatorRadar
DiscoverAI ToolsAI AgentsInsights
Submit a ToolFind My Solution
OperatorRadar

Find the tools, systems, and ideas that move your business forward. Timeless business thinking, rebuilt for the AI era.

Discover

  • Discover
  • AI Tools
  • AI Agents
  • Software
  • Agencies
  • Categories

Decide

  • Decision Guides
  • Compare
  • Find My Solution
  • Insights

Execute

  • Prompts
  • Workflows
  • Submit a Tool
  • Contact

Company

  • About
  • Privacy
  • Terms

© 2026 OperatorRadar. All rights reserved.

Built by Ekofi

  1. Home
  2. Prompts
  3. Build a Competitive Battlecard from Verified Facts
Featured
intermediate
Claude or ChatGPT (verify current model choice)
v1.0.0

Build a Competitive Battlecard from Verified Facts

Build a battlecard that wins deals. Compare your product against {{competitor_names}} using only facts you can defend in a discovery call—no marketing fluff, no guesses.

Full prompt

You are a competitive intelligence analyst for {{company_name}}. Your job is to build a battlecard that sales can use in real conversations.

Our product: {{product_description}}
Our pricing: {{pricing_tiers}}
Our key differentiators: {{differentiators}}

Competitors to compare against:
{{competitor_list}}

For each competitor, research and document:
1. Core features (list 10–15 capabilities, mark parity vs. gaps)
2. Pricing model (subscription tier, per-seat cost, enterprise custom pricing)
3. Deployment options (SaaS, self-hosted, hybrid)
4. Target buyer (SMB, mid-market, enterprise)
5. Known limitations or common customer complaints
6. When we win vs. when they win (honest assessment)

Output format:
- Feature comparison matrix (rows = features, columns = products)
- Pricing summary table
- Win/loss narrative for each competitor (2–3 sentences per competitor)
- Source citations (links, docs, or last verified date)
- Honest gaps section: where we're behind and why it doesn't matter for our ICP

Constraints:
- Only include facts you can verify from public docs, pricing pages, or customer reviews
- If you're unsure about a feature or price, mark it [UNVERIFIED] and flag for sales to confirm
- Avoid marketing language; use neutral, technical descriptions
- Assume the reader is a sales rep who will use this in a call within the hour

How to use

1. Fill in {{company_name}}, {{product_description}}, {{pricing_tiers}}, {{differentiators}}, and {{competitor_list}} with your actual data. 2. Run the prompt through your AI tool (Claude, ChatGPT, or internal LLM). 3. Copy the output into a shared doc (Notion, Confluence, or Google Drive). 4. Have your product and sales leads review for accuracy—flag any [UNVERIFIED] claims and research them before sharing with the team. 5. Update the battlecard quarterly or whenever a competitor releases a major feature. 6. Share the link in Slack so reps can reference it during discovery calls.

Example input

Our product: {{company_name}} = Acme Analytics
{{product_description}} = Real-time data pipeline for e-commerce, built on streaming SQL. Ingests from Shopify, Stripe, and custom APIs. No code required.
{{pricing_tiers}} = Starter ($500/mo, up to 10M events/month), Pro ($2,500/mo, up to 100M events/month), Enterprise (custom, unlimited)
{{differentiators}} = No-code SQL, sub-second latency, Shopify-native connectors, 99.99% uptime SLA
{{competitor_list}} = Segment, mParticle, Tealium, Treasure Data

Example output

# Competitive Battlecard: Acme Analytics vs. Segment, mParticle, Tealium, Treasure Data

## Feature Comparison Matrix
| Feature | Acme | Segment | mParticle | Tealium | Treasure Data |
|---------|------|---------|-----------|---------|---------------|
| No-code SQL | ✓ | ✗ | ✗ | ✗ | ✓ [UNVERIFIED] |
| Sub-second latency | ✓ | ✗ (batch) | ✓ | ✓ | ✗ (batch) |
| Shopify native | ✓ | ✓ | ✗ | ✓ | ✗ |
| Self-hosted option | ✓ | ✗ | ✓ | ✓ | ✓ |
| 99.99% SLA | ✓ | ✓ | ✓ | ✓ | ✗ (99.9%) |

## Pricing Summary
| Product | Entry Price | Per-Unit Model | Enterprise |
|---------|-------------|----------------|------------|
| Acme | $500/mo | Events/month | Custom |
| Segment | $120/mo | MTUs (tracked users) | Custom |
| mParticle | $1,500/mo | Events + users | Custom |
| Tealium | $2,000/mo | Visitors | Custom |
| Treasure Data | $1,200/mo | Events | Custom |

## Win/Loss Narrative
**vs. Segment:** Segment is the market leader for CDP, but they batch data. If your customer needs real-time personalization (e.g., dynamic pricing on checkout), Acme wins. Segment wins if they need a pre-built audience sync to 200+ tools.

**vs. mParticle:** mParticle has real-time, but requires code. Acme wins for non-technical teams. mParticle wins for enterprises with dedicated data engineering.

**vs. Tealium:** Tealium is tag-heavy and expensive. Acme wins on simplicity and cost. Tealium wins if they have legacy tag infrastructure they can't rip out.

**vs. Treasure Data:** Treasure Data is batch-focused and pricey. Acme wins on speed and ease. Treasure Data wins for massive-scale data warehousing (100B+ events/month).

## Honest Gaps
- **No pre-built audience sync:** Acme doesn't sync audiences to ad platforms (Facebook, Google). Workaround: API or Zapier. Matters if customer is ad-tech heavy.
- **Smaller partner ecosystem:** Segment has 400+ integrations; Acme has 50. Matters for enterprises with niche tools.

## Sources
- Segment pricing: segment.com/pricing (verified 2024-01-15)
- mParticle features: docs.mparticle.com (verified 2024-01-10)
- Tealium SLA: tealium.com/legal (verified 2024-01-12)
- Treasure Data: treasuredata.com/pricing (verified 2024-01-14)

Customization tips

  • Add a 'Red Flag Questions' section: questions reps should ask prospects to disqualify competitors early (e.g., 'Do you need real-time or batch?' filters out Segment for latency-sensitive use cases).
  • Create a 'Proof Points' subsection under each competitor: specific customer wins, analyst reports (Gartner Magic Quadrant), or third-party benchmarks that back up your positioning.
  • Include a 'Pricing Sensitivity' row: flag which competitors undercut you on price and what you offer instead (speed, support, ease of use) so reps know how to handle budget objections.
  • Build a 'Feature Roadmap' section: if you're shipping something in Q2 that closes a gap vs. a competitor, note it here so reps can use it as a tiebreaker in close conversations.
  • Add a 'Common Objections' section tied to each competitor: 'Prospect says Segment is cheaper' → 'True, but Segment batches data; we're real-time. Here's the cost of a delayed personalization decision.'