AI didn’t kill SaaS. It exposed broken revenue design.

Nearly $300 billion in software market value vanished in a matter of days earlier this year.

The catalyst was the release of new AI agent systems, like OpenAI’s Frontier and Anthropic’s Claude Cowork, that made investors confront an uncomfortable question: What happens to SaaS when software is no longer primarily used by humans?

For two decades, SaaS companies were valued on the predictability of subscription revenue. Seats expanded, contracts renewed, and ARR compounded. The market rewarded consistency.

But AI agents don’t behave like employees. They don’t “occupy” seats or scale linearly as a company grows. They execute work continuously, across systems and often autonomously.

When the primary user shifts from humans to agents, value becomes less tied to access. Instead, it’s tied to activity and outcomes, which are more variable.

SaaS isn’t dead, but this “SaaSpocalypse” has shown that the economic assumptions underneath it are being rewritten in real time. Surviving this shift requires SaaS companies to move beyond static, access-based pricing.

SaaS was priced for humans, not agents

Traditional SaaS pricing was built around a stable unit: the human seat. A human logged in to access valuable features that would help them complete their work. Revenue and expansion followed customer growth, and forecasting mapped neatly to contracts.

AI agents break this model. An agent can do the work of many humans in seconds and operate continuously, multiplying usage exponentially.That introduces a new economic reality:

• Seat count is no longer an accurate proxy for value.
• Usage is no longer linear, and can spike or compress unexpectedly.
• Cost structures move independently of pricing tiers.
• Forecasting is more difficult and requires real-time visibility into usage.

Surviving the SaaSpocalypse requires rethinking revenue strategy and internal processes

All of this indicates that the SaaSpocalypse is not a one-off shock but a stress test of how resilient your revenue model really is. To navigate what comes next, companies not only need to redesign what they charge so it better reflects value, but also build the discipline to continuously evolve their monetization strategy.

Move from access-based to value-based monetization

If pricing remains tied only to access, it no longer maps to how customers receive value. The companies that navigate this shift successfully understand that and won’t cling to seat-based models out of habit. They’ll rethink what exactly they’re monetizing.

Some questions that companies should ask themselves include:

• Should revenue scale with seats, usage, outcomes, or some hybrid?
• What value metrics do customers actually care about?
• How do we design a value metric that works when both humans and agents use our product?
• How do we forecast revenue when workload patterns can double overnight?

Not all pricing models are equally equipped for this new world of AI agents. The table below summarizes the tradeoffs to consider across three main approaches.

Turn pricing into a core discipline

What’s being exposed right now is slow, disorganized pricing execution that results in pricing being an afterthought rather than a strategic priority.

In most organizations, pricing runs like a broken relay race, where finance, product, engineering, and GTM work in isolation. . When pricing needs to change, coordination becomes a source of friction full of missed handoffs and miscommunication.

Revenue design is the discipline that replaces the relay race with a system. It has a few defining characteristics:

• Cross-functional collaboration: Finance, product, engineering, and GTM all work in sync to make decisions and execute pricing. There are clear swim lanes so that each team knows what they need to do to move your revenue strategy forward.
• Data-driven: Everyone has access to the same data, and decisions are grounded in actual usage and revenue data.
• Iterative: Pricing is not a one-time exercise. It constantly evolves, and iteration is fast yet safe.

Orb equips companies to operationalize revenue design

Revenue design requires infrastructure that goes beyond billing software, spreadsheets, or dashboards. It requires a unified system that brings together usage data, pricing logic, billing execution, and revenue intelligence.

That’s what Orb is built for.

At the center of Orb is the Revenue Graph, which connects every usage event to pricing and revenue outcomes. Instead of contracts acting as the sole source of truth, usage becomes a shared foundation across finance, product, engineering, and GTM.

With Orb, teams can:

• Test pricing changes against historical usage before shipping.
• Deploy new models safely with version control and migration orchestration.
• Automate billing and revenue recognition with audit-ready precision.
• Preserve raw event data for flexible pricing, easy backdating and corrections, and deeper analysis.
• Surface expansion and churn signals directly from product usage.

The companies that thrive in the AI agent era will be those who ensure their pricing aligns with value and have the ability to evolve pricing as quickly as product.

Future-proof your revenue

The SaaSpocalypse is a wake-up call, and the lessons it surfaces should be internalized by every SaaS company:

• When agents execute work, pricing tied to access no longer reflects value.
• When the market shifts, static pricing models become a liability.
• Revenue design is how companies can strategically evolve their pricing in response to the SaaSpocalypse and future changes.

Orb helps finance, product, engineering, and GTM teams automate billing, execute pricing with confidence, and grow revenue strategically, even as the rules of software change. To evolve your pricing to meet how software is now being bought, used, and valued, contact us today.