The tool I built needs one input. A sales rep pastes a screenshot of a client conversation, or types one rough sentence, and it returns the whole layout: request sorted, quote table filled, internal notes separated from the client-facing part. All of it follows rules I wrote. If you can paste an image, you are qualified to use it.

Its user count is one. Me.

Here is how my colleagues don’t use it. Not loudly. Nobody has said no to it or asked me to change anything. The screenshots just keep landing in the team chat the way they always have, with a “can you help sort this out?”, and someone sorts it out by hand. The tool sits there. Paste, one second, done. Instead: dump it on the humans, wait five minutes for the humans.

For a while I assumed something was missing. A walkthrough, maybe. A better button. Then I did the math from their side of the desk. Using the tool costs them one extra step. Dumping the screenshot costs them nothing, because somebody downstream always catches it. As long as that’s true, the tool loses to the chat window every single time. They know how to use it. They just won’t.

The recycling bin

I wrote before that this industry treats downstream time as free. I thought I was describing client briefs. Turns out I was also describing my own team chat.

An AI tool doesn’t get adopted into an empty room. It gets adopted, or not, into an org chart where someone is already absorbing the messy work for free. Every org has a default recycling bin: the person or team where unfinished work lands and gets handled, without anyone ever deciding it should. In our room, the bin is my team. So the tool never actually asked sales “do you want this done in one second?” It asked them “would you like to change your habit, so the people who currently do this for free can stop?” Framed like that, the adoption rate is not mysterious at all.

The AI debate in this industry is all about capability. Can it find the creators, write the brief, haggle. Inside a team, capability was never the bottleneck. Willingness is. And willingness is not something you can ship.

The part with no exit

The obvious advice: stop catching the screenshots, point at the tool, let the friction do the teaching. I’ve thought about it plenty. Here’s the bind. The recycling bin is me. If I refuse the screenshot, the work doesn’t happen and the client feels it. If I catch it, I’ve just demonstrated, one more time, that the tool is optional. Accomplice or crash test, and neither one ships adoption. A choice like that only exists two levels up, where nobody is reading adoption numbers for a tool they don’t know exists.

So I use my own tool, alone, every day. It works. The despair is quiet and very specific: I built something that solves his problem in one second, and he would rather spend five minutes of our time not touching it. A loading bar that finishes instantly, for an audience of one.

The tool works. The humans don’t.