Worked examples

Sales battlecard examples for SaaS competitive deals.

A useful battlecard helps a rep decide what to ask, what they can support, and what to prove next. These three examples show how the card changes when the buyer's concern changes.

By Case & Contrast · Published October 1, 2026

What belongs on a deal-specific battlecard?

Keep the immediate guidance short: buyer context, decision criterion, supported position, discovery questions, objection response, and the next proof step. Put detailed source notes behind it. A list of competitor features is background; the card must connect those facts to this buyer's decision.

Use the editable eight-section sales battlecard template to record the full context, competitor snapshot, proof, and source control. The examples below show how to fill the most decision-sensitive parts without turning assumptions into sales claims.

1. The competitor is cheaper

A regional operations team is comparing Northstar Analytics with SignalFrame before a reporting rollout. In this fictional exercise, the buyer supplies annual subscription quotes of $24,000 and $18,000. Both quotes still need a scope review.

Buyer's decision criterion: Can managers produce the agreed weekly report, and what will each option cost to implement and operate?
Recommended position: Acknowledge the $6,000 subscription difference. Compare the same users, usage, implementation work, support, and reporting workflow before claiming that either option costs less overall.

Discovery questions

Do both quotes cover the same users, usage limits, support, and contract period?
Who will configure and maintain the weekly report in each option?
Is subscription price the deciding factor, or is there an acceptable budget for a better workflow?

An objection response the rep can adapt

“Their subscription quote is lower. Before asking you to pay more, I would like to compare what each quote includes and test the reporting task your managers need. If the options meet the same requirements at a lower total cost, that matters.”

Proof plan and next owner

The rep gathers the two authorized proposals. The buyer defines one reporting task, and the solutions lead demonstrates Northstar against it. The buyer asks SignalFrame to demonstrate the same task. Record any additional fees and remaining assumptions before the proposal review.

2. The buyer already uses another vendor

A multi-location operator already uses SignalFrame. Its finance lead is considering Northstar because the current monthly review is difficult to prepare, but the operations lead is concerned about switching.

Buyer's decision criterion: Would the reporting improvement justify migration effort, disruption, and the risk of losing existing workflows?
Recommended position: Start with what the current system does well and the specific unresolved problem. Compare fixing the existing setup with changing vendors. Do not treat dissatisfaction with one report as permission to replace the entire system.

Discovery questions

Which current workflows must keep working during and after a change?
What has your team already tried to improve the monthly review?
When does the contract renew, and who owns data export, migration, and sign-off?

An objection response the rep can adapt

“Staying with a familiar system may be the right decision. Could we isolate the reporting problem and test whether we address it? We should also compare the work of improving your current setup with the work of moving.”

Proof plan and next owner

The buyer documents the problem and the workflows that must be preserved. The implementation lead reviews an authorized export and maps what could migrate, what requires manual work, and what is still unknown. Agree on a limited demonstration and acceptance criteria before discussing a replacement timetable.

3. The competitor appears to have a better integration

A finance team says SignalFrame advertises a connector for its accounting system. Northstar’s rep believes an API-based workflow might cover the requirement, but the actual data flow has not been reviewed.

Buyer's decision criterion: Can the required records move securely, in the correct direction and frequency, with an acceptable support burden?
Recommended position: Treat the advertised connector as a lead to investigate. Define the required workflow and verify both options. A connector logo, an API, and a supported end-to-end workflow are different claims.

Discovery questions

Which records and fields must move, in which direction, and how often?
Which system editions, authentication requirements, and permissions apply?
Who handles failed transfers, mapping changes, implementation, and ongoing support?

An objection response the rep can adapt

“That connector could be an advantage. Let’s write down the exact workflow and verify what it supports. I also need our technical team to confirm whether our approach meets the requirement today, including who would maintain it.”

Proof plan and next owner

The technical owner reviews current documentation for the relevant editions, then tests a permitted sample workflow with agreed success criteria. The rep records supported behavior, exclusions, setup effort, and the support owner. If Northstar cannot meet a must-have requirement, mark the gap clearly before the next sales call.

Turn an example into a card for your own deal

Replace the scenario with authorized deal context. Name the buyer's requirement, the alternative, the next conversation, and the decision owner. Remove any illustrative figures.
Check each material claim. Link current documentation or authorized proposals, record the date and relevant edition, and separate what was observed from what the buyer said or your team inferred.
Give uncertainty a next step. For an unknown capability, write the question, verification owner, and deadline. Do not fill a blank with a favorable guess.
Make the response usable. Keep the recommended answer easy to scan, then link the source appendix. Agree on the proof needed before the next call.

For a complete filled-in format, open the editable fictional battlecard example. For a broader view of the deliverable, see the public Competitive Deal Kit sample PDF. The competitor-objection guide explains how to move from the buyer's first objection to a verifiable next step.

When is the free template enough?

Use it when your team already has reliable evidence and someone can turn it into guidance for the opportunity. If the research, positioning, and proof plan still need to be built around a named competitor and an active deal, review the $500 sales battlecard service. It covers one competitor and one opportunity, with delivery within three business days after cleared payment and completed intake. Fit is confirmed before invoicing.

Need the research done for a live deal?

Build the card around your buyer's decision.

See the sample, then tell us which competitor is in the opportunity and what your team needs to verify. We confirm fit before invoicing.

Check fit for the $500 kit