The Competitive Battle Card: Arming Sales Against Legacy Rivals
Objective: Build an executive one-page sales battle card for a modern cloud customer service platform competing against complex legacy enterprise vendors, translating technical capabilities into objection-handling talk tracks, landmine questions, and quantified proof points.
You are a Senior Product Marketing Manager at Freshworks (FRSH) supporting the enterprise sales team. In head-to-head mid-market opportunities against legacy helpdesk software, reps are getting bogged down in 200-item RFP feature checklists. You need to author a battle card that shifts the conversation to deployment speed, total cost of ownership, and modern omnichannel usability.
Follow the lesson's battle card structure to construct a complete sales enablement asset: top 3 differentiated strengths, top 3 competitor traps to expose, 2 landmine questions for reps to plant early in discovery, and objection reframes for price vs value.
Before you start
What you'll need
Free path (everything below is enough to finish)
Structured tabular layout for cross-functional comparison
Clean executive formatting ready for sales distribution
Paid upgrades (optional, faster/deeper)
Real-time contextual enablement during active sales cycles
The process
4 steps
Step 01 of 04
The lesson highlights that core PMM deliverables include positioning documents and battle cards that distill product strengths into clear, evidence-backed proof points for sales reps.
What are the top 3 differentiated strengths and verified proof points that separate modern cloud support from complex legacy competitors?
Procedure
- Identify 3 core areas where modern cloud customer support outperforms legacy platforms (e.g., 30-day onboarding vs 9-month implementation, unified omnichannel inbox, predictable all-inclusive pricing)
- Attach a verified customer proof point or benchmark to each strength
- Draft a 15-second elevator pitch summarizing the core value proposition for sales reps
DIFFERENTIATION MATRIX (Freshworks vs Legacy Enterprise): 1. Time-to-Value: Live in 30 days vs. 6-9 month complex setup (Proof: 4,000+ mid-market migrations) 2. Unified Omnichannel: WhatsApp, Email, Phone, Chat in one agent screen (Proof: 35% reduction in handle time) 3. Total Cost of Ownership: Zero mandatory implementation consultant fees (Proof: 60% lower 3-year TCO)
Healthy
Every strength is backed by a concrete operational outcome and quantified proof point that a sales rep can state in 10 seconds.
Unhealthy
Listing generic claims like 'better user interface' or 'faster' without proof points or comparative benchmarks.
What this means
A competitive strength is only effective in sales enablement if it is specific, provable, and directly tied to an executive buyer's ROI.
So what do I do about it?
| Symptom | Action | Effort |
|---|---|---|
| Reps make vague claims about usability during demos | Equip reps with exact time-to-value benchmarks (30 days vs 9 months) | 5 min |
Step 02 of 04
The lesson's battle card structure specifies identifying competitor weaknesses backed by G2 reviews, pricing structure, and deployment traps to steer buyers away from competitors.
Which 3 competitor vulnerabilities expose the total cost of ownership traps and operational overhead of legacy vendors?
Procedure
- Audit competitor public pricing and review site complaints regarding hidden add-on costs and paid professional service requirements
- Synthesize findings into 3 crisp vulnerability points
- Formulate the exact trap reps should help the prospect identify in their evaluation
COMPETITOR VULNERABILITY AUDIT: 1. Hidden Implementation Cost: Legacy vendors mandate expensive third-party systems integrators costing $50k+. 2. Add-on Pricing Penalties: Basic analytics, SLA routing, and additional channels require paid premium tier upgrades. 3. Clunky Agent Experience: Disconnected legacy tools cause tab-switching fatigue and higher support agent turnover.
Healthy
Focuses on structural weaknesses (cost architecture and implementation delays) that the competitor cannot easily fix.
Unhealthy
Attacking minor UI bugs or features that the competitor is likely to patch in their next sprint.
What this means
Aim competitive attacks at business model flaws and architectural overhead rather than surface-level feature checklists.
So what do I do about it?
| Symptom | Action | Effort |
|---|---|---|
| Prospect believes the competitor's sticker price is comparable | Provide a 3-year TCO calculation worksheet detailing integration and admin costs | 30 min |
Step 03 of 04
Discovery-driven battle cards arm reps with 'landmine questions'—inquiry questions that lead prospects to discover competitor shortcomings on their own during sales conversations.
What 2 landmine discovery questions can sales reps ask to expose the competitor's implementation and customization friction?
Procedure
- Formulate questions that prompt the prospect to ask competitors about implementation timelines and admin maintenance hours
- Ensure questions sound consultative rather than confrontational
- Provide reps with the expected customer response and follow-up talk track
LANDMINE QUESTIONS FOR DISCOVERY CALLS: - Question 1: 'When you evaluated your last support platform, how many hours per week did your team spend maintaining custom routing scripts?' Goal: Exposes heavy administrative overhead required by legacy tools. - Question 2: 'Did the quote you received include the third-party implementation consultant fees, or is onboarding billed separately?' Goal: Exposes hidden 5-figure professional service fees.
Healthy
Questions invite the buyer to reflect on their own operational pain and uncover hidden vendor costs.
Unhealthy
Leading questions that sound like aggressive sales traps and put the prospect on the defensive.
What this means
A good landmine question makes the customer ask the competing vendor tough questions during their next demo.
So what do I do about it?
| Symptom | Action | Effort |
|---|---|---|
| Prospect is running parallel demos with legacy vendors | Send the discovery checklist for the prospect to take into competitor meetings | 5 min |
Step 04 of 04
Stage 4 (Enablement) requires turning common prospect objections into structured 'When They Say / You Say' reframes so reps maintain deal momentum under pressure.
How should reps reframe the common enterprise objection: 'Legacy Vendor X is the safe, established industry standard'?
Procedure
- Document the top 2 enterprise objections heard in win/loss reviews
- Draft the 'When They Say / You Say' script acknowledging the concern and pivoting to modern agility
- Package the complete asset into a clean, 1-page reference card
OBJECTION HANDLING TALK TRACK: - When They Say: 'Legacy Vendor X is the enterprise standard; nobody gets fired for buying them.' - You Say: 'Legacy Vendor X was built 15 years ago for desktop-only ticketing. Today's modern support teams choose us because our consumer-grade interface gets agents fully productive in days, not months, cutting onboarding time by 70% and saving $40,000 in annual consulting retainers.'
Healthy
Validates the customer's instinct for safety while demonstrating that modern speed and lower TCO are the true low-risk choice.
Unhealthy
Dismissing the competitor's reputation or arguing defensively about feature parity.
What this means
Effective objection handling reframes the buyer's risk perception from 'established brand' to 'hidden organizational drag.'
So what do I do about it?
| Symptom | Action | Effort |
|---|---|---|
| Deals stall in security and executive committee reviews | Attach executive summary one-pager with enterprise security certs (SOC2, ISO) and ROI proof | 30 min |
Final deliverable
A complete, field-ready one-page competitive sales battle card containing differentiated strengths, competitor vulnerability teardown, landmine discovery questions, and objection reframing scripts.
See a reference example
Figma vs. Adobe InDesign/Illustrator Enterprise Battle Card (Sample Extract)
ONE-SENTENCE POSITIONING:
'Figma is the only browser-native product design platform that unites designers, developers, and product managers in real time, eliminating version drift and expensive desktop license lock-in.'
TOP 3 STRENGTHS & PROOF POINTS:
1. Real-Time Multiplayer Collaboration: Zero sync lag; PMs and devs inspect live files without purchasing full design licenses.
2. Frictionless Browser Access: Runs on any OS (Mac, Windows, Chromebooks) with zero local software installation.
3. Single Source of Truth: Design system components update instantly across all team projects.
COMPETITOR WEAKNESSES TO EXPOSE:
1. Disconnected Desktop Files: Requires manual file sharing, leading to broken developer handoffs and version confusion.
2. Heavy Hardware Requirements: Demands high-end local workstations and rigid per-seat licensing.
3. Slow Feedback Cycles: Non-designers cannot comment directly on canvas without third-party plugins.
LANDMINE DISCOVERY QUESTIONS:
- 'How many days does your engineering team typically wait between a design spec handoff and production QA?'
- 'What percentage of your non-design stakeholders actually open desktop design files today?'
OBJECTION REFRACTION ('When They Say / You Say'):
- When They Say: 'We already have enterprise Adobe Creative Cloud site licenses.'
- You Say: 'Creative Cloud is great for print and illustration, but Figma is purpose-built for digital product software teams. Our customers keep CC for marketing graphics while moving product engineering to Figma, cutting handoff cycle time by 60%.'Success criteria
You're done when you can:
- Populates all 4 core battle card sections with specific, verified evidence
- Includes 2 consultative landmine questions and structured objection reframes
- Focuses on business outcomes and total cost of ownership over raw feature specs