Competitive Battle Card Review Meeting Template

This meeting template gives RevOps and sales leaders a 60-minute, high-output session to build or update competitive battle cards. It uses real call data from Gong and Outreach, applies the MEDDPICC framework for qualification gaps, and produces a shared artifact that reps can use in the next deal cycle.

The meeting is designed for a team of 6-12 people—mix of AEs, SDRs, and RevOps.

1. Warm-Up: The Last Lost Deal (10 min)

Time: 10:00 AM – 10:10 AM Goal: Surface the most recent competitive loss and get the team’s collective memory on a specific competitor.

Script: “Everyone, pull up your CRM. Find the last deal you lost to a named competitor—Salesforce, HubSpot, Workday, whoever. Write down three things: the competitor name, the deal size, and one objection they used that you couldn’t counter. You have 2 minutes. Go.”

After 2 minutes, go around the room. Each person shares in 30 seconds. The facilitator captures the competitor names on a whiteboard or shared doc.

Facilitator says: “We’re going to use these losses to build a battle card for the competitor that came up most. If it’s a tie, we’ll pick the one with the highest total deal value lost. Today’s target: [Competitor Name] .”

Output: A single competitor chosen for the session. All other losses are parked for future meetings.

2. Data Dive: Pull Real Call & CRM Signals (15 min)

Time: 10:10 AM – 10:25 AM Goal: Extract objective evidence from Gong call transcripts, Salesforce opportunity records, and Outreach email sequences. No opinions—only data.

Script: “Open Gong. Search for calls tagged with the competitor name in the last 90 days. Filter for deals that were ‘Closed Lost’ with that competitor listed.

Export the top 5 call transcripts. Also open Salesforce, run a report for ‘Closed Lost’ opportunities where the primary competitor field equals [Competitor Name] . Pull the ‘Loss Reason’ field and any notes in the ‘Competitor Analysis’ section.

Finally, open Outreach and find any email sequences that mention the competitor. Look for replies where the prospect said ‘we’re going with [competitor].’”

Facilitator says: “We’re looking for three specific data points: (1) the exact objection the competitor used, (2) the deal stage when we lost, and (3) the MEDDPICC element that was weakest at that stage. Write each on a sticky note. We’ll group them.”

Example from a real session (HubSpot vs. Salesforce):

• Objection: “HubSpot’s native CPQ is cheaper than your Salesforce CPQ + Revenue Cloud bundle.”
• Stage: Evaluation (Stage 4 of 6).
• Weak MEDDPICC element: Economic Buyer—never met the CFO who approved the HubSpot deal.

Output: 3–5 clustered objection themes, each linked to a deal stage and a MEDDPICC gap.

3. Build the Battle Card: Objection → Counter (15 min)

Time: 10:25 AM – 10:40 AM Goal: Write 3–5 counter-narratives for the top objections. Each counter must include a data point, a story from a won deal, and a specific action for the rep.

Script: “Take the first objection cluster. Write a counter that has three parts: (1) a verifiable fact about the competitor’s weakness, (2) a short story from a deal we won against them, and (3) a specific question the rep should ask to flip the conversation. Use this format exactly:”

`` Objection: [Exact phrase from Gong transcript] Counter: [Fact + Story] Rep Action: [Question to ask] ``

Facilitator says: “For the HubSpot CPQ objection, here’s a real counter from a Winning by Design case study: HubSpot’s CPQ lacks multi-currency support for international deals. In our Q3 win against them at Acme Corp, the CFO needed to invoice in EUR and USD. HubSpot couldn’t do it.

We won that $2.1M deal. Rep action: Ask the prospect, ‘Does your finance team need multi-currency or multi-entity billing today?’”

Repeat for each objection cluster. The facilitator types directly into a shared Google Doc or Notion page.

Output: A draft battle card with 3–5 objections and counters, each with a rep action.

4. Roleplay the Counter (10 min)

Time: 10:40 AM – 10:50 AM Goal: Test the counters in a live, timed roleplay. One rep plays the prospect, one plays the AE. The rest observe and score each counter on clarity and effectiveness.

Script: “Pair up. Person A is the AE, Person B is the prospect who just said the first objection. You have 3 minutes. AE, use the counter you just wrote. Prospect, push back hard—use a real objection from your own lost deal if you want. Go.”

After 3 minutes, the facilitator asks: “Raise your hand if the AE successfully flipped the conversation. What worked? What didn’t?”

Facilitator says: “If the counter didn’t land, rewrite it now. Change the fact, the story, or the question. We’ll test the revised version next meeting.”

Output: A revised battle card with counters that survived live testing.

5. Embed in Your Workflow (5 min)

Time: 10:50 AM – 10:55 AM Goal: Assign ownership for publishing the battle card in the tools reps actually use—Salesforce, Outreach, or a shared Slack channel.

Script: “Who owns the final version? [Name] , you’ll add this as a PDF attachment to the ‘Competitor’ field in Salesforce. [Name] , you’ll create a snippet in Outreach that reps can insert into email sequences. [Name] , you’ll post the key counters in the #competitive-intel Slack channel with a pinned message. Deadline: end of day tomorrow.”

Facilitator says: “Every rep must have this battle card in their next discovery call. If you don’t use it, you’re flying blind. Set a reminder in your calendar for 7 days from now to review usage data from Gong—how many times did reps mention the counter?”

Output: A named owner for each distribution channel, with a deadline.

6. Close & Next Meeting (5 min)

Time: 10:55 AM – 11:00 AM Goal: Set the date for the next battle card review and define the single metric that will tell you if the battle card is working.

Script: “Next meeting is in 2 weeks. Same time. Before then, each rep must use the battle card in at least one competitive call.

RevOps will pull the Gong tag for the counter phrases and report back on how many times they were used. The metric we’re tracking: Win rate against [Competitor Name] in the next 30 days. If it doesn’t move, we rebuild the battle card.”

Facilitator says: “One last thing: Write down one thing you’ll do differently tomorrow because of this session. Share it in the Slack channel. Meeting done.”

Output: A scheduled next meeting, a single KPI, and a Slack thread with individual commitments.

FAQ

Q: How often should we run this meeting? A: Run it every 2 weeks if you have 3+ active competitors. For a single dominant competitor, monthly is enough. Use Gong’s competitive tag volume to decide—if calls mentioning a competitor double, schedule an emergency session.

Q: What if we don’t have Gong or Outreach? A: Use call recordings from your phone or Zoom. Pull Salesforce notes manually. The process is the same—the tools just speed it up. Without Gong, you lose the exact objection phrasing, but you can still get the gist from rep notes.

Q: Who should attend? A: 6–12 people max. Include at least 2 AEs who lost deals to the competitor, 1 SDR who set meetings against them, and 1 RevOps person to pull data. If you have a product marketer, bring them too.

Q: How do we know if the battle card is working? A: Track win rate against that competitor. Also check Gong for usage—if reps aren’t saying the counter phrases, the battle card isn’t embedded. A 5% win rate improvement within 30 days is a good target.

Q: Can we reuse this template for a different competitor? A: Yes. The template is competitor-agnostic. Just change the competitor name in step 1 and re-run the data pull. Each competitor gets its own battle card.

Q: What if the roleplay reveals the counter is weak? A: Rewrite it immediately. Don’t publish a counter that fails in roleplay. Use the feedback to find a stronger fact or story. If you can’t find one, escalate to product marketing for a deeper competitive analysis.

Q: How do we keep battle cards up to date? A: Assign a quarterly review for each battle card. If a competitor releases a new feature, update the card within 1 week. Use the same meeting template but skip the data dive if the competitor hasn’t changed.