What an AI agent really costs

A demo is not the whole cost

A demo shows a model can do a task. A business system also needs the right information, connections to the tools people use, permissions, tests, and a way to recover when something fails.

That is why two projects with the same-looking chat box can have very different scopes. A read-only assistant on a small document set is not the same as a system that changes records across several tools. Price the responsibility, not the interface.

Separate building from running

Building includes understanding the process, preparing data, connecting tools, designing review steps, and checking behavior. Running includes model usage, hosting, subscriptions, monitoring, human review, and maintenance. Ask for both.

A low usage charge does not make a system cheap to operate. A large build does not mean the monthly cost must stay high. Count the human work too. If an agent saves five minutes drafting and adds four minutes checking, the saving is one minute.

What a production change actually involved

Moving a sales agent to a new production runtime involved more than choosing the runtime. We verified the connection to the team’s work surface, preserved pending workflow state, checked approval ownership and duplicate controls, tested restart behavior, and restored a backup into an isolated location to prove recovery.

The old runtime stayed available as a rollback while the new release was observed. No test message reached a customer. These are documented delivery tasks, not estimates of the client’s costs.

They show why model usage is a poor proxy for the price of a dependable system. Integration, state, testing, recovery, and continued care are real work even when the visible result is a short conversation.

Value it against the hire, not the minutes

The cleanest value case is a hire you no longer need to make. Count it only if the agent really absorbs that work, and set the cost of running the agent against the full cost of the role. If nobody’s pay changes, minutes saved are capacity, not cash.

Revenue benefits need the same discipline. Count contribution after variable costs, not gross sales. Keep assumptions separate from measured outcomes, and never count one benefit twice.

Ask what happens after release

A serious proposal says who maintains the system, how changes are handled, what usage is measured, and what you own. It also says what happens when the first problem is solved.

Sometimes the next priority is obvious. Sometimes the right move is handing over a stable system. An ongoing fee should be worth it because of the work and care it buys, not because the system is switched on.