Vendors repriced in a day, contracts run for years: the buyer’s side of the software selloff

The week

On Tuesday, February 3, 2026, a selloff in software, data and professional-services stocks deepened sharply in the United States and Europe. Legal and financial information providers were among the hardest hit. Reuters reported that Thomson Reuters was on track for its biggest one-day fall on record. Some investors blamed a set of plugins, covering legal, sales, finance and data work, that Anthropic had released for its Claude Cowork agent the previous Friday. Commentators framed the fear as “seat compression”: if AI agents do task-level work, customers may need fewer paid user licenses, and model providers may sell finished workflows rather than components. Other analysts called the reaction overdone. Market moves of this kind say more about investor expectations than about what any customer will do next quarter.

Investors can sell a stock in a minute. A bank, health system or agency that wants to change how it uses a core application is bound by an agreement that may run for three or five years. That asymmetry is why the selloff matters to buyers. Most enterprise software is priced per named user, sold on multi-year terms and governed by contracts that assume a human logs in. AI agents work differently. They act through APIs, at machine speed, on behalf of people who may never open the application.

A software agreement governs four things over its life, and agents strain each of them: how the buyer pays, how long it is committed, what its automated tools may reach, and how it can leave. We take them in that order.

How you pay: the pricing metric

Per-seat pricing ties cost to headcount. If agents take over part of a team’s routine work, the number of human users might fall. It might also stay flat while automated usage rises sharply. Vendors were already responding with consumption pricing, agent licenses and credit bundles. Each moves risk in a different direction. A consumption metric can be cheaper than seats or far more expensive, depending on volumes that are hard to forecast in the first year.

A finance team can test this before signing. Take one process, such as invoice review in accounts payable or prior authorization intake in a health system. Estimate how agent use would change both seat counts and transaction volumes over the term. Price the result under each metric the vendor offers. The exercise is rough, but it shows which metric carries the most risk, and it gives the negotiating team its own numbers rather than the vendor’s.

Three clauses then matter. A spending cap or alert threshold under any consumption metric. A rule that agent licenses are not charged on top of the seat held by the person the agent works for. And a definition of “user” that says plainly whether an automated process counts as one.

How long you are committed: term and flexibility

Multi-year agreements with fixed seat minimums made sense when headcount was stable. They look different when human use could fall within the term. Health systems that buy large enterprise agreements and agencies that buy through cooperative contracts are both exposed, for different reasons. The health system has negotiated a discount it would lose by shortening the term. The agency may be using a vehicle whose pricing structure is fixed for the life of the award.

Useful terms include the right to reduce seats within a band at each anniversary and the right to convert unused seats into other products or credits. Shorter terms suit products whose category is most likely to change. None of these is free. Each trades some unit price for flexibility. The trade is worth making for applications that sit closest to the work agents are likely to absorb, such as document review, research, reporting and first-line service. It is rarely worth making for systems of record. Public buyers should confirm with their procurement office whether a cooperative vehicle permits these terms before asking for them.

What your agents can reach: access and data rights

Agents need programmatic access. Many existing contracts restrict API use, set low rate limits, prohibit automated access or charge separately for it. Some restrict use of the customer’s own data with third-party AI tools. A buyer that plans to run its own agents across its systems needs agreements that permit it, with stated limits and prices. Otherwise the vendor can make its own agent the only practical route to the buyer’s data.

Access rights also carry control obligations in regulated settings. An agent working in systems that hold customer financial data, protected health information or criminal justice information must meet the same authentication, logging and least-privilege requirements as a person would. Contracts should require that audit logs record agent actions distinctly from human ones, and that the vendor supports scoped, revocable credentials for automated access. Without that, an examiner’s question about who changed a record may have no clean answer.

How you can leave: exit and data portability

The selloff rested on a view that some categories of software could be partly replaced. Whether or not that happens, the option to move has value, and it is set at signing. Exit terms should cover export of data in usable formats, including configuration, rules and workflow definitions. They should include a reasonable transition period and assistance at defined rates. Workflows built inside a vendor’s own agent tools deserve particular attention, because prompts and automations written there may not export at all.

Exit planning also has a regulatory side. Banks are expected to plan for the exit of critical third parties, and agencies need records and data back in forms they can use. A contract that is silent on export leaves the buyer’s ability to adopt better tools dependent on the incumbent’s goodwill.

Together, the four parts cover the commercial relationship from first invoice to departure. None requires a view on which vendors will win. Each requires reading current agreements with agents in mind, starting with those whose renewal falls in the next eighteen months.

With hindsight

The February drop was not a one-day event. Software stocks stayed under pressure through the spring, and market commentary in July still described the sector as well below its January level, while infrastructure names recovered faster. Core systems in banks, health systems and agencies were not replaced in 2026, and we would not read the share prices as a forecast that came true.

What changed was the commercial conversation. Large vendors were already offering agent-based and consumption pricing alongside seats, and those options moved to the center of enterprise renewals. Buyers who reviewed their largest agreements before renewal could negotiate caps, conversion rights and access terms. Those who renewed on familiar per-seat terms risked buying automation rights separately later. The market overreacted to the vendors. The contractual question it raised for buyers was sound.