How to Respond to “My Team Won't Use It”: 3 Useful Answers
“My team won't use it.”
The owner is sold, but worries their people won't adopt it. Three ways to bring the team into the decision and take the burden of adoption off the buyer.
Practice this objectionWhy buyers say it
Someone who says this has already bought, at least in their head, a tool nobody ended up using. They remember the complaints, the paper forms creeping back, the wasted money. Now they're afraid of reliving that scene and looking like the boss who forces things on people. It's not an objection to the product. It's an objection to the effort of changing other people's habits, and to the strain on their authority. Sometimes it also hides the fact that the owner isn't sure they'd use it either, and the team becomes a convenient excuse. To answer it, you have to free them from the job of convincing everyone else.
What it often means
- A tool they bought before that employees never touched
- Fear of forcing a change and losing goodwill
- A quiet doubt that they wouldn't use it either
Three answers that work
Who on the team would use it most, realistically? Let's run a trial with just that one person for [period], without involving anyone else. If they say it works, they'll convince their coworkers better than you or I ever could.
Why it works: You move the decision from “the whole team” to “one person,” and you pick the one with the most to gain. A coworker who likes using it is the only argument that actually beats resistance to change.
Let me ask you this: what do your people do today for [task], and what annoys them about how they do it? If the tool removes that annoyance, they'll use it. If it doesn't, you're right and there's no point going further.
Why it works: You center the benefit on the people doing the work, not the owner. Admitting it might not be worth it makes you credible and gets the buyer looking for the upside for their team on their own.
That happens a lot, and it usually comes down to how you start. Let me run a session with your team where they're the ones asking questions. They decide whether it's worth it. If they say no, we both accept that.
Why it works: You give the team a voice in the choice instead of pushing it on them, and you take the owner out of the middleman role. People adopt what they chose far more readily than what they were handed.
Avoid this one
Just make the call and make it mandatory, they'll all get used to it.
Why not: You're recommending the exact scenario they're afraid of: impose it, then manage the pushback alone. It's also not true. Mandated tools get worked around, and when it fails, the blame lands on the product and on you.
Example dialogue
BuyerFor restaurant shifts it looks great, but my servers are twenty years old and don't even check email. They'd never use it.
YouHow do they get their shifts right now?
BuyerA sheet taped up in the kitchen and a photo on WhatsApp. Then they call me because the photo's blurry.
YouThen for them only one thing changes: the shift shows up on their phone as a notification, no app to learn. They don't have to do anything. Try it with next week's schedule and see whether the blurry-photo calls drop.
BuyerIf all they have to do is receive it, that could work. Okay, let's try next week.
Practice this objection
A simulated buyer says it to you out loud (or in writing), you answer, and you get a score plus the model answer. Free, no account, 2 minutes.
FAQ
How do I involve the buyer's team without going over the owner's head?
Always ask the owner first and have them sit in. Suggest a short call or visit where the people who'll use the tool ask you questions directly. You answer, the owner watches. You're not bypassing them; you're relieving them of the job of convincing their own people, which is exactly what they dread.
Is free training a good way to overcome this objection?
Yes, if it's short and concrete: one session on the buyer's real case, not a course. Say clearly how long it takes and what the team will be able to do afterward. Long, generic training is scarier than the tool itself. A half-hour call on the first real task plus a direct contact for follow-up questions works best.
What if the owner is actually the one who doesn't want to use it?
It happens, and you can tell when the team is never mentioned with specific names or roles. Then ask plainly: “And you, would you use it?” If the answer is shaky, work on their doubt, not the team's. Pushing on the employees when the owner is the brake wastes everyone's time.