Your AI pilot worked and nothing changed

The pilot ran for six weeks. It worked. Everyone agreed it saved real time.

The pilot ran for six weeks. It worked. Everyone agreed it saved real time.

An automated quote goes out at 10:40 on a Tuesday. The price is wrong by a factor of ten. A customer has already opened it.

Your operations manager resigns on a Friday. On Monday you find out the approval rules for your three largest accounts lived in her head and in one chat thread nobody else was in.

Your operations lead sends a message on Friday afternoon. She wants to use a new AI tool to summarise client calls. It costs $30 a month. She needs an answer.

A 40-person logistics firm wanted to automate its customer complaint responses. The volume was there. Around 30 a month, all arriving by email, all needing a reply inside a day. On paper it was a clean candidate.

Someone changes a process in March. The page describing that process still says what it said in January. Nobody decided to let it drift. It drifted because updating the page was a separate job, and separate jobs get dropped.

Someone asks what discount a reseller qualifies for. Three people answer. All three sound certain, two are wrong, and nobody can point to where the rule actually lives.

AI sounds like a developer tool. Read the coverage and you would think the whole point of it is shipping code faster.

The automation did not break because the AI got dumber overnight. It broke because the one person who understood it was on vacation.

Your team can read a messy document and still get it right. They fill the gaps from memory. An AI tool cannot. It only has the words on the page.