How Much Does Salesforce Enterprise Cost in 2026: Pricing, AELA and Real TCO

How much it costs to implement Salesforce in an enterprise operation has no single answer. It is an equation with three pricing variables that add up over the life of the contract: the license per user/month, ranging from US$ 25 in the Starter edition to US$ 550 in Agentforce 1; operational support after go-live; and, from 2026 onward, the new AELA model for those intending to operate Agentforce at scale without locking the budget into individual credits. This guide brings the three layers together in one place — something currently spread across official documentation, international analyses, and fragmented support content — so that the financial buyer (CFO, Procurement, project sponsor) can build the real TCO before signing any contract.

How much does Salesforce cost per user/month in 2026?

Salesforce charges per user/month, billed annually, and the price ranges from US$25 to US$550 depending on the edition purchased. This is the foundation of any budget, but it is far from the total cost: implementation, integrations, and ongoing support are added to it, as you will see in the following sections.

Official pricing table by edition, in US dollars, consulted on 21/08/2026 (source: salesforce.com/br/pricing/ and salesforce.com/pricing/flexible-buying-models/):

Edition	Price per user/month (USD, billed annually)	Best suited to
Starter	US$ 25	Small teams getting started with CRM
Pro Suite	US$100	Growing companies with more mature sales and service processes
Enterprise	US$165	Enterprise operations with customization, automation, and integrations
Unlimited	US$ 330	Enterprise operations requiring premium support and higher limits
Agentforce 1	US$ 550	Operations that place autonomous AI agents at the centre of service and sales

Three important points about this billing model:

• It is per named user, not per usage. Each license is assigned to one person, regardless of whether they log in every day or once a month. This makes the right-sizing the number of licences is one of the greatest savings levers, discussed later.
• Annual billing is the rule, not the exception. Monthly contracts exist, but they cost more per user. The discount built into the annual plan is part of the negotiation.
• Billing is always in US dollars. The Salesforce master agreement is in USD, and this is where the differentiator that WeeNow presents in this guide comes in: how official Salesforce Partner, we can structure quotations and billing in Brazilian reais for your operation, eliminating direct exchange-rate exposure at the contract level.

What changed in 2026: the new AELA (Agentic Enterprise License Agreement) model

The AELA (Agentic Enterprise License Agreement) is a fixed-price, two- to three-year agreement that provides unlimited use of Agentforce, Data 360, and MuleSoft with no charge per credit consumed. It was created to solve a real problem: how to budget for agentic AI when consumption varies month to month and credit-based billing makes costs unpredictable. No Portuguese-language content covers this model to date, and this is precisely where the CFO needs to pay attention before choosing between AELA and the traditional credit model.

Alongside AELA, Salesforce maintains the so-called buying models for those who prefer to pay for consumption through Flex Credits:

• Pay-as-you-go: you pay for what you consume, with no prior volume commitment. Flexible, but with the highest risk of unplanned variable costs.
• Pre-commit: you commit to a minimum consumption volume in exchange for a lower unit price per credit, while maintaining some flexibility of use.
• Pre-purchase: you buy a batch of credits in advance at a discount off the unit price, but take on the risk of unused credits (consumption shelfware).

Forrester's market analysis of this change is straightforward: AELA repositions AI agents as productive assets within the technology budget, rather than as a pay-per-use utility. It is a shift in financial framing, not just pricing.

This does not mean AELA is the right choice for every operation. Two risks deserve attention in the negotiation:

• Renewal baseline: flat-fee contracts tend to set the prior period's consumption level as the floor at renewal, even if some of that consumption was temporary or optimistically projected.
• Aspirational scope: it is common for the initial AELA proposal to be sized according to usage potential of the operation, rather than on projected actual usage based on historical data. Negotiating scope based on the conservative scenario rather than the ideal scenario is the buyer's greatest source of leverage.

Editions, Sales Cloud, Service Cloud, and Agentforce: which should you choose for an enterprise operation?

For most enterprise operations, the practical decision is between Enterprise, Unlimited, and Agentforce 1. Starter and Pro Suite rarely meet the process complexity, integration, and scale requirements of a large operation. Enterprise is the minimum technical starting point for genuine customisation and automation. Unlimited adds premium support and expanded limits. Agentforce 1 is the choice when autonomous AI agents move beyond pilots and into production in sales or customer service.

Those who do not sign AELA and choose to consume AI through credits need to understand the Flex Credits model: Agentforce action consumption is charged per unit of work performed by the agent, with a market reference of around US$ 0.10 per action. For operations with a high and predictable volume of interactions, AELA tends to pay off. For operations still testing use cases, the on-demand credits model avoids premature commitment.

One point often overlooked in this decision: modules such as CPQ have their own pricing and licensing logic, which is added to rather than replaces the platform license. It is worth understanding how CPQ works in Salesforce before closing your operation's edition package.

What are Salesforce's hidden costs (TCO beyond the license)?

The license rarely represents more than half of the total cost of ownership of an enterprise implementation. Implementation, integrations, data migration, storage, AppExchange apps, and ongoing support make up the rest, and it is precisely this total that separates a realistic budget from an optimistic one.

The main hidden cost items:

• Initial implementation: discovery, configuration, automation, and testing. This is the largest non-recurring cost item in the project.
• Integration with other systems, including MuleSoft: ERPs, e-commerce platforms, and legacy systems rarely communicate natively with Salesforce. More robust integration projects usually involve MuleSoft in practice, with its own licensing and implementation costs.
• Data migration: cleansing, mapping, and loading historical data, especially critical when the operation migrates from a legacy CRM or spreadsheets.
• Additional storage: the data and file limits included in the editions are typically insufficient for enterprise operations with many years of history.
• AppExchange apps: industry- or process-specific functionality often requires paid apps, billed separately from the platform license.
• Application Management Services (AMS): the recurring cost of keeping the operation running after go-live. We cover this in detail in the next section, because this is where most TCO budgets go wrong through oversimplification.

Support (AMS): how much does it cost to keep Salesforce running and how can you compare proposals?

Salesforce ongoing support, also known as AMS (Application Managed Services), is charged under four main models: blocks of hours, per ticket/SLA, fixed monthly retainer, or ad hoc hourly rates. There is no universally 'right' model. The right choice depends on your operation's volume of recurring requests and the budget predictability you need.

The four models in practice:

• Block of hours (monthly hour bank): you contract a fixed number of hours per month, with rollover or loss of unused hours depending on the contract. Good for operations with relatively stable demand.
• Per ticket or SLA: billing tied to opened tickets and contracted response times. It works well when ticket volume is low and unpredictable.
• Retainer / fixed monthly contract: a fixed monthly fee covering a defined support scope, usually with a dedicated or shared squad. More predictable for multi-year budgeting.
• Ad hoc hourly / project: one-off engagement without a recurring commitment, more expensive per hour but with no long-term commitment.

As an international market benchmark, ongoing support ranges typically vary from US$1,500 to more than US$25,000 per month, depending on the size of the operation, the complexity of the org, and the contracted SLA level. The same logic applies, proportionally, to contracts in Brazilian reais with Brazilian partners.

The most common mistake when comparing support proposals is to look only at the final monthly fee. Two proposals with the same price can differ enormously in change governance, technical documentation, and the ability to reduce technical debt over time. And it is accumulated technical debt — not the monthly fee — that usually explains why an operation gets stuck and stops evolving months after an apparently successful go-live.

Outsourced support vs. in-house build: the comparison CFOs need to see

The decision between building an in-house team and hiring outsourced support is rarely just about the hourly rate. It is about continuity risk, the specialisation curve, and the speed of response to business changes. Comparing only an administrator's salary with the monthly fee of an AMS contract underestimates the real cost of an in-house build.

An in-house Salesforce administrator typically earns a base salary of R$4,000 to R$12,000, plus employment costs of roughly 70% to 80% of the base salary, before accounting for recruitment costs, ramp-up, absences, and turnover risk — which in practice means rebuilding the org's knowledge curve from scratch. An ongoing support contract with an official partner spreads this risk across a team with multiple specializations, built-in coverage for absences, and usually a contractual SLA. However, it requires diligence in choosing the partner, since ongoing-support quality varies as much as the quality of an in-house hire.

There is also a lens that rarely enters this calculation: the cost of inheriting an org with years of undocumented customizations versus rebuilding parts of it from scratch (the greenfield approach) with an official partner. Orgs with accumulated technical debt tend to require more support hours per month, not because the contract is poor but because the base being supported was already compromised from the start. Before comparing AMS proposals, it is worth understanding how to choose a Salesforce consultancy that assesses this technical debt as part of the scope, rather than as a surprise in the third month of the contract.

How CFOs and Procurement should build the business case: a financial decision framework

Building the Salesforce business case requires deciding three things before signing any proposal: whether the investment is treated as capex or opex, how much risk of idle or excess consumption the operation is willing to assume, and what return is reasonable to expect from AI agents over the contract term. None of these decisions is purely technical. They are financial decisions that the technology area should not make alone.

Capex vs. opex in buying models: pre-purchase follows a capex-like logic, with an upfront payment that is recognized over consumption and the risk of unused credits. Pay-as-you-go is pure opex, with no volume commitment but lower budget predictability. Pre-commit sits in between: a minimum volume commitment at a better unit price, retaining part of opex flexibility.

Due-diligence questions before signing an AELA:

• What is the exact consumption metric accounted for in the contract, and how is it audited?
• What happens in the event of an overage, meaning consumption above the flat fee?
• Does the agreement explicitly define the renewal baseline, or is it left open for future negotiation based on consumption in the preceding period?
• Is there a clause for reallocating capacity between products (Agentforce, Data 360, MuleSoft) within the same contract?

ROI vs. the risk of shelfware and overage: the expected return on an Agentforce investment must be weighed against two opposing risks: paying for licenses or credits that are not used (shelfware) and paying overage because actual consumption was underestimated. A simple decision framework is to project consumption across three scenarios (conservative, expected, aggressive) and determine under which of those scenarios each buying model — pay-as-you-go, pre-commit, pre-purchase, or AELA — pays for itself.

Real TCO: a numerical example for an enterprise operation in 2026

For an operation with 200 users on the Enterprise edition (US$ 165/user/month, billed annually), the annual licensing cost is US$ 396,000 (200 × US$ 165 × 12 months), excluding implementation, integrations, support, or AI consumption. This figure alone shows why TCO should never be confused with list price.

For the same operation evaluating an AELA scenario for unlimited use of Agentforce, Data 360, and MuleSoft, the relevant comparison is not licence against licence, but rather the AELA flat fee (negotiated case by case according to the projected volume of agents and actions) against the estimated cost of Flex Credits under the pay-as-you-go model for the same usage volume. If the operation projects a high, consistent volume of agent interactions throughout the agreement, the flat fee tends to be less expensive and more predictable. If the volume is uncertain or seasonal, the on-demand credit model avoids paying for idle capacity.

Added to this licensing amount are the hidden costs already described (implementation, integrations, data migration, storage, AppExchange) and recurring support, whose billing model (hour blocks, SLA, retainer, or ad hoc hourly) you choose according to the operation's demand profile. Because licenses are always billed in dollars, the final amount in Brazilian reais depends on the exchange rate in effect when the contract is signed. Therefore, structuring a quotation in reais with an official Salesforce partner is part of financial planning, not an operational detail.

How to reduce and optimize Salesforce licensing and ongoing support costs

Reducing Salesforce TCO does not mean negotiating an aggressive discount without criteria. It means eliminating structural waste before negotiating price. The most effective levers are:

• Right-sizing the number of licenses: because billing is per named user, licences assigned to inactive or very low-usage users are the most common and easiest-to-correct waste.
• License mix by usage profile: not every user needs Unlimited or Agentforce 1. Segmenting by edition according to each team's actual needs reduces average cost per user without losing capacity where it matters.
• Pre-renewal review: renegotiating the contract months before expiry, with actual usage data in hand, is when you have the greatest bargaining power. Negotiating after renewal means negotiating without leverage.
• AELA scope negotiation: when evaluating an AELA contract, negotiate scope based on projected actual consumption, not on the aspirational scenario presented in the proposal, and seek contractual flexibility to reallocate capacity among products over the term.

Frequently asked questions about Salesforce pricing in 2026

How much does Salesforce cost per user/month in 2026? Official prices range from US$ 25/user/month for the Starter edition to US$ 550/user/month for Agentforce 1, with annual billing (consulted on August 21, 2026, salesforce.com/br/pricing/). Enterprise operations generally choose among Enterprise (US$ 165), Unlimited (US$ 330), and Agentforce 1 (US$ 550), according to automation maturity and agentic AI use.

What is an AELA (Agentic Enterprise License Agreement), and when is it worthwhile? It is a fixed-price, two- to three-year agreement with unlimited use of Agentforce, Data 360, and MuleSoft, without charges per credit consumed. It is worthwhile for operations with high and consistent volumes of AI-agent usage. For operations still testing use cases, the on-demand credit model is generally safer.

What is the difference between pay-as-you-go, pre-commit, and pre-purchase for Flex Credits? Pay-as-you-go charges for actual consumption, with no prior commitment. Pre-commit requires a guaranteed minimum volume in exchange for a lower unit price. Pre-purchase is the advance purchase of a discounted batch of credits, but carries the risk of unused credits. The choice depends on the predictability of your operation's AI consumption.

How much does Salesforce support (AMS) cost and what are the billing models? The most common models are blocks of hours, per ticket/SLA, fixed monthly retainers, and ad hoc hourly work. As a market reference, monthly fees typically range from US$1,500 to more than US$25,000, depending on the size of the operation and the contracted SLA level.

Is it better to outsource support or build an internal team? It depends on the continuity risk the company is willing to accept: an internal administrator costs base salary plus 70% to 80% in employment costs, as well as turnover and ramp-up risk. An outsourced support contract spreads that risk across a team with coverage and a contractual SLA. Orgs with significant technical debt tend to benefit more from the structure of a specialized partner.

What are the hidden costs beyond the Salesforce license? Initial implementation, integrations (including MuleSoft), data migration, additional storage, AppExchange apps, and recurring ongoing support. Together, these items often exceed the license cost in the first year's total TCO.

How can you negotiate or reduce Salesforce's total cost of ownership (TCO)? The most effective levers are right-sizing the number of licences, tailoring the edition mix to user profiles, reviewing the agreement before renewal, and, for AELA agreements, negotiating scope based on projected actual consumption rather than the aspirational scenario presented in the proposal.

Is Salesforce priced in U.S. dollars or Brazilian reais? Salesforce contract billing is always in US dollars (USD). For operations in Brazil, structuring quotations and billing in Brazilian reais depends on an official Salesforce partner, which can negotiate this condition within the contracting process.

---

Building the real Salesforce TCO (license, AELA, ongoing support, and in-house build) requires comparing scenarios using your operation's data, not market averages. Request a Salesforce licensing and TCO assessment from WeeNow, an official Salesforce partner, and receive a quote in Brazilian reais for your enterprise operation.