The Licence Type Problem Nobody Audits
In most large Salesforce deployments, a sizeable proportion of users were assigned full Sales Cloud or Service Cloud licences not because they need all of those capabilities, but because it was the default at deployment time. IT simply provisioned every user with the same licence type, the project went live, and the cost structure was locked in.
Platform licences — specifically Salesforce Platform Starter and Platform Plus — exist precisely for users who access Salesforce for reasons other than selling or servicing customers. Finance teams pulling reports, operations teams managing workflows, HR teams running approval processes, logistics teams tracking fulfilment: none of these users need access to Leads, Opportunities, or Cases. Assigning them a full CRM licence means paying $165 to $350 per user per month for a licence type they are using at roughly ten to twenty percent of its capability.
This is not a trivial inefficiency. A 500-user enterprise with 150 non-sales users incorrectly on Enterprise Sales Cloud at $175 per user per month is paying $26,250 per month — $315,000 per year — for functionality those users will never touch. Switching them to Platform Starter at $25 per user per month brings that cost to $3,750 per month, a saving of $22,500 per month or $270,000 annually. Before annual uplift compounds the gap even further.
What a Salesforce Platform Licence Actually Provides
Salesforce offers two Platform licence types: Platform Starter and Platform Plus. Both give users access to a defined set of Salesforce functionality centred on the platform layer — custom apps, workflow automation, and core data objects — rather than the full CRM product stack.
Platform Starter
Platform Starter is priced at approximately $25 per user per month and provides access to up to 10 custom objects. Users on this licence can access Accounts and Contacts (the two core CRM objects that are universally included), Reports and Dashboards, Salesforce Flow for automation, and any custom-built applications deployed in the org. They cannot access Leads, Opportunities, Forecasts, Quotes, Cases, Campaigns, or any other standard Sales Cloud or Service Cloud objects.
For users whose entire Salesforce interaction is limited to a specific internal application — an approval workflow, an asset management system, a custom operational dashboard — Platform Starter is both sufficient and dramatically cheaper than a full CRM seat.
Platform Plus
Platform Plus (formerly Lightning Platform Plus) extends the custom object allowance to 110 objects and is priced at approximately $100 per user per month. This licence type suits organisations that have built complex internal applications on Salesforce that involve significant custom data models. Users can access the same core objects as Platform Starter, plus the expanded range of custom objects, automation tools, and the Salesforce mobile app.
Platform Plus bridges the gap between a stripped-back platform access licence and a full CRM seat, and it is the appropriate choice when custom application complexity exceeds what Platform Starter accommodates.
The Platform Login Licence
A third option worth noting is the Platform Login licence, which charges per login session rather than per named user. This model suits sporadic or infrequent users — field inspectors, external contractors, part-time operational staff — whose access patterns make a monthly per-user licence economically inefficient. Platform Login pricing is negotiated as part of the enterprise agreement and typically works out at a fraction of the equivalent monthly named licence cost for users who access Salesforce fewer than eight to twelve times per month.
Are your users on the right Salesforce licence type?
We audit licence assignments across 500+ user deployments and identify misallocation in 80% of estates.What Full CRM Licences Include That Platform Does Not
Understanding the exact dividing line between Platform and full CRM access is essential for accurate licence assignment. The capabilities that require a full Sales Cloud or Service Cloud licence include the following standard objects and features.
Sales Cloud Exclusive Objects
Leads, Opportunities, Forecasts, Quotes, Price Books, Products, and Campaigns are all Sales Cloud objects. None of these are accessible on a Platform licence. Any user who manages pipeline, creates quotes, runs sales forecasts, or works with campaign attribution needs a full Sales Cloud seat — there is no workaround within Salesforce's standard licensing framework.
Service Cloud Exclusive Objects
Cases, Entitlements, Service Contracts, Work Orders, and the Knowledge Base are Service Cloud objects. Support agents, field service coordinators, and anyone managing customer issue resolution requires a Service Cloud licence. Platform licences cannot access these objects regardless of custom configuration.
Einstein AI and Advanced Analytics
Einstein AI features — predictive lead scoring, opportunity insights, conversation intelligence — are tied to Enterprise and Unlimited tier CRM licences. Platform licences do not include Einstein capabilities by default, though some AI features are available as paid add-ons. With Agentforce now available as a per-conversation add-on at approximately $2 per conversation (or via the Flex Credits model at $500 per 100,000 credits), AI capability can in theory be layered onto Platform licences for specific use cases, but this requires explicit contract provisions and is not standard.
Apex and Advanced Development
Both Platform Starter and Platform Plus include full Apex development access, so developers and technical administrators do not require a full CRM licence purely for coding and configuration work. This is frequently overlooked: a team of Salesforce developers or system administrators can operate entirely on Platform licences unless they need to interact with CRM-specific objects in their day-to-day work.
The Cost Comparison in Real Numbers
Salesforce's list pricing for 2026 places the key licence types at the following per-user-per-month rates:
- Platform Starter: $25 per user per month (approximately $300 per user per year)
- Platform Plus: $100 per user per month ($1,200 per user per year)
- Sales Cloud Professional: $80 per user per month ($960 per user per year)
- Sales Cloud Enterprise: $175 per user per month ($2,100 per user per year)
- Sales Cloud Unlimited: $350 per user per month ($4,200 per user per year)
The saving from moving a non-CRM user from Enterprise to Platform Starter is $150 per user per month at list price — $1,800 per user per year. For an enterprise with 200 misclassified users at Enterprise tier, the annual overpayment is $360,000 before negotiated discounts are factored in. At a typical enterprise discount of 30 percent off list, the overpayment is still $252,000 per year.
The Annual Uplift Trap
Salesforce order forms standardly include an annual price escalator, typically 8 to 10 percent per year. This clause is often positioned as non-negotiable by Salesforce account executives, though it is in fact a contractual term subject to negotiation, not a regulatory requirement.
The significance of the uplift clause in the context of licence type selection is that it applies to your entire base licence spend. If you are overpaying by $252,000 per year on misclassified licences, a 9 percent uplift adds another $22,680 to your overpayment in year two, $24,721 in year three, and so on. Over a five-year contract, the cumulative cost of licence misclassification combined with annual uplift can easily reach seven figures for a mid-size enterprise.
Enterprises negotiating renewals should push to cap annual uplift at 3 to 5 percent, and to tie any uplift to actual usage metrics rather than blanket percentage increases. Salesforce reps will resist, particularly as they approach their fiscal year end on January 31, but the leverage to negotiate exists in every renewal cycle for customers willing to prepare thoroughly.
When Platform Licences Create Compliance Risk
Platform licences are not a universal solution for reducing costs. Assigning the wrong licence type in the other direction — giving a Platform licence to a user who genuinely accesses Sales or Service Cloud objects — creates a licence compliance exposure that Salesforce can identify during an audit.
Salesforce's licence compliance mechanisms check user profile assignments, object access permissions, and feature usage logs. If a user on a Platform licence has been given a profile that grants access to Leads or Opportunities (even if they rarely use those features), that user is technically in violation of their licence type. Salesforce has the contractual right to charge for the difference retroactively, typically framed as a "true-up" at renewal.
The practical mitigation is a proper licence usage analysis — not a one-time snapshot, but a continuous review that maps each user's actual object interactions against their assigned licence type. Users who touch CRM objects even infrequently should be on a full CRM licence or the access removed from their profile. Users who have never accessed CRM objects can safely be downgraded to Platform.
Contractual Restrictions on Custom Object Replication
Salesforce's licensing agreement includes a critical restriction that affects Platform licence optimisation strategies: you cannot build custom objects that replicate the functionality of standard CRM objects to circumvent the licence boundary. Creating a custom "Opportunity" object to avoid paying for Sales Cloud licences for users who manage deals is a contractual violation, not a clever workaround.
This restriction is enforced through Salesforce's audit and compliance processes and can result in retroactive charges for the equivalent CRM licence type across all users who accessed the replicating custom object. The safeguard when building Platform-licensed applications is to ensure they serve genuine business processes that are distinct from Sales Cloud or Service Cloud functionality, not architecturally adjacent to it.
Building a Licence Optimisation Strategy
A structured approach to Platform versus full CRM licence assignment involves three steps: analysis, remediation, and governance.
Step 1: User Activity Analysis
Pull login history and object interaction data for all active Salesforce users. Classify users into three groups: those who interact regularly with CRM-exclusive objects (Sales or Service Cloud licences required), those who interact only with Accounts, Contacts, and custom objects (Platform licence candidates), and inactive or infrequent users who may be candidates for Platform Login or full deprovisioning.
Step 2: Profile Audit
Audit the profile and permission set assignments for all users. Even users who have never accessed CRM objects may have profiles that grant that access, creating latent compliance risk. Remove CRM object permissions from profiles assigned to Platform licence candidates before migrating their licence type.
Step 3: Renewal Negotiation
Present the revised licence mix to Salesforce during renewal negotiations. Converting misclassified users to Platform licences mid-contract may require a formal amendment; consolidating the optimisation into the renewal cycle is typically cleaner and creates an opportunity to negotiate improved rates on the remaining full CRM seats alongside the downgrade.
Stay Ahead of Salesforce Licence Changes
Salesforce updates its licence terms and pricing structures regularly. Subscribe to the Redress Salesforce knowledge hub for quarterly updates on licence types, pricing changes, and optimisation strategies.