AI Product Marketing
Battlecard

How to sell against an incumbent competitor

To sell against an incumbent, the product your buyer already runs, build the battlecard around the switch. In our method, you never discredit a product the buyer owns. In our view, list why they chose it and name the cost of moving as your weakness. Ask discovery questions before the buyer frames the deal on that product's terms.

Last updated by Omair Dawood.

On this page

The five steps that change when the rival is already installed

The method is our own: the eleven-step battlecard skill behind our Battlecard tool, set out in full in How to build a competitive battlecard. It still needs its three inputs: a competitor profile no older than 30 days, your current messaging, and real objections from calls. Six steps run as written. These five change when the buyer already uses the rival, listed in the method's order.

  1. Step 3: list where they win, starting with why the buyer chose them. The method asks for things a buyer would really choose the rival for, each with a dated public source. It bans throwaways like "bigger brand". In our view, "they were there first" is a throwaway too. In our view, the real wins are the reasons buyers like this one choose them. Find them in public sources and date them.
  2. Step 5: count the move as your weakness. The method requires at least one honest weakness on your side, as plainly as theirs. In our view, against an installed product the first one is the switch: data to move, tools to reconnect, a team to retrain. Write it down before the buyer says it.
  3. Step 6: find the trap in the migration question. The method names three traps, including the question that makes you look evasive. In our view, against an incumbent it is the migration question: how long the move takes, and who does the work. The card says what to do instead. In our view, answer with the plan you really offer, or say you do not know yet.
  4. Step 7: answer "we already use it" without running it down. The method's rule is plain: never discredit a product the buyer already owns. The tool's own example objection is this case: "Coda already does docs and tables, why would we switch?" In our view, the honest answer says what changes for this buyer. The when-to-walk line says when staying put is the better call.
  5. Step 8: ask discovery questions first. The method's discovery questions surface the difference early, before the buyer has framed the deal on the competitor's terms. In our view, an incumbent's buyer has worked inside those terms for a while, so the first questions should ask what they work around today and what the current setup costs them to keep.

Steps 1, 2, 4, 9, 10 and 11 stay the same. They check freshness, write the one-line read, prove your wins, source every claim, fit one page and get a review.

Worked sample: HubSpot's switch-from-Salesforce page

In our view, real battlecards stay inside sales teams, so a public "switch from" page is the closest public copy of the claims a card draws on. HubSpot's page addresses buyers who already run Salesforce. One section says:

"Switching software can be intimidating"

"Especially if you’re migrating tons of data from Salesforce."

Read on . Source: HubSpot, Switching from Salesforce to HubSpot

The next paragraph says, in part:

"Our team consistently moves businesses from legacy software like Salesforce to HubSpot with minimal disruption by migrating in a phased approach while they have both systems turned on, leading to no loss in productivity."

Read on . Source: HubSpot, Switching from Salesforce to HubSpot

What the copy does well. In our reading, the heading names the fear a buyer brings to a switch, which is step 5 done in public. It answers with a method: a phased move, with both systems on. Further down, the page splits the work into four parts: records, integrations, automation and reports. Its questions section asks how long implementation takes, which is the step 6 trap, and answers it.

What a card could not take as written. "legacy software like Salesforce" labels a product the buyer owns. Step 7 keeps that label out of a seller's answers. In our view, a buyer page can use it, and a seller on a live call with a Salesforce admin cannot. "no loss in productivity" is HubSpot's claim. Under step 9, a card writes "HubSpot states" with the page and date, or marks it UNVERIFIED.

The fix. Here is the paragraph rewritten for a seller's card, using only the page's own claims:

Before: "Our team consistently moves businesses from legacy software like Salesforce to HubSpot with minimal disruption by migrating in a phased approach while they have both systems turned on, leading to no loss in productivity."

After: "We move teams off Salesforce in phases, with both systems running during the move."

And here are the card lines this page can fill. The other slots stay open, because only your calls and your numbers can fill them.

## Our honest weaknesses against them
- The move is work: records, integrations, automation and
  reports all move or get rebuilt (HubSpot's own migration plan,
  hubspot.com/switch-from-salesforce, checked 2026-10-14)

## Three traps
2. The question that makes us look evasive: how long the move
   takes and who does the work (HubSpot's FAQ asks it, checked
   2026-10-14). Instead: [the plan you really offer: needs your delivery team]

## The real objections
| [buyer's words: needs real calls] | [what changes for this buyer] | [when staying on Salesforce is the better call] |

Common mistakes

  • Calling their product "legacy" on the call. In our view, the buyer chose it and may have built it. The method never discredits a product the buyer already owns.
  • Leaving the switch off your own weaknesses. The method requires at least one honest weakness on your side. In our view, against an installed rival, the cost of moving is the first gap a buyer will catch.
  • Writing the objection yourself. "We already use X" is only on the card if a buyer said it on a real call. The method's reason: invented objections train sellers for a conversation nobody has.
  • No when-to-walk line. Every objection gets one. The method's reason: a card without it teaches reps to bluff.

Questions people ask

How do you outsell an incumbent?

In our method, you build a card for that one rival and start from its real strengths, each with a dated source. Then name at least one honest weakness; in our view, the first is the cost of switching. Answer "we already use it" honestly and ask your discovery questions early. Every objection also gets a when-to-walk line.

What tactics do you use to displace an entrenched incumbent in enterprise accounts?

Our method has no displacement tactic. It has a card for one rival and one buyer seat. When one person picks the tool and another signs, the method notes both and says which one the card is for. Then steps 3, 5 and 8 above do the work.

How do you break inertia in enterprise sales?

In our view, inertia is the installed product plus the cost of moving off it, and the method's step 8 aims at it: three to five discovery questions that surface the difference before the buyer frames the deal on the current tool's terms. In our view, an honest switch plan, as on HubSpot's page, then answers the fear of the move.

Sources

Build a card against the tool your buyer already uses

Name one rival, or leave the name and website blank and the tool picks the closest competitor, or the standard product buyers compare you to. It asks for your positioning or homepage copy, then two or more objections buyers actually say, one per line. The buyer seat is optional; skip it and the card speaks to the person who picks the tool. You get a dated profile of the competitor and where they win and where you win, honestly. You also get three traps, the real objections and questions to ask on the call. It takes about 3 minutes of typing.

Build a battlecard against the rival your buyer already runs