How to sell to a company that already uses a competitor

Selling against competitors in B2B can feel difficult when a prospect already uses a product in your category. They may have an established workflow, trained employees, an existing contract, and little appetite for changing something that works well enough.

That does not mean the opportunity is closed. It means the buyer needs a credible reason to consider an alternative.

Rather than criticising the incumbent or listing every feature your product offers, focus on understanding the customer's current experience, identifying an unmet need, and establishing whether a change would be worthwhile.

Understand why the company chose its current solution

Before trying to displace an incumbent, find out what the buyer values about it. Their current vendor was selected for a reason, even if that reason is no longer relevant.

A prospect may value ease of use, integration with existing systems, a familiar interface, customer support, or a particular capability. Understanding those priorities helps you avoid presenting an alternative that solves the wrong problem.

Start with questions such as:

• What originally led your team to choose the current solution?
• Which parts of the workflow work well today?
• What would you not want to lose if you changed tools?
• Has the team's needs changed since the original decision?
• Is there anything you still handle manually or outside the current platform?

These questions are not an invitation to interrogate the buyer about their vendor. Ask them naturally and focus on understanding the workflow.

You may discover that the incumbent is meeting the company's needs perfectly. If so, pushing for a replacement is unlikely to be productive. You may also uncover a gap worth exploring, such as a new requirement, an inefficient process, or a change in team size.

Look for a meaningful reason to change

A company rarely changes a familiar tool simply because another product has a longer feature list. Switching involves evaluation, implementation, training, internal coordination, and the risk that the new solution will create problems.

The potential benefit needs to justify that effort.

Look for evidence of a genuine reason to reconsider the current solution:

• An unmet requirement: The existing product does not support a capability the business now needs.
• A workflow problem: Employees rely on manual workarounds that create avoidable effort or inconsistency.
• A change in scale: The company has grown or changed its process, making the previous solution less suitable.
• A commercial concern: The current arrangement no longer fits the team's usage or budget.
• A new business priority: The company needs to achieve an outcome that was not important when it selected its existing vendor.
• A service or implementation gap: The buyer is struggling to get the support or adoption needed from the current solution.

Do not assume these problems exist because they would make your product easier to sell. Ask questions, listen to the answers, and confirm whether the issue is important enough to justify a conversation about alternatives.

Position your product around the gap, not every feature

Once you understand the buyer's situation, select the capabilities that directly address the identified problem. A competitive pitch should be specific enough that the prospect can see why it is relevant to them.

For example, imagine a fictional company that uses a sales platform but still spends significant time finding contact details manually. A competing solution that helps with contact enrichment may be relevant to that particular workflow.

The message should explain the connection:

• Current situation: The team spends time locating contact information outside its main sales process.
• Unmet need: Representatives want a more direct way to find the details required for outreach.
• Relevant capability: Your product can help find verified work emails and phone numbers for suitable prospects.
• Evaluation question: Does this capability address enough of the team's problem to justify adding or changing a tool?

This approach avoids claiming that one product is better at everything. It also gives the buyer a practical way to evaluate whether the difference matters.

If you need a framework for checking whether a potential account is worth approaching, read the five-minute prospecting test. Competitive outreach still depends on choosing accounts where a relevant problem may exist.

Handle switching costs honestly

Even when a buyer sees a potential benefit, they may hesitate because changing systems creates work. This is a legitimate concern, not necessarily an objection that can be overcome with better persuasion.

Explore the practical implications before recommending a switch.

• Data migration: What information would need to move, and in what format?
• Integrations: Which existing systems need to work with the new product?
• Training: How much time would employees need to become comfortable with the change?
• Process disruption: Could the transition interfere with important day-to-day work?
• Contract commitments: Are there existing commercial terms or renewal dates that affect the decision?
• Internal approval: Who needs to evaluate and approve the change?

Not every concern can be resolved immediately. If the prospect has a long contract remaining, it may make more sense to reconnect closer to renewal than to force an immediate evaluation.

Where appropriate, propose a limited evaluation of the relevant workflow. Agree on what the buyer wants to test, what evidence would be useful, and how they will assess the result. Do not promise that migration or implementation will be effortless unless you can support that claim.

Build a fair comparison instead of attacking the incumbent

Competitive selling loses credibility when it relies on vague claims about a rival's weaknesses. Buyers may have years of experience with their current solution and will recognise exaggeration.

A fair comparison should focus on factors that matter to the buyer:

• Which required capabilities are available in each product?
• How well does each option fit the current workflow?
• What are the total costs at the expected level of usage?
• Which integrations and export options are needed?
• What implementation and training effort is involved?
• What limitations or trade-offs should the buyer understand?

Use current, reliable product information when making specific claims about competitors. Features and prices change, so avoid relying on old comparison pages or assumptions based on a vendor's reputation.

Our article, prospiq vs Apollo: an honest comparison, illustrates the value of evaluating tools against actual requirements rather than treating a competitive comparison as a contest of broad claims.

Reach the right people in the buying process

A person who uses the incumbent every day may understand the workflow problems but lack authority to approve a change. A budget owner may control spending but have limited knowledge of the practical frustrations experienced by the team.

Identify the people who can help evaluate the problem and the decision. Depending on the purchase, that may include users, a team manager, procurement, finance, or technical stakeholders.

Ask the prospect who else should be involved rather than assuming that one conversation represents the whole company. When appropriate, help your contact explain the business case internally with a concise summary of the problem, potential benefit, costs, and evaluation criteria.

This is especially important for software purchases that affect several teams or require integration with existing systems. A convincing individual conversation may be only the beginning of the decision.

Know when to pursue the opportunity and when to move on

Not every competitor customer is a realistic prospect. Some are satisfied, some cannot switch yet, and some have no business reason to change.

A useful qualification process considers both fit and motivation. Is there a problem your product can solve? Does the buyer consider it important? Is there a plausible path to evaluating an alternative? Are the costs of change proportionate to the expected benefit?

If those conditions are absent, do not invent urgency. Respect the buyer's decision and move on, or agree on a suitable time to reconnect if they have indicated that circumstances may change.

Selling against competitors works best when you give buyers a clear way to assess whether a change makes sense. Understand what they have, uncover what they need, demonstrate a relevant difference, and be honest about the work involved. You do not have to prove that the incumbent is bad. You have to establish whether your solution is a better fit for this particular situation.

Start free with prospiq.