The Three Gates: How to Tell a Real AI Project From a Demo

Most AI “opportunity lists” deserve a NO-GO — not because AI doesn't work, but because the list was built backwards. Three gates, five minutes per idea, tell you which projects are worth your team's energy.

Every company we talk to has a list. Sometimes it's a real document — “AI Opportunities,” sitting in somebody's drive. More often it's a loose pile of ideas that surface in meetings: a chatbot for the website, an agent for the inbox, something — anything — with the word copilot in it.

Here's the uncomfortable math: most of that list deserves a NO-GO. Not because AI doesn't work — it works. The list deserves a NO-GO because most of it was built backwards. It starts with what AI can do and goes looking for a home, instead of starting with the work and asking what actually deserves help.

So before we build anything — for a client or for ourselves — we run the idea through three gates. It takes about five minutes per idea, and a healthy list loses half its items at this stage. That's the system working.

Gate 1 — Real work

Does it attach to a workflow someone on your team runs every single week? Frequency beats wow. An unglamorous workflow that runs fifty times a year will beat a spectacular one that runs twice — every time — because repetition is where the hours hide and where the learning compounds.

The ideas that pass this gate sound boring on purpose:

• The compliance matrix you build for every RFP.
• The account research your reps do before every first call.
• The variance questions finance answers every close.

The ideas that fail it sound exciting: the all-knowing assistant, the automation for a task that happens twice a year, the tool for a workflow that doesn't exist yet. That last one matters most. AI doesn't create discipline, it amplifies it — if nobody runs the workflow today, AI won't summon it into existence.

Gate 2 — Owned

Can your people run it, fix it, and extend it without us? There's a graveyard in most companies: automations a vendor or a long-gone employee built, that still technically run, that nobody understands, that everyone is afraid to touch. That's not a capability. That's a dependency with a login.

If an idea can only live as something an outside party maintains forever, it fails this gate — even if it works. Especially if it works, because that's the dependency you'll feel the most.

Gate 3 — Measured

Can you point to hours saved or work won — not vibes? Pick the number before you build. Hours per RFP response. First calls booked per week. Days to close the books. If you can't name the number in advance, you won't be able to defend the spend later — and “everyone seems to like it” does not survive a budget review.

The number doesn't have to be big. It has to be real, and it has to be visible to someone who signs things.

A NO-GO is a gift

Killing an idea at the gate stage costs you five minutes. Killing it after a quarter costs you the quarter — plus the budget, plus something harder to win back: the team's belief that the next idea is worth their effort. The discipline isn't generating ideas. Ideas are free. The discipline is killing them while they're still cheap to kill, so the two or three that pass get the focus they need to survive contact with a Tuesday.