Revenue Models for AI Products: A Founder’s Pricing Playbook (2026)

· 27 min read

A pricing playbook for AI products in 2026. Five revenue models that actually work, with real ARR numbers from Sierra, Harvey, Cursor, Devin, Intercom, and the framework for picking the right one.

Table of contents

  1. The $285B mistake everyone is still making
  2. Why every old pricing playbook is wrong now
  3. The Revenue Model Map: 5 ways to charge for AI
  4. Per-seat: Why it is dying (and where it still works)
  5. Per-action and usage: The honest cost-pass-through
  6. Outcome-based: The model with the best margins (if you can build it)
  7. Hybrid: The model 70% of new AI companies are using
  8. Flat-rate: The model you should run from in 2026
  9. The unit economics math every founder must run
  10. How to pick your model in 60 minutes
  11. The contrarian take: most pricing advice is wrong for early founders
  12. What to do Monday morning
  13. FAQ

The $285B mistake everyone is still making

On a Wednesday morning in February 2026, the SaaS index lost $285 billion in 48 hours. Atlassian reported its first-ever decline in seat counts. Workday (a workforce management vendor) cut 8.5% of its own workforce. Forward P/E for software fell to 22.7x, below the S&P 500 for the first time in history.

The market had finally figured out what AI-native founders had been pricing into their plans for two years. Per-seat SaaS was over. Not slowing. Over.

The reason is simple math. The marginal cost of a new SaaS user used to be near zero. The marginal cost of a new AI workflow is real compute. And the workflows that customers actually want (agents that take actions, not assistants that suggest things) burn through 10 to 100 times more tokens per task than chat interfaces did in late 2023.

So the old equation broke. You can’t sell seats to customers who are firing the people who used to fill those seats. You can’t sell flat-rate subscriptions to customers whose usage just jumped 50x. You can’t price like SaaS when your gross margin is 50% and the buyer expects 80%.

Most founders I talk to in 2026 know per-seat is broken. They are stuck on what to do instead. So they default to the safest move (a $20-$50/month subscription), watch their best customers blow through their token budget, and either go bankrupt or piss off the customers they wanted to keep.

This post is the playbook I wish someone had handed me before I priced my first AI product. Five revenue models that actually work in 2026. Real ARR numbers from companies running each one. Gross margin math. And the decision framework for picking yours.

Why every old pricing playbook is wrong now

Pricing books from 2018 to 2023 told you three things. Charge per seat. Pick a freemium funnel. Anchor your price 30% below the next-cheapest competitor. That advice killed dozens of AI startups in the last 18 months.

Here is what changed.

The cost of goods is not zero anymore. Traditional SaaS gross margins ran 80-90% because servers were cheap and a new user cost almost nothing. AI products run 50-60% gross margin because every active user is making model calls. OpenAI’s compute margin on its top tier was around 70% in late 2025, and that is the company that actually owns the model. If you are an app sitting on top of someone else’s API, you are paying retail and reselling. Your margin is what is left.

Usage is unpredictable in ways nothing was before. A single agent loop with 5 tool calls and a retry can burn 50,000 tokens. A user who lets the agent run overnight can burn 5 million. On April 4, 2026, Anthropic cut off third-party agentic tools because users were exploiting the flat-rate Claude subscription to run unbounded agent loops. That is the failure mode of mispricing in the agent era. Not lost margin. Existential.

The buyer no longer has a reference price. When you sold a $50 per-seat tool, the buyer had 12 other tools at $50 per seat to compare it to. When you sell an AI agent that closes 200 customer support tickets in a weekend, what does the buyer compare that to? The salary of the support rep? The cost of the previous chatbot tool? The token bill if they built it themselves? Each comparison gives a different price. The reference is missing, which means the founder gets to define it. That is an opening if you know what you are doing. It is a graveyard if you do not.

Renewals are now real for the first time. Most AI vendors signed enterprise pilots in 2025 with promotional pricing or “land grab” rates that ignored unit economics. Those pilots are renewing in 2026. The pricing has to reflect actual value delivered, not the discount you used to get the foot in the door. Companies that cannot show measurable outcomes are watching renewals collapse.

The five models below are how the AI companies that are actually growing have responded.

The Revenue Model Map: 5 ways to charge for AI

I sat down with the public revenue numbers for 23 AI companies that hit $50M ARR or higher in 2024-2026 and built this map. The vertical axis is who bears the cost risk (the vendor or the customer). The horizontal axis is what the customer is actually buying (access vs. work done).

The Revenue Model Map: 5 Ways to Charge for AIVendor bears riskCustomer bears riskSelling accessSelling work doneFLAT-RATEVendor eats overage costExamples: ChatGPT Plus, Cursor ProBest for: consumer, predictable useRisk: unbounded usage attacksMargin profile: 30-50% (volatile)Cursor: $500M ARR (60% gross)OUTCOME-BASEDVendor only paid for resultsExamples: Sierra ($1.50/resolution)Best for: clear binary outcomesRisk: vendor loses on failed attemptsMargin profile: 60-75% if >80% successSierra: $150M ARR (24 months)PER-SEATCustomer pays for access by userExamples: Harvey ($1,000-$1,200/atty)Best for: regulated B2B, expert usersRisk: dies when AI replaces seatsMargin profile: 60-70% (stable)Harvey: $195M ARR (3.9x YoY)PER-ACTION / USAGECustomer pays per unit of workExamples: Devin ACUs, OpenAI tokensBest for: variable workload buyersRisk: bill shock, slow adoptionMargin profile: 55-70% (predictable)Anthropic: $30B annualized

The fifth model (Hybrid) sits in the middle. It is base subscription plus usage or outcome overage, and it is now the most common shape for new AI companies. I cover it after the four pure plays.

Important framing before we go deeper. There is no “best” model. There is only the best model for a specific combination of buyer, workflow, and your unit economics. The job of this post is to give you a framework for picking, not a verdict on which one wins.

Per-seat: Why it is dying (and where it still works)

The instinct most founders have is to start with per-seat. It is familiar to enterprise buyers. It is easy to forecast. It is what every SaaS company you ever worked at did. And in 2026 it is the wrong starting point for almost every AI product.

The reason is structural. Per-seat pricing assumes the seat is the unit of value. When the buyer is replacing 10 seats with one AI agent, you cannot price your AI as a seat. The whole point of buying it is to not need seats. If you charge per seat, you are competing with the cost savings the customer is trying to capture. You will lose that fight.

So when does per-seat still work?

It works when the AI augments a high-cost expert and the expert is non-negotiable. Lawyers. Doctors. Investment bankers. Senior engineers in regulated industries. The buyer is not trying to fire the lawyer. The buyer is trying to make the lawyer 3x more productive. Per-seat works because the seat is the value-bearing unit and the AI is an accelerant.

Harvey AI is the canonical example. Harvey charges $1,000 to $1,200 per attorney per month. Hit $195M ARR in 2025, up 3.9x from $50M end of 2024. The buyer (a law firm) is not eliminating attorneys. The buyer is making each attorney bill more hours of substantive work and fewer hours of document review. Per-seat is the right unit because the lawyer is the value-bearing asset.

The same logic applies to a small set of expert-augmentation tools. Cursor (per-seat for individual devs) at $500M ARR. GitHub Copilot (per-seat for individual devs) at over $400M ARR. The dev is the value bearer. The AI accelerates the dev. Per-seat captures the right unit.

But notice what these companies all have in common. The seat is a high-value seat. A lawyer billing $500-$1,000 an hour can pay $1,200 a month for an AI tool that saves them 10 hours. That math works. A customer support rep at $25 an hour cannot pay $1,000 a month for an AI tool to assist them. The arithmetic falls apart.

If your buyer has cheap seats, per-seat is dead. If your buyer has expert seats and you are augmenting (not replacing) them, per-seat can still hold. But even then, in 2026 you should run it as part of a hybrid (base seat fee plus usage overage) so you do not get killed by the one customer who turns Claude into an autonomous agent and runs it 24/7.

Per-action and usage: The honest cost-pass-through

Per-action pricing (sometimes called usage-based) charges the customer per unit of work delivered. Per token. Per API call. Per document processed. Per minute of audio transcribed. The customer’s bill scales linearly with their actual consumption.

This is the model the foundation model companies use. OpenAI charges $1.75 per million input tokens for GPT-5.2. Anthropic charges $3 per million input and $15 per million output for Claude Sonnet 4.6, $5 and $25 for Opus 4.6. Anthropic hit $30B annualized in March 2026, up 14x year-over-year, on this exact model. It works for the platform layer because the platform’s cost actually does scale with usage.

It also works for products where the customer’s usage is predictable enough that they can budget for it. Devin’s Agent Compute Unit (ACU) model is a clean example. An ACU is a normalized measure of compute (VM time + inference + networking) that Devin uses to ship code. Customers buy ACU packs. They burn ACUs on tasks. The pricing reflects actual cost, with margin baked in.

The core advantage of per-action pricing is that your unit economics are basically built in. If your blended cost per action is $0.30 and you charge $1.00, your gross margin is 70% on every transaction. You cannot lose money on a customer. The worst case is you make less money than expected.

The core disadvantage is that it terrifies enterprise buyers. CFOs hate variable costs. They want a predictable monthly bill. A per-action invoice that swings 4x month-to-month is a procurement nightmare. So pure per-action works best in two scenarios.

One, you are selling to developers or technical buyers who already think in API calls (foundation model APIs, Stripe, Twilio, the entire infra layer). Two, you offer a credit-pack on top of the per-action engine so the customer pays a known amount upfront and burns it down. The Devin ACU is exactly this. So is Relevance AI’s credit model.

Three failure modes to avoid.

Don’t price per-token directly to non-technical buyers. The buyer has no intuition for what a token is worth. They will either over-buy (and feel ripped off) or under-buy (and feel throttled). Wrap tokens in a customer-legible unit (documents, agents, minutes, resolutions, whatever maps to their workflow).

Don’t set the per-action price below 2.5x your blended cost. This was the rule that came out of the Bessemer 2026 pricing playbook and it matches the unit economics math I run on every product I price. You need 2.5-3.5x to cover failed retries, support overhead, and the 90th-percentile cost month when usage spikes. Anything lower and one bad month wipes your margin.

Don’t forget to cap usage at the customer level. The Anthropic April 4 incident (cutting off third-party agentic tools) is the warning. A single customer running an agent loop overnight can burn $10K of your tokens and pay $50. Build hard caps into the contract or credit pack. No exceptions.

Outcome-based: The model with the best margins (if you can build it)

Outcome-based pricing is the model that gets the most attention in 2026 and the model that fails most often when founders try to copy it. It is also the model with the best gross margins when it works and the model with negative gross margins when it does not.

The setup is simple. The customer pays only when the AI delivers a defined outcome. Sierra charges roughly $1.50 per ticket the AI agent resolves end-to-end without human escalation. Intercom Fin charges $0.99 per resolved customer issue, $0 if the AI fails. HubSpot Breeze switched on April 14, 2026 from $1.00 per conversation to $0.50 per resolved conversation. Adobe announced outcome-based pricing for its CX Enterprise AI suite in 2026.

The companies with the cleanest outcome-pricing stories are now the fastest-growing AI companies on the planet. Sierra hit $100M ARR in 21 months and crossed $150M+ by early 2026. Half their customers have $1B+ in revenue. One in four has $10B+. Bret Taylor’s framing (which I think will be the dominant pricing philosophy of the next decade) is “salespeople get paid commission, why not the AI?”

Why does outcome-based pricing work so well?

Three reasons.

First, it solves the buyer’s biggest fear. Enterprise buyers in 2026 are not price-sensitive, they are risk-averse. They have been burned by AI pilots that did not deliver. Outcome-based pricing transfers that risk back to the vendor. The buyer pays nothing if the AI fails. That is the safest possible procurement decision, which means it closes faster than any other pricing model.

Second, it aligns the customer’s success with the vendor’s revenue. The vendor only makes money when the AI works. So the vendor has every incentive to make the AI work. The customer can feel that alignment in the sales conversation, in the implementation, in the renewal. It is a trust signal that subscription pricing cannot match.

Third, the margins are obscene if you get the success rate above 80%. Sierra’s reported gross margin is 65-75%. Why? Because the cost per attempt is fixed (compute + model calls), but the revenue scales with success. If you charge $1.50 per resolution and your cost per attempt is $0.20, your margin at 90% success is over 75%. At 70% success, it is under 50%. The slope of margin to success rate is steep, which is why the companies that win at outcome pricing become best-in-class at agent reliability.

Three preconditions you must hit before you can run outcome pricing.

The outcome must be measurable and binary. A ticket is resolved or not. A meeting is booked or not. A document is filed or not. If the outcome is fuzzy (“better marketing copy”) you cannot price on it because you cannot agree on whether it happened.

You must own the data on success. If the customer disputes the count, you lose. Sierra owns the conversation transcript and the resolution flag. Intercom owns the same. If you are running outcome pricing on a metric the customer measures themselves, you have a billing dispute waiting to happen.

Your success rate must be above 70% on day one. Below that, you lose money on every customer in the early period and your margins do not recover until you ship better models or workflows. Some companies (Salesforce Agentforce) launched at $2 per conversation regardless of resolution exactly because their success rate was not high enough to support pure outcome pricing. They got criticized for it. They were also being honest about their unit economics.

Hybrid: The model 70% of new AI companies are using

If outcome pricing has the best margins and per-action pricing has the cleanest unit economics, why are most new AI companies running a hybrid?

Because hybrid is the only model that gives you predictable revenue, captures upside on heavy users, and does not blow up if usage suddenly 10x’s. It is the safest answer in a market where unit economics are still moving fast.

The shape is: a base subscription (which guarantees revenue and access), plus a usage or outcome overage (which captures upside and prices the variable cost). The 2026 hybrid templates I see most often are these.

Hybrid pattern Base Variable component Best for Real example
Seat + usage $/user/month Tokens or actions over included quota Expert tools (legal, dev, finance) Cursor Pro $20 + Pro+ usage
Platform fee + outcome $10K-$100K/year platform Per-resolution or per-outcome Enterprise customer service Intercom Fin (platform + $0.99)
Credit pack + actions $X/month for Y credits Top-up credits at retail rate Variable usage prosumer/SMB Devin ACU packs
Subscription + agent fee $/month for the workspace $/agent/month deployed SDR, support, ops automation 11x AI ($/SDR-equivalent)
Tiered subs with usage caps $/month tiers Hard usage caps per tier Consumer and prosumer apps ChatGPT Plus / Claude Pro / Cursor

The Bessemer 2026 pricing playbook surveyed over 50 AI companies and found that the singularly-focused model is now the minority. The majority of AI companies use a hybrid that combines subscription tiers with usage-based elements, credit pools, or consumption overages. Metronome’s catalog of 50+ AI pricing models showed the same pattern.

The reason hybrid won is risk distribution. Pure subscription puts the cost risk on the vendor (who eats the overage). Pure usage puts the cost risk on the buyer (who hates the unpredictability). Pure outcome puts the cost risk on the vendor (who eats the failed attempts). Hybrid splits the risk. Buyer gets a predictable base for their procurement team. Vendor gets a margin-protecting overage for the heavy user. Nobody is unhappy in the bad case.

If you are launching a new AI product in 2026 and you cannot decide which model to use, the default answer is hybrid. Pick a base that covers your fixed cost to serve a typical customer, and pick a usage or outcome overage that covers the variable cost above that. You can always migrate to a purer model once the data shows you which one wins.

Flat-rate: The model you should run from in 2026

Flat-rate is the model where the customer pays a fixed price (say $20/month) for unlimited or near-unlimited usage. ChatGPT Plus pioneered this. Cursor Pro at $20/month uses it. Every prosumer AI app launches with it because it is dead simple to communicate.

It is also the model that destroys you fastest if you misjudge the heavy user.

The math is unforgiving. A ChatGPT Plus subscriber paying $20 a month who uses GPT-5 like a normal person costs OpenAI maybe $3 a month. The same subscriber who runs an agent loop in API mode (or routes their entire team’s queries through their account) can cost OpenAI $200 a month. The mean user is profitable. The 95th-percentile user is wildly unprofitable. And you do not get to opt out of the 95th percentile, because the heavy users are also your power users and your evangelists.

Anthropic learned this the expensive way. The April 4, 2026 cutoff of third-party agentic tools was the company conceding that the Claude flat-rate sub had become a vector for arbitrage. People were buying $20 Claude subscriptions and routing their agent traffic through them, getting $500 of compute for $20. Anthropic pulled the plug. Hard.

If you launch a flat-rate plan in 2026, you must build three things into the product on day one.

Per-user usage caps that bite. Not soft warnings. Hard limits that throttle or pause when the user crosses a threshold. The cap should be set at the 80th-percentile cost (you can support 80% of users at full speed, the heavy 20% gets throttled or pushed to a higher tier). If you are scared the cap will alienate your power users, you have your answer: those users belong on a paid tier, not a flat-rate plan.

A clear next-tier path. When a user hits the cap, they need a frictionless way to upgrade to a higher tier or pay-per-use. If the upgrade path is broken or hidden, you are converting your best users into churn risk. Cursor does this well: hit the limit on the $20 Pro tier and a one-click upgrade to Pro+ (with usage overage) is presented in the editor. Conversion is high because the friction is low.

A monitor for arbitrage patterns. Build a daily report of users whose token consumption is more than 5x the median. Most of them are legitimate power users (good, push them to a paid tier). Some are arbitrageurs running scripts. You need to identify the second group within days, not weeks, because they are bleeding your margin in real time.

If you do not have the operational maturity to run all three of these on day one, do not run flat-rate. Run a hybrid with a small included quota and clean overage pricing instead.

The unit economics math every founder must run

Pricing without running the unit economics is gambling. Here is the math that determines whether your model survives contact with real customers. I run this for every product I price, and it has caught fatal pricing flaws four times in the last 18 months.

The 5-Step Unit Economics Check1Blended cost per unitcost = inference + tools + overheadTokens (input + output) × rate+ tool calls + storage + monitoring2Success rate adjustmenteffective_cost = cost / success_rateIf 80% success, effective cost = cost ÷ 0.8Failed attempts cost the same as successes3Price floor (2.5-3.5x)price >= effective_cost × 2.5Covers retries, support, peak months3.5x for high variance workloads4Margin sensitivity testmodel usage at p50, p90, p99Heavy user shouldn’t break modelSet caps where p99 hits 0% margin5Model cost decline checkrecheck at -50% inference costInference is dropping 10x/yearMake sure you can lower price tooIf model survives all 5 checks, you have a defensible priceMargin holds at p90 usage, recovers at lower inference costs, and pays for failed retries

Let me walk through a concrete example. Say you are pricing an AI agent that drafts pull-request reviews for engineering teams.

Step 1: Blended cost per review. Each review uses roughly 8,000 input tokens (the diff plus context) and 1,500 output tokens (the review comments). At Claude Sonnet 4.6 rates ($3/M input, $15/M output), that is $0.024 + $0.0225 = $0.047 per review. Add a tool call for static analysis ($0.01) and infra overhead ($0.01) and you are at $0.067 per review.

Step 2: Success rate. Say the agent is usable on 75% of reviews (the other 25% need human follow-up). Effective cost = $0.067 / 0.75 = $0.089.

Step 3: Price floor. 2.5x is $0.22. 3.5x is $0.31. Pick a number in that range. Let’s say $0.25 per review (or wrap into a $99/month plan that includes 400 reviews).

Step 4: Margin sensitivity. If a heavy team submits 1,000 reviews a month against your $99 plan, your effective price is $0.099 per review against an effective cost of $0.089. Margin is 10%. That is too thin. Either raise the cap or raise the plan price. If a typical team uses 200 reviews, your effective price is $0.495 per review against $0.089 cost, margin is 82%. Comfortable.

Step 5: Model cost decline. Inference is dropping roughly 10x per year. In 12 months, your $0.067 cost will be closer to $0.007. Your $0.25 price now has 97% margin. You can drop price to $0.05 and still make 86%. That gives you ammunition for competitive moves later. Build the plan with that decline in mind.

The teams that skip this math end up either pricing too low (and watching their best customers destroy their margins) or pricing too high (and losing deals to competitors who did the math). The teams that run it have a price they can defend in front of any customer.

How to pick your model in 60 minutes

Here is the decision framework I run with founders when they cannot decide which revenue model to use. It takes about 60 minutes to run honestly. Most people lie to themselves on at least one of these and that is exactly why they pick the wrong model. So answer each question with the answer your customers would give, not the answer you wish was true.

The 5-Question Pricing Decision TreeQ1: Is the outcome binaryand measurable by you?NoYesQ2: Is buyer a high-valueexpert (lawyer, dev, etc)?Q3: Is your successrate currently >= 70%?NoYesNoYesQ4: Is usagehighly variable?Per-seat hybrid:$/user + usage overageHybrid: platform fee+ per-attempt chargePure outcome$/resultNoYesFlat-rate+ hard capsPer-action orcredit pack hybridDefault to hybrid if any answer is uncertain. You can move to a purer model once usage data is in.Run unit economics math (5-step check) before committing to any terminal answer.

Q1 is the gate. If you cannot measure the outcome cleanly, outcome pricing is off the table. Period. I have seen four founders try to run “outcome pricing” on metrics they could not actually measure (like “leads generated” when the customer wouldn’t share their CRM). Every one of them ended up in billing disputes within 90 days.

Q2 is the seat-vs-no-seat decision. If your buyer has high-cost expert seats and you augment those experts, per-seat hybrid is your best move. If your buyer has cheap seats or is replacing seats with your AI, kill per-seat immediately.

Q3 is the brutal honesty test. If your success rate is below 70%, you cannot run pure outcome pricing without losing money on every customer. You can run hybrid (platform fee that covers your fixed cost plus a per-attempt charge that limits your downside) until your success rate climbs.

Q4 splits the remaining cases. Highly variable usage means flat-rate will kill you. Predictable usage means flat-rate is safe.

Run this for 60 minutes. Be honest. The answer might be “hybrid with these specific components” rather than a pure model. That is fine. The point is to land on a defensible structure, not the most elegant pure model.

The contrarian take: most pricing advice is wrong for early founders

Here is what almost every pricing playbook gets wrong, including the better-known ones.

They optimize for the steady-state business with thousands of customers and predictable usage data. You do not have that. You have 12 customers (or zero), no usage data, and a model whose success rate you can only estimate. The pricing decisions you need to make in that state are different from the decisions a $50M ARR company is making, and most pricing advice does not acknowledge this.

Three things I push back on whenever a founder cites Bessemer or Reforge or anyone else’s pricing playbook.

“Outcome-based pricing is the future” is true and unhelpful. It is the future for a specific subset of AI products with a specific maturity level. It is not the right starting point for most founders. Sierra got to outcome pricing after they had a 70%+ success rate on day one. They had a 70%+ success rate because the founders had been running this exact problem at OpenAI for two years. If you have 60% success on day one, outcome pricing puts you out of business by month three.

Start with hybrid. Specifically, a low base subscription (to cover your fixed cost and signal to the buyer that you are a real company) plus a usage or per-attempt component (to cap your downside). Migrate to outcome pricing only when your success rate is consistently above 75%. The path is more important than the destination.

“Anchor your price 30% below the next-cheapest competitor” is bad advice for AI. Anchoring at a low price tells the buyer you are commodity. It also makes the upgrade conversation harder later. The right move in AI is to price at parity or slightly above the closest competitor and put your differentiation in the success rate, the integration depth, or the outcome guarantee. Buyers in 2026 are not looking for the cheapest AI, they are looking for the safest AI. Cheap signals risk.

The exception is when you are explicitly attacking a horizontal incumbent with a vertical specialization. Then anchor below them on price and above them on outcome. That is the Harvey playbook. Charge per attorney less than a generic legal-AI tool would, but ship 10x better legal accuracy. The price-quality positioning is what wins, not the absolute number.

“Charge what the market will bear” is dangerous in 2026. The market will bear a high price right now because enterprises are still in adoption mode and unit economics are still being figured out. That window is closing. Adobe, Salesforce, HubSpot all repriced toward outcome models in 2026 because the market repriced first. If you set a high price now without a path to lower it as inference costs drop, you will get repriced by your customers next year.

The smarter move is to set a price that gives you 70%+ margin at today’s costs and build into the contract a benchmark that adjusts price as model costs drop. Keep the discount in the customer’s pocket as long as possible. Trust will be your moat in 2027 and 2028, not price.

The thing nobody tells you: pricing is a product feature in AI, not a finance task. The pricing model shapes the buyer’s mental model of what they are buying. Per-seat says “this is software.” Per-action says “this is infrastructure.” Outcome says “this is a service.” Customers behave differently in each frame. Pick the frame you want them to be in, then build the pricing to match.

What to do Monday morning

If you are pricing an AI product and you do not know if your model is right, here is the 7-step audit to run before Friday.

  1. Pull your top 10 customers’ usage data. Look at the p50, p90, and p99 of usage per customer. If your top user is more than 10x the median, your pricing is leaking margin. Pause and check.
  2. Run the 5-step unit economics math on a typical customer. Blended cost, success rate adjustment, 2.5-3.5x price floor, sensitivity test, model cost decline check. Most founders skip steps 4 and 5 and that is where the bombs are.
  3. Identify your binary outcome. Even if you do not run outcome-based pricing, you should know what counts as a “success” for the customer. Document it. Measure it. It will become the basis for case studies, pricing migrations, and renewal conversations.
  4. Map your buyer’s reference price. What did they pay for the previous tool? What does the manual labor cost? What is the next-cheapest AI option? You need to know all three numbers before any pricing conversation.
  5. Build the migration plan. If you are starting with hybrid (which most should), document the conditions under which you would shift to outcome pricing. Specific success rate threshold, customer cohort, contract length. Pre-decide.
  6. Set hard usage caps. Pick a number that throttles the 95th-percentile user. Tell the customer about it in the contract. The clarity is good for both sides.
  7. Stress-test against AI cost decline. Run your unit economics at 50% of today’s inference cost and at 25%. Make sure you have a price floor that survives the next year of model cost drops.

If the audit surfaces a problem, the fix usually takes one or two weeks of work. Better to find it now than after a year of subsidizing your heaviest users.

Frequently asked questions

Should I use freemium for my AI product?

Freemium works in a narrow band. It works for consumer AI products where viral growth is the GTM motion (chatbots, generators, prosumer tools). It does not work for B2B AI products where the buyer is procurement and the user is an employee. The free tier in B2B does not convert to revenue, it just trains the buyer to expect the price to be lower. If you must offer a free tier, make it heavily limited (one workflow, one workspace, one user) and ensure the upgrade trigger is functional, not just a usage cap. The Cursor model (free tier with hard message limits, then $20 Pro, then Pro+ with usage overage) is the cleanest 2026 freemium template.

How do I price an AI agent vs a copilot?

Copilots augment a person. Price them per-seat or per-seat hybrid. The seat is the value-bearing unit. Agents do work autonomously. Price them per-action, per-outcome, or hybrid. The unit of work is the value-bearing unit. The mistake is pricing an agent like a copilot (per-seat). The buyer does not have the seat anymore. They have the work output. So the price has to be for the work, not the access.

What gross margin should I target for an AI product?

60% on day one is the floor. 70-75% is the realistic ceiling for the first 18 months. 80%+ is achievable in years 2-3 as inference costs drop and you optimize prompts, caching, and routing. Anything below 50% is a structural problem, not a temporary phase. If your model says you cannot get to 60% with your current pricing, your pricing is wrong (or your costs are too high, often because you are not using the cheapest model that meets quality).

Should I bill in tokens or a customer-friendly unit?

Almost always a customer-friendly unit. Tokens are a developer concept. Documents, agents, minutes, resolutions, runs, conversations, transactions, those are customer concepts. If you are selling to developers (foundation model API, dev tools, infra), tokens are fine. If you are selling to anyone else, wrap the tokens in a unit that maps to their workflow. The pricing math is the same. The conversation is dramatically easier.

How often should I reprice?

Once a year for B2B contracts (renewal cycle). Twice a year for consumer products. Continuously for usage-based components (the per-action rate should track inference costs and your success rate). The big strategic repricing (changing the model itself, not the rate) should happen when the unit economics or the market shifts. Sierra, Salesforce, HubSpot, Adobe all repriced strategically in 2026 because the market shifted. You will know when it is time, your customers will tell you in renewal conversations.

What is the worst pricing mistake AI founders make in 2026?

Picking a model that does not match the unit of value the customer is buying. Specifically, charging per-seat for AI that replaces seats. The buyer is trying to consolidate seats. You are charging them as if seats are still the unit. The misalignment is so visible that smart buyers will not even take the meeting. The second worst mistake is unbounded flat-rate. Both are killable in the same month with a hybrid restructure.

Is outcome-based pricing too risky for an early-stage startup?

Yes, almost always. Outcome pricing requires a success rate above 70% to break even. Early-stage startups rarely have that level of reliability on day one. The right move is to start with hybrid (platform fee that covers fixed cost + per-attempt charge that limits downside) and migrate to outcome pricing once the success rate clears 75% consistently. Sierra, Intercom, and HubSpot all built up to outcome pricing. None of them launched with it on day one.

How do I know if my pricing is wrong?

Three signals. First, your top users have radically lower effective rates than your median users (margin leak). Second, your sales cycles are dragging because the buyer cannot map your price to a value they understand (positioning failure). Third, your renewals come in at a discount even when usage grew (anchor problem). If you see one of these, run the 5-step unit economics math this week. If you see two, restructure within the month.

This post is part of the AI-native founder series. If you are pricing your AI product, you will probably also want to read:

If you want my pricing audit template (the 5-step unit economics check as a spreadsheet) sent over, find me on X at @vikasmalpani and ask. Free, no list.