All insights

AI

The tool isn't the hard part. Embedding it is.

Most AI pilots stall after the demo, and it's rarely the technology that lets them down.

Pretty much every business has run an AI pilot by now, whether it's a content generator, a chatbot or a clever spreadsheet someone built on a Friday afternoon. Most of them look great in the meeting and then quietly disappear within a quarter.

Why pilots stall

In my experience it usually comes down to ownership. Nobody's job depends on the pilot working, so it sits off to the side of the real workflow and people have to remember to go and use it. And because nobody agreed up front how success would be measured, nobody can say whether it worked, so it never earns more time or budget.

What sticks

The ones that last tend to look fairly unexciting from the outside. They take one workflow at a time, chosen because it saves real time or moves revenue, and they're built inside the tools the team already uses rather than in a new tab nobody opens. They have clear guardrails about what AI does and what a person checks, and they start with a baseline so there's a number to beat.

I'd much rather see a team start small enough to actually finish, and then make it boring. Boring is the goal, because it means the thing has become part of how you work.

Let's talk.

Book a thirty-minute call or flick me an email.