Product & Delivery · Chapter 7 of 8
Pricing and unit economics
Named in 39% of product postings. The half of product management that engineers-turned-PMs most often skip.
Cost and budget language appears in 39% of product postings and 42% of delivery ones. For anything with variable cost per use — which now includes most AI features — this is not a finance concern you can delegate.
The three numbers
- Cost to serve one unit of value. Not cost per API call — cost per resolved task, including retries, failures and human escalation. The denominator is the whole question.
- The distribution, not the mean. A small tail of expensive users can invert the margin while the average looks healthy. Price against the 95th percentile, not the median.
- Willingness to pay, which is anchored on what they do today. A customer paying three people to do something manually has told you the ceiling.
Structures, and what each protects against
| Structure | Protects you from | Costs you |
|---|---|---|
| Per seat | Usage spikes | Revenue when usage grows and headcount does not |
| Usage tiers with overage | Unbounded cost | Budget predictability for the customer — a real enterprise objection |
| Seat plus fair-use cap | Both, mostly | Complexity in the sales conversation |
| Pure pass-through | Margin risk entirely | Enterprise deals — nobody can budget for it |
| Outcome-based | Nothing, until you can measure the outcome reliably | A measurement dispute with every customer |
Two things to insist on from day one
Instrument cost per customer immediately. You cannot retrofit it, and without it you will not discover the loss-making segment until it is large.
Build a circuit breaker — a per-account spend cap that degrades rather than bills without limit. The first real incident in any usage-priced product is a runaway loop on one account, and it is much better to have decided in advance what happens.