AI Agent Pricing Models: Seat, Usage, Project, Outcome
Every AI agent pricing model answers one question: who pays when the agent does not do the job? Per seat, per usage, fixed project and outcome-based pricing give four different answers. We sell AI agents on outcome-based pricing, and the system in our case study runs that way, so this comparison comes from the vendor side of the table.
Per seat
You pay a monthly fee for each person who uses the software. The price is easy to budget and has nothing to do with how much work the AI finishes. A team of ten pays the same in a month when the AI drafts 20,000 replies as in a month when it drafts none that anyone sends.
Seat pricing fits tools that help a person work faster. It fits badly when the point of the agent is to take the work over, because the better the agent gets, the fewer seats you need, and the vendor's income falls as its product improves.
Per usage
You pay for what the system consumes: model tokens, messages, API calls or conversations started. Cost follows activity, which is fair for infrastructure. The weakness is that activity is not results. A reply that is drafted three times and thrown away costs three times as much as one that is drafted once and sent.
Usage also depends on engineering choices you do not see. In one of our cases a long email thread sent to the model as raw text used 37,604 input tokens. After the thread was distilled into structured facts first, the same case used 4,722, and the answer got better. Under usage pricing the first design earns the vendor eight times more than the second.
Fixed project price
You agree a scope and a price, the vendor builds it, and you own or license the result. You know the cost before you start. The risk sits in the scope: it is frozen on the day of signing, and a real business process keeps changing. Return rules change, a new carrier is added, a product line launches. Each change after delivery is a new quote.
A fixed price also pays for delivery, not for use. The vendor is paid when the system passes acceptance, whether or not your team is still using it six months later.
Outcome-based: pay per completed task
You pay for each unit of work the agent finishes: a conversation answered, an email reply sent, a document produced. Work that is not finished is not billed. A refund that waits for your decision is not billed until it is done.
The vendor carries the risk. If the agent handles little, the invoice is small. That puts the vendor's attention where yours is: on how much real work gets through and how good it is.
This model has one hard requirement. "Completed" must be something both sides can count from the same records. In customer service that is straightforward, because every conversation and every sent email is already a record in a system. Over 30 days the system in our case study produced these countable units: 15,445 chat conversations answered, and 25,576 email replies sent using an AI draft, of which 2,756 were sent by the AI on its own, 3,463 were approved by an agent without an edit and 19,357 were edited by an agent and then sent.
What you must define before paying per outcome
- The unit. One conversation, one sent reply, one document. Drafts are not units: one email can be drafted several times, and only the reply that goes out is work done.
- What counts as completed. For an email, the reply was sent. For an action such as a refund or a reshipment, the action was carried out and written back to the ticket.
- Who approves. Anything that moves money or goods is approved by your people. A unit is complete after that approval, not before.
- Where the count comes from. Your own system's records, visible to you line by line, not a number on the vendor's dashboard.
- How to stop. Monthly billing with no minimum term keeps the model honest.
How the unit price gets set
A unit price quoted before any work has been seen is a guess. We set it after a pilot: the agent is connected to the client's existing systems and runs real cases for 2 to 4 weeks, the client's team reviews every record, and the pilot shows how much the agent handled and how accurately. The unit price is agreed on those numbers. The steps of that pilot are in how to run an AI agent pilot.
Which model fits which situation
- A tool your staff use while they keep doing the work themselves: per seat.
- Raw model access for a team that builds its own system: per usage.
- A one-off build with a process that will not change: fixed project.
- Daily, repetitive work that lives in a system and can be counted: outcome-based.
For what sits behind a development quote, see custom AI agent development cost. For turning the agent's output into a number your finance team accepts, see how to calculate AI agent ROI. Our free plan states the unit we would count for your work within two working days.