Salesforce's Agentic Enterprise License Agreement (AELA): The "All-You-Can-Eat" Trap

Updated

Salesforce's Agentic Enterprise License Agreement (AELA): The "All-You-Can-Eat" Trap

To counter enterprise buyer resistance to highly unpredictable, consumption-based AI pricing, Salesforce introduced the Agentic Enterprise License Agreement (AELA). This flat-rate, seat-based, "unlimited-use" model over two or three years covers Agentforce, Data Cloud, and MuleSoft.

While the predictability of a flat-rate deal is highly attractive to CFOs, the strategic intent behind it is long-term, high-friction lock-in.

Willing to Lose Money for 20-Year Lock-In

Salesforce's executive leadership has openly admitted that they are comfortable losing money on AELA contracts in the short term because of the massive lock-in it creates. Speaking at the Barclays 23rd Annual Global Technology Conference in December 2025, Salesforce President and Chief Revenue Officer Miguel Milano stated:

"We take the risk because we want our customers to be successful. There's nothing that I would love more than a customer that I price... at $5 million incremental AELA, and the customer deploys so much that all of a sudden, that deal is not profitable for me. If that is not profitable for me, it means that the customer is the happiest customer in the world. And then I have another 20 years to monetize that customer."

By shifting the commercial conversation from a metered utility to a flat "digital labor" bundle, Salesforce is encouraging rapid, pervasive adoption of its agents. This makes its platform operationally irreplaceable before the contract ever comes up for renewal.

Gartner's Warning: The Renewal Cost Shock

Enterprise software procurement experts warn that this "all-you-can-eat" buffet won't last forever. In January 2026, Gartner issued a warning to Salesforce users, advising them to scrutinize the exit and renewal terms of AELAs before signing.

Hannah Decker, Gartner Director Analyst for IT Sourcing and Procurement, warned:

"Gartner believes that these are going to be converted into defined quantity contracts at the end of the agreement... If they're moving to a defined quantity contract, there needs to be limits on price increases at renewal. Making sure there are caps that protect you when the agreement ends is critical."

Gartner highlighted several critical risks for buyers under these agreements:

  1. Lack of Historical Baseline: Because agentic AI is a brand-new capability, enterprises have no historical data to accurately forecast how many credits or "conversations" they actually need once the flat-rate period ends.
  2. Unilateral Multiplier Changes: In many consumption-based credit agreements, vendors retain the right to unilaterally change the multiplier or consumption rate of credits mid-term. This means an enterprise's credit consumption could surge even if their actual usage remains unchanged.
  3. Compounding Uplifts: Broad Salesforce price hikes of 6% to 15% are feeding directly into renewal uplifts, making future defined-quantity renewals steeply expensive.
What This Means for Founders

For founders competing with Salesforce, the AELA strategy is a formidable defensive play. Salesforce is using its balance sheet to subsidize AI compute costs in exchange for deep, multi-decade behavioral lock-in.

  • Compete on Price Predictability and Portability: Founders should highlight the "renewal trap" of AELAs. Offer price caps, transparent consumption models, and data portability to appeal to risk-conscious procurement officers who fear future cost shocks.
  • Outcome-Based Pricing: While Salesforce locks buyers into multi-year agreements, smaller startups can win by anchoring their pricing to clear, immediate, and measurable business outcomes rather than seat licenses.1

  1. An instance of AI is turning software companies into heavy utility businesses — This advice directs software startups to abandon traditional per-user subscription models in favor of pricing based strictly on the work or results their AI delivers. ↩︎

Part of

This finding is an example of a pattern recurring across your work:

Revision history

  • Updated without a stated reason.
    · by migration
  • Updated without a stated reason.
    · by migration
  • Updated without a stated reason.
    · by migration
  • Updated without a stated reason.
    · by migration