The Closer Mindset Prepare My Next Sales Meeting Free

Competitive selling · Battlecard example

A sales battlecard should help you win the next decision.

A feature comparison tells you what is different. A useful competitive battlecard tells you why that difference matters to this buyer—and what to do in the next meeting.

  • For B2B software sellers competing against an incumbent.
  • 7 minute practical guide

What a battlecard is for

Build for the deal, not the competitor's feature list.

Walk into a competitive meeting with a point of view: which business problem matters most, where the current approach falls short and how your solution handles that work differently. A useful battlecard gives you a clear opening, questions that uncover a reason to change and a buyer commitment to ask for.

TemplateA practical sales battlecard template: buyer problem → commercial consequence → incumbent advantage → differentiated approach → objection response → buyer commitment. Keep the format; rewrite the talking points around the deal in front of you.

Worked example

Win the onboarding workflow, not a suite replacement.

Illustrative B2B software scenario. The company, products and buying situation are fictional.

  1. Situation

    A US B2B SaaS company's operations director uses an established work-management suite. Enterprise onboarding crosses Sales, Security and Implementation, but requests still arrive through email and chat. Recent launches slipped while teams chased approvals and ownership. The suite renews in 90 days, ahead of a larger onboarding wave.

  2. Buyer stakes

    For this buyer, billing begins at go-live. Slipped launches delay first invoices, consume implementation capacity and leave Customer Success explaining broken commitments. The director needs a credible way to handle more launches without adding another coordinator. That connects the workflow discussion to revenue timing and capacity, not just tidier task lists.

  3. Incumbent strengths

    The suite is the company standard: broad project coverage, existing integrations, familiar dashboards and trained users. IT has approved it, and its cost is already in the budget. The buyer can also configure its automation. Your competitor is selling continuity and consolidation, not just features.

  4. Alternative value

    Your specialist product offers a ready-to-run intake workflow: each request gets an owner and deadline, exceptions escalate and the onboarding lead sees stalled handoffs in one view. Demonstrate the Sales-to-Implementation handoff while keeping project work in the existing suite. Compete on earlier visibility and less coordination work, rather than a bigger feature catalogue.

  5. Talking point

    You're not looking for another task board. You need signed customers to reach go-live without requests getting lost between teams. Keep the suite for project work; use our intake workflow to give launch-blocking requests an owner and an escalation path before they put the date at risk.

Scenario questions

Four questions to uncover a reason to change.

  1. Q01

    Which recent launch slipped furthest, and where did ownership break down?

    Why ask it
    Find the costly handoff your product can address, rather than collecting general complaints.
    Follow up
    Walk through that request with the director: who received it, who chased it and when the delay became visible.
  2. Q02

    Do stalled Security and Implementation requests reach you before or after the go-live date is at risk?

    Why ask it
    Expose the difference between tracking tasks and intervening early enough to protect a launch.
    Follow up
    Show how an owner, deadline and escalation would change that same request's path.
  3. Q03

    What does a delayed go-live change for first billing, the expansion plan and the customer relationship?

    Why ask it
    Connect the workflow gap to consequences the CRO and finance team care about.
    Follow up
    Ask which consequence matters most this quarter, then use it to frame the business case.
  4. Q04

    With renewal 90 days away, who needs to see what result to back a focused workflow rollout?

    Why ask it
    Identify the decision team, timing and buying criteria while there is still time to act.
    Follow up
    Get the implementation lead and IT administrator into the next meeting; agree what they need to see.

Scenario objections

  • Buyer saysThe suite can probably do this.

    You respondIt has automation, absolutely. The question is how quickly your team can get this handoff working while managing the next launch wave. Let's run one recent request through your current setup and our ready-to-run workflow, then compare owner visibility, escalation and the admin work involved.

  • Buyer saysWe have already invested in the rollout.

    You respondExactly—and we can build on that. Leave project management and reporting in the suite. Focus this conversation on the intake gap that's delaying launches. Could your implementation lead join us to map that handoff and see how this fits alongside the rollout?

Next-step strategy

Leave with a workshop and a decision path.

ProposeBefore the call ends, book a 45-minute workflow workshop this week with the operations director, implementation lead and IT administrator. Ask the director to bring two delayed-launch requests. Map one through today's process, then demonstrate your intake and escalation flow. Agree on time to an accepted owner, overdue unowned requests and rollout effort as evaluation measures. Send a one-page success plan that day with an owner for each action, and book the decision meeting ahead of renewal.
  1. Champion's takeaway

    Give your champion a decision story they can repeat internally: the launch delay costing the business, the handoff you will improve, the result the team will measure and the date for the next decision.

Incumbent positioning

Compete on the handoff that affects revenue.

  1. Build on the incumbent investment.

    Open by acknowledging the suite's reach and adoption. Make your role specific: keep project management there, improve how launch-blocking requests enter the process and reach an accountable owner. This gives the buyer a focused change to sponsor.

  2. Make the difference visible in their work.

    Use a delayed request from their team, not a generic demo. Show who receives it, how a missed deadline escalates and what the onboarding lead sees. Tie those moments to fewer chases and earlier intervention before a launch slips.

  3. Give the buyer a reason to act this quarter.

    Connect the renewal window and upcoming launch volume to delayed billing and team capacity. Agree on the rollout effort with IT, then equip your champion to compare that effort with the cost of leaving the handoff unchanged.

Competitive objections

Answer the concern. Advance the conversation.

  • Buyer saysWe're happy with our current provider.

    You respondGood—let's keep what's working. You mentioned launches getting held up between Sales and Implementation. That's the part I'd focus on. I'll show you how we handle that handoff alongside your suite, using one of those delayed launches as the example.

    IntentSeparate satisfaction with the provider from the specific business problem you can solve.

  • Buyer saysYour competitor has more features.

    You respondThey cover a lot of ground. For this decision, you need requests owned sooner, exceptions escalated and fewer people chasing updates. Let's put your must-haves on one page and walk the same onboarding request through both approaches. You'll see the workflow and admin effort side by side.

    IntentMove the comparison from total features to the work and outcome driving this purchase.

  • Buyer saysSwitching would be too difficult.

    You respondA company-wide switch would be a big project. I'm proposing a smaller first step: keep the suite and focus on one intake workflow. Let's bring your IT administrator in to map the integration, team training and rollout effort, then put dates and owners against that plan.

    IntentTurn a broad switching concern into a manageable implementation conversation with the right people.

Competitive strategy in TCM

Turn competitive intelligence into a meeting plan.

A static battlecard gives every rep the same competitor notes. TCM helps you prepare for the buyer and meeting in front of you. Provide your prospect, product or solution, meeting objective and competitor context to get meeting-specific preparation—not just another feature grid to memorize.

TCM generates meeting-specific preparation from the context you provide and available research. It is not a continuously updated competitor database. Get 3 complete sales preparation reports free. No credit card required.

  1. Positioning

    Prepare a competitor angle around your solution and this buyer's situation, so you can open with a relevant point of view.

  2. Discovery questions

    Use meeting-specific questions to uncover the priority, commercial consequence and decision criteria behind the conversation.

  3. Value proposition

    Connect what you sell to why this prospect should care, rather than repeating a generic list of benefits.

  4. Objection handling

    Prepare responses for the likely pushback in this meeting and rehearse how each response moves the deal forward.

  5. Next steps

    Go in with a next action tied to your meeting objective, ready to turn a productive discussion into buyer commitment.

Your meeting, not a template

Your prospect. Your solution. Your competitive meeting.

3 free preparations. No credit card required.

Prepare My Next Sales Meeting Free