Platform licenses are the most underused leverage in Salesforce license optimization. Where Sales Cloud and Service Cloud licenses provide the full CRM functionality at premium prices, Platform licenses provide the underlying Salesforce platform — custom objects, custom applications, the Lightning interface, basic data model, and integration capabilities — at substantially lower per-user pricing. For organizations whose user populations include large numbers of people who don’t need the CRM-specific functionality (Accounts, Contacts, Opportunities, Cases) but who do need to participate in custom applications built on the Salesforce platform, the Platform license strategy can produce significant savings without functional compromise. This guide walks through the Platform license landscape in 2026, the use cases that fit best, and the negotiation moves that capture the savings.
The Platform license landscape in 2026
Salesforce’s Platform license offerings have evolved across many product cycles, with the naming and bundling shifting as the company has restructured its packaging. In 2026 the principal Platform license SKUs:
| License | List per user/month | Principal use case |
|---|---|---|
| Platform Starter | $25 | Lightweight custom application access; limited objects |
| Platform Plus | $100 | Broader custom app access; more objects and capability |
| Customer Community | Member-based (login or member) | External customer portal access |
| Partner Community | Member-based | External partner portal access |
| Identity-only / Identity | ~$5 | SSO and identity-only use cases |
The list prices and packaging have moved across cycles; current customers should validate the specific SKU economics at contract time. The general structure has remained consistent: Platform licenses provide access to the Salesforce platform without the CRM-specific objects, at a fraction of the CRM-license price.
What Platform licenses include
The general structure of Platform licenses:
Lightning platform access. Users with Platform licenses can use the Lightning Experience interface, navigate apps, and interact with custom objects in the same way as CRM-license users.
Custom objects and applications. Platform-licensed users can interact with custom objects (the ones the customer or AppExchange package has created) up to defined object limits. The limit depends on the specific SKU.
Standard objects (limited). Platform licenses include access to certain standard objects (typically Accounts and Contacts in read-only fashion, plus some others) but exclude the CRM-defining objects like Opportunities, Cases, and Leads. The specific exclusions matter and depend on the SKU.
Reporting and dashboards. Platform-licensed users can view reports and dashboards built on objects they have access to.
Workflow and automation participation. Platform users can participate in workflows, Flow processes, and automation that operates on the objects they can access.
Chatter and collaboration. Platform users can participate in Chatter (in some configurations) and other platform-wide collaboration features.
Mobile and API access. Platform users have access through the Salesforce mobile apps and (with some SKU variations) through APIs.
What Platform licenses don’t include
The exclusions are the principal reason Platform licenses cost less:
Sales Cloud features. Platform users cannot access the Sales Cloud-specific objects (Opportunities, Forecasts, Quotes), the Sales Cloud-specific functionality (forecasting, territory management), or Sales Cloud-specific reports.
Service Cloud features. Platform users cannot access Service Cloud-specific objects (Cases, Solutions, Knowledge, Service Console), or service-specific functionality.
Marketing Cloud and other product-specific features. Platform licenses do not include access to the broader product cloud features.
Some Einstein capabilities. Platform licenses have constrained access to Einstein features compared to full CRM licenses.
Some integration and API capabilities. Specific API access patterns may be restricted on certain Platform SKUs.
The use cases that fit best
The Platform license strategy fits best for several specific use cases:
Custom application users. Organizations that have built or purchased custom applications on the Salesforce platform for HR processes, IT request management, employee onboarding, project management, or similar use cases. These users need the custom application but don’t need Opportunities or Cases.
Cross-functional collaborators. Users from finance, legal, operations, or other functions who participate in Salesforce-resident workflows (approvals, document routing, process management) but who don’t use the CRM-specific objects.
Light-touch executives. Senior executives who view dashboards and reports periodically but don’t actively manage opportunities or cases. Platform licenses can suffice if the dashboards are on custom objects; if executives need to see live opportunity pipeline, the Platform license doesn’t work.
AppExchange application users. Users of specific AppExchange applications (built on the Salesforce platform) who don’t use the core CRM. Many AppExchange packages are designed to operate on Platform licenses.
Field workforce on custom apps. Field employees using custom mobile applications built on Salesforce for inspections, surveys, or operational data capture.
Read-only stakeholders. Internal stakeholders who need to view Salesforce data but don’t modify it. Platform licenses can fit if the read access is on objects within the Platform scope.
The Customer and Partner Community licenses
For external user populations, the Community licenses provide a separate license category with member-based or login-based pricing models:
Customer Community licenses provide external customer portal access at meaningfully lower per-user pricing than internal CRM licenses. The pricing models include per-login (priced per active login per month) and per-member (priced per provisioned user per month).
Partner Community licenses provide external partner portal access with somewhat more capability than Customer Community licenses, supporting partner relationship management use cases.
The Community license decision (login-based versus member-based) has its own economics that depend substantially on usage patterns. Customers should model both structures before committing.
The savings math
The savings from Platform license deployment can be substantial. Consider a 5,000-user deployment with the following population mix:
2,000 full Sales Cloud users (need Opportunities, full CRM functionality)
1,500 Service Cloud users (need Cases, service-specific features)
500 cross-functional collaborators (HR, finance, operations)
1,000 executives and read-only stakeholders
At list prices with the all-Sales-Cloud-EE default: 5,000 users × $165 = $825,000 per month, or $9.9 million per year.
At list prices with the right-sized mix: 2,000 SC EE + 1,500 Service Cloud EE + 1,000 Platform Plus + 500 Platform Starter = $330K + $247.5K + $100K + $12.5K = $690K per month, or $8.28 million per year.
The savings: $1.62 million per year on list, or roughly $1 million per year after enterprise discounts. The capability delivered to the broader population is comparable, but the cross-functional and read-only users are licensed appropriately rather than over-licensed.
The implementation considerations
Several implementation considerations affect whether Platform licenses work for a specific use case:
Object access mapping. The user’s required object access must fit within the Platform license’s permitted objects. If the user needs to see Opportunities, Platform Plus may not work regardless of the per-user economics.
Custom application design. Custom applications must be designed to use objects accessible to Platform-licensed users. Applications that depend on Opportunity data, for example, cannot serve Platform-licensed users directly.
AppExchange package compatibility. Not all AppExchange packages support Platform licenses. The package’s license requirements should be validated before assuming Platform-licensed users can use it.
Reporting and dashboard design. Reports and dashboards exposed to Platform-licensed users must be on objects within their permitted scope.
License governance. Mixed-license deployments require disciplined license governance to ensure users are on the right license type and to handle license changes as user roles evolve.
The Identity-only and SSO use case
For a narrow set of use cases — primarily users who need single sign-on into Salesforce-integrated systems but don’t actually use Salesforce as their work surface — Identity-only licenses at around $5 per user per month provide the SSO and identity capabilities without broader platform access. The use case is narrow but real for organizations using Salesforce Identity as the identity provider for broader applications.
Negotiation moves on Platform licenses
Several moves consistently produce better Platform license outcomes:
1. Audit current license assignments before contract. The current state often shows users on full CRM licenses who could be served by Platform. The audit data informs the right license mix and the negotiating position.
2. Negotiate Platform licenses as part of broader Salesforce deals. Account teams sometimes resist allocating effort to Platform-license negotiations because the per-user revenue is lower. Bundling the Platform negotiation with broader Salesforce conversations produces better outcomes.
3. Address the upgrade path. Platform-licensed users whose roles evolve may need to upgrade to CRM licenses. The contract should specify the upgrade economics with pricing protection.
4. Document the mixed-license structure. The contract should clearly document the population mix and the per-license pricing, with renewal-cap protection applying to each license type.
5. Negotiate Community license economics deliberately. The login-versus-member decision and the absolute pricing on Community licenses are substantial conversations in their own right. Defaults rarely produce the best outcome.
6. Validate AppExchange compatibility. Where Platform licenses depend on specific AppExchange packages, the compatibility should be validated explicitly, not assumed.
7. Plan for ongoing optimization. Platform license optimization is a recurring conversation, not a one-time initiative. License usage shifts as user roles evolve and applications change.
What to verify before signing Platform license terms
- The license mix reflects the actual user populations and their required object access.
- Object permissions on the Platform licenses match what the assigned users actually need.
- AppExchange package compatibility is confirmed for the applications used by Platform-licensed users.
- Upgrade economics from Platform to CRM are documented with pricing protection.
- Renewal cap applies to each license type, not just the full CRM licenses.
- Community license structure (login vs member, with absolute pricing) reflects actual usage patterns.
- Reduction rights at renewal apply across license types.
- Mixed-license governance processes are in place to maintain the right license assignment over time.
Across the 500-plus engagements our advisory has supported, Platform license optimization has consistently produced material savings — often in the $200K to $1M+ annual range for enterprise customers. The $420 million in cumulative savings our advisory has delivered across the Salesforce portfolio includes a meaningful Platform-license component, sourced principally from right-sized license deployments rather than from price negotiations alone.
The 34 percent average reduction against Salesforce’s opening positions on broader Salesforce deals includes the contribution from Platform license optimization. Customers who do the license-mapping work rigorously consistently outperform the benchmark; customers who accept the default all-CRM-license deployment overpay materially for capability the broader user population doesn’t actually use.
The Platform license strategy isn’t for every organization or every use case. But for organizations whose Salesforce footprint extends beyond core CRM into custom applications, cross-functional collaboration, and read-only stakeholder access, the Platform license is one of the most consequential optimization levers available. The discipline of evaluating user populations against license types — rather than defaulting all users to full CRM licenses — consistently produces savings that more than justify the analytical work required.