How to respond when a prospect asks for a comparison chart
Stop sending a static comparison PDF when a prospect asks how you stack up. Here is how to answer on LinkedIn and turn the request into a conversation.
Get startedShort answer
Don't send a PDF or a screenshot of a feature matrix when a prospect asks for a comparison on LinkedIn. The file ends the conversation and lets them count checkmarks instead of understanding what they'd get. Acknowledge the request, ask what problem sent them looking, and offer a short call to cover the two or three differences that matter to them.
Why the chart usually backfires
A comparison chart feels like the safe answer. They asked for one, you have one, so you send it. What usually happens next is nothing. The file lands, they skim the rows, and the conversation between the two of you stops.
The chart also hands the framing to whoever built it. Every row is a claim, and the prospect has no way to check whether your "advanced reporting" means the same thing as theirs. They end up counting checkmarks, and a count is a poor way to choose software.
The bigger loss is information. Once they have the document, they have no reason to tell you which competitor is actually in the running or what set off the search. That detail is what would let you answer the question properly, and you've traded it for a PDF.
The file-first reply
- Sending a PDF with twenty rows of checkmarks
- Writing "here is our comparison guide, let me know if you have questions"
- Waiting for them to read it and come back
The question-first reply
- Naming the competitor back to them so they confirm the shortlist
- Asking what problem sent them looking in the first place
- Offering ten minutes to cover the two rows that actually matter
What to say in the first reply
Answer the question, then ask one about them. Two sentences is enough. Long replies read like a pitch and give them more rows to skim.
Say the competitor's name back. It shows you aren't dodging, and it gets them to confirm who else is on the shortlist. If they name a company you rarely see, that tells you something about the deal and how they buy.
Then ask what they're trying to fix, not what features they want. A feature request is a guess about a solution. The problem behind it is what you can work with.
Example
- Prospect
This looks interesting. Do you have a comparison chart against Acme? I want to see how you stack up on features.
- You
I can show you where we differ from Acme. So I point at the parts that matter to your team, are you trying to fix the automation side or the reporting side right now?
- Prospect
Reporting. Our current setup is a mess and I can't get clean numbers for the board.
- You
Then that's the part worth comparing. Acme handles reporting one way, and it tends to struggle once you need board-level numbers pulled from several sources. Do you have ten minutes on Tuesday to go through how we do it?
Turning the request into a call
Offer a short, specific slot. Ten minutes on Tuesday beats "happy to chat whenever suits". The call isn't a demo. It's a chance to find the one or two rows that matter and talk about those.
On the call, let them talk first. Ask what they've seen from the competitor that they liked. Whatever they name is the row you have to win, and now you know which one it is before you open your mouth.
If they won't take a call, don't force it. Answer in the chat with two real differences and a question about which one matters more. Some buyers need to see you be useful before they'll spend time.
- 1
Find the trigger
Ask what happened recently that made them start comparing tools. A new hire, a failed audit, a board meeting. The trigger tells you how urgent this is.
- 2
Isolate the row that matters
Get them to name the one or two things the competitor claims that they actually care about. Ignore the rest of the matrix, including the parts where you win easily.
- 3
Talk about the outcome
Describe what the buyer gets, not the menu option. If the competitor has something you lack, explain how your approach gets a similar result another way.
- 4
Check the shift
Ask whether that changes how they're weighing the two options. If it doesn't, you've learned the decision is being made on something else, usually price or an internal preference.
When they insist on the document
Some prospects will push back and ask you to just send the file. Often they're early in research and collecting documents, or they've dealt with a vendor who dodged every question and they expect the same.
Don't refuse flatly and don't apologize. Say what you'll do instead, then do it. A short answer that names a real difference is worth more than a matrix nobody reads twice.
Never apologize for not sending a chart. Say what you'll do instead, then do it in the same message.
Paste this job
Happy to. One thing first: those charts treat every row as equal, so they tend to mislead more than help. Give me two minutes on a call and I'll tell you exactly where we win against Acme and where we don't. Does Thursday morning work?
What belongs in a chart if you do send one
There is a point where a document helps. That's when the prospect has to explain the choice to someone who wasn't on the call. Build the chart for that job: a summary of the differences you already discussed, in the order they came up.
Keep it short enough to read in a lift. Five rows that matter beat thirty that don't, and the ones that matter are the ones they asked about.
Rows
- Part of the chart
- Only the differences you covered on the call
- What to put there
- Every feature either product happens to have
Wording
- Part of the chart
- Plain description of what the buyer gets
- What to put there
- Checkmarks and marketing labels
Your gaps
- Part of the chart
- The gap, plus how buyers usually work around it
- What to put there
- Silence, or a row that quietly disappears
Commercials
- Part of the chart
- A note that the number depends on their setup
- What to put there
- A figure that will be wrong in a month
Next step
- Part of the chart
- One line on what happens after they read it
- What to put there
- A generic contact page
Following up after the call
Send a two-line recap the same day. Name the row that mattered and what you said about it. That note is the comparison document they were actually after, written after you understood the question.
Keep the recap in the same thread where the conversation started. A document in an email is easy to lose. A message they can scroll back to is not.
If they go quiet, one follow-up that quotes their own words back. "You said the board needs clean numbers from three systems" works better than "just checking in". If that gets nothing, leave it alone.
Doing this with Kinlead
Most of these conversations start before the prospect asks for anything. The Steal Customers agent in Kinlead watches competitor company pages, plus founder or employee profiles you choose, and reads the comments on their recent posts. Commenters who look like buyers become leads, and each lead keeps the post URL, what the post was about and what they wrote.
That gives you a reason to open with something specific about the competitor instead of waiting for a chart request. You can read about Steal Customers or book a demo.
Frequently asked questions
Related
Get started with Kinlead
Prefer markdown? How to respond when a prospect asks for a comparison chart.md