How to Write Battle Cards for New Category Creation

The hardest battle card to write is the one with no competitor on it. When sales asks "who do we lose to?" and the honest answer is "spreadsheets, an intern, and the buyer's reluctance to admit the problem exists," the standard battle card template collapses. There's no logo to put in the header. No pricing grid to mock. No feature column to win.

That's the position of every PMM trying to create a category. The threat is real — deals stall, champions go silent, procurement asks for a comparison the rep can't produce — but it doesn't have a name. Sales gets handed a battle card that says "we have no direct competitors" and learns nothing useful for the next call.

In category creation, the competitor isn't a company. It's the buyer's current reality and the adjacent categories they'll mistake you for.

The three opponents in a category-creation deal

When there's no direct competitor, the rep is fighting on three fronts simultaneously, and most lose because they only prepare for one.

The status quo. Whatever the buyer does today — manually, badly, in a spreadsheet, with a half-built internal tool. This is the default winner of every category-creation deal. Doing nothing has zero implementation cost, zero political risk, and an existing line item.

The adjacent category. The closest established product the buyer might mistake you for. If you're building "AI-native positioning analysis," the adjacent category is brand strategy consulting, or marketing analytics platforms, or sales enablement tools. The buyer has heard of those. They'll try to file you under one and then complain you're missing features that category solves for.

The internal build. Especially in technical buyers. "Couldn't we just build this with [LLM API / our data warehouse / a contractor]?" This is the third opponent, and it's the one most battle cards ignore entirely.

A battle card for category creation has to defend against all three, and each requires a different play.

What the standard battle card gets wrong

Most battle card templates are built around a head-to-head frame: their logo, your logo, a feature grid, a price comparison, three objection-handlers. This works when the buyer has already decided they need a product in your category and is choosing between vendors. It fails completely when the buyer hasn't decided the category exists.

The category-creation rep has a different job in the call. They're not winning a bake-off — they're teaching the buyer to recognize a problem, name it, and accept that solving it requires something other than what they have today. The battle card has to support that conversation, not the bake-off conversation.

The category battle card structure

After auditing battle cards from fourteen companies attempting category creation in 2025 — six AI-native infrastructure plays, four developer tools, four go-to-market software — a structure emerges that the better cards share. It has five sections, in this order.

The play for each opponent

The middle section — the three opponents — is where most of the work happens. Each gets its own treatment.

Against the status quo

The status quo wins by being invisible. The buyer has been doing it this way long enough that the cost has become background noise. The rep's job is to make that cost legible.

The play is a quantification question, not a product demo. "How much time does your team spend on [specific task] in a typical month? What does that hour look like? What slips when it doesn't get done?" The card should give the rep three or four of these questions, ranked by which buyer persona they work best on.

Against the adjacent category

The adjacent category is the most dangerous opponent because it sounds plausible. The buyer hears your pitch, files you under "oh, that's like [established thing]," and then judges you against that thing's features and price. You lose by comparison to a product you weren't trying to be.

The play here is the explicit re-frame. The card should arm the rep with one sentence that names the adjacent category, acknowledges the surface similarity, and draws the line.

A worked example: "We're not a brand strategy agency. We're a positioning analyst. The difference: an agency runs a six-week project once a year. We run a continuous diagnostic across every page, deck, and pitch."

Against the internal build

This is the opponent the rep is least prepared for, because the buyer rarely raises it explicitly. It surfaces as silence after the demo, or as the technical evaluator going dark for two weeks, or as a procurement question about "build vs. buy."

The play is to surface it first. The card should give the rep permission — and a script — to name it: "A lot of teams in your situation consider building this internally. We've watched four do it. Here's what happened." Then a specific, honest account of why the build failed or stalled. Not a sales pitch about how hard it is. A story about a real team that tried and what they learned.

What goes on the card itself

A category battle card lives on one page. Two pages and the rep doesn't read it. The visual hierarchy matters as much as the content.

The maintenance cadence

Category-creation battle cards age faster than competitive ones, because the category itself is moving. The adjacent category you're contrasting with this quarter may have launched a feature next quarter that closes the gap. The status-quo workaround may have been displaced by a new manual tool. The internal-build calculus changes every time a major LLM provider drops API prices.

What to do Monday

Open your existing battle card — or your blank doc, if you don't have one — and write the problem statement section first, before you touch anything else. Two sentences. The buyer's language, not yours.

If you can't write those two sentences without using your product name, you don't have a battle card problem. You have a positioning problem, and the card will fail no matter how well you structure it.

If you can write them, send the draft to your top three reps before you design the rest of the card. Ask them one question: "Is this what the buyer says, or is this what we wish the buyer said?" Their answer is the entire card.