← All posts

You bought the AI tool. Why isn't anyone using it?

Every week another business owner tells me they bought a tool and nobody touched it after day one. The tool wasn't the problem. The rollout was.

I hear some version of this story at least once a week now: "I spent three thousand on an AI platform for the team and after the first fortnight nobody's logged in." It stings because the money's gone but worse than that — they're right that they needed it, and wrong about why it didn't stick.

The instinct is to blame the tool. Too complicated. Overhyped. Not fit for purpose. Sometimes that's true. But more often the tool was fine. The approach to getting people to use it was broken.

I run a team on a sales floor and I build software for other people's teams. I've seen this fail enough times to recognise the pattern. Here's what actually goes wrong, and what to do instead.

The tool solves a problem nobody has

This is the most common one. The owner experiences a pain — they're drowning in admin, or they can't see what's happening with deals, or they're spending evenings on paperwork — and they buy a tool that solves that pain. But the team doesn't have that pain. The team has their own pain: making the phone ring, getting through the day's calls, keeping customers happy. The owner's problem and the team's problem are different, and the tool was bought for the first one.

The fix: Ask the team what slows them down before you buy anything. Not rhetorically. Sit with them. Watch them work. The tool you end up with might be different from the one you had in mind, but it'll be one people actually open.

The rollout was a hand grenade

"Here's the login. It does everything. Figure it out." A slack message, a group email, an all-hands where you demo for fifteen minutes while everyone nods. That's not a rollout. That's abandonment wrapped in hope.

A good rollout has three phases and they don't happen on the same day. First: one person on the team uses it for a week, finds the rough edges, figures out the shortcuts. Second: that person becomes the internal guide — shows three more people. Third: the tool is the norm, not the new thing. That's a week, maybe two. It requires patience, which people skip because they've already paid for it and want it to work now.

It added work instead of removing it

This is subtle and deadly. A tool promises to save time, but on day one it costs time: setting it up, learning it, logging into another thing, remembering another password, changing your routine. If the tool doesn't deliver visible relief inside the first few uses — if the benefit is back-loaded — most people won't reach the payoff. They'll revert to whatever they were doing before, because that's faster right now.

The fix: Pick one narrow job the team already does — one thing, not everything — and make that job noticeably easier on day one. Not on day thirty. Show them a win before lunchtime. Then layer on the next thing.

Nobody was measured on it

This is awkward but true. If a new tool is optional and nobody checks whether it's being used, it won't be used. People are busy. They have a way of working that gets them through the day. Adding a tool without making it part of how success is measured means it'll quietly die.

I'm not talking about surveillance. I mean something as simple as "the first thing you do when a new lead comes in is send this template" or "before end of day, check deals in this status." Make the tool part of the workflow, not an optional extra that sits next to it.

The pattern nobody admits

Sometimes the real problem isn't the team. It's that the owner wants a software fix for a management problem. No tool saves you from needing to lead the change. You have to explain why this matters, model using it yourself, follow up, celebrate the wins, and give it more than a week before deciding it failed. A tool adopted that way has a good chance of sticking. A tool dumped on people and hoped for does not.

If you've bought something that's gathering dust, it might not be too late. Pick the one thing it does best, find the one person most open to it, and try a proper rollout this time. The tool that collects dust and the tool your team won't work without are often the same piece of software. The difference is how it arrived.