Customers say “I’ll wait for the next version” for a reason. Here is what usually sits behind it, how to respond and what to avoid.
The customer expects something better soon and does not want to commit to something that may be outdated. It may also be a polite stall. Be honest about what you know and do not make promises about future features you cannot confirm.
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.
“What are you hoping the next version will do that this one does not? If it matters to you, I would like to know, and I will tell you honestly what I can and cannot say.”
Put the options side by side, including the cost of doing nothing.
“Waiting has its own cost: another few months without it. If the current version already covers most of what you need, it may make sense to start and take the next release when it arrives.” Only if that is true.
Shrink the decision to something low-risk that moves things forward.
“If the new version is what you want, could we agree to talk again when it is released, and meanwhile keep a short list of what you need? Then you can decide with the full picture.”
After your response, ask:
Which of the things you need could not wait until the next version?
Avoid: The next version will definitely have all of that.
A promise about an unreleased feature may be wrong, and a customer who buys on it will hold you to it.
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 objectionThe customer expects something better soon and does not want to commit to something that may be outdated. It may also be a polite stall. Be honest about what you know and do not make promises about future features you cannot confirm.
Clarify before you answer: “What are you hoping the next version will do that this one does not? If it matters to you, I would like to know, and I will tell you honestly what I can and cannot say.” Compare like with like: “Waiting has its own cost: another few months without it. If the current version already covers most of what you need, it may make sense to start and take the next release when it arrives.” Only if that is true. Propose a smaller step: “If the new version is what you want, could we agree to talk again when it is released, and meanwhile keep a short list of what you need? Then you can decide with the full picture.”
Which of the things you need could not wait until the next version?
Avoid “The next version will definitely have all of that.” A promise about an unreleased feature may be wrong, and a customer who buys on it will hold you to it.
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.