Question 1

Limitations of per-user pricing

Accepted Answer

The per-seat subscription model was elegant: revenue scales with headcount and apparent penetration, renewal math is straightforward, and expansion is often measured by net new seats. But the model depends on a tacit assumption — that human labor is the primary input to business workflows. As autonomous AI agents replicate and often exceed human throughput, that assumption no longer holds.

Question 2

The economics of headcount vs. output

Accepted Answer

Traditional SaaS unit economics tied revenue to headcount; the implicit unit was the "seat." Unit economics were modeled as revenue per seat, churn, and customer lifetime value. In an agentic world, however, the primary economic unit becomes work completed — tasks, transactions, reports generated, cases resolved. The transition requires rethinking LTV, churn definitions, and marginal cost curves.

Question 3

Defining Agentic Volume

Accepted Answer

"Agentic Volume" is the aggregate throughput of autonomous agents executing discrete, measurable work. This may include generating analytics reports, performing reconciliation, drafting contracts, triaging tickets, or running continuous monitoring and remediation. Importantly, Agentic Volume is measurable, metered, and intrinsically tied to business outcomes rather than human presence.

Question 4

Outcome-Based Billing mechanics

Accepted Answer

Outcome-Based Billing (OBB) charges customers based on successful completion of defined tasks or achieved outcomes, rather than seats or feature tiers. Mechanically, an OBB arrangement typically specifies (1) a definitional contract for a "task" or "outcome", (2) measurement methodology, (3) success criteria, (4) price per success event, and (5) reconciliation and dispute resolution clauses.

Question 5

Multiples under pressure

Accepted Answer

The shift to agentic billing has immediate implications for valuation multiples. Historically, public SaaS valuations leaned heavily on revenue growth and recurring revenue visibility. Price-to-sales (P/S) and EV/Revenue ratios were simple and effective priors. Under agentic economics, those priors require adjustment because revenue growth can decouple from value creation if pricing remains seat-based.

Question 6

Winners and losers on NASDAQ

Accepted Answer

NASDAQ has already priced this narrative: some legacy leaders that swiftly integrated agentic capabilities and re-priced contracts have seen relative outperformance, while others relying on seat-based expansion faced downgrades. Winners combine four capabilities: (1) strong telemetry and instrumentation, (2) robust models and inference pipelines, (3) flexible commercial motions to transition customers to outcome billing, and (4) macro scale compute economics to keep marginal costs manageable.

Question 7

Infrastructure-to-Outcome ratio

Accepted Answer

Investors are focused on the Infrastructure-to-Outcome ratio (I2O): the amount of compute, storage, and engineering required to deliver a unit of outcome. High I2O implies thin margins even at scale; low I2O implies efficient monetization. As compute costs scale with model complexity and inference frequency, firms that optimize I2O through model sparsity, caching, and specialized accelerators gain durable advantages.

Question 8

R&D, compute, and consolidation

Accepted Answer

The agentic pivot dramatically increases R&D and infrastructure commitments. Delivering reliable agents requires continuous model improvement, robust evaluation pipelines, and rapid incident response. These investments are capital-intensive and favor larger incumbents that can absorb short-term margin dilution for long-term extraction of Agentic Volume economics.

Question 9

Modeling revenue from tasks

Accepted Answer

To value companies in the agentic era, investors must build forward-looking models that replace seats with task-based drivers. Key inputs include projected task demand per customer cohort, price per successful task, expected success rate and refunds/credits, marginal cost per task (compute + human verification), and churn framed as loss of task volume rather than seat attrition.

Question 10

Portfolio strategies and risk management

Accepted Answer

For portfolio construction, a mix of strategies reduces exposure to execution and technology risk. Consider the following allocations and hedges: (1) Core incumbents with strong customer bases and clear transition plans, (2) AI-native winners with high agentic margins but higher growth volatility, (3) infrastructure and tooling plays that monetize the compute layer, and (4) niche vertical agents with defensible data moats.

Latest Stories

The Unseen Consequences of Banning TikTok: A Detailed Examination

Wireless Internet Terminology - Confusion Or Clarity?