Seat-Based AI Pricing Fell To 15%. Here Is What To Charge Instead.
Seat-based AI pricing fell from roughly 21% to 15% of vendors in a single year, and Futurum's 1H 2026 buyer survey found fewer than one in five buyers still prefer classic per-user deals. Here's how a first-time founder should actually pick between seats, usage and outcomes.
Seat-based pricing fell from roughly 21% of AI vendors to 15% in a single year. That isn't a trend piece. That's a category repricing itself while most first-time founders were still arguing over $29 or $49 per user per month.
Here's what sits underneath it. Futurum Research's 1H 2026 Enterprise Software Decision Makers survey found 43% of buyers prefer consumption-based pricing and 27% prefer outcome-based structures. Fewer than one in five still want classic per-user pricing. Futurum's May 12, 2026 write-up said the quiet part out loud: vendors stuck on seat-only pricing now risk getting cut before the demo.
The public companies moved first. Intercom's Fin charges $0.99 per resolution. No resolution, no charge. Zendesk announced outcome-based pricing for its AI agents on August 28, 2024, billing automated resolutions instead of AI seat licenses. Salesforce launched Agentforce at $2 per conversation, then added Flex Credits in May 2025 at about $0.10 per action.
So. You're a founder with a first product, four customers, no pricing page. What do you actually do on Friday?
Why do seats stop working when the software does the work?
Seats price access. They assume a person logs in, does the job, and the software helps them do it faster. That worked for twenty years because headcount was a decent proxy for value delivered.
AI breaks the proxy. If your product resolves the ticket, drafts the contract, or reconciles the invoice, then the better it gets, the fewer people your customer needs. Price per seat and you've built a company that earns less as it works better. a16z made this exact point in its December 2024 enterprise newsletter, using Zendesk's roughly $115 per agent per month: once AI handles resolution, the natural unit is the resolution. They carried the argument into Big Ideas 2026.
Buyers caught on. Procurement is asking why they're renewing 40 licenses when six people log in and a bot handles the rest.
But seats aren't dead. If your product amplifies a human and value scales with headcount (design tools, shared workspaces, anything collaborative), seats are still the cleanest thing on earth to sell. If your software replaces the work instead, seats will cap you.
The three models you're actually choosing between
There are three. Everything else is a remix.
Per seat. Predictable, forecastable, easy for procurement to approve. Fine when humans do the work.
Usage. You bill per unit of work: documents processed, minutes transcribed, credits burned. Revenue tracks cost, which protects margin. Buyers hate the unpredictability.
Outcome. You bill only when the thing the customer wanted actually happened. Alignment is beautiful. Operations are brutal.
| Model | You get paid when | Best when | Where it hurts |
|---|---|---|---|
| Per seat | A person has access | Headcount tracks value | Your product removes headcount |
| Usage | Work gets consumed | Buyers can forecast volume | Bill shock, lumpy revenue |
| Outcome | A defined result occurs | The result is countable | Attribution and failed attempts |
| Base plus usage | Both | Almost always, in 2026 | Harder to explain on one page |
The real read: outcome pricing sounds like the obvious answer right up until you have to define the outcome, attribute it, defend it in a billing dispute, and swallow the inference cost of every attempt that failed.
The margin trap nobody warns you about
Your cost of goods is variable now. Your price probably isn't. That gap is where first-time founders quietly go broke.
Classic SaaS ran at 80% to 90% gross margin because one more customer cost roughly nothing. AI-native companies commonly land in the 50s and 60s, because every request burns inference. Sell a flat $200 per month plan, watch one power user run 900 agent tasks in March, and you've paid for the privilege of serving them.
So model it before you publish. Not a five-year forecast. One page: cost per unit of work, expected units per customer per month, and what happens at your 95th percentile customer rather than your average one. The average customer never breaks your pricing. The heaviest one always does. You can do this in a spreadsheet, or in a planning tool like Foundra that has templates for exactly this kind of unit-economics work.
Two rules I'd hold. Never pass model price changes through one to one; you'll wreck your own pricing power. And put a fair-use ceiling on any flat plan from day one, because adding one later reads as a price increase to everyone already over the line.
Your AI co-founder is ready when you are.
Foundra turns everything in this article into an actual plan. Validation, customers, pricing, launch. In one place, in your voice, in an afternoon.
Get started→$39/month. Cancel anytime.
How do you pick an outcome unit nobody argues about?
Use the dispute test. Look at the line item on the invoice and ask whether a reasonable customer, on a bad Monday, would argue with it. If yes, pick a different unit.
Intercom's resolution passes because both sides can see it in the transcript. Zendesk goes further, using a quiet period after closure so a reopened ticket doesn't count. Salesforce's per-action credit passes because an action is a logged event with a timestamp.
Bad units, for reference:
- "qualified lead" (whose definition, yours or their SDR's?)
- "hours saved" (measured against which baseline?)
- "revenue influenced" (that's a lawsuit with a price tag)
- "engagement" (no)
- "productivity gain" (also no)
Four properties a workable unit has: your system logs it, the customer sees it in near real time, counting it needs no human judgment call, and it fails closed. That last one matters most. If you're not certain the outcome happened, don't bill it. Being generous on a $0.99 line item is cheaper than an hour on Zoom defending it.
Why a base fee plus usage keeps beating the pure models
The companies growing fastest in 2026 mostly aren't picking one. They stack: a base platform fee, then usage or outcome on top. Futurum's May 2026 note lists Adobe, Salesforce, ServiceNow, UiPath and Automation Anywhere all running some version of the blend.
The reason is structural. The base fee covers your fixed cost of serving the account and gives you revenue you can forecast. The metered layer means you grow when the customer gets more value, without reopening the contract. And it hands the buyer a floor and a ceiling to take to their CFO, which is the actual objection you're solving.
My bias, and it is a bias: for a first product, base plus metered is right maybe 80% of the time. Pure outcome pricing is a strong move once you know your success rate cold. Before that, you're writing a check against a number you've never measured.
What do you charge when you have zero pricing data?
You charge anyway. Free pilots teach you a lot about product and almost nothing about willingness to pay.
Five things that work when you have no data:
- Charge from customer one. A paid $500 pilot tells you more than ten free ones.
- Sell to a person, not a committee. Find the individual whose number your product moves and who controls a budget line. Committees benchmark you against incumbents; individuals compare you to their own pain.
- Anchor on the alternative. What does this customer spend today doing it badly? Contractors, an ops hire, a competitor's tool. Your price is a fraction of that, not a multiple of your costs.
- Quote ranges, close on calls, publish later. For the first ten or fifteen customers, price on the phone. Four conversations beat four months of A/B tests.
- Raise prices. If you're winning nearly every deal without pushback, you're cheap. Raise for new logos, grandfather the old ones for a renewal cycle, say it once in writing with a date.
Stop copying a public company's pricing page when you have four customers
This is the specific mistake, and it's close to universal.
Intercom's $0.99 works because they know their resolution rate across an enormous volume of conversations, so they know their margin per outcome. You don't know yours. Salesforce prices Agentforce against an installed base it's defending; you have nothing to defend. Their pricing encodes a sales org, a brand, a cost structure and years of data you do not have.
Copy the structure. Never the numbers.
What to actually do this week
- Write down the single unit of work your product does that a customer would call valuable. One line.
- Pull your last 30 days of inference and infrastructure spend, divide by that unit. Now you know your floor.
- Apply the dispute test. Say the unit out loud to someone outside your company. If they ask a clarifying question, it fails.
- Draft a two-tier page: a base fee covering your cost to serve, plus a metered layer at three to five times unit COGS. Add a fair-use ceiling.
- Call four prospects. Read them the price. Watch the pause. A long pause means roughly right; an instant yes means cheap.
- Ship it.
- Set a reminder 90 days out to revisit, because you'll be wrong and that's fine.
Frequently asked questions
Should I just copy Intercom and charge per resolution?
Only if you can define your outcome as tightly as they define theirs and you know your success rate. There are millions of conversations behind that $0.99. If you can't tell a customer in writing exactly what triggers a charge, you're not ready.
Is per-seat pricing dead?
No. Going from around 21% to 15% of AI vendors in a year is a decline, not an extinction. Seats still work when a human does the job and value tracks headcount. They break when your product does the job instead.
How big should the base fee be?
Big enough to cover your cost of serving that account, including support, before a single metered unit. For most early B2B products that's $200 to $2,000 a month depending on the buyer. If the base doesn't clear the floor, every new customer makes your P&L worse.
What if a usage bill spikes and the customer is furious?
Credit it the first time, then fix the pricing. Bill shock in month three kills more accounts than a higher headline price ever has. Build spend alerts and a monthly cap before you need them.
Can I change my pricing model later?
Yes, and you will. Grandfather existing customers through one renewal, announce the change once with a date, and never let anyone discover it from an invoice. Repricing is normal; surprising people is not.
You just read the theory. Ready to build the thing?
Foundra is your AI co-founder. It turns an idea into a validated business plan, a go-to-market, and your first 10 customers. In an afternoon, not a semester.
$39/month. Cancel anytime. Works in 20 languages.