Every AI vendor has impressive demos. Every consultancy has glowing case studies, usually attributed to “a regional insurance company” or “a mid-market logistics firm” — anonymous enough that nobody can check them, specific enough to sound like evidence.

This post has none of those, on purpose. An unverifiable number attached to an unnamed company tells you nothing about your business, and the ones you find in vendor material are selected for being impressive rather than typical. What follows instead is the mechanism: where the return actually comes from, what it costs to get, and how to work out whether the arithmetic clears for you before anyone quotes you.

Where the return actually comes from

Almost every AI project that pays for itself does so through one of three mechanisms. Being clear about which one you are buying matters, because they have different risk profiles and very different failure modes.

Time removed from a repeated task. The most predictable of the three. A task happens many times, each instance takes a few minutes, and some fraction of that is mechanical. The return scales with volume, which makes it easy to estimate in advance and easy to verify afterwards. It is also capped: you cannot save more time than the task consumes, so a process taking two hours a week has a ceiling of two hours a week no matter how good the technology is.

Errors that stop happening. Harder to estimate, frequently larger. When work is re-typed between systems, some percentage is entered wrong, and the cost of a mistake is rarely the thirty seconds it takes to correct. It is the reconciliation at month end, the customer who noticed, the delivery that went to the wrong site. Most businesses have never measured this, which is exactly why it tends to be underestimated.

Work that was not happening at all. The quotes that got one follow-up instead of three. The after-hours enquiries nobody returned. The reviews never requested. This is not a saving — it is revenue that was being left on the table, and it is usually the largest of the three. It is also the hardest to prove, because you are comparing against a counterfactual.

The common thread in projects that work: they start from one specific, measurable process, not from a strategy. “We should be doing something with AI” reliably produces a demo that impresses everyone and gets used by nobody.

The honest cost breakdown

Four costs. Typically only the first gets quoted, which is why so many projects feel like a surprise six months in.

  • Implementation. The number on the proposal. A focused, well-scoped project generally starts around $5,000; anything spanning several systems, or replacing something a business runs on, climbs from there and is worth scoping properly rather than guessing at. It is real, visible, and usually the smallest of the four costs over a couple of years.
  • Running costs. $200–$2,000 a month is a fair planning range for compute and API usage, scaling with volume. Anything doing multi-step reasoning re-reads its own working at each step, so cost tracks the number of steps rather than the length of the request.
  • Maintenance. The one nobody budgets. Models get retired and replaced on a vendor’s schedule, not yours, and a system tuned against one version does not behave identically on the next. APIs change. Your own process changes. Either someone owns this or the thing quietly drifts out of usefulness and you find out from a customer.
  • Internal time. Budget 20–40 hours of your own team’s time across the project for data preparation, testing and getting people to actually use it. This is the cost most people forget, and the one that sinks the most projects.

A payback period of two to four months is realistic for high-volume, well-bounded work. Four to six months is realistic for anything touching judgement or analysis. Something showing no clear value after six months usually has a scope problem rather than a technology problem.

Where AI doesn’t pay off

Being straight about this matters more than the section above it, because these are the cases where people spend real money and regret it.

  • Low volume. Below roughly an hour a week of the underlying task, the build costs more to maintain than it saves. Automation is not free once it ships.
  • No clear success metric. If you cannot define what better looks like in measurable terms, you cannot tell whether it worked, and you will end up arguing about vibes at renewal time.
  • Unreliable source data. AI does not clean up inconsistent, incomplete or badly maintained data — it propagates the problem faster and with more confidence. Most disappointing AI projects are undiagnosed data projects, and the discovery arrives after the money is spent.
  • The process is broken. Automating a bad process gives you a bad process that runs faster and is now harder to change. Fix it on paper first, with the people who do it. What remains is often much smaller than what you started with.
  • The task is the relationship. Some of the contact customers value most is exactly what looks inefficient on a spreadsheet. Automating it saves twenty minutes and costs you the reason people chose you.

The four-question framework

Before greenlighting anything, answer these four. They take an afternoon and they are cheaper than finding out later.

  • Volume. How many hours a month does this process consume across everyone involved? Track it for a week rather than estimating — frequency is the number people get wrong, usually by about half.
  • Error cost. What does a mistake actually cost, counting rework, customer trust, compliance exposure and lost revenue? Include the ones that currently go unnoticed.
  • Measurability. Can you tell within 30 days of deployment whether it is working, cheaply and without a research project?
  • Data readiness. Is the information already captured and reasonably clean, or does capturing it have to happen first? If the answer lives in someone’s head, that is a different project and it comes first.

Favourable on all four and you have a real case. Weak on any one and the right move is to address that dimension before starting, or pick a different use case where the fundamentals are stronger.

The best AI investments are rarely the most technically impressive. They are the ones with the shortest, clearest path from deployed to paid for itself — and they are chosen by people who were willing to conclude, at least once, that the answer was no.