Member licenses sat idle on 30 to 45 percent of named seats and were billed in full every year, because the member commitment paid for access nobody used
Members feel safe and logins feel risky. The bill says the answer is almost always a hybrid, with quarterly conversion as the operating gate.
Prepared by Redress Compliance · August 19, 2026 · Salesforce engagements benchmarked. 40 to 55 files, 2024 to 2025.
Executive summary
Idle members ran 30 to 45 percent of named seats, billed in full every year, across roughly 40 to 55 Salesforce engagements benchmarked between 2024 and 2025.
Login pools were sized to average traffic, then overran at retail across 2 to 4 peak months, which is the mirror image of the same planning failure.
External Apps was quoted late in 3 of 5 large estates, after the member commitment had already been locked.
Experience Cloud was the line item buyers understood least, and the median renewal reduction achieved was 24 percent.
What is Experience Cloud and who is it for?
It is the portal product. Customer communities, partner portals, employee self service and increasingly the front end of agent products all sit on this platform.
Salesforce sets out the offering on the Experience Cloud pricing page.
The 2026 posture introduced firmer discount floors, a tighter login conversion ratio, and a sharper push toward External Apps for partner volume. The combination moved the renewal math.
How the editions map to use cases
- Customer Community: read mostly, low write volume, consumer portals.
- Customer Community Plus: heavier write, role hierarchy, partner like access.
- Partner Community: full sales pipeline access for external partners.
- Channel Account: the SKU for very large channel populations, set against the wider platform editions.
How does the pricing actually work?
Three metrics, and they behave completely differently under the same traffic.
Member licenses are an annual seat. Each named member counts whether they log in or not, so the metric is stable but expensive for sporadic users.
Login licenses are a monthly pool where each login consumes one credit. The metric flexes, but the pool runs out fast on a high traffic site.
What External Apps changes
External Apps is a newer SKU targeting very large partner or customer populations on a transaction or platform basis, documented in the Salesforce documentation.
The 2026 list price is higher than the legacy partner SKUs, but the per user effective rate is materially lower at scale.
| License type | Metric | Best fit | Risk |
|---|---|---|---|
| Member | Per named seat per year | Stable, high engagement audience | Pays for inactive users |
| Login | Per login from monthly pool | Sporadic, large audience | Overage at retail |
| External Apps | Per platform plus transactions | Very large customer or partner base | Governance complexity |
| Channel Account | Aggregate channel population | Multi tier partner programs | Edition lock at scale |
| Customer Plus | Per member with write access | Partner like external users | Role hierarchy sprawl |
- Your implied discount measured against the 2026 list ladder
- Unused seat waste quantified per audience, member against login
- Compounding renewal uplift modelled before you agree the term
Which license type wins for each audience?
It depends on login frequency, and the crossover is measurable rather than a matter of judgement.
When member wins
On stable, predictable audiences with high engagement. Pricing the member SKU only makes sense above roughly two and a half logins per user per month.
Below that, the login pool is cheaper.
When login wins
On sporadic audiences. Customer support portals, learning sites and infrequent partner check ins all suit the login model.
The pool must be sized to handle the peak, because overage on logins is billed at retail, often double the in pool effective rate.
When External Apps wins
At scale. Once the audience crosses tens of thousands of monthly active users, the per user math collapses and External Apps becomes the cheapest path.
The trade off is governance overhead, because it needs more deliberate identity and data architecture.
Login metering for a single quarter usually settles the member against login argument faster than any list price comparison.
The Salesforce renewal negotiation playbook
The seat metering test, the crossover math, and the renewal levers before the quote arrives.
Get the playbook →What 40 to 55 Salesforce engagements showed
Across the engagements benchmarked between 2024 and 2025, Experience Cloud was the line item buyers understood least.
The three patterns that recurred
- Member licenses sat idle on 30 to 45 percent of named seats, billed in full every year.
- Login pools were sized to average traffic, then overran at retail across 2 to 4 peak months.
- External Apps was quoted late, after the member commitment was locked, in 3 of 5 large estates.
Notice that the first two are the same mistake pointed in opposite directions. Both come from sizing to an assumption rather than to measured logins.
The hidden cost most estates miss
Each edition includes an API call allocation, and the allocation is per org rather than per community. High traffic portals burn through it and the overage bills at retail.
Inventory API usage before renewal and negotiate a top up at a non retail rate.
Research briefingRunning the Salesforce renewalWhere seat metrics, edition scope and the renewal calendar meet, and which of them a buyer still controls.
Where the common advice on Experience Cloud is wrong
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 estates rebuilt, a large block of named members logged in less than twice a month, so the member commitment paid for access nobody used.
Meter actual logins for one quarter, convert the idle members to a right sized login pool, and hold External Apps in reserve as the scale fallback.
Members feel safe. Logins feel risky. The actual answer is almost always a hybrid, with quarterly conversion as the operating gate.
Member licenses billed in full for access nobody used.
Where a large block logged in less than twice a month.
Achieved across the engagements in the file.
Related work sits in the renewal war room checklist, the renewal timeline, and the utilization calculator, with the full sequence in the renewal negotiation playbook.
Your first five moves
- Meter actual logins for one full quarter, because that single measurement settles the member against login question.
- Convert idle members to a right sized login pool, sized to the peak rather than to the average.
- Hold External Apps in reserve as the scale fallback, and get it quoted before the member commitment locks rather than after.
- Inventory API call usage before renewal and negotiate a top up at a non retail rate.
- Set quarterly conversion as an operating gate, so the mix keeps tracking the audience instead of drifting back.
Frequently asked questions
How many member seats sit idle?
Between 30 and 45 percent of named seats across the engagements benchmarked, billed in full every year regardless of use.
What is the difference between member and login?
A member license is an annual named seat counted whether they log in or not. A login license is a monthly pool where each login consumes one credit.
Where is the crossover?
Roughly two and a half logins per user per month. Above it the member SKU makes sense, below it the login pool is cheaper.
What goes wrong with login pools?
Sizing to average traffic. Pools sized that way overran at retail across 2 to 4 peak months, and overage is often double the in pool rate.
When does External Apps win?
At scale. Once the audience crosses tens of thousands of monthly active users, the per user math collapses and it becomes the cheapest path.
What is the trade off with External Apps?
Governance overhead. It needs more deliberate identity and data architecture than the per seat SKUs require.
Why does quoting order matter?
Because External Apps was quoted late in 3 of 5 large estates, after the member commitment was already locked and the comparison no longer mattered.
Is the member license the safe default?
No. In roughly 3 of 5 estates rebuilt, a large block of named members logged in less than twice a month.
What settles the argument fastest?
Login metering for a single quarter. It resolves the question faster than any list price comparison.
What hidden cost catches high traffic portals?
The API call allocation, which is per org rather than per community. Overage bills at retail unless a top up is negotiated.
