Human Meets Digital
← All notes

Why the impressive AI demo falls apart on real work

Everyone's seen a jaw-dropping AI demo. Here's why it so often stops working the moment it meets your actual mess — and what to do about it.

You’ve probably seen the demo. Someone shows you AI reading a contract, answering a customer, or writing an email in seconds, and it’s genuinely impressive. So you try to use it for real, and within a week it’s quietly disappointing. The technology didn’t get worse between the demo and your office. The conditions did.

What the demo quietly leaves out

A demo is built to show the best case. That’s its whole purpose, and there’s nothing wrong with it — until you mistake the best case for the normal case. Pull a slick demo apart and it’s almost always leaning on a few things your actual business doesn’t have:

  • A tidy example. The demo used one clean, well-chosen document. Your real ones are half-filled forms, bad scans, and a note someone typed in a hurry.
  • Someone who already knew the answer. The person running the demo could see when it was right. When a customer or a junior staffer is on the other end, nobody’s there to catch the mistakes.
  • One try, with everyone watching. Real life is hundreds of these a day with nobody watching — and the one it gets wrong is the one that matters.
  • No connection to your actual systems. The demo lived on its own. Yours has to plug into your inbox, your files, your booking system — the place the work really lives.
A demo proves the AI can do something. It tells you almost nothing about whether it’ll hold up on a busy Tuesday.

The gap is mostly unglamorous work

When I’m brought in to fix a stalled AI experiment, the work that closes the gap is rarely the clever part. It’s the plumbing. It’s deciding what happens when the AI isn’t sure. It’s catching the made-up answer before it reaches a customer. It’s connecting the thing to where your work already happens so nobody has to copy and paste. It’s the small, careful set-up that turns a party trick into something you can lean on.

And it’s checking. The single biggest difference between a demo and something you can trust is that the trustworthy version has a way of knowing when it’s wrong. That means testing it against a stack of your real examples, with known answers, so you find the problems before your customers do — not after.

The pattern Plenty of surveys last year found that most businesses experimenting with AI saw no real payoff. Take the exact numbers with a grain of salt — but the shape of it matches what I see everywhere: the failures aren’t about the AI being dumb. They’re about nobody owning the messy part between a good demo and daily use.

Why nobody owns it

This gap sticks around for a boring reason: it belongs to no one. The person who showed you the demo has done their job once you’re impressed. The software company that sold you the subscription stops at their own product’s edge. Your own team is already flat out. So the bit in the middle — your messy files, your odd cases, your staff and customers — just sits there unfinished.

That middle is the entire job I do. Not advise on it from a distance. Climb into your specific situation and build the part everyone underestimates, until it actually works for you.

Three questions worth asking

Before you trust any AI tool with real work, ask the person selling it — or yourself — three things, and watch for flinching:

  • What does it do with a bad example? If the answer is “we only tried the good ones,” it isn’t ready.
  • How would we know if it got something wrong? If there’s no answer, you’d find out from an angry customer.
  • Who fixes it when it breaks? If no name comes up, it’s a demo, not a tool.

None of this means AI isn’t worth it. It often is. It just means the demo was the easy 10%, and the part that actually helps your business is the other 90% — the part someone has to sit down and build, in your world, with your real work.

Next step

Something eating your time?

If there’s real, repetitive work AI could take off your plate, that’s what I build.