# Sales Competitive Intel

> Build a per-competitor battlecard — comparison matrix, honest win/loss lines, objection reframes, and landmine questions to plant.

- Skill: `matrixx0070/sales-competitive-intel` (Agent Skill)
- Install (CLI): `npx skillmds@latest add matrixx0070/sales-competitive-intel`
- Raw SKILL.md: https://api.skillmd.com/api/skills/matrixx0070/sales-competitive-intel/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: Matrixx0070 (https://skillmd.com/u/matrixx0070)
- Updated: 2026-09-08
- Page: https://skillmd.com/skills/matrixx0070/sales-competitive-intel

---


# Sales Competitive Intel

## When to use
Use this when a deal is competitive or a prospect names an alternative, and you need a battlecard: where you win, where you lose, how to reframe, and the traps to set.

**Not for:** general account research (use sales-account-research); internal roadmap or pricing strategy; broad market sizing. This is a per-competitor, deal-facing weapon.

## Method
1. **Scope the field.** Confirm your product and the specific competitors in play. A battlecard is per-competitor, not generic.
2. **Gather facts.** For each competitor collect positioning, target segment, pricing model, key features, integrations, and recent moves. Prefer verifiable sources; mark rumor as rumor.
3. **Map strengths and weaknesses honestly** — theirs and yours. **Decision point:** if you can't name a real place they beat you, you haven't researched enough; keep going.
4. **Find the wedge.** Identify 2-3 differentiators that matter to *this* buyer's use case, not just any difference.
5. **Build the matrix.** Compare you vs. each competitor across the criteria the buyer actually weighs.
6. **Write objection handling.** For each "but competitor X does Y," give a truthful reframe and a discovery question that exposes the trade-off. **Decision point:** if the reframe requires spin, concede the point and pivot to a criterion you own.
7. **Set landmines.** Questions the prospect should ask the competitor that surface their weaknesses.

## Example
Competitor "Rival Inc" is cheaper and prospect knows it. Matrix shows you win on native integrations and support SLA, lose on price and time-to-deploy. Objection: "Rival is 30% cheaper" → "True on sticker price — most teams find the integration work they charge extra for erases that; how are you scoping integration cost?" Landmine to plant: "Ask them what their P1 response SLA is in writing."

## Pitfalls
- **Overstating your edge.** The prospect catches the exaggeration and stops trusting the whole card.
- **Generic battlecards.** "We're more enterprise-grade" wins nothing; tie every claim to a buyer criterion.
- **Rumor as fact.** Unverified competitor claims backfire when repeated to the buyer.
- **No landmines.** A defensive card with no questions to plant cedes the offense.

## Output format
```
Competitors covered: <list>
Comparison matrix:
  | Criterion | Us | Competitor A | Competitor B |
  |-----------|----|--------------|--------------|
Where we win: <honest list>
Where we lose: <honest list>
Key differentiators (buyer-valued): <2-3>
Objection handling:
  - "they say <X>" → "you say <reframe + discovery question>"
Landmines to plant:
  - <question for the prospect to ask the competitor>
Confidence: <verified vs. assumed sources>
```