60-Min Sales Training: The Competitive Teardown Workshop

The deal that gets lost in the last ten minutes

Picture a mid-market SaaS team, twelve reps, average contract value around $38,000, sales cycle roughly 70 days. Deals move cleanly through discovery and demo. Then, somewhere in week eight, procurement loops in a second vendor and the rep gets a one-line email: "We're also evaluating [competitor] — can you send a comparison?" What the rep sends back is usually a feature grid built by product marketing eighteen months ago, listing checkmarks against a version of the competitor that no longer exists.

That is the moment competitive teardown training is built to fix, and it is worth being precise about why it fails today. The rep is not lazy. The rep genuinely does not know three things: what the competitor's current pricing page actually says, what their own customers who switched from that competitor complained about, and what the competitor's rep is saying about them in the room they were not in. Those three gaps are all knowable, and none of them are solved by a slide.

The pattern shows up in the numbers your CRM already holds. Pull closed-lost opportunities from the last two quarters and filter on a competitor loss reason. In most teams that field is either blank on more than half of records or populated with a single word — "price." When a loss reason field is 50%+ blank, you do not have a competitive problem yet; you have a data problem that masquerades as one. The first teardown workshop for most teams is therefore partly an archaeology exercise: reps reconstruct, from memory and email threads, what actually happened in five to eight recent losses.

A second scenario is worth naming because it is more common than the head-to-head bake-off: the silent comparison. The buyer never tells you a competitor is involved. They read the rival's website, their G2 category page, and two analyst summaries, form a mental default, and then run your process against that unspoken baseline. Reps lose these without ever seeing the shape of the loss. A teardown that only prepares reps for named competitive deals misses the majority of competitive influence, which is why the workshop should always end with language reps can deploy proactively — a framing question in discovery — rather than only a rebuttal they deploy defensively.

The 60-minute constraint is not arbitrary in this context. Sales teams do not reliably show up for a half-day offsite four times a year, and when they do, the artifacts produced get filed and never opened. An hour fits inside an existing weekly team meeting or a Friday enablement slot. It is short enough that the facilitator cannot allow open-ended discussion, which is exactly the discipline that makes the output usable. Every minute in this workshop is assigned.

How the hour is actually structured

The workshop runs in three phases with hard time boxes. The facilitator — usually an enablement lead, a sales manager, or a product marketer — picks the competitor before the meeting starts. Letting the group choose the target burns ten minutes and produces the competitor everyone is already comfortable with rather than the one costing the most revenue. Pick from data: the competitor named in the most closed-lost records over the trailing 90 days.

Phase one, roughly 15 minutes: evidence gathering. Reps split into pairs, and each pair owns one evidence stream. One pair reads the competitor's own site — pricing page, product pages, the language on the homepage above the fold. One pair reads review-site content on G2 or Capterra, filtering to reviews from the last twelve months and sorting to the two- and three-star reviews, because five-star reviews are marketing and one-star reviews are usually a support incident. The interesting material lives in the middle. One pair pulls the CRM: every opportunity in the last two quarters where this competitor appears, won and lost, with the notes attached. If you have a conversation intelligence tool recording calls, one pair searches transcripts for the competitor's name and listens to two or three clips where the buyer raised it unprompted.

Fifteen minutes is enough because the assignment is narrow. Each pair is looking for three things and writing them into a shared doc: a specific claim the competitor makes, a specific complaint their customers make, and a specific thing the competitor's sales process does that yours does not.

Phase two, roughly 25 minutes: structured analysis. The pairs report back, and the facilitator fills a single grid on screen. Five rows, and the questions under each row are what turns a report-out into analysis:

• Product — where does functionality genuinely overlap, where is there a real gap in either direction, and which gap does a buyer actually feel in month three rather than in a demo?
• Pricing and packaging — what is the list price and unit of pricing (per seat, per usage, platform fee plus consumption), what is bundled at each tier, and where do costs appear later that are not on the pricing page?
• Messaging — what is the promise on their homepage, and what job does that promise do for the buyer emotionally? Reduce risk? Signal sophistication to their own leadership?
• Sales motion — do they lead with a free trial, a self-serve tier, a proof of concept, a paid pilot? How many people from their side show up on a call? How fast do they discount, and at what point in the cycle?
• Customer sentiment — from the two- and three-star reviews, what is the recurring complaint pattern, and is it a product complaint, an implementation complaint, or a support complaint?

The discipline here is that every cell needs a source. "I think they're expensive" does not go on the board. "Their published pricing page shows three tiers and the middle tier excludes the API, which appeared as a complaint in four of the eleven recent reviews we read" does.

Phase three, roughly 20 minutes: build and roleplay. The group converts the grid into artifacts. A one-page battle card gets drafted live: three sentences on when this competitor typically shows up, three genuine strengths stated honestly, three areas where you win and the evidence for each, and three questions a rep can ask a buyer that surface the difference without naming the competitor at all. Then two or three objection-handling responses get written and immediately spoken out loud, with one person playing the skeptical buyer. Written but unspoken language does not survive contact with a live call.

The facilitator's hardest job is cutting off phase two. Analysis is comfortable and roleplay is not, so groups will happily spend forty minutes on the grid and skip the part that changes behavior. Set a visible timer. When it hits, the grid is done regardless of how complete it feels — an incomplete grid that produced a rehearsed script beats a beautiful grid nobody can speak.

The numbers that tell you it worked

Measuring a single training hour is genuinely hard, and it is worth being honest that most claimed ROI figures for sales training are unverifiable. What you can measure are leading indicators inside your own CRM, and you should baseline them before the first workshop so the comparison means something.

Competitor field completion rate. Before the workshop, measure the percentage of closed-lost opportunities where a competitor is named. Most teams start somewhere between 30% and 60%. The workshop's most reliable effect is on this number, because reps who have just spent an hour on a competitor start noticing and recording it. Getting to 80%+ within two quarters is a realistic target, and it is the precondition for every other measurement being trustworthy.

Competitive win rate, tracked separately from overall win rate. Segment opportunities into those with a named competitor and those without. These two win rates usually differ by a wide margin — competitive deals typically close at a meaningfully lower rate — and blending them hides the effect entirely. Track the competitive segment quarter over quarter, and give it at least two full sales cycles before drawing conclusions. If your cycle is 70 days, that is roughly five months before the data means anything.

Stage where competitive deals die. This is the most diagnostic number and the least tracked. Pull the last stage reached on competitive losses. If deals die late — in negotiation or legal — the problem is usually pricing or contract terms, and no amount of battle card language fixes it. If they die at the demo or evaluation stage, the problem is positioning and the workshop directly addresses it. If they die in discovery, you are being disqualified before you ever compete, which points at inbound routing or ICP fit rather than competitive skill.

Discount depth on competitive deals versus non-competitive deals. Compare average discount percentage across the two segments. A spread here quantifies what competitive weakness costs in margin. If competitive deals close at, say, 8 points deeper discount, and competitive deals are 40% of your closed-won volume, the arithmetic on your average contract value tells you what a better answer to "why you over them" is worth annually. Do this calculation with your own numbers; do not accept a benchmark from a vendor blog.

Battle card usage. If your enablement library or CRM shows document opens, track them. A card that gets opened in the first two weeks and never again is a card nobody trusts. Cards that keep getting opened during active deals are the ones worth refreshing.

On cadence: quarterly per major competitor is the reasonable default. In fast-moving categories where rivals ship and reprice frequently, monthly on your top one or two and quarterly on the rest works better. The maintenance cost matters — a battle card older than about two quarters is more dangerous than no card, because a rep confidently citing a pricing tier the competitor discontinued loses credibility instantly and mid-call. Put a review date on every card and treat an expired card as archived, not as reference.

On group size: six to twelve people is the workable band for a 60-minute format. Below six you cannot staff four evidence pairs. Above twelve, phase two report-outs eat the roleplay time, and you should either split into two sessions or extend to 90 minutes. Do not extend to 90 minutes casually — the constraint is doing useful work.

Trade-offs, and what to run instead

The 60-minute teardown is one point on a spectrum, and it is not always the right one.

Teardown workshop versus a dedicated competitive intelligence function. Companies past a certain size hire competitive intelligence specialists and license platforms — Crayon and Klue are the established names in this category — that continuously monitor competitor sites, pricing changes, and job postings, and push updates into the CRM. This is genuinely better intelligence than twelve reps can gather in fifteen minutes. The trade-off is that centrally produced intelligence has an adoption problem: reps do not read what they did not help build. The workshop's real advantage is not the quality of the analysis, it is that the people who will use the language wrote the language. The strongest setup is both — a CI function or tool supplies the raw monitoring, and the workshop is where reps convert it into things they will actually say. If you have a CI tool and reps still can't handle the competitor objection, more monitoring is not the missing piece.

Teardown versus win/loss interviews. Structured win/loss programs, where a neutral third party interviews buyers after the decision, produce far more reliable causes than reps' self-reported loss reasons — reps systematically over-attribute losses to price. Win/loss interviews are slower and cost real money, and they tell you what happened rather than teaching anyone what to say. Run win/loss to find out which competitor to tear down and what the true loss cause is; run the teardown to build the response.

Teardown versus call review. An hour spent listening to recordings of your own reps handling the competitor question, with the group critiquing, teaches delivery better than a teardown teaches it. But call review only surfaces language reps already have. If nobody in the room has a good answer, playing eight recordings of bad answers just documents the gap. Sequence matters: teardown to build the answer, call review a month later to sharpen delivery.

Teardown versus feature-comparison content from product marketing. Product marketing's comparison pages are built for search and for buyers, and they are legally reviewed. They are usually accurate and usually useless in a live call, because they are written to be defensible rather than persuasive. Keep them — reps need something to send — but do not confuse having one with having trained the team.

The biggest structural trade-off is depth versus frequency. A quarterly 60-minute teardown on four competitors gives every rep shallow coverage of the full landscape. A single 3-hour deep teardown on your primary competitor gives deep coverage of one. If more than roughly half your competitive losses concentrate on one rival, go deep on that one and skip the others entirely; breadth is a luxury for teams whose losses are genuinely distributed.

Where these workshops go wrong

Turning it into a hate session. The failure mode is a room of reps listing everything wrong with the competitor, leaving energized and overconfident. Buyers can hear contempt, and a rep who badmouths a rival reads as insecure. The corrective is procedural: require the battle card to state three genuine competitor strengths, written honestly, before any weakness goes on the page. Reps who can articulate why a buyer would reasonably choose the competitor are the ones who can credibly explain why this buyer should not.

Analyzing features instead of buying behavior. Feature grids are seductive because they are easy to build and easy to argue about. But buyers rarely choose on feature count; they choose on perceived risk, on who the decision makes them look like internally, and on which vendor seems more likely to still be around and supported in three years. The most valuable cell in the grid is usually the sales-motion row — knowing the competitor runs a free 14-day trial changes what you do in week one far more than knowing they have a Gantt view.

Stale artifacts. A battle card citing a pricing tier the competitor retired is worse than nothing. Date every card, assign an owner, and set a hard expiry. If nobody refreshes it by the expiry date, archive it rather than leaving it in the library. Reps will trust a small set of current cards; they will trust nothing in a library where half the content is wrong.

No roleplay. The single most common cut when the hour runs short, and the one that guarantees the workshop produces no behavior change. Language written but never spoken does not transfer. Protect the final twenty minutes absolutely — if phase two has to end mid-grid, end it mid-grid.

Unsourced claims. Someone in the room "heard" the competitor is losing customers or raised prices 30%. That rumor propagates into a battle card, a rep repeats it on a call, the buyer knows it is false, and the deal is over. Every claim needs a link or a record ID. If it cannot be sourced, it does not ship.

Fabricating competitor pricing. Many competitors do not publish pricing at all. The honest card says "pricing not published; from three recent deals in our CRM, their quoted range was X to Y at similar seat counts" and names those records. It does not say "they charge $X per seat" on the basis of one rep's recollection.

No owner after the hour. The workshop ends, the doc lives in someone's drive, and nothing reaches the CRM. Assign a named owner in the last two minutes, with a 48-hour deadline to publish the card where reps work — attached to opportunity records, in the enablement library, wherever they already look. An artifact that requires a rep to go find it will not be found.

Skipping the proactive framing. Teams build rebuttals and forget that the best competitive move happens in discovery, before the competitor is named. Two or three questions that surface the evaluation criteria you win on — asked routinely, of every buyer — do more than any rebuttal. Put them on the card.

Related questions

How long should a competitive battle card be?

One page, readable in under ninety seconds. Three lines on when this competitor appears, three honest strengths, three areas you win with evidence, three discovery questions. Anything longer does not get read mid-call, which is the only moment it matters.

Who should facilitate the workshop?

Enablement or product marketing, not the top-performing rep. The facilitator's job is enforcing time boxes and demanding sources, which is a different skill from selling. If a rep facilitates, the room defers to their opinions instead of the evidence.

Should reps ever name the competitor on a call?

Only if the buyer names them first. Volunteering a rival's name introduces them into a deal where they might not have been. When the buyer raises it, acknowledge the competitor's genuine strengths first — that credibility is what makes the rest of your answer land.

What if we do not have call recordings or clean CRM data?

Run the workshop anyway with review sites and the competitor's public site, which cost nothing. Then use the gaps you hit as the argument for fixing the data. The first session's most useful output is often a list of what you cannot answer.

Can this work for a non-software product?

Yes. Replace the product row with specs, lead times, and service terms; replace pricing tiers with contract structure and total cost of ownership. The evidence streams change — trade publications and distributor feedback instead of G2 — but the three phases hold.

FAQ

Is there a formal certification for a competitive teardown workshop?

No. This is a repeatable internal team exercise, not a credentialed program, and no vendor owns the format. Related material is widely published by revenue intelligence and sales enablement companies, and competitive positioning is a component of broader methodologies like MEDDIC and Challenger. Treat any claim of an official certification skeptically.

How often should a team run one?

Quarterly per major competitor is a sensible default. Monthly on your top one or two rivals if the category moves fast — frequent repricing, rapid feature releases, heavy funding activity. The gating factor is maintenance capacity: only commit to a cadence you can sustain, since an outdated battle card actively damages credibility.

What tools help with competitor intelligence?

Crayon and Klue are the established competitive-enablement platforms, aggregating competitor changes and delivering battle cards into the CRM. G2 and Capterra provide free review data. Conversation intelligence products such as Gong and ZoomInfo's Chorus let you search call transcripts for competitor mentions. None replace the workshop; they supply raw material for it.

What is the single biggest mistake teams make?

Stopping at feature comparison. The teardown that changes outcomes examines how the competitor sells — their trial motion, their discounting timing, who they bring to calls, what emotional promise their messaging makes — rather than cataloguing what they have built. Buyers experience the sales process long before they experience the product.

How do you compare against a competitor with a totally different pricing model?

Build a total cost of ownership view over a realistic term, usually three years. Include implementation, training, admin overhead, integrations, and the cost of growth at your buyer's expected trajectory. Per-seat versus consumption pricing only becomes comparable at a specific volume, so model it at the buyer's actual numbers rather than arguing list price.

Can a 60-minute session really change win rates?

One session, on its own, rarely does. What it reliably produces is an artifact and rehearsed language that did not exist an hour earlier. Change shows up when the cadence is sustained across two or more sales cycles and the cards stay current — measure competitive win rate as a separate segment, and give it five months before judging.

Sources

1. G2 — software review data used as competitive evidence: https://www.g2.com
2. Capterra — software reviews and category comparison: https://www.capterra.com
3. Gong — revenue intelligence and sales call analysis: https://www.gong.io
4. Crayon — competitive intelligence platform: https://www.crayon.co
5. Klue — competitive enablement and battle cards: https://www.klue.com
6. ZoomInfo Chorus — conversation intelligence: https://www.zoominfo.com/products/chorus
7. HubSpot Sales Blog — sales process and enablement guidance: https://blog.hubspot.com/sales
8. Gartner Sales research and insights: https://www.gartner.com/en/sales

Related on PULSE

• [The Pipeline Review Workshop — 60-Min Training — Pulse Sales Trainings](/knowledge/st244)
• [The Forecasting Calibration Workshop — 60-Min Training — Pulse Sales Trainings](/knowledge/st250)
• [The Multi-Threading Strategy Workshop — 90-Min Training — Pulse Sales Trainings](/knowledge/st247)
• [The Enterprise Account Planning Workshop — 120-Min Training — Pulse Sales Trainings](/knowledge/st243)
• [The LinkedIn Social Selling Workshop — 90-Min Training — Pulse Sales Trainings](/knowledge/st253)
• [60-Min Sales Training: Forecasting Accuracy for AEs](/knowledge/st0469)