# How to price an AI SaaS product on real unit costs

> How to price an AI SaaS product: start from your 90th-percentile customer cost, not the average, and cap what sits beyond it. Worked math inside.

URL: https://getculpa.com/how-to-price-an-ai-saas-product
Last reviewed: 2026-08-01

## Answer
Price an AI SaaS product from your 90th-percentile customer cost rather than the average, then cap the tail beyond it. Usage is long-tailed, so an average-priced plan loses money on the heaviest accounts. Culpa, a local-first LLM cost, margin, and forecast ledger, tags spend to a customer and reconciles it against revenue you type in or import.

## Why this happens
Traditional SaaS pricing assumes serving one more account is nearly free. AI products broke that. Your heaviest account can cost fifty times your lightest on the same plan, so a single flat price produces both your best and your worst margin at once. Pricing from an average puts roughly half your customers above the line you budgeted for, and the ones furthest above it are the ones who like the product most.

## What this usually looks like
- Your blended gross margin looks fine while a specific plan tier loses money on every heavy account.
- Nobody can name the least profitable customer, so nobody can act on it.
- Usage limits were set from a guess rather than from the token profile of real power users.
- A large new logo lands and the model bill jumps by more than the contract's monthly value.

## Common mistakes
- Setting the price from average cost per customer. Why it hurts: On a long-tailed distribution the average sits nowhere near the accounts that decide your economics. Do instead: Price from the 90th percentile and bound the tail with a usage cap or an overage rate.
- Launching an unlimited plan before measuring the tail. Why it hurts: Unlimited is a promise priced against a maximum nobody has computed, and the maximum keeps moving. Do instead: Publish a generous included allowance with a stated overage, which reads as fair and bounds the risk.
- Treating model cost as fixed when it changes monthly. Why it hurts: Prices and model mix both move, so a margin computed once quietly drifts out of date. Do instead: Recompute margin per account monthly against a dated price book, and alert when any account crosses a threshold.

## Self-check
- Compute model spend per customer for last month and sort descending. Read the top ten by hand.
- Find the 90th percentile. That number, not the mean, is your pricing floor.
- Divide each account's cost by what it pays. Anything above a third of revenue deserves a conversation.
- Check whether any account already costs more than it pays, and whether a cap would have caught it.
- Re-run the whole calculation at next month's rates if a model you use has a dated price change coming.

## Pricing a plan from the tail instead of the mean (illustrative)
A product on Claude Sonnet 5 at its real introductory rates, $2.00 per million input and $10.00 output. The usage distribution below is modelled on a typical long tail across 500 accounts.
  Median account: 3M input, 600k output = (3 x $2.00) + (0.6 x $10.00) = $6.00 + $6.00 = $12.00
  90th percentile: 14M input, 3M output = (14 x $2.00) + (3 x $10.00) = $28.00 + $30.00 = $58.00
  Heaviest account: 60M input, 14M output = (60 x $2.00) + (14 x $10.00) = $120 + $140 = $260
  Price at 3x the median ($36) and the 90th-percentile account costs 161% of revenue
  Price at 3x the 90th percentile ($174) with a cap at that usage, and the tail is bounded
The median says $12 and the tail says $260. A plan priced off the median loses money on a fifth of the base, and the fix is a floor set by the 90th percentile plus a cap.

## Cost figures
Every figure carries its confidence and its source. No figure on this site is provider-reported.
- $12.00 to $260.00 — modelled monthly model cost from median to heaviest account on identical usage-based pricing [estimated] Source: Both endpoints computed at real Claude Sonnet 5 introductory rates per 1k tokens from the price book, effective 2026-07-02. A range because the usage distribution is modelled.
- $58.00 — modelled 90th-percentile monthly customer cost, the figure a plan price should clear [calculated] Source: (14 x $2.00) + (3 x $10.00) per million, using real Claude Sonnet 5 introductory rates. Token volumes are modelled.

## FAQ
Q: Should I price an AI product per seat or per usage?
A: Per seat is simpler to sell and decouples revenue from cost, which is dangerous when usage varies fiftyfold between accounts. A hybrid works well: a seat price with an included allowance and a stated overage above it.

Q: What gross margin should an AI SaaS product target?
A: There's no defensible industry figure to quote, and numbers that circulate usually come from companies with very different usage profiles. The useful target is your own trend and knowing which accounts sit below it.

Q: How often should I revisit pricing?
A: Whenever your model mix or a provider rate changes, not on a calendar. A dated price change like Claude Sonnet 5's move from $2 to $3 per million on 2026-09-01 shifts your unit costs by 50% with no action on your side.

## Sources
- Anthropic pricing: https://platform.claude.com/docs/en/docs/about-claude/pricing

Run the free Cost Leak Scan: https://app.getculpa.com/scan?source=pseo&slug=how-to-price-an-ai-saas-product&cluster=margin

Machine-readable index of every guide: https://getculpa.com/api/pages
Human-readable index of every guide: https://getculpa.com/guides
Site overview: https://app.getculpa.com/llms.txt

Privacy: Culpa runs on your infrastructure. Your prompts and responses never leave it. Culpa counts calls to run your plan, and it fails open, so if it ever breaks your app keeps running.