You Can't Build a Battlecard in 30 Seconds

Every few months another tool shows up promising a battlecard from one URL in under a minute. Paste in a competitor's domain, wait a bit, and out comes a document: pricing, features, maybe a quote pulled off a review site. It looks like magic the first time you see it. It's also not the hard part of building a battlecard, and treating it like the hard part is why so many of these documents get generated once and never opened again.

What a fast battlecard actually contains

Run a competitor's homepage and pricing page through an LLM and you'll get back something that reads like research: a features table, some bullets on positioning, a price comparison. All of that is public. Anyone on the other side of the deal could pull up the same pricing page, and most prospects already have. A battlecard that stops at "here's what they say about themselves" is a worse version of the tab your rep could just open mid-call.

The part that takes longer than 30 seconds

What actually helps on a call is knowing why your last several deals against this specific competitor went the way they did. Was it price? A missing integration? A line in their deck that oversells a feature that doesn't quite work the way they claim? None of that is sitting on their website. It's sitting in your own CRM, in call notes, in the reason field someone filled out after a deal closed or slipped. A tool that only reads a competitor's public pages has no way to know any of it, because it was never public. It's yours.

We wrote before about how messy that data usually is, and why pulling a real pattern out of a hundred loosely-worded loss reasons takes more than a glance. That's the actual work. Scraping a pricing page is the easy part.

Why this matters more than it sounds like it should

A battlecard built entirely from public information can tell a rep what a competitor charges. It can't tell them the last three deals against that competitor were lost on implementation time, not price, so leading with a price comparison on the next call would be arguing the wrong point entirely. That's the gap between a document that sounds informed and one that actually changes how a call goes.

None of this makes the fast version useless. A quick pull of public pricing and hiring data is a fine starting point, and it beats a battlecard nobody's touched in a year. But it's a starting point, not the finished thing, and a tool promising the whole battlecard in 30 seconds is mostly promising the part that was never the bottleneck.

What we do instead

Ripplewatch still reads the public stuff: pricing pages, hiring, product changes. But every finding gets scored against your own win/loss history, not just against a competitor's marketing copy. A battlecard is more useful when "why we win" is actually built from deals you closed, not written by someone guessing what a rep might need on a Tuesday. If you're building one by hand right now, here's the template we'd start with.