How to Write a Competitor Battlecard in a Google Doc

How do you build a battlecard your reps will actually open?

Keep it to one page per competitor, build it from real deal notes, and put it where reps already work. A shared Google Doc with a fixed structure is enough for most small teams. Fancy enablement tools can wait. What matters is that the content is honest, current, and quick to scan mid-call.

This tutorial is written for one situation: a B2B team with a few reps, no dedicated enablement person, and one or two competitors that come up in most deals. If you have a large sales org with a competitive intelligence team, you need more than this. If you are a founder still doing every call yourself, this is exactly the right size.

Many battlecards die because they were written once by marketing and never touched again. The approach below fixes that by making the document small, sourced from deals, and owned by a named person with a review rhythm.

What is a competitor battlecard and what should it not be?

A battlecard is a short reference that helps a rep handle a specific competitor in a live conversation. It covers when you win, when you lose, the questions to ask, and honest answers to common objections. It should not be a feature comparison table or a list of insults about the other product.

The difference matters because reps use battlecards under pressure. A buyer says they are also looking at a named competitor, and the rep has seconds to respond. A dense feature grid does not help in that moment. A clear sentence about where you are stronger, and a question that exposes the buyer's real need, does.

Avoid trash talk. Buyers can usually tell when a rep is attacking a rival, and it lowers trust. I take the same stance on public content, which I explained in writing a comparison page without trashing a competitor. Internal documents leak into calls, so write them as if the buyer might read them.

Step one: what do you gather before writing anything?

Gather evidence from closed deals first. Pull the last batch of deals where the competitor appeared, both won and lost, and read the notes, call recordings, and lost reasons. Talk to the reps who ran them. Write down exact buyer phrases about why they chose either product. That raw material becomes the card.

If your CRM tracks a competitor field and a lost reason, filter on both. If it does not, add those fields now, because the next version of the battlecard depends on them. My guide to building a lost deal reason report in HubSpot shows how to structure the reasons so they are usable rather than free text chaos.

Also read the competitor's own public pages: their homepage, pricing page, and recent product announcements. You are looking for how they position themselves in their own words, not for ammunition. Note the date you checked each page, because positioning and pricing change and the card must show when facts were last verified.

Step two: how do you set up the Google Doc structure?

Create one Google Doc per competitor inside a shared folder named Battlecards. Use the same headings in every doc so reps learn where to look. I use six sections: the one line summary, where you win, where you lose, questions to ask, objection answers, and proof. Add a last updated line at the top.

In Google Docs, use the built-in Heading styles for each section so the document outline in the left panel becomes a clickable table of contents. That lets a rep jump straight to objection answers during a call without scrolling. Keep the body text short, with each point written as one or two plain sentences.

Put the owner's name and the review date under the title. Set sharing so the whole sales team can comment but only the owner can edit. Comments become the feedback channel. A rep who hears a new objection on a call adds a comment, and the owner folds it in at the next review.

Step three: how do you write the win and loss sections honestly?

Write the situations, not the features. "Wins when the buyer needs the CRM sync to work without an admin" is useful. "Better integrations" is not. For losses, be equally specific: "Loses when the buyer already runs everything inside one suite and values a single invoice over flexibility."

Base each line on at least one real deal and note which one, using the deal name or ID in a comment rather than in the body text. This keeps the card credible to reps, who will ignore claims that do not match their experience. If you cannot find a deal that supports a line, cut the line.

The loss section is the most valuable part, and the part most teams skip. Knowing when you are likely to lose lets a rep qualify out early or reframe the deal before investing weeks. A rep who walks away from a bad fit deal in the first call saves more time than any objection script.

Step four: what questions and objection answers belong on the card?

Include three to five discovery questions that surface the needs where you are strong, and short answers to the objections reps hear most. Each answer should acknowledge the competitor's strength, then pivot to the buyer's situation. Write them as a rep would say them aloud, not as marketing copy.

Good questions are neutral but revealing. If you win on ease of setup, ask "who will own this day to day after launch, and how much time do they have?" The buyer's answer often makes the case for you. If you lose on breadth, ask early whether the buyer truly needs every module or just two.

For objection answers, keep a simple pattern: agree with what is true, add context, ask a question. For example, "That is fair, they do have more native modules. Most teams your size use two or three. Which ones matter most to you this year?" This keeps the rep credible and moves the conversation forward.

Step five: how do you add proof without overclaiming?

Add proof that a rep can share safely: a customer story that switched from the competitor, a relevant case study link, or a short quote approved for use. Only include claims you can back with something real. If a proof point is internal only, label it clearly so it is never sent to a buyer.

Avoid numbers you cannot source. A rep who quotes a made up performance difference and gets challenged loses the deal and their credibility. If you have a verified customer outcome, include it with the customer's permission and a link to the source. If you do not, describe the outcome qualitatively instead.

Facts about the competitor need the same care. If the card says their pricing starts at a certain level, add the date you checked and a link to their pricing page. Prices change, and an outdated claim used on a call damages trust. When in doubt, tell reps to point buyers to the competitor's own page.

Step six: how do you keep the battlecard current?

Assign one owner per card and set a recurring review, monthly for active competitors and quarterly for minor ones. At each review, read new comments, scan recent deals where the competitor appeared, and check their public pages for changes. Update the last updated date even if nothing changed, so reps know someone looked.

A simple automation helps. When a deal closes with a competitor field filled in, a workflow in your CRM or a Zapier step can post a message to the card owner with the deal link and outcome. That keeps fresh evidence flowing without anyone remembering to send it.

Retire cards that are no longer used. If a competitor has not appeared in deals for two quarters, archive the doc with a note. A folder full of stale cards teaches reps to distrust the whole set. A small set of current cards is far more valuable than a complete set of outdated ones.

What should you do next?

Pick the one competitor that appears most in your deals. Pull the last batch of won and lost deals involving them, read the notes, and talk to two reps. Then create the Google Doc with the six sections, fill each with lines backed by real deals, and share it with comment access.

Ask reps to use it on their next few calls and leave comments on what helped and what was missing. Review it after two weeks, tighten the language, and set the recurring review on your calendar. Only after the first card is working should you start the second.

If you want help connecting your CRM so deal outcomes and competitor data feed your battlecards automatically, reach out through pravinkumar.co. I build the websites and the automations behind them for lead generation, and sales enablement that stays current is a natural extension of that work.