Back to blog

Most teams already have the AI tools. What they're missing is permission.

Most mid-sized firms have already bought the AI tools. Adoption stalls because no one has shown people what good use looks like in their role, or made it clear they're allowed to use it.

I sat with an operations team last week that had Copilot licences for everyone. Full deployment, paid for months ago. When I asked how many people used it on a normal day, the honest answer was two, and one of them only for tidying up emails.

This is the pattern I see most in mid-sized firms. The tools are bought, the rollout email went out, and then very little changes, because nobody told people it was actually meant to be part of how they work now.

The problem usually isn't the tool

When adoption stalls, the instinct is to question the software. Wrong tool, wrong vendor, perhaps we backed the wrong one. Almost always the software is fine. What's missing is narrower and more human. People don't know what good use looks like in their particular role, and they aren't certain they're allowed to lean on it for real work.

So they keep AI for the low-stakes jobs. A tidy-up here, a first draft there. The genuinely useful applications, the ones attached to the work that actually eats the week, sit untouched. Not because they're hard, but because no one has shown them and no one has said it's fine.

What shifts it

Two things, usually. The first is permission, said plainly by someone senior. Use this for client work. Use it for the board report. Here's the line we don't cross, and everything short of it is encouraged. Ambiguity kills adoption, not a lack of capability.

The second is showing people the work rather than the tool. A walkthrough of features teaches nothing that survives the week. Sitting beside a finance lead while they rebuild their own reconciliation, in their own system, with AI handling the repetitive part, teaches something that stays.

Where to start

Pick one workflow per team that everyone quietly dreads. The reconciliation, the weekly report, the follow-up backlog. Get one person genuinely fluent at handing the dull parts of it to AI, in front of their colleagues. Capability spreads sideways between peers far faster than it travels down from the top.

You probably don't need to buy anything else. You need to make it unmistakable that the things you've already bought are meant to be used, and then show a handful of people how. The licences were never the hard part. The capability is.