AI Agents Don’t Buy Seats—Why Your Pricing Should Follow Suit In the past 12 months, a clear pattern has emerged: as AI systems replace manual effort with automated intelligence, pricing structures tied to “seats” no longer reflect the value customers receive. Pricing models have surfaced as a hot topic with every portfolio company at Mosaic Ventures and is top-of-mind for nearly every founder building applied-AI products. When one person and an AI agent can outperform an entire legacy team, charging per user starts to feel arbitrary; what matters is how much business impact the product delivers. Founders are experimenting with three broad approaches: 1. Usage-metered plans that bill against tokens, API calls, or minutes of inference time. These create a direct bridge between consumption and margin and nudge teams to track cost from day one. 2. Outcome-based pricing that charges per lead booked, ticket resolved, or document drafted—tying revenue to measurable results. It’s the software analogue of value-based care. 3. Hybrid “starter bundle plus runway” tiers: a predictable monthly fee with a healthy allowance of AI credits, then pay-as-you-go beyond that. This balances budget certainty for customers with upside capture for the vendor. Across our portfolio, a few design principles keep showing up: 1. Anchor on a metric the customer already tracks. If your product shortens sales cycles, price per opportunity accelerated—not per login. 2. Bundle enough volume to eliminate credit anxiety. No one wants to ration prompts. 3. Expose real-time usage. Transparent dashboards prevent bill shock and build trust. 4. Instrument cost early. Metering and billing belong in the product backlog, not the finance queue. 5. Plan for non-linear jumps. When a model upgrade multiplies compute, re-grade tiers before your gross margin does it for you. AI’s promise is to shift human effort from repetitive execution to higher-order creativity. If our pricing still counts bodies instead of business results, we undermine that promise. The companies that map price to outcomes—while keeping the buying experience refreshingly simple—will capture the most upside. I’d love to hear how others are managing the move from seats to usage and outcomes. What’s working, what still feels messy, and where do you see the biggest opportunities to innovate on pricing? #appliedAI #pricing #startups
Adaptive Pricing Models
Explore top LinkedIn content from expert professionals.
Summary
Adaptive pricing models are modern strategies that adjust prices based on how customers use products, the outcomes they achieve, or a mix of usage and access, rather than simply charging per person or seat. This approach helps balance business goals with customer needs, especially as AI and automation change how people interact with software and services.
- Choose relevant metrics: Set your pricing based on metrics your customers already track, such as workflow volume or business impact, to make charges feel fair and transparent.
- Offer flexible plans: Combine predictable base fees with usage-based or outcome-based tiers to accommodate different needs and help customers manage their budgets.
- Monitor cost patterns: Regularly review how your highest and lowest users impact costs to adjust pricing and avoid margin surprises as usage evolves.
-
-
Having founded two SaaS companies (Statista and ECDB), I've watched pricing models evolve from simple seat-based subscriptions to something far more nuanced. Today, I want to share my findings on what pricing model works for many SaaS companies, and what we’ve learned. Seat-based pricing means you buy x seats, use 70-80% actively, and everyone gets tool access. Simple. But the world has changed. Today, data flows through multiple channels, which means a seat does not reflect actual usage anymore. Data can now be accessed in various ways: 📈 Direct API integrations with BI tools 🤖 AI assistants answering ad-hoc questions 🖥️ Automated workflows pulling market data daily 🧑💻 MCPs (APIs for LLMs) enabling new use cases A single developer might automate queries for an entire organization. Ten analysts may share one dashboard but rarely log in. Why should they all pay the same? It doesn’t make sense. According to an OMR/hy study, usage-based pricing adoption in SaaS jumped from 31% to 67% in just two years. The reason? AI and automation are making per-seat models obsolete. When one employee can automate what previously required five, charging per seat doesn't reflect value delivered. The software’s true value comes from enhancing efficiency, output, or outcomes, not the headcount. That is why we at ECDB are moving to a hybrid model: platform access + consumption credits. 👇 Here's our approach: 1. Platform tiers remain - You still choose a plan based on team size and features needed. 2. Credits introduced - Each plan includes base credits for downloads and light API usage. Heavy automation requires add-on credit bundles with volume discounts. 3. Fair pricing across channels - Whether you access a data point via xls, API call, or AI query - same credit cost. No more arbitrary pricing based on how you access the data. We found that this model works best for us right now. I welcome feedback from our customers, other SaaS founders, and industry experts. Are you seeing similar shifts in your products?
-
Seat-based pricing is dying faster than most CEOs realize. 12 months ago: 50% of B2B SaaS used flat or seat-based models Today: Down to 27% Projected 2027: <10% The shift? 41% of companies are now using hybrid pricing models. At SaaS Metrics Palooza, I walked through why this is happening, and the framework we use to build hybrid models that actually work. Here's the reality: AI changed who does the work. It's not just humans anymore. It's systems completing tasks, generating summaries, resolving tickets, approving requests, all autonomously. So how do you charge for that? By the person? The product? The outcome? Answer: It depends on who's doing more of the work. The BAM Framework - Base, Allowance, Meter These 3 layers create 5 different hybrid pricing models: 1/ Access Tiers (Base only) - Different AI complexity per tier, fair usage policy 2/ Flat + Unit (Base + Meter) - Platform fee + outcome-based hybrid pricing 3/ Flat + Limit + Unit (All 3 layers) - Most popular hybrid, includes volume + overages 4/ Credit-Based (Base + Allowance) - PLG favorite hybrid, but don't fall into cost-plus trap 5/ Pay-As-You-Go (Meter only) - Pure consumption, AI infrastructure The pattern from 400+ transformations: Companies using Flat + Limit + Unit (Model 3) are seeing the most traction. Why? It gives customers predictability (base fee + included volume) while capturing expansion value (usage after allowance). But, and this is critical, you need safety mechanisms. → Predict usage (dashboards, estimators) → Prevent surprises (match reset timing to contracts) → Protect customers (caps, true-up options, don't penalize usage) The companies winning with hybrid pricing aren't just picking a trendy model. They're designing the model that fits how their AI actually creates value. Based on Tremont's research: Hybrid models are capturing 3-4x more expansion revenue than traditional seat-based pricing. The question isn't "should we go hybrid?" It's "which hybrid model fuels OUR growth?" Which model fits your product? Person doing the work or product doing the work?
-
If you’re still pricing #GenAI like SaaS, you’re not “innovating” — you’re gambling with your margins. AI-enabled business models are just emerging, but a recent article from Bessemer Venture Partners, "AI Pricing & Monetization Playbook" (in the first comment) nails the core shift: AI doesn’t monetize access; it monetizes outcomes — in a world where every token (and human-in-the-loop) has a real COGS line item. Practically speaking, start with the business model you’re really building: Copilot vs. Agent vs. AI-enabled Service → different economics, different charge metrics. Then pick a charge metric as a strategic choice (consumption → workflow → outcome): tighter value alignment means you’re taking on more cost risk. Next, use hybrid pricing (base + usage/outcome tiers) to balance predictability with upside. Finally, test value-first, then “find the price through friction” (if it’s an instant yes, it’s probably too low). Most importantly, treat pricing as your operating model: it shapes sales motions, CS incentives, what you measure, and how you scale from 10 to 1,000 customers. This resonates strongly with what I’ve been seeing in my research and in the classroom at The Wharton School: in AI-enabled business models, pricing isn’t a “packaging” decision—it’s where strategy, unit economics, and organizational design meet. #AI #GenAI #Pricing #Monetization #BusinessModels #UnitEconomics #GoToMarket #SaaS #Wharton
-
$7,225 for one day of coding. And Cursor isn't even the worst example. Replit's margins went negative. Anthropic throttles its best users. I mapped pricing across 50 AI startups. Six distinct patterns emerged. The core tension: traditional SaaS has near-zero marginal cost per user. AI products pay for compute on every interaction. A casual Claude user costs pennies. A developer running Claude Code all day costs tens of thousands per month. Your best users are your most expensive users. That tension is breaking every pricing model in the market. Cursor charged a flat 500 requests/month. Worked fine until users leaned into multi-step agent workflows. They switched to credit pools. One developer burned 500 requests in a single day. The plan description changed from "Unlimited" to "Extended" twelve days after launch. Replit grew 15x in ten months ($16M to $252M ARR). But they were buying revenue with compute. When they launched a more autonomous agent, margins crashed to negative 14%. They had to invent "effort-based pricing" mid-flight. Anthropic played it differently. Their $17/$100/$200 tiers map to genuinely different user personas, not volume bands. A casual user and a Claude Code developer are different products with different willingness to pay. The lesson across all 50 companies: before you set any price, pull the cost distribution. What does your P10 user cost? P50? P90? If the ratio exceeds 10x, flat pricing will break. In AI products, it almost always exceeds 10x. Full guide with all 6 models, 4 case studies, and a decision tree: https://lnkd.in/gdKaQSMk
-
Selling to ENT without changing your pricing model is like showing up to a black-tie event in flip flops. MM pricing models don’t survive in enterprise sales. Why? Because selling 1,000 licenses to an enterprise isn’t 20x harder than selling 50 - but if you don’t adjust your pricing strategy, it will be 20x more painful. Enterprise buyers don’t think in per user terms. They think in budgets, forecasts, and cost centers. They want predictability, not a CPQ nightmare where they’re adjusting seat counts every quarter. If you’re moving upmarket, here’s how to avoid looking like a tourist at the grown-ups’ table: 1. Kill per-user pricing for large accounts. Enterprise CFOs see per-user models as a ticking time bomb...every new hire adds cost. Instead, sell in committed tiers, annual volume contracts, or all-you-can-eat licenses. - Instead of “$50 per user, per month,” structure it as, “$X for up to 1,000 users.” - Price for usage, not headcount - think storage, API calls, transactions, etc. 2. Enterprise doesn’t “expand naturally.” Build in expansion from day one. For MM, you can land small and grow. Enterprise doesn’t work that way. - Ramp pricing: Year 1 at 60%, Year 2 at 80%, Year 3 at 100%. Predictable growth, no CFO freak-outs. - Auto-expansion clauses: If usage exceeds X%, licenses auto-scale. Protects you from procurement pulling a “we’ll just add seats later” stunt. 3. Enterprise buyers expect to “win.” Give them a win - without losing. These buyers are trained to negotiate. They want a lower per-unit cost, but they’ll commit bigger dollars to get it. - Introduce an ENT Rate...lower per-unit cost, but higher minimum commit. CFOs love “efficiency,” and you get more ARR locked in. - Structure custom packaging that makes them feel special. Limited access to beta features, priority support, or bundled services. Want to win in enterprise? Stop selling like an SMB rep. Price for scale, control the expansion, and let procurement “win” on terms that make your CFO smile.
-
If your AI replaces five people, your pricing model should too. Ashu and Jaya wrote about a shift playing out across four stages: → Seat-based: Still common, but misaligned when usage varies or value spikes. Harvey charges law firms roughly $1k per lawyer per year. But during renewal conversations no one’s talking about seats. The value is framed around hours saved, not user count. → Usage-based: Metered by tokens or queries - easy to track, but not always easy for buyers to understand the value. Bland, a voice AI platform, prices by minutes spoken. That’s clean and defensible, but it creates a paradox: the more efficient the AI becomes, the shorter the calls, and the smaller the bill. → Workflow-based: Pricing tied to jobs done, like documents reviewed or tickets resolved. Customers like the predictability of workflow-based pricing. And vendors get tighter alignment between usage and value, but defining and measuring “a completed job” reliably can be challenging. → Outcome-based: Directly linked to business impact (if you can deliver results reliably enough) This model sounds ideal in theory, but most startups aren’t there yet. You have to be able to deliver results predictably to make it work. The variability of sales outcomes across industries, buyer types, and internal processes is why many AI SDR tools still fall back on task-based models, charging per email or call instead of per closed deal. Bottom line: Pricing models that reflect real-world value are starting to resonate. Curious to know, what pricing shifts are you seeing in your corner of the market?
-
SaaS pricing expertise should be valued in virtually every other industry. Why? For one, savvy SaaS pricers understand time sensitivity ⏱️ and long-term value/cost scaling dynamics 🎯. They anticipate shifts in cost-to-serve and value delivered and pre-plan pricing accordingly—through add-ons, tiering, or metered models. Here's a classic "SaaS" challenge from James D. Wilton's "Capturing Value": "𝗔 𝗳𝗲𝗮𝘁𝘂𝗿𝗲 𝘄𝗵𝗶𝗰𝗵 𝗵𝗮𝘀 𝗮 𝘃𝗲𝗿𝘆 𝗵𝗶𝗴𝗵 𝘂𝘀𝗮𝗴𝗲 𝗰𝗼𝘀𝘁 𝗺𝗮𝘆 𝗺𝗮𝗸𝗲 𝘆𝗼𝘂𝗿 𝗽𝗮𝗰𝗸𝗮𝗴𝗲 𝘂𝗻𝗽𝗿𝗼𝗳𝗶𝘁𝗮𝗯𝗹𝗲 𝗶𝗳 𝘂𝘀𝗮𝗴𝗲 𝗲𝘅𝗰𝗲𝗲𝗱𝘀 𝗮 𝘁𝗵𝗿𝗲𝘀𝗵𝗼𝗹𝗱 𝗹𝗲𝘃𝗲𝗹, 𝗮𝗻𝗱 𝗶𝗳 𝘁𝗵𝗲 𝗽𝗿𝗶𝗰𝗲 𝗼𝗳 𝘁𝗵𝗮𝘁 𝗽𝗮𝗰𝗸𝗮𝗴𝗲 𝗱𝗼𝗲𝘀𝗻’𝘁 𝘀𝗰𝗮𝗹𝗲 𝘄𝗶𝘁𝗵 𝘂𝘀𝗮𝗴𝗲. 𝗧𝗵𝗲𝗿𝗲𝗳𝗼𝗿𝗲, 𝗶𝘁 𝘄𝗼𝘂𝗹𝗱 𝘂𝘀𝘂𝗮𝗹𝗹𝘆 𝗺𝗮𝗸𝗲 𝘀𝗲𝗻𝘀𝗲 𝘁𝗼 𝗯𝗿𝗲𝗮𝗸 𝗼𝘂𝘁 𝘀𝘂𝗰𝗵 𝗳𝘂𝗻𝗰𝘁𝗶𝗼𝗻𝗮𝗹𝗶𝘁𝘆 ... 𝗶𝗻𝘁𝗼 𝗮𝗻 𝗮𝗱𝗱-𝗼𝗻 𝘀𝗼 𝘁𝗵𝗮𝘁 𝗶𝘁 𝗰𝗮𝗻 𝗯𝗲 𝗺𝗼𝗻𝗲𝘁𝗶𝘇𝗲𝗱 𝗮𝗽𝗽𝗿𝗼𝗽𝗿𝗶𝗮𝘁𝗲𝗹𝘆, 𝗮𝗻𝗱 𝗺𝗮𝗸𝗲 𝘀𝘂𝗿𝗲 𝘁𝗵𝗮𝘁 𝗰𝗼𝘀𝘁𝘀 𝗮𝗿𝗲 𝗰𝗼𝘃𝗲𝗿𝗲𝗱." 𝗧𝗵𝗲 𝗟𝗲𝘀𝘀𝗼𝗻 𝗕𝗲𝘆𝗼𝗻𝗱 𝗦𝗮𝗮𝗦 This isn’t just a SaaS problem—it’s a cost-to-serve problem. Across industries when pricing doesn’t flex with shifting customer behaviors, profits can vanish. From CPG to Manufacturing to Business Services, from freight and returns and MOQs to high-complexity SKUs and high-touch Customers ... costs to serve are rarely well accounted for. 📉 The issue? Most companies—especially in the middle market—price based on what’s known today from backward-looking data. Then they miss the economic value of key terms. ❌ They ignore how time can compound an "unexpected" cost-to-serve. ❌ They allow pricing or costs loopholes to erode profitability. ❌ They assume "this is just the cost of doing business"—until margins dive. ❌ They hesitate to challenge customers, hoping next quarter / year the problem will get smaller. 𝗟𝗲𝘀𝘀𝗼𝗻𝘀 𝗳𝗿𝗼𝗺 𝗦𝗮𝗮𝗦 for other industries: 𝗣𝗿𝗶𝗰𝗲 𝗳𝗼𝗿 𝘁𝗵𝗲 “𝗪𝗵𝗮𝘁 𝗜𝗳𝘀” ✅ Segment customers by value and cost-to-serve and build pricing models that account for long-term shifts. ✅ Use add-ons, tiers, surcharges or metered pricing to align with cost-to-serve & scaling value. ✅ Implement clear terms or tiered pricing to prevent cost-to-serve creep. ✅ Leverage rebates to reward customers who optimize behaviors and outcomes. ✋ Some of the best SaaS pricing books (shoutout to Marcos Rivera, James D. Wilton, Ulrik Lehrskov-Schmidt) teem with lessons that apply far beyond SaaS and tech. Getting the "what ifs" right isn't just about protecting margins—it’s about anchoring right who pays for outlier costs or value delivered. Because once your terms are set, customers won’t easily agree to make you whole later. ➡️ ➡️ What failure to plan for what-ifs do you see in your industry's pricing? Would thinking with your SaaS hat on help? #PricingStrategy #SaaS #CostToServe #ValueBasedPricing #Profitability
-
AI pricing is broken, and everyone knows it. Orb just analyzed 66 AI companies and found something interesting: 𝟗𝟐% 𝐡𝐚𝐯𝐞 𝐚𝐥𝐫𝐞𝐚𝐝𝐲 𝐝𝐢𝐭𝐜𝐡𝐞𝐝 𝐬𝐢𝐧𝐠𝐥𝐞-𝐦𝐨𝐝𝐞𝐥 𝐩𝐫𝐢𝐜𝐢𝐧𝐠. Quietly, completely, across the board. Why? Because usage is unpredictable, infra costs are high, and old SaaS pricing just doesn’t cut it anymore. We’re not pricing features anymore. We’re pricing intelligence. Some insights from the report: ◾𝐇𝐲𝐛𝐫𝐢𝐝 𝐩𝐫𝐢𝐜𝐢𝐧𝐠 𝐢𝐬 𝐭𝐡𝐞 𝐧𝐞𝐰 𝐬𝐭𝐚𝐧𝐝𝐚𝐫𝐝 – 92% blend subscription, usage, freemium, and tiers in one structure ◾𝐓𝐡𝐞 𝐦𝐨𝐬𝐭 𝐜𝐨𝐦𝐦𝐨𝐧 𝐜𝐨𝐦𝐛𝐨? Subscription + usage + freemium + tiered plans ◾𝐏𝐞𝐫-𝐬𝐞𝐚𝐭 𝐢𝐬𝐧’𝐭 𝐝𝐞𝐚𝐝, 𝐛𝐮𝐭 𝐢𝐭’𝐬 𝐧𝐞𝐯𝐞𝐫 𝐚𝐥𝐨𝐧𝐞 – 85% of companies using SaaS pricing now pair it with usage-based pricing ◾𝟏𝟐% 𝐫𝐮𝐧 𝐦𝐮𝐥𝐭𝐢𝐩𝐥𝐞 𝐦𝐨𝐝𝐞𝐥𝐬 𝐢𝐧 𝐩𝐚𝐫𝐚𝐥𝐥𝐞𝐥 – often segmenting between business and individual users … This shift is more than cosmetic. It reflects a deeper reality: AI products don’t fit cleanly into legacy monetization models. They need pricing systems that scale with usage, support experimentation, and reflect actual value delivered. If you’re building in AI, your pricing strategy isn’t just a detail, it’s a growth lever. 📊Full report https://lnkd.in/g-R3_cwU It’ll reshape how you think about monetizing AI.
-
The smartest pricing shift happening in AI right now Hit my daily limit on Claude (Anthropic)today. Got two choices: 1. Pay per message to keep going 2. Upgrade to next tier (10x more expensive) This solves what I call the "gap pricing" problem—and Kyle Poyar's research shows why it matters. In Kyle Poyar's experience tracking AI companies, 70-80% of token consumption comes from just 10% of users. That means traditional flat pricing breaks—you either lose money on power users or overcharge everyone else. Most SaaS companies assumed AI costs would drop 10x every year. That's not happening. While per-token costs are declining, overall costs are rising as agentic use cases add complexity—companies like OpenAI went from $20 per seat to $200 per seat. Credit-based models let customers see a straightforward usage pool while vendors can adapt pricing to monetize higher-value actions and navigate evolving LLM costs. Major players are validating this shift. Salesforce added credit-based pricing in May. OpenAI replaced seat licenses with pooled credits for Enterprise plans. Microsoft, Adobe, and dozens of startups followed. Don't force customers into plans that don't match their usage patterns. Build bridges between tiers. Let people pay for the spike, not the monthly average. The companies winning right now? They're treating pricing like product—iterating constantly based on real usage data, not assumptions about where costs are heading. Usage limits aren't restrictions. They're opportunities to offer exactly what someone needs in that moment.