SaaS competitive battlecard template

Prepare a concise buyer-focused comparison with dated evidence, discovery questions and approved claims. This worksheet supports the broader b2b saas marketing plan.

The working template

A worked example

If one product supports a required deployment option and the other does not, ask about the buyer’s deployment constraints before presenting the difference.

The example is illustrative. It does not describe a measured customer result or create a promise about your own outcomes. Use it to understand the level of specificity the document needs.

How to complete the worksheet

1. Choose one project, account segment or decision. A document that attempts to cover the whole company usually hides important differences.
2. Gather the evidence required by the fields above. Use approved customer research, current product information and the relevant business records.
3. Draft the answers with the person responsible for doing the work. Keep unresolved questions visible and assign a next action to each one.
4. Review the document with the people who depend on it. Confirm scope, responsibilities and any constraints before treating it as an operating agreement.
5. Save the version and review date. Update it when the underlying offer, process or customer evidence changes.

Review before sharing

Do not confuse an unverified absence in public documentation with proof that a competitor lacks a capability.

A useful working document makes disagreements visible while there is still time to resolve them. Ask a colleague to explain the intended decision from the filled-in version without additional narration. If they cannot identify the next step or the evidence behind it, revise the relevant field.

Remove confidential customer details from any public copy. Keep names, prices and results only when you have permission and can explain their context. An empty evidence field is a signal to investigate, not an invitation to supply a plausible-sounding number.

Continue the work

• How to Build a B2B SaaS Marketing Strategy
• How to Market to a B2B SaaS Buying Committee
• The B2B SaaS Marketing Funnel, Stage by Stage
• B2B SaaS Sales Cycle Length
• B2B SaaS Demand Generation Playbook

Find more templates and checklists for adjacent tasks.

Apply saas competitive battlecard template in a working review

Make a copy of the working file and complete one representative row before filling the entire document. Replace example values with evidence from the actual project. Add an owner and a review condition where the template calls for a decision. A blank marked unknown is more useful than an invented number that makes the file look finished.

For this topic, involve the account owner, customer champion and relevant implementation specialist and work from the buying-process map and current evaluation record. The relevant unit is one buying account with a specific workflow. State the question the review should resolve before choosing a chart, an asset or a tool. If participants disagree about the unit or scope, resolve that disagreement before combining their evidence.

Evidence to prepare

Distinguish the user, the commercial approver and the person who can block implementation. A contact can be enthusiastic without owning the budget or the required system access. Keep confirmed statements separate from inferred intent, and let the next step resolve an actual buyer question.

Two situations that can change the interpretation

When enterprise content cannot travel internally

A one-page decision brief can link to deeper evidence while preserving the actual scope and the buyer’s unresolved questions.

Use this check: Ask what each approver needs to know and whether the asset states assumptions, limitations and sources without narration. Do not remove material qualifications to make the document shorter.

The focused diagnostic guide provides the correction process and a working evidence sheet.

When security review starts after the buyer is ready

An early scope conversation can reveal that a questionnaire requires a specialist response rather than a generic trust-page link.

Use this check: Ask which review is required, who owns it and what verified material the vendor can provide. Marketing must not promise controls, certifications or contractual commitments outside verified scope.

The focused diagnostic guide provides the correction process and a working evidence sheet.

Record the decision and the limit

A champion may understand the product while still needing a security review and a data owner to participate. Sending another broad deck does not resolve those dependencies. A short acceptance exercise and a named owner for each requirement can make the decision more concrete.

Keep the conclusion beside the evidence that supports it. Record what the team will do, who owns the next action and which event or date will trigger a review. If the underlying definition, audience or product behavior changes, revisit the conclusion rather than assuming the old result still applies. A clear limit is useful information; it tells the next reader where additional investigation is required.

Use the complete topic collection for related methods and the category field guides when the product’s buying situation or implementation requirements change how the method should be applied.