Skip to content
Hiclix
Menu

The end of per-seat pricing? What agents change in the SaaS business model

· Tarek Nachnouchi

Paper-cut illustration: an office chair turns into a stack of yellow tokens on a midnight-blue background, a symbol of the shift from per-seat pricing to usage-based billing.

In one week, G2 published a survey that rejects per-seat pricing for AI agents, and HubSpot let its customers convert seats into credits. I think the renegotiation of your SaaS contracts starts now, ahead of the 2027 renewals.

What buyers say

G2 surveyed 1,019 B2B decision-makers in July 2026 across North America, EMEA and Asia-Pacific. The report, "Crossing the Agentic Chasm", came out on 14 October. According to Software Marketing Resource's summary, the preference for pay-as-you-go pricing rose from 38% in 2025 to 57% in 2026. Pay-per-outcome rose from 11% to 19%. Fixed pricing fell from 35% to 21%.

The figure that interests me most is elsewhere: 46% of buyers report higher operating costs than they expected. They first ask for real-time usage dashboards and monthly caps. Next come cost-per-outcome reporting, the option to send some tasks to cheaper models, and a cost forecast before deployment.

The survey also flags a commercial risk for vendors. 30% of buyers would consider switching vendor for better agents, and 44% would pilot an alternative before renewal.

What vendors are doing

On 3 September, Salesforce grouped its offers into three editions, from $195 to $550 per user per month. Each edition includes a stock of "Flex Credits" for agents. Its support agent, Help Agent, is billed on outcomes: the customer pays when the issue is resolved.

On 15 October, HubSpot put the emphasis on control. It now switches on, by default, an account-level credit limit set up to 50% above monthly credits. Customers can swap seats for credits without waiting for renewal. They choose between credit packs at a flat monthly rate and pay-as-you-go. HubSpot's Customer Agent and Prospecting Agent had already moved to outcome-based pricing earlier in the year.

I read these announcements as a forced adaptation. A seat counts the humans who log in. An agent works continuously, sometimes overnight, and its value depends on what it produces. So vendors keep the seat for access and add a consumption layer for the work. This hybrid model fits value better. It is also much harder for the buyer to forecast.

Two stories about willingness to pay

I have lived this question as a vendor. I launched a product called CreatorVault, designed for creators. The analysis showed that their willingness to pay was too low. I repositioned the product towards French-speaking B2B experts, under the name Signalum AI. I kept a working rule from it: a pricing model has to follow the value perceived by the person who signs.

On the buyer side, a user of r/SaaS explains, in a comment dated 29 April 2026, that they treated AI as a separate line in their vendor reviews. They offered vendors two options: a fixed per-seat uplift with clear caps, or a usage ceiling with automatic cut-off and no billed overage. When a vendor refused to write these guardrails into the contract, they asked for a discount or a shorter term. This account cannot be verified. It still describes well the discipline I recommend.

What I recommend before your next renewal

  1. Take stock. List your SaaS contracts that include AI features or agents, with their renewal dates. Start with those expiring within six months.
  2. Ask for a written definition of a credit. Ask what a typical task consumes and under which conditions the vendor can change that scale during the contract.
  3. Get a cap written in. A monthly limit with an alert, or a cut-off, belongs in the contract. HubSpot shows it is technically possible.
  4. Negotiate the conversion. If an agent takes over part of a team's work, ask to convert unused seats into credits.
  5. Test before signing. A 30 to 60-day pilot lets you measure actual consumption, time saved and review time.
  6. Define the outcome. For an outcome-based clause, a "resolution" needs a verifiable definition and a right to dispute.
  7. Check the European terms. Salesforce states that availability varies by region and depends on customer agreements. Ask in writing for the terms that apply to your entity, in euros.

When I support a contract review of this kind, I include it in a digital project management assignment.

Checklist: is your SaaS contract ready for agents?

#QuestionYes / No
1Is a monthly consumption cap written into the contract?
2Are the definition of a credit and its scale written down?
3Do you have a real-time usage dashboard?
4Can you convert seats into credits before renewal?
5Do billed outcomes have a verifiable definition?
6Can you exit the contract if the scale changes?

How to read it: 5 or 6 yes, your contract is ready. 3 or 4 yes, open negotiations this quarter. Fewer than 3 yes, prepare a competitive tender before the deadline.

My takeaway

I think the seat will not disappear quickly. It will remain the entry ticket, and the variable part will grow with agent usage. For a European executive, every 2027 renewal becomes a business-model negotiation. I will come back to the subject when the first buyers publish their real invoices.

If you would like to discuss this for your organisation, I offer a first conversation of 30 to 45 minutes, free and with no commitment.