How to Explain AI Costs to a Non-Technical Client

Your client is not asking what a token is. They are asking whether this thing is going to surprise them on a Tuesday. Answer that question and the rest of the conversation gets easier. Lead with tokens and you will spend twenty minutes teaching a unit of measurement to somebody who will never use it, and they will still not know whether they can afford it.

The comparison that works

AI is metered like electricity, not licensed like software. There is no seat fee, nothing to buy up front, and nobody to negotiate a contract with. You pay for what runs, every time it runs, and the meter reads zero on a quiet month. That framing answers the two questions a business owner actually has, which are what happens if nobody uses it and what happens if everybody does. The honest answers are nothing and it goes up roughly in line with use.

Give them a range and a ceiling

A single number invites a single question, which is whether that number is right. A range invites a better one. Show what the workload costs on a cheap model and on an expensive one, say which you plan to use and why, and name the figure you would be surprised to exceed. Clients do not need precision here. They need to know the worst case is survivable, and they will remember that you told them the ceiling rather than the best case.

Leave them one lever, not five

Do not hand over a menu of optimizations. Give them the one decision that is genuinely theirs: how good the answers need to be. Cheaper models handle routine work well and cost a fraction of the flagship tier, and that single choice moves the bill more than everything else combined. Everything else, the caching and the batching and the prompt trimming, is your job and belongs in your workflow rather than in their inbox.