Imagine a mid-sized company that sells invoicing and collections software to Indian manufacturers. Call it Dhara Systems. In one year it meets a bigger rival, Orbit Finance, in 40 deals. In the first half of the previous year, Dhara won half of such contests. This year, it is winning three in ten: 12 wins instead of 20. A drop from 50% to 30% is a 40% fall in the win rate, and the sales director wants to know why.
The product team points to the battle card published last year. It is a table of sixty features with ticks and crosses, mostly ticks on Dhara’s side. It is fourteen pages long. Reps say they have never opened it. Both statements are true, and together they explain a lot.
What a battle card is for
A battle card is a short document that helps a salesperson handle one named competitor in a live deal. It is used in a specific moment: the prospect says “we are also looking at Orbit”, and the rep has about thirty seconds to respond sensibly and ten minutes before the next call to prepare. A document that serves that moment is quite different from a product comparison written for analysts.
Dhara’s director starts by looking at the 28 lost deals. Not by reading the loss reasons typed into the CRM, which tend to say “price” for nearly everything, but by listening to recordings and asking the reps and, where possible, the buyers. A pattern emerges. Orbit has begun bundling a payments-gateway integration into its entry package. Dhara’s reps keep arguing about reporting depth, which the buyers do not care about as much as getting paid faster. The ticks on the old card did not help, because the fight was on a different feature.
The rebuilt card
The new card fits on one page and answers a short list of questions, in the order a rep needs them.
- Who is Orbit, briefly? Size, typical customer, how it sells, what its reputation is. Only facts the team can support from public sources and from customers, not gossip.
- Where do we usually win, and where do we usually lose? This comes from the closed deals: for instance, Dhara wins when the buyer has multiple plants and complex tax set-ups, and loses when the buyer is a single-site business wanting the cheapest start.
- Why customers choose them, stated fairly. If Orbit’s payments bundle is genuinely attractive, the card says so. Reps who deny a competitor’s strengths lose credibility with buyers who have seen the demo.
- Questions that bring out our strengths without attacking. “How many plants will need to run on one set of rules in two years?” is better than “Orbit cannot handle multi-plant setups”, especially if the second statement might be out of date.
- Their likely objections to us, and honest answers.
- Landmines: topics where we are weak and the buyer may be primed to ask. Better that the rep expects the question than meets it cold.
- Proof: two or three customer references who switched from or compared against Orbit, with permission to name them.
- The date it was last checked, and who owns it.
The traps Dhara had to avoid
A temptation in this situation is to cut Orbit’s price attack with Dhara discounts. If the real issue is a bundled integration, discounting raises the cost of winning without fixing the reason deals are lost. It can be worth testing a matching offer in a few deals while the product team decides whether to build or partner, but it is a stopgap and should be tracked as one.
Another is writing claims about the competitor that are untrue or unprovable. Statements about a rival’s finances, security or customer losses that cannot be sourced can expose a company to complaints, and buyers dislike negative selling. In India there is also a body of law on misleading comparative advertising and unfair trade practices, so claims in written sales material should be accurate and verifiable. When unsure, state what your own product does, and let the buyer compare.
A third is gathering information from improper sources. If a customer offers you the rival’s confidential pricing, the answer is no. Public information, publicly available demos, customer feedback freely given about their own experience, and your own win and loss notes are enough.
Keeping it alive
A battle card ages quickly. Competitors change pricing, add features and shift positioning. The simplest practice is to have one person responsible for each main rival, a monthly ten-minute slot in a sales meeting where reps report what they heard, and a rule that a card older than six months is flagged as stale. Reps open a card that has been updated recently because they have learned it is accurate.
It is worth tracking the head-to-head win rate against each competitor over time, since that is the number Dhara’s director used to notice the problem. Small sample sizes matter, though: 40 deals can swing by a few wins from one large account, so a one-quarter change deserves attention, not alarm. The more useful signal is whether the loss pattern, read in the deals themselves, has a theme.
Figures and names in the examples are illustrative.
Leave a Reply