# How to respond to requests for competitor comparisons
> Stop sending generic feature charts on LinkedIn. Learn how to pivot comparison requests into outcome-based conversations that win more B2B deals.
- HTML: https://getkinlead.com/reply-to-prospect-asking-for-comparison-chart
- Markdown: https://getkinlead.com/reply-to-prospect-asking-for-comparison-chart.md

**Short answer:** Don't send a PDF chart when a prospect asks for a comparison on LinkedIn. Charts make you a commodity and invite the buyer to choose on price. Acknowledge the request and ask which outcomes they're comparing so you can answer the real question.

## Why you shouldn't send a feature matrix

A buyer asking for a competitor comparison is usually not asking for a spec sheet. They are trying to make a decision and want a shortcut. If you send a 20-row grid, you accept their framing: both tools are the same category, so the buyer can compare checkmarks and price.

That framing hurts you. A checkmark says a feature exists, not that it solves the buyer's problem. It also hides the work that makes a feature useful: setup, data, process, support. The buyer sees two yes marks and picks the cheaper one. You end up defending a price instead of explaining a result.

A prebuilt matrix also goes stale. It makes claims for every buyer, including the ones who don't care about that feature. It can be forwarded to procurement without your context. The person reading it sees a row that says no and kills your chances without asking why.

A generic chart shows you know the market, but it doesn't show you know the buyer. When you send a pre-made matrix, you tell the prospect your value is the same for everyone. That is rarely true, and the buyer can feel it.

The better move is to slow the request down by one question. You want the buyer to tell you what decision the comparison will support. That answer is worth more than any PDF.

**Feature-led reply**

- Here is our comparison PDF with 24 rows
- We have everything Acme has plus extra automation
- The checkmarks show we are stronger

**Outcome-led reply**

- Which decision are you trying to make this quarter?
- What happens today when you try to qualify a lead?
- I can compare how Acme handles that case and how we do

## The first response: shift from features to outcomes

Your first reply should acknowledge the request, then narrow it. Ask for the one detail that makes the comparison useful. Keep it to one question so the reply is easy to type on a phone.

Most prospects will answer. The answer tells you what to compare. If they say automation, ask what step is manual today. If they say reporting, ask who reads the report and what decision it changes. If they say price, ask what budget range they are working with and what has to be true for the tool to pay for itself.

You are changing the unit of comparison from features to outcomes. The buyer gets a useful answer, and you get to talk about the part of your product that matters to them. That is the whole move.

Keep the tone helpful. You are not withholding information. You are making sure the information fits their situation. Most buyers respect that because they have been sent too many generic decks already.

- **them:** Hey, we're looking at you and Acme. Can you send a comparison matrix or feature list?
- **you:** I can share how we differ from Acme. I don't keep a generic matrix because it tends to make every tool look the same. What are you trying to fix?
- **them:** Our reps spend too long qualifying leads. It's all manual research.
- **you:** That's the part worth comparing. Acme's setup usually means your team builds lists and checks profiles by hand. Our approach scores leads against a written profile first, so reps start with the ones that fit. Is the problem list building, or deciding who to contact first?
- **them:** Deciding who to contact first.

> The first reply should get one useful detail, not send a document. If you answer the matrix request with a matrix, you lose the chance to learn what the buyer is deciding.

## Handling the 'just send it' pushback

Some buyers will insist. They may be in procurement, they may need to show a boss two documents, or they may not want a call. You can still avoid a raw grid. Send a short summary that states where you win and where the competitor wins. Honesty makes the claims you do make more credible.

Write the summary for a person who will read it in two minutes. Use three to five lines. Name the buyer type each tool fits. Then ask for a short walkthrough of the one row that matters.

Do not invent a weakness. If you don't know the competitor's current pricing or roadmap, say so. Compare what you can support with evidence from your own product and from the buyer's stated goal.

Some buyers will still say no to a call. In that case, send the summary and one written question. You keep the conversation alive without turning it into a document dump.

1. **Send a curated summary.** Use three to five lines that describe differences in approach or result. Leave out button-level details.
2. **Name who each tool fits.** Say plainly when the competitor is the better choice, for example a large enterprise with a long implementation budget. Then say who you fit.
3. **Ask for a short walkthrough.** Request ten minutes to go through the one comparison that affects their decision. Bring the buyer's words back to them.

## Building a custom comparison for the win

Once the buyer tells you the goal, build a one-page comparison around it. Use their words in the left column. In the middle, describe how the competitor's approach handles that goal. On the right, describe how your approach handles it. Keep each cell to one sentence.

Compare the method behind each feature. If the goal is faster qualification, compare the steps a rep takes before they send a message. If the goal is safer outreach, compare how sends are paced and who controls the limits. If the goal is better replies, compare what information the first message uses.

The page should be short enough to read on a phone. It should also be specific enough that the buyer could forward it to a colleague without adding a paragraph of explanation. That is the test.

Fill the template with the buyer's language. A custom comparison with one weak row is better than a generic matrix with twenty. The weak row gives you something to fix on the call.

The one-page format matters. A long document invites skimming. A short page with the buyer's goal at the top gets read and forwarded.

| | Buyer goal | Competitor approach | Your approach |
| --- | --- | --- | --- |
| Cut lead research time | Reps build lists and check profiles by hand | Leads are scored against a written profile before outreach |
| Write a first message | Templates with a first name and company | The message opens with the trigger that made the person relevant |
| Keep outreach inside limits | Each rep tracks sends in a spreadsheet | Sends run inside daily limits and a time window |

```
Here is the comparison you asked for, based on [goal].

Acme's approach: [how it works]. That means [tradeoff for your team].

Our approach: [how it works]. That means [outcome you care about].

The part I would test with you is [specific scenario]. Worth a 10-minute call to see if it holds up?
```

## Doing this with Kinlead

Kinlead can find buyers who are already talking about your competitor. The Steal Customers agent watches competitor company pages and optional founder or employee profiles. It reads the comments on their recent posts and turns commenters who look like buyers into leads.

Each lead keeps the post URL, what the post was about and what the person commented. You can point a campaign at the lead group and open with the reason they became a lead instead of a generic comparison request. See [Steal Customers](/features/steal-customers) for the setup.

## Related

- [Steal customers feature](https://getkinlead.com/features/steal-customers.md)
- [AI LinkedIn outreach](https://getkinlead.com/features/ai-linkedin-outreach.md)
- [Book a demo](https://getkinlead.com/demo.md)

## Common questions

**Should I ever mention a competitor by name in a first message?**

Only when you know they are evaluating that tool or the buyer brings it up. Otherwise, name the problem and let them bring the competitor into the conversation.

**How do I handle a prospect who says a competitor is cheaper?**

Acknowledge the price and ask what the cheaper tool includes for their specific goal. Compare the cost of the workaround, not the sticker price.

**Is it okay to point out a competitor's weakness?**

Yes, if you can support it with a fact and tie it to the buyer's goal. Say what the competitor is designed for and where that design creates a tradeoff.

**What if they won't get on a call?**

Send the short summary and one question they can answer in writing. Keep the door open without dumping a full matrix.

[Create a Kinlead account](https://getkinlead.com/signup) or [book a call](https://getkinlead.com/demo) to talk through pricing and setup.
