Customers say “My team won’t use it” for a reason. Here is what usually sits behind it, how to respond and what to avoid.
What is really behind it
The decision-maker or influencer fears wasted money and a change nobody follows. It may reflect a real history of failed tools, or a team that has not been asked. Adoption is the real issue, and it can be tested before it is paid for.
Typical in: Software and SaaS, Professional services, Contact centre and customer service
How to respond
Pick the framework that fits the customer. The wording is an example direction, not a script: say it in your own words.
Clarify before you answer
Ask what sits behind the objection, so you answer the real concern.
“Thank you, that is a real risk. What has made people reluctant in the past: too complicated, no time, or not seeing the point?” Their answer shapes your answer.
Propose a smaller step
Shrink the decision to something low-risk that moves things forward.
“We could try it with a few of the people who are open to it, and let the others see the result. Would you be willing to start with two or three, and review in a few weeks?”
Offer proof
Offer an example, a reference or a sample the customer can check. Never an invented figure.
“I can show you how teams typically introduce it and what makes people use it or ignore it, so you can judge whether your team would. Would ten minutes on that be useful?”
The follow-up question
After your response, ask:
Which one or two people in your team would you choose to try it first, and why them?
What not to say
Avoid: Everyone uses it once they see how good it is.
It ignores a specific, credible concern with a generalisation. Adoption problems are real, and denial makes you look naive.
Practise it out loud
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.
The decision-maker or influencer fears wasted money and a change nobody follows. It may reflect a real history of failed tools, or a team that has not been asked. Adoption is the real issue, and it can be tested before it is paid for.
How do you respond to “My team won’t use it”?
Clarify before you answer: “Thank you, that is a real risk. What has made people reluctant in the past: too complicated, no time, or not seeing the point?” Their answer shapes your answer. Propose a smaller step: “We could try it with a few of the people who are open to it, and let the others see the result. Would you be willing to start with two or three, and review in a few weeks?” Offer proof: “I can show you how teams typically introduce it and what makes people use it or ignore it, so you can judge whether your team would. Would ten minutes on that be useful?”
What should you ask after “My team won’t use it”?
Which one or two people in your team would you choose to try it first, and why them?
What should you not say when a customer says “My team won’t use it”?
Avoid “Everyone uses it once they see how good it is.” It ignores a specific, credible concern with a generalisation. Adoption problems are real, and denial makes you look naive.
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.