Salesforce and monday.com Shift AI Agent Pricing Beyond Seats

What changed

Enterprise AI pricing is moving beyond the seat, but not simply replacing it. Salesforce currently offers several Agentforce buying models at once: Flex Credit consumption pricing, per-conversation pricing, per-user licenses and resolution-based pricing.¹ Its rate card lists 100,000 Flex Credits for $500, with a standard action consuming 20 credits and a voice action consuming 30. At the listed rates, those units calculate to $0.10 and $0.15 respectively, although the cost of an end-to-end business process will depend on how many billable actions it requires.¹

monday.com made the hybrid structure explicit in its May 11, 2026 first-quarter disclosure, announcing a seats-plus-credits model for its AI portfolio.² The company’s support documentation says customers covered by that model buy seats for people and credits for AI usage.³ Management characterized the change as a move toward consumption-based pricing and argued that its business can grow as AI performs more work for customers; that is a vendor claim about the model’s economics, not an independently established outcome.²

Meta has disclosed another variation. The company told investors that Meta Business Agent monetization would combine subscriptions with volume-based token pricing.⁴ Independently, TechCrunch reported that Respond.io prices according to conversation volume rather than seats, limiting the direct revenue effect when AI handles work previously performed by people.⁵ The Information has likewise reported that enterprise software providers are experimenting with consumption- and outcome-based structures because AI agents weaken the relationship between software use and employee headcount.⁶

The event, therefore, is not the universal death of per-seat software. It is the emergence of multiple commercial meters alongside seats. Salesforce still sells a per-user Agentforce option,¹ and Microsoft told Fortune in March 2026 that its customers currently preferred per-user pricing.⁷ Forkast’s October 16, 2026 analysis described four competing approaches to agent monetization, but its categorical framing that per-seat pricing is dying goes beyond the evidence.⁸ The verified pattern is a transition toward hybrid contracts that can charge separately for human access and machine-executed work.

Why it matters

For CIOs, the central buying question is changing from “How many employees need access?” to “What work will the system perform, which events create charges, and how variable will the resulting bill be?” Seat counts are relatively observable before deployment. Agent consumption depends on workload volume, process design and the vendor’s definition of a billable unit. A credit, token, action, conversation and completed resolution can each represent a different scope of work, so their published prices are not directly comparable.¹⁴

That distinction invalidates simplistic price comparisons. Forkast cited a claimed 40-to-50-times price advantage for Meta, but the underlying units do not support a reliable like-for-like conclusion: Meta described subscription and token-volume pricing, while Salesforce lists actions, conversations, users and resolutions.⁸¹⁴ A lower price per token cannot establish a lower cost per completed workflow unless the buyer also knows how many tokens, actions, retries and human interventions the workflow requires. The analytical implication is that CIOs must compare vendors at the level of a defined workload or accepted outcome, not at the level of the vendor’s preferred meter.

The budget model changes with it. Under a seat contract, automation that reduces the number of human users can reduce the software bill at renewal. Under consumption pricing, the same automation may increase usage because the agent performs more transactions. monday.com explicitly presents that alignment as a benefit to its business, saying it can grow as AI does more customer work.² Buyers should read that statement as a clear description of the supplier incentive: greater machine activity can generate greater vendor revenue even when employee headcount does not rise.

Gartner estimated that up to $234 billion—about 20% of projected enterprise application SaaS spending—could be exposed to “agentic arbitrage” by 2030 and said the development breaks the traditional relationship between seats and licenses.⁹ Fortune separately reported that CIOs want suppliers to move away from per-seat fees and that agentic AI is pressuring per-user pricing.¹⁰ Those findings support the direction of travel, but Microsoft’s reported customer preference for per-user pricing shows why CIOs should not assume one successor model will dominate immediately.⁷

The decision model must consequently add workload forecasts, unit-definition scrutiny and consumption-risk controls to conventional license management. CIOs need to determine whether a contract rewards useful automation or merely monetizes activity. They also need to test whether an “outcome” is objectively accepted by the enterprise, whether retries are billable, and whether a vendor can change the work represented by a credit. These are analytical requirements created by the documented pricing structures; they are not claims that every vendor currently applies the same terms.

Frontier take

The decisive commercial battleground for enterprise agents will be control of the billing unit, not the nominal price attached to it. That is the strongest conclusion supported by the coexistence of Salesforce’s credits, actions, conversations, users and resolutions; monday.com’s seats-plus-credits model; and Meta’s proposed mix of subscriptions and token volume.¹³⁴

A seat has an imperfect but familiar denominator: a person authorized to use the product. Agent pricing fractures that denominator into vendor-specific abstractions. Suppliers can present each abstraction as closer to value, but a billing unit is not an outcome merely because it is generated by AI. An action may be one step in a process. A conversation may end without resolution. Tokens measure processing volume rather than business completion. Even resolution pricing requires agreement on what counts as resolved. The unit’s definition therefore determines whether automation transfers economic value to the buyer or converts that value into an expanding variable charge.

Per-user licensing will persist where buyers value predictability or where human access remains a reasonable usage proxy. Salesforce’s active per-user option and Microsoft’s reported customer feedback are direct counterevidence to claims of an immediate, universal collapse.¹⁷ The more credible structural shift is toward layered contracts: seats for people, consumption meters for agents and, in some cases, charges tied to conversations or outcomes. Independent reporting already documents experimentation with those alternatives across the market.⁶¹⁰

CIOs should therefore treat pricing architecture as part of system architecture. A workflow design that uses more agent actions, longer conversations or greater token volume can alter economics even when the software’s sticker rate does not change. Procurement cannot evaluate these contracts separately from process engineering, and engineering cannot optimize an agent without visibility into the commercial meter. The winning enterprise discipline will be the ability to translate every proposed billing unit into cost per accepted unit of work—and to reject contracts where that translation cannot be audited.

Three moves for CIOs

— Build a workload bill of materials before comparing agent prices Select representative workflows and map every expected billable event: human seats, agent actions, conversations, tokens, retries and accepted outcomes. Require each shortlisted vendor to price the same workload under every available model, then calculate expected cost and a high-volume scenario per enterprise-accepted outcome. Keep vendor-native units visible rather than converting them through unsupported equivalencies.
- Decision trigger: Make this analysis mandatory whenever a proposal includes more than one billing unit, combines seats with variable consumption, or cannot state the expected cost of a defined end-to-end workflow.
- Why now: Salesforce already exposes several simultaneous meters, while monday.com and Meta have documented different hybrid structures.¹³⁴ Comparing their headline unit prices would confuse unlike scopes of work. A workload bill of materials gives the CIO a common denominator without pretending that an action, token, conversation and resolution are equivalent.
— Contract for semantic stability, not only price protection Define each billable unit in the order form, including treatment of retries, failed actions, test activity, duplicate events and human escalation. Require auditable usage records, advance notice of measurement changes and a repricing or termination right if the vendor changes how credits are consumed. Add budget alerts and a hard approval gate before overages can exceed the enterprise’s agreed ceiling.
- Decision trigger: Escalate the contract when the supplier can change credit consumption, redefine a resolution, charge for unsuccessful work or permit variable spend above the approved ceiling without affirmative customer approval.
- Why now: The documented models meter fundamentally different events.¹⁴ As machine activity becomes a revenue driver, nominal rate protection is insufficient if the supplier can alter how much work one credit represents. Locking down the unit’s meaning protects the economics of automation rather than merely preserving a published price.
— Run seat and consumption models in parallel before committing During a controlled production period, calculate the same workload under per-user, credit, conversation and outcome-based alternatives wherever the vendor offers them. Compare not only average cost but also cost variability and the share of charges associated with unsuccessful or unaccepted work. Favor the structure whose bill most closely tracks an outcome the enterprise can verify.
- Decision trigger: Require a parallel-model test before renewal when agent adoption could reduce human seats, when usage volume is materially uncertain, or when more than 10% of measured charges arise from retries, failures or work the enterprise does not accept as complete.
- Why now: Per-seat pricing has not disappeared: Salesforce retains a per-user option, and Microsoft reported continued customer preference for that model.¹⁷ CIOs can use the coexistence of old and new structures as negotiating leverage. Testing both exposes whether a usage model rewards productive automation or simply shifts demand uncertainty from the vendor to the customer.

Salesforce and monday.com Put AI Agents on Usage Meters, Breaking SaaS’s Seat-to-Value Link

Take the argument with you.

What changed

Why it matters

Frontier take

Three moves for CIOs

Sources