The Shift Away from Per-seat Pricing in AI

Consider a company that buys software for its customer support team. Under per-seat pricing, the bill rises or falls with the number of people who hold a license. Adding a worker adds a seat, and removing a worker removes one. The price is anchored to headcount, not to what the software actually accomplishes.

The question this article follows is what would happen if the vendor priced the software differently. The source describes a set of structures that are replacing per-seat pricing. Instead of anchoring the price to headcount, these structures attach it to the engagement itself, to the volume of work done, or to the value the work produces.

The easiest way to see the shift is to follow the same customer support operation through two billing models. The first model counts people. The second counts work. The diagram below shows what the bill is anchored to in each case. Notice that the change is not in the software's output; it is in the quantity the price is attached to.

The before side of the diagram is the seat-based model from the opening example. The after side is consumption-based pricing applied to high-volume agent operation. The source describes that pairing directly: consumption-based pricing is the structure for high-volume agent operation, and the bill follows how much the agent operates rather than how many people hold a license.

The source names three structures that take the place of per-seat pricing. Each one attaches the price to a different thing. The three are best learned as three separate answers to the question of what a customer is paying for. The subsections below take them one at a time, and the diagram after them shows how each one maps to a kind of work.

The three structures are easiest to remember as a matching exercise. Each one fits one kind of work. The comparison below pairs each pricing structure with the work it is used for, using only the categories the source names.

Read the diagram from left to right. The left column is the structure a vendor might choose, and the right column is the kind of work that structure is used for. The source gives the pairings, but it describes the work categories briefly, so the sublabels above are plain-language glosses rather than quoted definitions.

To see how a milestone structure behaves over time, the timeline below shows a generic engagement. It is an illustration of the general pattern implied by attaching the price to milestones. The source does not list the specific stages or payment triggers used by any company, so treat the steps as an example of the shape rather than as fact about a product.

The key idea is that the payment is connected to a point in the engagement rather than to a headcount or a running usage count. Work moves forward, a milestone is reached, and the price attached to that milestone is the event that matters for billing. The same engagement, billed per seat, would produce a bill that depends only on who holds a license during the period.

The source makes two claims that are easy to blur together. The first is that the transition is happening at different speeds in different categories. The second is that the direction is the same everywhere. A category can be slow and still be moving the same way as the fast ones. Read together, these claims describe a single trend that has reached some categories sooner than others.

The named companies serve a specific role in the source. They show that the shift is occurring in practice. The source does not list the pricing terms those companies use, so nothing in this article should be read as a catalog of their prices.