The pricing page has three columns and the middle one is highlighted, because every pricing page has three columns and the middle one is highlighted. It took longer to agree than the architecture did, and unlike the architecture it could not be refactored quietly on a Thursday.

Pricing is the most consequential product decision most founders treat as a marketing decision. It determines which customers you attract, which ones you can afford to keep, what your salespeople argue about, and whether growth improves your margin or destroys it.

In a category where serving a customer costs real money per request, it also determines whether your most enthusiastic user is an asset or a liability.

Per seat is dying, and the reason is arithmetic

Seat-based pricing fell from around twenty-one percent of software companies to about fifteen percent inside twelve months. That is a fast move for something as sticky as a pricing model, and the cause is not fashion.

If your product means one person can now do the work that used to take ten, then per-seat pricing asks the customer to pay you in proportion to the number of people who did not get more productive. Your revenue falls as your value rises. You have built a machine that reduces the size of your own invoice.

Buyers worked this out quickly, and the more successful your deployment the faster they work it out. It is a difficult position to argue your way out of at renewal, because the customer is right.

Per seat is not dead. It remains sensible where the product augments a person who still does the job, where usage per person is roughly uniform, and where the buyer’s mental model is headcount. It is a poor fit for anything that completes work autonomously.

The four models and where each one wins

Per seat. Predictable for both sides, easy to forecast, easy to sell. Breaks when one seat can do ten seats of work, and breaks badly when consumption varies by an order of magnitude between users on the same plan.

Per unit of consumption. Charging by tokens, calls or compute. Natural for infrastructure and developer products where the buyer is technical and understands what they are consuming. In an application sold to a business buyer it creates billing anxiety, which is a real commercial problem: a finance team that cannot forecast your invoice will cap usage, and capped usage is capped value.

Per outcome. Charging when something measurable happens. Per resolved support conversation is now an established pattern at prices well under a dollar, and it has spread from support into sales and back-office work. The alignment is genuinely elegant: the vendor is paid when the thing works. The difficulty is definitional. What counts as resolved? Who decides when the customer disputes it? What happens when the model does eighty percent of the work and a human finishes it? Every one of those becomes a contract clause and eventually a support ticket.

Hybrid. A base subscription with an included allowance, plus overage above it. This is now the default. Adoption rose from roughly twenty-seven percent to forty-one percent in a year, and by some counts more than nine in ten AI software companies use some blended model with a consumption component in it.

The reason hybrid won is not that it is elegant. It is that pure models each fail in one direction. Pure subscription exposes you to the heavy user. Pure consumption exposes the customer to an unforecastable bill. Pure outcome exposes you to definitional argument and leaves money on the table with high-frequency users. Hybrid fails in none of those directions completely.

The rule

There is one principle underneath all of this and it is short enough to write on the wall.

The unit you charge for should be the unit that costs you money.

When those two diverge, the customer who loves your product most is the one damaging you most, and you find out at exactly the moment you would like to be celebrating. A flat rate plan with an unbounded heavy user is the clearest version. That account uses the product forty times more than the median, costs you real money on every request, renews without hesitation, gives you a testimonial, and quietly consumes the margin from six other accounts.

You do not have to charge per token. You do have to make sure that when consumption goes up substantially, revenue goes up too.

Designing the hybrid

Four components, and each one has a job.

• The base. It covers your floor: the cost of existing, the cost of operating, and the cost of serving the included allowance. If the base does not cover the allowance at full consumption, you have priced a loss and made it recurring.
• The included allowance. Size it so that the large majority of customers never exceed it. That matters psychologically more than financially. A customer who never sees an overage experiences your product as a predictable subscription, which is what their finance team wants, while the meter is still there for the ones who need it.
• The overage rate. Priced with real margin, not at cost. Overage is not a penalty and it is not a favor. It is the part of the model that keeps you solvent at the top of the distribution.
• A cap or an alert. Nobody should ever receive a surprise invoice from you. A notification at eighty percent of allowance and a hard ceiling that requires a decision to lift buys you more goodwill than any discount.

Three ways this goes wrong

You price against the trial month rather than year three. This is the mistake buyers make and vendors mirror. The cheapest model at low volume is frequently the most expensive at scale, and the reverse. What matters is the shape of the cost curve at projected volume: linear, sub-linear or step function. Model your own pricing at ten times current usage before you publish it, because you will live with the structure much longer than the numbers.

You adopt outcome pricing without being able to define the outcome. Outcome pricing is the most aligned model and the most operationally demanding. Before you commit, write the definition, write the dispute process, and write what happens in the partial case. If you cannot write those three paragraphs clearly today, you are not ready to sell it, and you will spend the first year arguing about invoices instead of selling.

You set it once. Willingness to pay moves. It rises as a category matures, as your product improves, and as the buyer’s alternatives get worse or better. Companies that grow well revisit pricing at least twice a year, deliberately, with data. Companies that set a price in month four and defend it for three years are leaving a great deal on the table and usually discover it during a competitive loss.

Charge for the thing that costs you money, or your best customer becomes your worst one.

Tomorrow: the usage dashboard, and the loan you are making every time somebody signs up for free.