competitive-battlecard
Create sales-ready competitive battlecards comparing your product against a specific competitor — positioning, feature comparison, objection handling, and win/loss patterns. Use when preparing sales teams, creating competitive materials, or responding to 'why not competitor X?'
What this skill does
## Competitive Battlecard Create a concise, sales-ready battlecard for use against a specific competitor. ### Context You are creating a competitive battlecard for **$ARGUMENTS**. Use web search to research the competitor's current product, pricing, positioning, and recent changes. If the user provides files (feature lists, win/loss data, sales call notes), read them first. ### Instructions 1. **Research the competitor** (use web search): - Current product offerings and features - Pricing tiers and model - Target market and positioning - Recent product launches or changes - Known strengths and weaknesses - Customer reviews and sentiment (G2, Capterra, Reddit) 2. **Create the battlecard** with these sections: ### Company Overview - Founded, HQ, funding/revenue (if public) - Target market and ICP - Positioning in one sentence ### Quick Comparison | Capability | Us | Them | Winner | |---|---|---|---| | [Feature area 1] | [Our approach] | [Their approach] | [Us/Them/Tie] | | [Feature area 2] | ... | ... | ... | | Pricing | ... | ... | ... | | Support | ... | ... | ... | ### Where We Win - [Advantage 1]: [Proof point or customer quote] - [Advantage 2]: [Specific capability they lack] - [Advantage 3]: [Better approach with reasoning] ### Where They Win - [Their strength 1]: [Our counter-positioning] - [Their strength 2]: [How we mitigate this gap] ### Common Objections & Responses | Prospect Says | Respond With | |---|---| | "Competitor X has [feature]" | "[Our alternative approach and why it's better for them]" | | "They're cheaper" | "[Value framing: total cost of ownership, ROI, hidden costs]" | | "They're more established" | "[Our advantages: speed, innovation, focus, support]" | ### Landmines to Plant Questions to ask the prospect that highlight competitor weaknesses: - "How important is [area where we excel] to your team?" - "Have you evaluated [specific capability they lack]?" ### Win/Loss Patterns - We tend to win when: [pattern] - We tend to lose when: [pattern] - Key differentiator in competitive deals: [what tips the scale] 3. **Keep it scannable**: Sales reps need to reference this during calls. Use tables, bold text, and short bullets. Save as markdown. Format for easy printing or sharing in Notion/Confluence. --- ### Further Reading - [How to Design a Value Proposition Customers Can't Resist?](https://www.productcompass.pm/p/how-to-design-value-proposition-template)
Related in Sales & CRM
process-mapper
IncludedUse when a BizOps lead, COO, or process-improvement owner needs to document an end-to-end business process (procurement, employee onboarding, incident handoff, customer-onboarding, claims adjudication) in BPMN-style notation, measure cycle times by stage, surface where work spends most of its time waiting vs. being worked, and quantify the gap between processing time and total elapsed time. Pairs Lean / Six Sigma / Theory-of-Constraints canon with deterministic stdlib-only Python tools to produce a process map, a ranked bottleneck list (with severity + root-cause hypothesis), and a cycle-time analysis (P50, P90, value-add ratio, Little's-Law throughput). Distinct from sales-pipeline, system-reliability (SLO), and strategic-OKR work — this is tactical process documentation for internal operations.
payment-integration
IncludedIntegrate payments with SePay (VietQR), Polar, Stripe, Paddle (MoR subscriptions), Creem.io (licensing). Checkout, webhooks, subscriptions, QR codes, multi-provider orders.
customer-success-manager
IncludedMonitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success
sales-engineer
IncludedAnalyzes RFP/RFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win/loss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'.
customer-success-manager
IncludedMonitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success
sales-engineer
IncludedAnalyzes RFP/RFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win/loss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'.