---
title: "Your Agents Are Making Seats Redundant. Fix the Contract Before the Renewal."
description: "Per-seat pricing is collapsing across enterprise software, and most buyers are still renewing on it. Here is how agent deployments change what you should be paying for, and the four clauses worth fighting for at your next renewal."
image: "https://foundrysoft.co/api/og?type=article&title=Your+Agents+Are+Making+Seats+Redundant.+Fix+the+Contract+Before+the+Renewal.&cat=Insights+%2F%2F+Cost&rt=11+min+read&au=Varun+Raj+Manoharan&dt=2026-08-20"
url: "https://foundrysoft.co/blog/agent-era-saas-pricing-renewal"
---

Insights // Cost 2026-08-20 11 min read

# Your Agents Are Making Seats Redundant. Fix the Contract Before the Renewal.

Per-seat pricing is collapsing across enterprise software, and most buyers are still renewing on it. Here is how agent deployments change what you should be paying for, and the four clauses worth fighting for at your next renewal.

![Varun Raj Manoharan](https://foundrysoft.co/images/about/founder.webp)

Varun Raj Manoharan Founder & Principal Engineer

AI Agent Pricing SaaS Renewal Outcome-Based Pricing Agentic AI AI Cost Management

## Key takeaways

-   Per-seat pricing has fallen from around 21% to 15% of SaaS vendors in a year, and a large majority of SaaS CEOs say they intend to retire it. Buyers renewing on old seat terms are on the wrong side of a transition the vendors have already priced in.
-   When an agent handles the routine volume, your seat count falls but your consumption rises. If the contract only flexes in one direction, you pay for both.
-   Hybrid pricing, a committed base plus usage, is the dominant transition model. Negotiate the usage half properly, because that is where the surprises live.
-   The clause that matters most is what happens when an agent, rather than a person, is the one making the calls. Many contracts still do not define it.

In January, Anthropic shipped Claude Cowork, a desktop mode that reads your files, connects to your tools, and produces finished work while you go and do something else. Within weeks the market decided this was an existential problem for software sold by the seat, and roughly $285 billion came off SaaS valuations in about 48 hours. By the end of the quarter the damage across enterprise software had passed a trillion.

I am not going to pretend to know whether the market was right. What I do know is what it changed on the buying side, and almost nobody I talk to has adjusted their renewals for it.

## The structural problem with seats

Per-seat pricing had a good run because it was legible. You have 400 people, they each need the tool, you pay 400 times a number. Finance could forecast it and vendors could plan around it.

Agents break the alignment underneath it, and the break is not subtle. If a vendor sells you a support tool at a price per agent seat, and their AI gets good enough that you need 30% fewer support staff, the vendor's revenue falls 30% as a direct consequence of their product working better. They are being paid to under-deliver.

No vendor is going to accept that for long, and they have not. Per-seat has gone from around 21% of SaaS companies to about 15% in twelve months. A survey of a few hundred SaaS CEOs this spring found the overwhelming majority planning to retire seat pricing within two years. Vendors on usage or outcome models are reportedly running materially better gross margins than the holdouts.

The transition state is hybrid: a committed base fee plus consumption charges for the AI-heavy parts. That is around 41% of the market and it is where most of your renewals are heading, whether or not anybody has told you.

## What this does to your bill

Here is the part that catches procurement teams out, and it is arithmetic rather than strategy.

You deploy agents. Your seat count goes down, because the routine work no longer needs a person clicking through a UI. Good, that is the saving you budgeted.

But your consumption goes up, and it goes up faster than the seat count came down. An agent does not use a system the way a person does. A person opens eight records in an hour. An agent queries four hundred, because it is cheap for it to check rather than assume. API calls, records processed, documents parsed, messages sent: every metered dimension rises.

If your contract has a floor on seats and no ceiling on usage, you have just built a machine that reduces the thing you cannot stop paying for and increases the thing you cannot cap. I have watched a client's total spend on one vendor rise 18% in a year during which their seat count fell by a third, and be genuinely surprised by it, because both halves of that were predictable and nobody had put them on the same page.

## Four things worth fighting for at renewal

I am not a procurement specialist and this is not legal advice. These are the four points that, in the deals I have been close to, actually changed the number.

**Seat flexibility that works downward.** Most contracts let you add seats mid-term and not remove them. If you are deploying agents into a function, you need the ability to reduce committed seats at renewal without a penalty, and ideally a true-down provision mid-term. Vendors resist this and will often trade it for a longer term, which is frequently a fine trade.

**A defined machine-usage rate.** Ask explicitly how the contract treats calls made by an automated system rather than a logged-in human. A surprising number of agreements are silent on it, and silence gets resolved in the vendor's favour when the invoice arrives. Some vendors have begun charging a premium for programmatic access, which may be reasonable, but you want to know the rate before you build the agent, not after.

**Consumption caps with a defined overage rate.** Not to avoid paying for what you use, but so that a runaway agent, a retry loop, or a badly scoped run does not produce a five-figure surprise. A hard cap with alerting at 70% and a pre-agreed overage price converts an unbounded risk into a known one. Every vendor I have seen asked for this has agreed to some version of it.

**Data and export rights that survive the relationship.** If you are going to move workloads to agents, your leverage at the next renewal depends entirely on whether you can leave. That means bulk export in a usable format, defined within a defined window, without a professional services engagement. This clause costs nothing to add today and is worth a great deal in two years.

## The question to ask before you renegotiate anything

Before the vendor conversation, work out what the function actually costs you now, per unit of work done.

Not per seat. Per resolved ticket, per processed invoice, per closed case. Take the total: licence fees, the labour, the integration maintenance, and now the model costs for the agent. Divide by units of work completed.

That number is the only one that lets you compare a seat deal against a usage deal against an outcome deal, and it is the number to bring into the room. It also has the useful property of being the same metric you should be using to evaluate whether the agent project is working at all.

Most teams cannot produce it on the first ask, which is itself informative. If you cannot say what a resolved ticket costs today, you cannot tell whether any pricing model is a good deal, and you certainly cannot tell whether your agent deployment paid for itself.

## On outcome-based pricing, briefly

There is a lot of enthusiasm for paying vendors per outcome: per resolved ticket, per successful collection, per qualified lead. In principle it aligns everyone perfectly.

In practice most of what is sold as outcome pricing is output pricing with better marketing. Paying per ticket the agent closed is not paying for outcomes unless closed means resolved, and resolution is measured by whether the customer came back, not by whether the agent marked it done. Once you define it properly, both sides have to agree on measurement, disputes have to have a process, and the contract gets considerably more complicated.

My view, and I hold it loosely: outcome pricing is a good fit where the outcome is unambiguous and independently observable, like a payment collected or an invoice matched. It is a bad fit where the outcome is a judgment call, because you will spend more on arguing about measurement than you save on alignment. For most functions, a hybrid with a well-negotiated usage half is the pragmatic answer for the next couple of years.

Gartner's projection is that by 2030 at least 40% of enterprise SaaS spend moves to usage, agent, or outcome pricing. That leaves a transition window, and the contracts you sign in it will be the ones that either give you room or take it away.

## What I would actually do this quarter

List your renewals for the next eighteen months, with the annual value and the pricing model for each.

Mark the ones where you have an agent deployed or planned in the same function. Those are the ones where the shape of your usage is about to change and the contract probably assumes it will not.

For each of those, work out cost per unit of work today. Then model it under two scenarios: agent handles 40% of volume, and agent handles 70%. See what the bill does under the current terms. It is often not what people expect, and finding out eleven months before renewal is a very different conversation from finding out three weeks before.

Then open the vendor conversation early, from a position of having done the arithmetic. Vendors are, in my experience, more flexible about pricing structure than about price. They know the seat model is on the way out. Many of them would rather move you to a hybrid now, with terms both sides can live with, than defend an old model into a renewal fight.

The buyers doing badly in this transition are not the ones paying too much per seat. They are the ones who deployed agents without noticing that the contract underneath had assumptions in it that no longer hold.

We spend a lot of our time on the technical side of this, working out what an agent workload will actually consume before anyone commits to it. If a renewal is coming and you want the usage model built out properly first, [we can help with that.](https://foundrysoft.co/services)

#### Related reading

[AI Voice Agents Answer the Phone Now. What That Actually Does to Your Support Org.

Enterprise voice agents crossed from novelty to normal this year. The technology question is largely settled. The interesting questions are what happens to your escalation path, your metrics, and the people left holding the hard calls.

AI Voice Agents Customer Support Contact Center AI

](https://foundrysoft.co/blog/voice-agents-support-org-economics)[Shadow Agents: Somebody in Your Company Has Already Built One

Over a million agents have been built in Copilot Studio alone, most of them by people who are not engineers. Shadow AI is not a hypothetical governance risk, it is the current state of most enterprises. Here is how to find them and what to do that is not a ban.

Shadow AI AI Governance Agentic AI

](https://foundrysoft.co/blog/shadow-agents-ai-governance)[What Agentic AI Actually Looks Like in Supply Chain and Manufacturing Operations

Supply chain is the function where agents have the clearest business case and the worst data. Here are the four workflows where AI agents earn their keep in manufacturing and logistics, and the two where they consistently disappoint.

Agentic AI Supply Chain Manufacturing

](https://foundrysoft.co/blog/agentic-ai-supply-chain-operations)

#### Next Article

[

88% of Companies Running AI Agents Had a Security Incident. Ask the Blast Radius Question First.

](https://foundrysoft.co/blog/agent-security-incident-blast-radius)

Available for new projects

## Let's build something great.

Have a project in mind? We are an elite software and AI development studio ready to bring your ideas to production. Let's talk about your roadmap.

Start a Project [See our work](https://foundrysoft.co/work)

```json
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "FoundrySoft",
  "url": "https://foundrysoft.co",
  "logo": "https://foundrysoft.co/logo.svg",
  "description": "FoundrySoft builds production-grade software and AI systems for US companies, from an India-based team of senior engineers.",
  "sameAs": [
    "https://github.com/foundrysofthq",
    "https://www.linkedin.com/company/foundrysoft",
    "https://www.instagram.com/foundrysoft/"
  ]
}
```

```json
{
  "@context": "https://schema.org",
  "@type": "WebSite",
  "name": "FoundrySoft",
  "url": "https://foundrysoft.co"
}
```

```json
{
  "@context": "https://schema.org",
  "@type": "TechArticle",
  "headline": "Your Agents Are Making Seats Redundant. Fix the Contract Before the Renewal.",
  "description": "Per-seat pricing is collapsing across enterprise software, and most buyers are still renewing on it. Here is how agent deployments change what you should be paying for, and the four clauses worth fighting for at your next renewal.",
  "url": "https://foundrysoft.co/blog/agent-era-saas-pricing-renewal",
  "mainEntityOfPage": "https://foundrysoft.co/blog/agent-era-saas-pricing-renewal",
  "image": [
    "https://foundrysoft.co/images/blog/agent-era-saas-pricing-renewal.webp"
  ],
  "datePublished": "2026-08-20",
  "dateModified": "2026-08-20",
  "keywords": "AI Agent Pricing, SaaS Renewal, Outcome-Based Pricing, Agentic AI, AI Cost Management",
  "author": {
    "@type": "Person",
    "name": "Varun Raj Manoharan"
  },
  "publisher": {
    "@type": "Organization",
    "name": "FoundrySoft",
    "logo": {
      "@type": "ImageObject",
      "url": "https://foundrysoft.co/logo.svg"
    }
  }
}
```

```json
{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "name": "Home",
      "item": "https://foundrysoft.co/"
    },
    {
      "@type": "ListItem",
      "position": 2,
      "name": "Blog",
      "item": "https://foundrysoft.co/blog"
    },
    {
      "@type": "ListItem",
      "position": 3,
      "name": "Your Agents Are Making Seats Redundant. Fix the Contract Before the Renewal.",
      "item": "https://foundrysoft.co/blog/agent-era-saas-pricing-renewal"
    }
  ]
}
```