Customers say “Another provider has a feature you don’t” for a reason. Here is what usually sits behind it, how to respond and what to avoid.
A missing feature is sometimes a deal-breaker and sometimes a tick-box nobody will use. The customer may have been shown it in a demo and remember it. Find out whether they need the outcome the feature produces, or only like it. Never claim you have something you do not.
Typical in: Software and SaaS
Pick the framework that fits the customer. The wording is an example direction, not a script: say it in your own words.
Ask what sits behind the objection, so you answer the real concern.
“Thank you for telling me. What would you use that feature for, and how often? I want to understand the result you need, because there may be another way to get there.”
Show you heard it, then ask an open question before you respond.
“You are right, we do not have that one, and I will not pretend otherwise. What I can do is show you how we handle the same task, and you can tell me whether that works for you. Fair?”
Check whether this is the only obstacle, so you do not answer one worry after another.
“If that feature were not a question, would you be happy with the rest of what we discussed? If so, it is worth looking at how much the feature really matters. If not, I would like to know what else is missing.”
After your response, ask:
How would you use that feature in a typical week, and what would happen if you did without it?
Avoid: You don’t need that feature, nobody really uses it.
You are telling the customer what they need, and you cannot know that. If they do need it, you have lost credibility.
Reading is not the same as saying it. Talk to an AI customer who raises this kind of objection and see in the report which sentence helped.
Practise this objectionA missing feature is sometimes a deal-breaker and sometimes a tick-box nobody will use. The customer may have been shown it in a demo and remember it. Find out whether they need the outcome the feature produces, or only like it. Never claim you have something you do not.
Clarify before you answer: “Thank you for telling me. What would you use that feature for, and how often? I want to understand the result you need, because there may be another way to get there.” Acknowledge, then ask: “You are right, we do not have that one, and I will not pretend otherwise. What I can do is show you how we handle the same task, and you can tell me whether that works for you. Fair?” Isolate the objection: “If that feature were not a question, would you be happy with the rest of what we discussed? If so, it is worth looking at how much the feature really matters. If not, I would like to know what else is missing.”
How would you use that feature in a typical week, and what would happen if you did without it?
Avoid “You don’t need that feature, nobody really uses it.” You are telling the customer what they need, and you cannot know that. If they do need it, you have lost credibility.
Educational conversation training. It is not legal or financial advice and it promises no results. Always follow your company’s rules, the terms of the product and a customer’s clear no.