Battlecards die in Notion. Here is how to build a competitive analysis that survives the field.
Competitive analysis is a sales artifact, not a strategy artifact
Most competitive analysis decks are built by product marketing for the executive team and then handed to sales as an afterthought. The result is a beautiful strategic document that sales never opens and never uses. The reverse approach — build the artifact for the field first, then derive the strategic view — produces an analysis that actually changes win rates. The field needs three things: positioning language they can use in a discovery call, objection handlers for the three most common objections each competitor raises, and a feature-by-feature comparison they can screenshot and send to a buyer. Build for those three needs and the strategic view falls out for free.
Pick three competitors, not ten
The competitive landscape slide that lists every possible competitor in the category is the slide that nobody reads. Pick the three competitors who actually show up in your deals — the ones your sales team mentions in pipeline reviews — and build deep analysis on those three. The other competitors get a one-line mention in an appendix slide. This concentration of effort produces battlecards that are deep enough to be useful, rather than shallow comparisons of a dozen vendors that none of your AEs can recall under pressure.
The win/loss section: lead with the patterns
Every competitive analysis should include a win/loss section based on the last twenty deals against each competitor. The section should lead with the three or four patterns that emerge — the segment where you consistently win, the segment where you consistently lose, the deal size where the dynamic shifts, the buyer persona that tilts the outcome. Pattern density is what makes the section actionable; deal-by-deal narration is what makes it ignorable. The DeckForge AI competitive analysis templates include a pattern-summary layout precisely for this section.
For a deeper companion read on this topic, see our recommended editorial guide.
The objection handler page: scripts, not bullets
The single most-used page of a competitive analysis is the objection handler. It should be structured as a short script, not a bullet list. For each of the top three objections each competitor raises against you, write the objection in the buyer's voice, the recommended response in the AE's voice, and the optional supporting proof point. Scripts work because AEs can adopt them verbatim under the pressure of a live call; bullet lists do not, because they require improvisation in the moment.
Refresh on a real cadence: quarterly, not on a vague trigger
Competitive analyses rot quickly. The discipline that keeps them alive is a quarterly refresh tied to the product roadmap and the win/loss data, with a clear owner and a published changelog. The changelog matters because it tells the field what is new since the last refresh, so they do not have to re-read the whole document to find the changes. The refresh should be timeboxed to two weeks per quarter, with a single output: an updated deck and a changelog email to the field. Without that cadence, the analysis becomes a museum piece within six months.
Working through this with your team? Our recommended workshop facilitation guide has a battle-tested run-of-show.
Templates that pair with this guide
The templates below are pre-structured around the playbook in this guide. Each one ships in both Google Slides and PowerPoint, and the master grid is set up for the slide-by-slide pacing the guide recommends.