Skip to content

    Research note

    AI Agents and SaaS Costs: A Research Note

    AI agents may reshape SaaS costs by shifting the unit of value from software access, priced per human seat, toward work execution, where agents act across business systems on behalf of people. This note examines what that shift could mean for enterprise software cost reduction and SaaS seat optimization, and why any savings should be treated as a hypothesis to test, not a guarantee.

    It is written for finance, procurement, RevOps, and IT leaders being asked whether agents will lower software spend. Our position is deliberately careful: the direction of the trend is real, the magnitude is unknown, and the answer is specific to each portfolio, contract, and control environment.

    Updated 2026-06-27

    Why seat economics are under pressure

    Most enterprise software is priced and governed around the human seat: a named user with login access, billed whether or not work runs through them. The model assumes people do the work inside each system.

    As AI agents begin to execute tasks across business systems, the link between seats and actual output loosens. Work that once required a logged-in person may now be initiated or completed by an agent acting on someone's behalf. This does not erase the seats, contracts, and shared workflows that still demand human access, but it raises a question finance rarely had to ask: are we paying for access, or for work?

    That question is the starting point for any serious look at SaaS cost structure in an agentic environment.

    Usage versus execution: two different cost signals

    Traditional SaaS cost analysis leans on usage signals such as license counts, active users, and login frequency. These tell you who has access and roughly how often they appear. They say little about what work was actually performed.

    An agentic operating model introduces a second, more granular signal: execution, the discrete units of work carried out across systems. Execution can describe what was done, where, and to what effect, independent of how many seats are provisioned.

    • Usage answers: how many people can log in, and how often they do.
    • Execution answers: what work ran, in which system, and on whose behalf.

    Both matter. Usage still governs contracts and compliance. Execution is where the connection between spend and value becomes visible, and where any optimization conversation should begin.

    Where SaaS cost signals actually come from

    To reason about cost honestly, you have to know where the signals live. In most enterprises, cost-relevant information is scattered across procurement records, license management, identity and access systems, and the operational logs of individual applications. None were designed to describe agent-driven work.

    A useful framing separates three layers without prescribing any particular tooling:

    • Contract layer: what you committed to buy, on what terms, and for how long.
    • Access layer: who and what is provisioned, including agent identities.
    • Work layer: the actual execution of tasks across systems.

    Cost-reduction opportunities typically appear where these layers disagree, for example where provisioned access far exceeds the work being performed. Surfacing those gaps is an operating and visibility problem before it is a savings problem.

    A measured framework for finance and procurement

    Treat agent-related SaaS savings as a structured hypothesis, not a line-item promise. A defensible approach moves through clear stages:

    • Baseline: document current seat counts, contracts, renewal dates, and known usage.
    • Observe: establish visibility into where work is executed before changing anything.
    • Hypothesize: identify specific seats or tiers where execution patterns suggest possible optimization.
    • Evaluate cross-functionally: review every candidate change with security, compliance, procurement, and the business owner who depends on the system.
    • Adjust and monitor: make contained changes, then watch for downstream effects on workflows and risk.

    The discipline here is restraint. A seat that looks idle may carry compliance, contractual, or workflow dependencies that no usage report shows. No seat should be removed on cost grounds alone.

    What this note does not claim

    It is worth being explicit about the limits of this analysis. We are not claiming that AI agents reduce SaaS costs by any specific amount, that every organization will see savings, or that seat reduction is the primary value of an agentic model. Cost is one lens among several.

    What we do observe is a structural shift worth preparing for: as more work is executed by agents, the historical link between seats and value weakens, and organizations that can see execution clearly will be better positioned to make sound procurement decisions. Whether that becomes lower spend depends on contracts, governance, risk posture, and how the change is managed.

    The responsible conclusion is to build visibility and governance first, and let any cost outcomes follow from evidence rather than expectation.

    Frequently asked questions

    Can AI agents reduce SaaS costs?
    They may, but it is not guaranteed, and the amount is specific to each organization. As agents execute more work across systems, the link between human seats and actual output can weaken, which raises the question of whether some access is still needed. Any potential savings should be tested against contracts, compliance, and business dependencies, and reviewed with procurement and security before changes are made.
    What is the post-seat enterprise?
    The post-seat enterprise is a framing in which the unit of value in enterprise software shifts from access, priced per human seat, toward work execution carried out by both people and AI agents. It does not mean seats disappear. It means organizations increasingly judge software by the work that runs through it rather than only by how many users can log in.
    How is execution different from usage in SaaS cost analysis?
    Usage describes access and login activity, such as license counts and sign-in frequency. Execution describes the actual units of work performed across systems, regardless of how many seats are provisioned. Usage still governs contracts and compliance, while execution makes the link between spend and real work visible. Sound cost decisions weigh both signals together.
    How should companies approach SaaS seat optimization with AI agents?
    Treat it as a structured hypothesis rather than an immediate cut. Establish a baseline of seats and contracts, build visibility into where work is executed, identify candidate seats or tiers, then evaluate each one with security, compliance, procurement, and the business owner. A seat that looks idle may carry dependencies invisible in a usage report, so none should be removed on cost grounds alone.
    Where do SaaS cost signals come from in an agentic environment?
    They are typically scattered across procurement records, license management, identity and access systems, and individual application logs, none of which were built to describe agent-driven work. It helps to separate the contract layer, the access layer, and the work layer. Cost-reduction opportunities usually appear where these layers disagree, such as where provisioned access exceeds the work actually performed.

    Related reading

    Private beta

    Preparing for the post-seat enterprise?

    Agent Cockpit is in private research and design-partner mode with enterprise operators exploring the shift from seat-based SaaS to agentic work execution.

    Request Private Access