Contents
Key takeawaysWhat Experience Cloud costsMember and login licensesWhich license is cheaperWhat we have seenThe API cost portals missWhat the account team saysOrder form termsRenewal review timelineWhat to do nextFAQExperience Cloud portals often overpay because every external user sits on one license type. Meter a quarter of logins, split members from login pools by audience, and price External Apps before the member commitment locks.
- Two metrics, very different bills. Member licenses charge for every named user each year, while login licenses charge one login per user per day from a pool that rolls over month to month.
- The crossover is about 2.5 logins. Above roughly two and a half logins per user per month a member seat is cheaper, and below it the login pool wins.
- Idle members are the largest waste. In the portals we reviewed, a large block of named members barely logged in yet was billed in full every year.
- Size pools for the whole year. Login overage is measured over 12 months and billed at retail, so peak seasons and growth belong in the pool size.
- Quote External Apps early. At tens of thousands of monthly active users it is usually the cheapest option, but only if it is priced before member quantities are set.
- API limits are per org. A busy portal shares one daily API allocation with every integration, so price a top up before renewal.
What is Salesforce Experience Cloud and what does it cost in 2026?
Experience Cloud is the Salesforce portal product, priced per external user as either a named member or a login.
The customer self service pricing page lists Service Portal Member at $10 per member per month, with unlimited sessions, and Service Portal Login at $4 per login, each login covering a 24 hour session. Partner Relationship Management lists at $25 per member per month, billed annually.
Customer communities, partner portals, employee self service sites and, increasingly, the front end of agent products all run on it. Salesforce lists the offering on the Experience Cloud pricing page, which now routes to separate pages by use case.
How the editions map to use cases
- Customer Community. Mostly read access with low write volume. Built for consumer and support portals.
- Customer Community Plus. Heavier write access plus role hierarchy and sharing, for external users who need partner like access to data.
- Partner Community. Full sales pipeline access, including leads and opportunities, for resellers and other external partners.
- Channel Account. The license for very large channel populations. It is counted by partner account, and each licensed partner account covers up to 40 partner users. Compare it with the wider platform editions before you commit.
- External Apps. Custom digital experiences such as brand engagement and loyalty sites, with room for 100 custom objects per license against 10 on the community licenses.
The discounts off those list prices changed in 2026 as well. Salesforce brought firmer discount floors, a tighter login conversion ratio and a stronger push toward External Apps for partner volume. Together those changes shifted the renewal economics for most portals we reviewed.
How does Experience Cloud pricing work for member and login licenses?
Every external license is sold on one of two metrics, and the same traffic produces two different bills. A member license is a named seat billed for the year. Each provisioned member counts whether they log in or not, so the cost is stable but expensive for people who visit a few times a year.
A login license draws on a pool of monthly logins. Salesforce counts daily unique logins, so a user who signs in five times on Tuesday uses one login, and switching between your sites after signing in uses none. The pool flexes with traffic, but a busy site drains it quickly.
The login pool rules that decide your bill
- Rollover. Unused logins carry from month to month, and overage is measured across 12 months from the contract start date.
- Annual total. Buying 1,000 monthly logins gives you 12,000 logins across the contract year.
- Provisioning ratio. You may provision up to 20 login users for each monthly login you buy, so 1,000 monthly logins allow 20,000 provisioned login users.
- Overage price. Logins beyond the annual total are billed at the retail rate, whatever discount you negotiated on the pool.
What External Apps changes
External Apps is the newer license for very large customer or partner populations, documented in the Salesforce documentation. It is sold per member or per login, with 10 times the custom object capacity of the community licenses. Its login license also carries 400 API calls per user a day, against 10 for Customer Community Plus and Partner Community logins.
In the 2026 quotes we reviewed, External Apps carried a higher list price than the older partner licenses. At scale, though, the effective rate per user came in well below them, which is why its timing in the negotiation matters so much.
| License type | How it is counted | Best fit | Main risk |
|---|---|---|---|
| Member | Per named seat, billed annually | Stable audience that logs in often | You pay for inactive users |
| Login | Per daily unique login, drawn from a monthly pool | Large audience that visits occasionally | Overage billed at retail |
| External Apps | Per member or per login, with higher object and API allowances | Very large customer or partner base | Identity and data governance work |
| Channel Account | Per partner account, up to 40 users each | Multi tier partner programs | Edition lock at scale |
| Customer Community Plus | Per member or per login, with write access | Partner like external users | Role hierarchy sprawl |
Salesforce Renewal Negotiation Guide
How to plan a Salesforce renewal, from license counts to the final order form.
Get the white paper →Which Experience Cloud license is cheaper for each audience?
Login frequency decides it, and the crossover can be measured. At the list prices above, $10 for a member divided by $4 per login puts the break even at 2.5 logins per user per month. On negotiated quotes we use the same rule of thumb, roughly two and a half login days per user per month.
When member licenses win
Members pay off for stable, predictable audiences with high engagement, such as partners who register deals every week. Price the member license only for groups whose measured average sits above the crossover. Below that line, the login pool is cheaper.
When login licenses win
Logins suit sporadic audiences: customer support portals, learning sites and partners who check in now and then. Size the pool so that 12 months of it covers your peak months and expected growth, because overage on logins is billed at retail, often double the in pool rate.
When External Apps wins
External Apps wins at scale. Once an audience passes tens of thousands of monthly active users, the cost per user on member and login licenses stops making sense, and External Apps usually becomes the cheapest path. The trade off is governance, because it needs deliberate identity and data architecture from the start.
A worked example at list price
Say you run a customer portal with 20,000 registered users on the Service Portal list prices. 4,000 of them are active customers who log in on 6 days a month. The other 16,000 log in on 1 day a month.
| Approach | 4,000 active users | 16,000 occasional users | Annual total |
|---|---|---|---|
| Everyone on member licenses | $480,000 | $1,920,000 | $2,400,000 |
| Everyone on a login pool | $1,152,000 | $768,000 | $1,920,000 |
| Split by audience | $480,000 (member) | $768,000 (login) | $1,248,000 |
The split costs $1,152,000 a year less than an all member contract, a 48 percent reduction, and $672,000 less than an all login pool. Each single model overprices one of the two groups. The same logic holds at discounted rates, so rerun it with the numbers on your own quote.
What happens when a login pool is sized to average traffic
Take a portal that sizes its pool to a normal month and buys 20,000 logins a month at a hypothetical negotiated $2 per login. Nine normal months use 20,000 each and three peak months use 30,000. The year totals 270,000 logins against 240,000 purchased, leaving 30,000 in overage.
At a retail overage price of $4, those 30,000 logins cost $120,000. Bought inside the pool at $2, they would have cost $60,000.
What have we seen in recent Experience Cloud renewals?
We benchmarked roughly 40 to 55 Salesforce engagements between 2024 and 2025. Experience Cloud was the line item buyers understood least, and after rework the median renewal reduction we achieved was 24 percent.
- Idle members. Member licenses sat idle on 30 to 45 percent of named seats and were billed in full every year.
- Undersized login pools. Pools sized to average traffic overran at retail prices across 2 to 4 peak months.
- External Apps quoted too late. In 3 of 5 large accounts, Salesforce quoted External Apps only after the member commitment was locked.
The first two patterns are the same mistake pointed in opposite directions. Both come from sizing to an assumption before anyone measured logins. The third turns a pricing question into a timing one, since a comparison made after signature changes nothing.
Why we do not treat member licenses as the safe default
The standard account team pitch is that member licenses are the safe default and login pools are a niche option for low traffic sites. We disagree. In roughly 3 of 5 accounts we rebuilt, a large block of named members logged in less than twice a month, so the member commitment paid for access no one used.
The better course is to meter actual logins for one quarter, move the idle members to a login pool sized for the full year, and keep External Apps in reserve as the fallback for scale. Login metering over a single quarter usually settles the member against login argument faster than any list price comparison.
Members feel safe and logins feel risky, but the bill almost always favors a hybrid that you rebalance every quarter.
Which hidden Experience Cloud cost do high traffic portals miss?
API capacity is the cost most buyers miss. Salesforce enforces API limits against the whole org over a rolling 24 hours, not per community, so a busy portal shares one allocation with every integration you run.
For Enterprise and Unlimited editions, the daily allocation is 100,000 calls, plus a set number per license, plus any API Call Add-Ons. Partner Community and Customer Community Plus members add 200 calls each, their login users add 10, and Customer Community adds none. Past the limit, Salesforce allows a short grace margin before a hard cap stops calls.
The fix Salesforce offers is more licenses or API Call Add-Ons at list price. Inventory API usage before renewal and negotiate a top up at a rate below list, written into the order form.
How to check your own position
- Setup, Company Information. The User Licenses list shows total and used seats for each external license, and the Usage based Entitlements list shows your login allowance and consumption. The same page shows API requests over the last 24 hours.
- Last Login on user records. A user report filtered by license type and sorted by Last Login shows which members have not signed in for 90 days.
- Login History. Setup keeps about 6 months of logins, including logins to your sites. Download it each quarter so you build a full year of data.
- A modeled split. Our utilization calculator turns those counts into a member and login split you can take to the account team.
What will the Salesforce account team say about Experience Cloud pricing?
Expect the conversation to favor larger member counts and later External Apps quotes, since both protect the recurring total. These lines come up often.
| What you will hear | What to say back |
|---|---|
| "Member licenses are the safe choice. You never have to watch a login count." | "A quarter of Login History shows this block signs in less than twice a month. We want them on logins, with both rates fixed for the term." |
| "External Apps is a separate project. We can look at it next year." | "Quote it now, next to the member renewal. We will not set member quantities until we have both prices." |
| "The 2026 conversion ratio makes moving members to logins expensive." | "Put the ratio in writing and we will model it against our logins. Conversion at renewal should be value for value." |
| "Size the pool to your average month. Overage rarely comes up." | "Then overage at our contracted per login rate costs you nothing. Write it in." |
| "More API capacity comes with a larger license bundle." | "Price API Call Add-Ons as a separate line at our discount level." |
What should the Experience Cloud order form say?
It should fix rates for both metrics, let you move users between them, and cap what overage and extra API capacity can cost. Ask for all of it in the same negotiation as the licenses, because each term gets harder to win after signature.
- Conversion right. The right to move users between member and login licenses at renewal, value for value, so the mix can follow the audience.
- Overage at the contracted rate. Logins past the annual total billed at your per login rate, with written notice before any overage invoice.
- Annual measurement confirmed. Rollover and the 12 month overage period as documented, with no monthly cap added in the order form.
- Price hold for additions. Member, login and External Apps rates held for additions during the term.
- Reduction right. The right to cut member quantities at renewal after removing idle users, without losing the discount on the rest.
- API top up price. A fixed rate for API Call Add-Ons below list.
How the priorities change with portal size
Take a hypothetical channel program with 800 partner accounts averaging 12 users each. On Channel Account that is 800 licenses instead of 9,600 named partner seats, so the account count, the 40 user ceiling and the price hold deserve most of the effort.
A hypothetical portal with 150,000 registered customers has the opposite problem. Most users are occasional, so idle members and pool sizing drive the bill. On logins, the 20 to 1 ratio alone requires at least 7,500 monthly logins for that audience.
When should you start reviewing Experience Cloud before renewal?
Start 12 months out, because a full year of login data takes that long to collect. Work back from the renewal date as below, and use the renewal war room checklist to run the negotiation itself.
| Months before renewal | What to do |
|---|---|
| 12 | Download Login History and schedule quarterly exports. List every site, audience and license type, and record daily API use. |
| 6 | Band users by login frequency. Model member, login and External Apps costs, and ask for an External Apps quote now. |
| 3 | Deactivate idle members. Send Salesforce the target mix plus the conversion, overage and API terms you want. |
| 1 | Check the order form line by line: rates per metric, login allowance, overage terms and API add ons. |
Our renewal timeline places this review inside the wider Salesforce renewal, and the renewal negotiation guide covers the full sequence. For the license rules by audience, see our Salesforce community licensing guide.
What to do next
- Meter logins for a quarter. Pull a full quarter of Login History by license type and band each audience by login days per month.
- Move idle members to logins. Convert them to a login pool sized so 12 months of it covers peak seasons and growth.
- Quote External Apps early. Get it priced before the member commitment locks, even if you do not plan to buy it this term.
- Inventory API usage. Check daily API requests against the org allocation and negotiate a top up below list.
- Write the terms in. Secure conversion, overage and reduction rights in the order form.
- Make conversion a quarterly check. Review the mix every quarter so it keeps tracking the audience as traffic changes.
- Get independent help early. Talk to our Salesforce advisory team before the renewal quote arrives.
Holding a Salesforce quote or renewal? Our Salesforce contract negotiation team works only for buyers, for a fixed fee or 25 percent of what we save you.
Frequently asked questions
How many Experience Cloud member seats sit idle?
Across the engagements we benchmarked, 30 to 45 percent of named member seats sat idle while being billed in full. The quickest test is a user report on Last Login filtered by external license type, which shows the idle block before the renewal quote arrives.
What is the difference between a member and a login license?
A member license is a named seat billed for the year whether the user signs in or not. A login license draws on a monthly pool, and each user uses one login per day however many times they sign in. Within one edition the access rights are the same on both, so frequency of use should decide.
Where is the crossover between member and login licenses?
Roughly two and a half logins per user per month. Divide the monthly member price by the per login price on your own quote to get your exact figure, then compare it with each audience's average login days.
What goes wrong with Experience Cloud login pools?
They get sized to average traffic. Pools sized that way overran at retail across 2 to 4 peak months in the accounts we reviewed. Rollover absorbs one busy month, but a peak season plus growth pushes the annual total past what you bought.
When does External Apps become the cheapest license?
Once an audience passes tens of thousands of monthly active users. It also allows 100 custom objects per license and a higher API allowance on login licenses, which matters for loyalty and brand sites that sit on custom data models.
What is the trade off with External Apps?
More governance work. You need a deliberate identity design, clear data sharing rules and ownership of the custom object model before launch, which the per seat community licenses rarely demand.
Why does the order of quotes matter?
In 3 of 5 large accounts, External Apps was quoted only after the member commitment was locked, when the comparison could no longer change anything. Ask for both quotes in the same round and refuse to set member quantities first.
Is the member license the safe default for external users?
No. In roughly 3 of 5 accounts we rebuilt, a large share of named members signed in less than twice a month. Members only make sense for audiences whose measured logins sit above the crossover.
What settles the member versus login question fastest?
One quarter of login metering by license type. Real login days per user answer the question faster than any list price comparison, and the same data supports your conversion request.
What hidden cost catches high traffic Experience Cloud portals?
The API allocation. It is counted per org rather than per community, so portal traffic competes with every integration. Past the limit Salesforce stops calls at a hard cap, and extra capacity is sold at list unless you negotiate a top up rate.