SaaS pricing is dead, agents charge per outcome

The $18/Seat Tax on Progress

In 2019, we were evaluating CRM tools for a client. The tool we liked best cost $18 per user per month. We had 12 people who needed access.

“Can we just get 5 seats and share logins?” the client’s CEO asked.

This is the original sin of per-seat pricing: it creates an incentive to restrict access. The CEO wasn’t being cheap, he was being rational. Five of those 12 people would use the tool maybe once a week. Paying $18/month for someone who checks the CRM every Friday to see if a deal closed felt wrong. But the tool’s value depended on everyone having accurate, up-to-date data, which required everyone having access.

We bought 12 seats. Total cost: $216/month, $2,592/year. Three of those seats were used less than once a week. The CRM data was still inconsistent because the people with seats didn’t update it regularly enough.

This story has played out millions of times across the SaaS industry. Per-seat pricing was an elegant solution to a 2005 problem: how do you charge for cloud software when you can’t sell perpetual licenses? Charge per user, like a utility.

But per-seat pricing was designed for an era when software was a tool that humans used. It assumed a direct relationship between the number of users and the value extracted. More users meant more value, so more seats meant more revenue. Simple.

AI agents shatter this assumption.

Why Per-Seat Doesn’t Work for Agents

An AI agent doesn’t sit in a seat. It doesn’t log in. It doesn’t have a user profile. It runs autonomously, potentially generating value 24 hours a day, seven days a week, for every person in the organization simultaneously.

How do you price that per seat?

Option A: Charge one seat per agent. Apollo Space has 12 agents. At $18/seat, that’s $216/month. But one of those agents, the SDR agent, might generate $50,000 in pipeline value per month. Another, the Meeting Digest agent, saves $3,600/month in recovered time. You’re charging $18/month for something that delivers $53,600/month in value. The pricing is absurd. You’re either leaving massive money on the table as a vendor, or you’re charging so much per “seat” that it stops being per-seat pricing and becomes something else entirely.

Option B: Charge per human user who interacts with agents. This is what some platforms do. You have 5 people who read agent reports? That’s 5 seats. But wait, the agent generated value for the entire company, not just the 5 people reading its output. The SDR agent’s outreach benefits the CEO, the sales team, and the product team (who gets market feedback from those conversations). Charging only the readers ignores most of the value chain.

Option C: Charge per API call or compute. Usage-based pricing, like what Twilio or AWS does. But this measures input cost (how much computing the agent used), not output value (what the agent accomplished). A poorly configured agent that burns compute without results costs the same as one that delivers transformative outcomes. This incentivizes the wrong things.

None of these options work. They’re all attempts to fit an old pricing model onto a fundamentally new type of product.

The Outcome-Based Alternative

Here’s what makes sense: charge for what the agent accomplishes.

• SDR agent books a meeting? That’s a billable outcome.
• QA agent catches a bug before production? That’s a billable outcome.
• Meeting Digest agent processes a meeting and extracts action items? That’s a billable outcome.
• Observability agent detects and resolves an incident without human intervention? That’s a billable outcome.
• Budget Monitor agent identifies a cost optimization that saves money? That’s a billable outcome (potentially a percentage of savings).

This model has three properties that make it superior to per-seat pricing:

1. Incentive Alignment

With per-seat pricing, the vendor’s revenue is decoupled from the customer’s success. Whether the CRM improves your close rate or sits unused, the vendor collects $18/seat/month.

With outcome-based pricing, the vendor only earns when the customer gets results. If the SDR agent doesn’t book meetings, the vendor doesn’t get paid for SDR outcomes. This creates a powerful incentive for the vendor to make the agent actually work, not just look good in a demo.

Industry analysts covering SaaS pricing have pointed to a broader shift toward usage-aligned pricing models, arguing that pricing which scales with customer value reduces the friction that makes customers hesitant to expand usage. The reason is straightforward: when your price scales with customer value, customers are more willing to expand usage because they’re never paying for something they’re not getting.

2. Small Team Advantage

Per-seat pricing is regressive for small teams. A 3-person startup pays $54/month for CRM access. An enterprise with 500 seats pays $9,000/month. The enterprise has 167x more seats but doesn’t get 167x more value per seat, they get bulk discounts, dedicated support, and custom features that the 3-person startup can’t access.

Outcome-based pricing flips this. A 3-person startup using Apollo Space’s SDR agent to book 20 meetings/month pays for 20 meetings worth of value. An enterprise using it to book 2,000 meetings/month pays for 2,000 meetings worth of value. The price is proportional to the value received, regardless of team size.

This matters enormously for the companies Apollo Space is built for, lean teams that need enterprise-grade capabilities without enterprise-grade budgets.

3. Elastic Scaling

Per-seat pricing creates friction around scaling. Every new hire requires a purchasing decision: “Do they need a seat? Which tier? Is there budget?” This administrative overhead might seem small, but procurement decisions for new SaaS seats routinely take the better part of a week for mid-market companies. That’s friction every time a team grows.

Outcome-based pricing has no scaling friction. If the agent does more work (because the company is growing), the cost grows proportionally. If the agent does less work (because it’s a slow month), the cost shrinks. No procurement decisions. No seat negotiations. No annual true-ups where you discover you’re paying for 50 seats but only 35 are active.

The Per-Seat Graveyard

The shift away from per-seat pricing is already happening, and it’s being led by the most sophisticated SaaS companies.

Intercom moved its Fin product from per-seat to per-resolution pricing in 2024, charging $0.99 per resolved conversation regardless of how many support agents, human or AI, are involved.

Figma introduced a per-editor model but made viewers free, implicitly acknowledging that not all “users” should be charged equally. The value is in editing, not viewing.

HubSpot launched “seats only for those who need them” tiers, separating view-only users from paying seats. It’s a half-step toward outcome-based, recognizing that per-seat is too blunt.

OpenAI’s API is usage-based from day one. You pay per token processed. This is closer to outcome-based than per-seat, though it still measures input (tokens) rather than output (value created).

The direction is clear: the industry is moving away from per-seat. The question is how fast and how far.

The Calculus for Buyers

If you’re a buyer evaluating AI agent products, here’s how to think about pricing models:

Per-seat AI products are optimizing for the vendor, not for you. They’re legacy pricing attached to new technology. You’ll pay the same whether the AI delivers value or not. You’ll pay more as your team grows, even if the AI’s value per person doesn’t grow proportionally.

Per-outcome AI products are optimizing for alignment. The vendor is betting that their product works well enough to justify charging for results. If the product doesn’t work, you don’t pay much. If it works brilliantly, you pay more, but you’re paying out of the value it created.

The test: Ask the vendor: “If your agent doesn’t deliver results, do I still pay?” If the answer is yes (because you’re paying per seat), the incentives are misaligned. If the answer is no (or “you pay a reduced base”), the incentives are aligned.

How Apollo Space Prices

We’ll be transparent about our approach, because we think pricing transparency is rare and valuable.

Apollo Space uses a hybrid model:

Base platform fee. A fixed monthly cost that covers the infrastructure, the director layer, and access to the agent ecosystem. This is predictable and covers our fixed costs. Think of it as the “operating system” fee.

Per-outcome fees. On top of the base, each agent charges for measurable outcomes:

• SDR agent: per qualified meeting booked
• QA agent: per test suite run
• Meeting Digest agent: per meeting processed
• Observability agent: per incident handled
• Budget Monitor agent: per anomaly flagged
• And so on for each agent

Outcome caps. To prevent cost anxiety, we offer plans with outcome ceilings. You pay per outcome up to a maximum, then everything above that is included. This gives you the alignment of outcome-based pricing with the predictability of a subscription.

The result: a 3-person team using Apollo Space might pay $200-400/month total, less than a single mid-tier SaaS seat at many enterprise tools, and get the operational coverage that would normally require 4-5 tool subscriptions and 2-3 additional hires.

Why This Matters Beyond Pricing

The shift from per-seat to per-outcome isn’t just about money. It’s about how we think about software.

Per-seat pricing treats software as a tool, something humans use. Per-outcome pricing treats software as a service, something that delivers results. This distinction reshapes the entire relationship between vendor and customer.

When software is a tool, the vendor’s job is to build features. Ship the feature, demo the feature, charge for access. Whether the customer uses it effectively is the customer’s problem.

When software is a service measured by outcomes, the vendor’s job is to deliver results. If the SDR agent isn’t booking meetings, the vendor has a direct financial incentive to diagnose and fix the problem. The vendor and the customer are on the same side of the table.

This is the business model equivalent of the agent-vs-chatbot distinction. A chatbot waits for you to use it. An agent does the work. Per-seat pricing charges you for access. Per-outcome pricing charges you for value.

In both cases, the shift is from passive to active. From potential to actual. From “here’s a tool, good luck” to “here’s a result, you’re welcome.”

The Inevitable Transition

We believe that within five years, per-seat pricing for AI-augmented software will be viewed as a historical artifact, like charging for software by the floppy disk.

The transition won’t be instant. Large enterprises have procurement workflows built around per-seat pricing. CFOs understand per-seat budgeting. Salespeople know how to sell seats. There’s enormous institutional inertia.

But the economics are irresistible. For buyers, per-outcome means paying for value, not access. For vendors, per-outcome means revenue that scales with customer success, creating natural expansion opportunities. For the market, per-outcome means lower barriers to entry for small teams, expanding the total addressable market.

The SaaS pricing model served us well for two decades. It democratized software access. It killed the tyranny of perpetual licenses and multi-year contracts. It deserves its place in business history.

But it was designed for a world where software was a tool and humans were the operators.

In a world where agents are the operators, we need pricing that reflects what agents do: deliver outcomes.

The seat is dead. Long live the outcome.