Sales

Free competitive sales battlecard builder

Name: Sales Battlecard Builder
Author: Charles Summers

By Charles Summers · Updated 8 August 2026 · Free, no signup

Short answer

This builds a competitive battlecard from your genuine advantage and theirs, classifying both onto an eight-axis library where every strength carries a structural cost. You get where you win, where you honestly lose, landmine questions that ask the buyer to verify a fact rather than making a claim, the traps the competitor will set from their own strength, and explicit walk-away rules. Deal type changes the card completely, because displacement, greenfield and renewal defence are three different fights with different deadlines and different definitions of a win.

Use the sales battlecard builder

What does this tool actually do?

It runs entirely in your browser. Nothing you type is sent to a server, no account is required, and there is no usage limit, because there is no cost per run to control.

A card that never loses gets ignored after the first deal

The only asset a battlecard has is that reps believe it. That belief survives exactly one meeting in which a buyer names a real strength of the competitor that the card does not mention, because at that moment the rep learns two things: the card is incomplete, and they are the one standing in front of the customer with nothing to say. After that they stop reading it, and the version marketing keeps updating is a document nobody opens.

So every card needs a section naming the buyer who should choose the competitor, and it should be near the top rather than buried. The commercial argument for this is not fairness, it is throughput. Reps who can identify a lost deal in week one instead of week nine get those weeks back, and a quarter has about six such weeks in it hidden inside deals everybody already suspected. Sales leaders tend to underrate this because time returned is invisible in the pipeline report while a deal removed from it is very visible indeed.

The other reason is what saying it does in the room. Buyers already know the competitor is better at something, because the competitor has been telling them for weeks. A vendor who names it first buys credibility that transfers to every other claim on the card, and the alternative, a rep insisting they win on all eight axes, gets everything else discounted too. There is a version of this that works in one sentence: name the case where they are the better answer, define it narrowly and accurately, then explain what makes this particular buyer not that case.

Every advantage is a trade-off, and the trade-off is where the questions live

Competitive strengths are not free-standing. They are positions on a curve, and the position implies what was given up to get there. Breadth is bought with depth and, in acquisitive vendors, with multiple underlying data models that surface as separate admin consoles and inconsistent permissions. Low price is bought with support ratio, so the answer arrives in a queue. Ease of use is bought with a configurability ceiling that nobody hits in a pilot and everyone hits in month eight. Deep specialisation is bought with adjacency gaps, which appear the moment the buyer's scope widens by one team.

This is what makes landmine questions work, and it is also what separates a good one from the kind that damages you. A landmine question asks the buyer to verify a fact with the other vendor. It contains no claim, so it cannot be argued with, and the buyer hears it as diligence rather than as attack. "Ask them which of those modules run on the same permissions model and when each was acquired" is checkable, specific, and impossible to answer smoothly if the answer is bad. "They are not really one platform" is a claim, it invites a rebuttal you will not be present for, and it makes you the vendor who talks about competitors.

The test for whether a landmine is worth planting is whether you would be comfortable if the competitor heard you plant it. Anything that fails that test tends to come back, because buyers repeat questions verbatim and vendors compare notes more than reps expect. The strongest ones are drawn from the competitor's own published material: their pricing page, their documentation, their release notes, their job adverts. A question that can be answered by reading their own website carries no risk to you and considerable risk to them.

Displacement, greenfield and renewal defence are three different games

In a displacement, your opponent is not the competitor's product, it is the switching cost plus the person who chose the incumbent and is still employed. The only real deadline in the deal is the incumbent contract's renewal date, and everything sequences backwards from it: enter roughly a quarter before, because inside the last thirty days the buyer takes the path of least resistance and auto-renews. Attacking the incumbent directly attacks the buyer's past decision, so aim at the seam instead, meaning the workaround, the export, the spreadsheet that reconciles two systems, the thing somebody does manually every month and has stopped mentioning.

In greenfield, the battlefield is the criteria document, and it is usually decided before you know a deal exists. Whoever shapes the requirements list has already won most of the argument, because every subsequent conversation is scored against a rubric written in one vendor's vocabulary. The diagnostic is blunt: read the criteria and count how many are phrased as capabilities only one vendor leads on. If the list reads like a competitor's feature page, you are responding to their proposal, and your options are to reframe the criteria openly or to spend six weeks losing politely.

Renewal defence is the one most teams handle worst, because it is not a sales problem at the point it becomes visible. An incumbent facing a competitive evaluation from their own customer has already lost the relationship; the buyer is now comparing a vendor they know the flaws of against a vendor whose flaws are still hidden, which is a structurally unfavourable comparison. The defence is built in months two and three of the contract through documented value, named users, and a quarterly record of outcomes. At renewal itself the useful moves are narrow: get the real reason from someone other than the person running the process, fix what can be fixed inside two weeks, and decline to compete on a feature checklist written by the challenger.

Where the content comes from and how fast it rots

Most battlecard content is written from internal opinion and it shows. The better sources are all public and all dated. A competitor's pricing page tells you what they will discount and what they have decided to make free. Their documentation tells you what is genuinely configurable rather than what is on the slide. Their release notes tell you what they have been fixing, which is a map of complaints. Their job adverts tell you where they are investing eighteen months out, and a run of hiring in a category they claim to already lead is informative. Review sites are useful mainly as a delta: not the star rating, but what the one-star reviews of the last two quarters have in common.

The most valuable source is the deal you lost, from someone other than your own rep. Loss reasons recorded in a CRM systematically over-report price, because it is the reason a buyer gives that ends the conversation politely and the reason a rep can report without implying anything about their own performance. A short interview with the buyer, ideally by someone not on the deal, produces a different distribution, usually weighted towards fit, perceived risk, and the internal politics of who sponsored what.

Then keep it short and keep it current. A card is read in the ninety seconds before a call while the invite is on screen, so anything longer than one screen is decoration. Pricing and packaging move quarterly at most vendors, so a card older than a quarter is a liability rather than an aid, and the failure mode is specific: a rep quotes an old competitor price, the buyer corrects them from the website, and everything else on the card is now suspect. Finally, never write anything on a card you would not want screenshotted, and never let one leave your company. Comparative claims you cannot evidence are a legal problem in several markets, and a leaked card is worth more to your competitor than any research they could commission.

Numbers worth knowing

Metric	Typical	What it means
Win rate by deal type against one competitor	measure separately, they differ by a lot	Displacement, greenfield and defence commonly sit tens of points apart for the same pairing. A blended competitive win rate averages three different games and directs coaching at none of them.
Deals where the competitor wrote the criteria	near unwinnable without a reframe	Read the requirements list and count how many are phrased as capabilities one vendor leads on. If most are, you are responding to their proposal under your own logo.
Useful battlecard length	one screen	It is read in the ninety seconds before a call. Anything past a screen is reference material, which is a different document with a different job.
Refresh cadence	quarterly, or when their pricing page changes	Pricing and packaging move fastest. A rep quoting a stale competitor price gets corrected by the buyer, and every other line on the card is then discounted.
Loss reasons in the CRM versus from the buyer	they disagree systematically	Price is over-reported internally because it is the polite exit line and the reason that implicates nobody. Buyer interviews shift the weight towards fit, risk and internal sponsorship.

Mistakes that quietly cost you results

Writing a card on which you win every category: It survives until the first meeting where a buyer names a real competitor strength, then the rep stops trusting the whole document. Name the buyer who should choose them, near the top, and define that case narrowly enough to be useful.
Arming reps with claims instead of questions: A claim gets rebutted in a meeting you are not in, and it marks you as the vendor who talks about competitors. Give them questions the buyer can verify from the other vendor's own documentation, which cannot be argued with and read as diligence.
Attacking the incumbent in a displacement deal: Somebody in the room chose it and is now defending a decision rather than evaluating yours. Aim at the seam instead: the workaround, the manual reconciliation, the export that happens every month and has stopped being mentioned.
Entering a displacement deal in the last month of their contract: Inside thirty days the buyer takes the path of least resistance and auto-renews, whatever they say about being open. Get the renewal date early and plan re-entry about a quarter before it, which is when the evaluation is genuinely open.
Defending a renewal by matching the challenger's feature checklist: The checklist was written by them and scores their strengths. You will lose it item by item while the actual issue, a value story nobody documented for eleven months, goes unaddressed. Get the real reason from someone other than the process owner.

What does the output look like?

This is the exact output the tool produces from the example inputs. It is generated by the same code that runs when you click the button, so what you see here is what you get.

BATTLECARD: a purpose-built field service scheduler versus a broad ERP suite with a scheduling module Deal type: Displacement, they are the incumbent Your axis: Depth and specialisation | Their axis: Breadth, one vendor for everything THE CLOCK The only real deadline is their contract renewal date. Get it in the first two calls and sequence everything backwards from it, entering about a quarter ahead. Inside the last thirty days the buyer takes the path of least resistance and renews, whatever they said in October. OPENING MOVE Find the seam, not the flaw. Ask what has been built or worked around to make the incumbent do this, which export runs every month, and which spreadsheet reconciles two systems. The person who chose the incumbent is in the room and is defending a decision, so the incumbent is never the target. WHERE YOU WIN Stated advantage: purpose-built depth for engineer routing, live in three weeks That wins with buyers for whom this workflow is the business rather than an overhead, and teams that have already outgrown a general tool and can name the exact point where it stopped. Qualify for it directly. If none of those descriptions fits the buyer in front of you, your advantage is real and irrelevant, which is the more expensive of the two ways to lose. WHERE YOU LOSE Their advantage: one vendor for the whole back office, already in the stack That wins with buyers with a consolidation mandate from above, small IT teams counting vendors rather than capabilities, and anyone who has just been through a painful integration project. You do not out-argue this. You either narrow the evaluation so it is not the deciding criterion, or you accept the deal is theirs. WHEN THEY ARE GENUINELY THE BETTER ANSWER Say it, in one sentence, early: if the deciding factor is breadth, one vendor for everything, a broad ERP suite with a scheduling module is the stronger choice and you should take it seriously. Then define the case narrowly and explain what makes this buyer different from it. Buyers already know their strength; naming it first is what makes the rest of your card believable, and a rep who claims to win on every axis gets everything discounted at once. It also returns weeks: a deal identified as lost in week one instead of week nine is several selling days recovered, and there are a handful of those in every quarter. TRAPS TO SET (questions, not claims) 1. Ask which of those modules share one permissions model and one audit log, and which year each was originally acquired. 2. Ask them to price the second year, including anything that is currently discounted, bundled or waived for year one. 3. Ask which parts of the demo were configured for this call and which are how it ships by default. 4. Ask for a reference at the same size, in the same industry, who went live in the last twelve months, and who does the same thing you are proposing. 5. Ask what the exit terms are: notice period, data export format, and what happens to your data ninety days after cancellation. Each of these asks the buyer to verify a fact with the other vendor. There is no claim in them, so there is nothing to rebut in a meeting you are not in, and the buyer hears diligence rather than mudslinging. TRAPS THEY WILL SET 1. They will reframe the decision as vendor consolidation rather than capability, so the comparison becomes your one product against their entire estate. 2. The structural cost of their own strength is depth in any single module, and in acquisitive vendors, several underlying data models that surface as separate admin consoles and inconsistent permissions. Expect that subject to be steered away from, and plant the question above rather than raising it yourself. 3. Whatever they are weakest on will arrive as a mandatory requirement in the criteria document rather than as an argument, because a requirement does not have to be defended. WALK AWAY WHEN 1. They renewed within the last three months and the contract has no break clause. 2. Nobody can name a workaround, which means the pain is theoretical and the switching cost is not. 3. The person who selected the incumbent still owns the budget and has not personally raised a problem. 4. The stated driver is price alone. Incumbents almost always match on price at renewal, and you will have spent the quarter setting up their discount. A card with no walk-away rules produces reps who work every deal to the end of the quarter. The rules are the point: they convert a judgement call made under pressure into a decision made in advance. MAINTENANCE Rebuild this when their pricing page changes, and at minimum every quarter. Keep it to one screen, because it is read in the ninety seconds before a call. Never send it outside the company, and never make a comparative claim you cannot evidence from their own published material.

Frequently asked questions

Why does the battlecard have to name deals I should lose?

Two reasons, and neither is about fairness. The first is throughput: a rep who identifies an unwinnable deal in week one instead of week nine gets eight weeks back, and there are several of those hidden in every quarter. The second is credibility in the room. The buyer already knows what the competitor is good at, because the competitor has been telling them. Naming it first makes every other claim on your card more believable, while insisting you win everything gets all of it discounted at once.

What is a landmine question and why is it better than a talking point?

It is a question you leave with the buyer to ask the other vendor, containing no claim of your own. Because there is nothing to rebut, the competitor has to answer the substance in a meeting where you are not present and cannot be blamed for the framing. Buyers hear it as diligence rather than as attack. The best ones are answerable from the competitor's own pricing page, documentation or release notes, which makes them zero-risk to you and awkward for them.

How does deal type change the card?

Completely. In displacement the deadline is the incumbent's renewal date and the enemy is switching cost, so you enter about a quarter before renewal and aim at workarounds rather than at the product. In greenfield the fight is over the criteria document, which is usually decided before you are involved. In renewal defence you are the incumbent, the comparison is structurally against you because your flaws are known and theirs are not, and the useful moves are narrow and mostly happened months earlier.

Where should the content come from?

Public and dated sources beat internal opinion every time: their pricing page for what they discount and what they made free, their documentation for what is genuinely configurable, their release notes as a map of what they have been fixing, their job adverts for where they are investing. Then win-loss interviews conducted by someone who was not on the deal, because CRM loss reasons over-report price for the simple reason that it is the polite answer that implicates nobody.

How often should a battlecard be updated?

At least quarterly, and immediately when the competitor changes pricing or packaging, which is the fastest-moving part. The specific failure is a rep quoting a stale price, the buyer correcting them from the website, and every other line on the card becoming suspect for the rest of the deal. Keep it to one screen so that updating it is cheap enough to actually happen.

Related free tools

Some links on this site are affiliate links, which means Hacking Demand may earn a commission if you buy through them at no extra cost to you. This does not influence which tools are listed. The tools on this page are free and have no affiliate relationship of any kind.