How to Write Battle Cards for New Category Creation

When a deal goes sideways for a category-creation company, it almost never loses to another vendor. It loses to a spreadsheet, an internal tool the buyer already half-built, or the second half of a meeting that gets eaten by a procurement question nobody prepared for. By "category creation" we mean any product whose buyer can't yet name what it is — the noun is wrong, missing, or borrowed from an adjacent space. That single condition rewrites what a battle card has to do.

The standard battle-card template assumes a feature-by-feature war with a known competitor. Sales pulls up the card, finds the four bullets that beat Acme on integration depth, and runs the play. That motion is useless when the deal is actually a fight against the buyer's status quo, an in-house build, or a misnamed adjacent category the buyer mentally filed you under.

This piece walks through how to build a battle card for the deals you actually lose. The structure assumes you've done the positioning work — if you haven't, the card won't save you.

What the card has to defend against

There are no direct competitors in the conventional sense. There are four substitutes, and each one wins differently.

A category-creation battle card is really four cards stitched together. The good ones acknowledge that the rep doesn't know which substitute they're fighting until discovery is half done.

The card's first job: name the category

Before the rep can defend, the buyer has to file the product under the right noun. If the buyer thinks you're a project-management tool, they will compare you to project-management tools and ask why you cost three times as much. The battle card opens with the category claim, in the words the rep should actually say out loud.

The category claim isn't a tagline. It's the sentence the rep delivers in the first three minutes of discovery, before any feature comes up. If the buyer pushes back on the claim — "isn't this just CRM?" — the card needs the response ready.

Step-by-step: building the four-quadrant card

The order matters. Most teams write the response plays first because they feel productive. The discovery question — the thing that decides which response play to even use — gets bolted on last and is usually wrong.

The internal-build conversation

Internal builds deserve their own treatment because they're the loss most PMMs underprepare for. Engineering teams at growing SaaS companies are constantly building internal tools. Your category, by definition, looks build-able to someone who hasn't tried.

The internal-build response play has three honest moves. First, agree that the engineering team could build it — refusing this loses credibility for the rest of the call. Second, name the maintenance tax: the on-call rotation, the version upgrades, the new requirement six months in that breaks the original design. Third, surface the opportunity cost in the team's own language. If the engineering org's roadmap mentions any specific shipping goal, the build of your category trades against that goal directly.

The procurement defense

Procurement kills category-creation deals quietly. The buyer champions the product, the security review passes, and then the deal vanishes for a quarter because no one has a budget code for "the new thing."

The card needs three pieces here. The line-item reframe says which existing budget this consumes — usually the budget that funds the substitute the buyer is currently using. If the buyer is replacing a spreadsheet workflow that takes the analyst team thirty hours a week, the budget is the analyst team's loaded hourly cost, not "new software." The metric reframe ties the spend to a number the CFO already tracks. The reference reframe gives the procurement team a comparable purchase at a comparable company — not a logo wall, but a specific deal size and structure.

When the buyer mis-files you in an adjacent category

The hardest substitute is the adjacent vendor — the tool the buyer already pays for that does some fraction of your job. The buyer's procurement reflex is to ask why they need a new vendor when the existing one "kind of does this." The card response is not to argue feature depth. It's to argue scope.

The pattern is consistent: name what the adjacent vendor was actually built to do (be generous, not dismissive), name the second-order job your product owns that they don't, and offer the integration story so the buyer doesn't have to choose. Most adjacent-vendor objections collapse the moment the buyer realizes you're not asking them to rip out the incumbent.

How the card evolves

Category-creation battle cards are wrong on day one. They're written from positioning hypotheses, not from win/loss data, because there isn't enough win/loss data yet. The card has to be revisited on a fixed cadence as the deals come in.

A card that hasn't changed in six months is either a finished masterpiece or — far more likely — disconnected from the deals sales is actually running.

What sales needs to actually use it

The best battle card in the world fails if it lives in a fifteen-tab Notion doc no rep opens during a live call. Three habits separate the cards that get used from the ones that don't.

The template

Below is the working template — six fields per substitute, plus the procurement defense and category claim. Fill it once for your highest-volume substitute and pressure-test it against three real lost deals before rolling it out to the team.

What to do Monday

Pull the last ten closed-lost deals. Read the loss reasons in the CRM. Count how many list a named competitor. The number is almost always under three. The other seven are your battle card. Start with whichever substitute appears most — usually the status quo — and write one card. Don't write all four at once; you'll get the structure wrong and have to redo them.

The card will be wrong. Ship it anyway. The version sales actually uses on Tuesday is worth more than the version still in draft on Friday.