Guides / how to price an ai saas product
How to price an AI SaaS product on real unit costs
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.
Free, no card, no account
Run the free Cost Leak Scan
It shows your most expensive conversation before you install anything.
Mistakes that cost the most
| Mistake | Why it hurts | Do instead |
|---|---|---|
| Setting the price from average cost per customer. | On a long-tailed distribution the average sits nowhere near the accounts that decide your economics. | 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. | Unlimited is a promise priced against a maximum nobody has computed, and the maximum keeps moving. | 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. | Prices and model mix both move, so a margin computed once quietly drifts out of date. | Recompute margin per account monthly against a dated price book, and alert when any account crosses a threshold. |
Run this check tonight
- 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 example
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.
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.
Every number, with its confidence and source
| Figure | What it means | Confidence | Source |
|---|---|---|---|
| $12.00 to $260.00 | modelled monthly model cost from median to heaviest account on identical usage-based pricing | estimated | 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 | (14 x $2.00) + (3 x $10.00) per million, using real Claude Sonnet 5 introductory rates. Token volumes are modelled. |
What a generic answer can’t know
Pricing needs two numbers from opposite sides of your business, model spend and revenue, joined on the customer. No provider has your revenue and no billing system has your token counts. The join has to happen where both are reachable. Culpa does it on your infrastructure, keeps your prompts and responses there, and counts the calls to run your plan.
Questions founders ask next
Should I price an AI product per seat or per usage?
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.
What gross margin should an AI SaaS product target?
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.
How often should I revisit pricing?
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.
On your infrastructure
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.
How Culpa works
Find the culprit. Not just the total.
Your dashboard shows what you spent. It stops short of who spent it. Culpa shows the conversation, the user and the feature behind it.
Your prompts stay local.
Culpa runs on your own infrastructure. What you send to a model reaches us at no point.
Every dollar has a name.
Follow any charge to the conversation, the user, the feature and the customer behind it.
See the bill before it lands.
Cost your next feature before you ship it. You get the likely bill and the worst case, at best, median, p90 and p99.
Three steps to your first answer.
Change one base URL.
Or drop in the Python or TypeScript library.
Find your most expensive conversation.
In the first session, not the first week.
Cost your next feature before you ship it.
Why the bill went up
Example dashboardCalls traced
418,209
across 3 projects
Spend this week
$378.41
+ $182 vs last week
Failed calls
312
74% retried, and you paid for all of them
+ $182 this week traced to one culprit
Spend over 14 days
Most expensive users
Next week forecast
Graded against reality. Accuracy shown as results land.
Free, no card, no account
Run the free Cost Leak Scan
It shows your most expensive conversation before you install anything.
Keep reading
Sources: Anthropic pricing. Last reviewed 2026-08-01. Plain text version.