Salesforce Platform Licensing Guide: Every Licence Type, Cost, and Optimisation Strategy

What Is a Salesforce Platform Licence?

A Salesforce Platform licence grants a named user access to the Salesforce platform layer — automation, reporting, custom applications, and a defined set of standard CRM objects — without including the full product stack of Sales Cloud or Service Cloud. Platform licences sit below full CRM licences in Salesforce's product hierarchy and are priced accordingly, making them the correct licence type for users who interact with Salesforce for operational, administrative, or custom application purposes rather than for core sales or service activities.

Platform licensing was introduced by Salesforce to address a straightforward business reality: not every person who accesses a Salesforce org is a salesperson or a support agent. Finance teams need to pull reports. HR teams need to trigger approval workflows. Logistics teams need to update custom objects. Operations managers need dashboards. None of these users require the CRM-specific functionality of Sales Cloud or Service Cloud. Assigning them full CRM seats is both more expensive and contractually unnecessary.

The gap between Platform Starter pricing ($25 per user per month) and Sales Cloud Enterprise pricing ($175 per user per month) is $150 per user per month. For an enterprise with 300 non-CRM users incorrectly on Enterprise tier, this represents $540,000 per year in unnecessary licence spend — before the 8 to 10 percent annual uplift clause in Salesforce order forms compounds the overpayment year over year.

The Four Salesforce Platform Licence Types

Salesforce offers four distinct Platform licence models, each suited to different user profiles and deployment patterns. Understanding all four is prerequisite to building an optimised licence architecture.

1. Platform Starter (Formerly Lightning Platform Starter)

Platform Starter is the entry-level Platform licence, priced at approximately $25 per user per month at list price. It provides access to the following Salesforce capabilities: the Accounts and Contacts standard objects, up to 10 custom objects, Reports and Dashboards, Salesforce Flow automation, the Salesforce mobile app, and any custom-built applications deployed within the org.

Platform Starter is appropriate for users whose entire Salesforce interaction is limited to a small number of custom objects or Salesforce-native apps that do not touch CRM-exclusive objects. Examples include an internal IT helpdesk app built on Salesforce, an asset management system using custom objects, or a simple operational approval workflow.

The 10-custom-object limit is the primary constraint. For organisations with simple internal applications using only a handful of data objects, Platform Starter is both sufficient and cost-effective. Where applications grow beyond ten objects, a move to Platform Plus is required — or users must be segmented across licence types based on their actual application access.

2. Platform Plus (Formerly Lightning Platform Plus)

Platform Plus extends the custom object allowance to 110 objects and is priced at approximately $100 per user per month. This licence type is designed for organisations that have built substantial internal applications on Salesforce — applications with complex data models, multiple custom objects, and layered automation — that still have no need for Sales Cloud or Service Cloud CRM functionality.

Platform Plus retains all the capabilities of Platform Starter while expanding capacity for complex custom development. It includes full Apex access, enabling developer and administrator work without requiring full CRM licences for technical staff. At $100 per user per month, Platform Plus delivers the same custom development environment as an Enterprise CRM seat at roughly 57 percent of the cost.

A common use case for Platform Plus is an organisation that has built a multi-object operational management system on Salesforce — a logistics platform, an HR case management tool, a project tracking application — with sufficient object complexity that Platform Starter is insufficient but where none of the users interact with standard CRM objects like Leads, Opportunities, or Cases.

3. Platform Login

The Platform Login licence replaces the per-user-per-month pricing model with a per-login-session pricing model. Rather than paying a fixed monthly fee for each named user, organisations purchase blocks of login sessions and users draw from the pool when they access Salesforce. Pricing is negotiated as part of the enterprise agreement and varies by volume, but the economics work out favourable for users who access Salesforce infrequently — typically fewer than eight to twelve times per month.

Platform Login is particularly valuable for three user categories. First, field workers or inspectors who access Salesforce periodically to log activity or retrieve information. Second, external contractors who have defined periods of Salesforce access that do not justify a permanent named licence. Third, occasional approvers — executives or department heads who interact with Salesforce only to action approval requests.

The compliance consideration with Platform Login is that session counts must be actively monitored. If the pool is exhausted, users cannot access Salesforce. Sizing the login pool requires historical access pattern analysis rather than simple headcount allocation.

4. OEM Embedded and OEM Reseller Licences

OEM (Original Equipment Manufacturer) Platform licences are a specialised category used by Independent Software Vendors (ISVs) and organisations that embed Salesforce functionality within their own products or external portals. OEM licences are distinct from standard Platform licences in that they can be deployed outside the parent Salesforce org context and licensed to end users who may not be direct Salesforce customers.

For most enterprise buyers, OEM licences are relevant in two scenarios: building a customer-facing portal using Salesforce Experience Cloud, or packaging internal operational tools built on Salesforce for delivery to business partners or subsidiaries. OEM licence pricing is entirely negotiated and does not follow the standard Platform licence list price. It is outside the scope of most internal licence optimisation exercises but is material for organisations using Salesforce as a development platform for external product delivery.

What Platform Licences Cannot Access

The licence boundary between Platform and full CRM is strictly enforced by Salesforce's permission framework and audit mechanisms. Understanding what is excluded is as important as understanding what is included.

Excluded Standard CRM Objects

Platform licences — all variants — exclude access to the following standard Salesforce objects: Leads, Opportunities, Forecasts, Quotes, Price Books, Products, Orders, Cases, Entitlements, Service Contracts, Work Orders, Knowledge Articles, and Campaigns. Any user who regularly interacts with any of these objects requires a Sales Cloud or Service Cloud licence, not a Platform licence.

The enforcement mechanism is at the profile and permission set layer. Salesforce's licence management tools detect when a Platform-licensed user has access permissions for excluded objects. During licence reviews — whether triggered by renewal negotiations or formal Salesforce audit processes — licence compliance is assessed against object access permissions, not just actual usage. A Platform user with an Opportunity read permission in their profile is flagged as a potential violation even if they have never actually opened an Opportunity record.

Excluded AI and Advanced Analytics Features

Einstein AI features — predictive lead scoring, opportunity insights, activity capture intelligence, and forecast AI — are tied to Sales Cloud or Service Cloud Enterprise and Unlimited tier licences. Platform licences do not include Einstein by default.

The Agentforce tier of AI capability — Salesforce's agentic AI product that operates on a per-conversation pricing model — is available as an add-on across multiple licence types, including Platform. Agentforce is priced at approximately $2 per conversation under the conversation-based model, or via Flex Credits at $500 per 100,000 credits (with individual actions costing 20 credits for standard actions or 30 credits for voice actions). For Platform-licensed users who need AI-assisted workflow automation, Agentforce credits can be purchased separately and applied without requiring a full CRM licence upgrade.

Excluded Einstein Analytics (Tableau CRM) Features

Advanced analytics capabilities — Tableau CRM, Einstein Discovery, and predictive analytics — require separate licences regardless of whether the base licence is Platform or full CRM. Platform licences include standard Reports and Dashboards; they do not include Tableau CRM or AI-driven predictive analytics.

The Custom Object Replication Trap

One of the most significant compliance risks in Platform licence deployments is the temptation to use custom objects to replicate the functionality of excluded CRM objects. Creating a custom "Opportunity" object, a custom "Case" object, or a custom "Lead" object to allow Platform-licensed users to manage deals, support tickets, or prospect records is a direct violation of Salesforce's licence agreement.

Salesforce's Master Subscription Agreement prohibits the creation of custom objects that duplicate standard functionality specifically to circumvent the licence boundary. This provision is enforced through Salesforce's Technical Account Manager relationships, licence compliance review processes, and in larger deployments, through formal licence audit procedures.

The financial consequence of a replication finding during a licence review is retroactive charging for the CRM licence equivalent across all users who accessed the replicating custom object from the earliest identifiable usage date. For large Platform-licensed deployments where a replicating custom object has been in use for two to three years, the retroactive exposure can be substantial.

The correct approach when building Platform-licensed applications is to scope the use case specifically and document it. An operations management workflow that happens to involve accounts and contacts as related data is a legitimate Platform use case. A pipeline management workflow that involves tracking deal stage, revenue, and close date probability is a Sales Cloud use case regardless of whether it is implemented via standard Opportunities or a custom object named something different.

Platform Licence Cost Analysis: Real Numbers for 2026

The following cost comparison is based on 2026 Salesforce list pricing. Enterprise customers negotiate discounts of 20 to 40 percent off list price, but the relative cost relationships between licence types remain consistent regardless of the discount level applied.

List Price Comparison per User per Month

• Platform Starter: $25 (approximately $300 per user per year)
• Platform Plus: $100 (approximately $1,200 per user per year)
• Sales Cloud Pro Suite: $100 (approximately $1,200 per user per year)
• Sales Cloud Enterprise: $175 (approximately $2,100 per user per year)
• Sales Cloud Unlimited: $350 (approximately $4,200 per user per year)
• Agentforce 1 (Sales): $550 (approximately $6,600 per user per year)

Savings Scenarios at Enterprise Scale

For a 1,000-user Salesforce deployment at Enterprise tier where 250 users are non-CRM operational staff incorrectly assigned Enterprise licences:

• Current annual cost for 250 users at Enterprise ($175/month): $525,000 per year
• Revised cost for 250 users at Platform Starter ($25/month): $75,000 per year
• Annual saving: $450,000 per year at list price
• At 30% negotiated discount: Annual saving of approximately $315,000 per year

This $315,000 annual saving is before considering the compounding effect of Salesforce's standard 8 to 10 percent annual uplift clause. At 9 percent annual uplift applied to the overpayment base, years two through five of a five-year contract add cumulative additional overpayment of approximately $1.4 million on top of the base misclassification cost.

The Annual Uplift Clause and Its Impact on Platform Decisions

Every enterprise Salesforce order form contains an annual price escalation provision. Salesforce's standard drafting positions this at 7 to 10 percent per year, and Salesforce account executives typically present it as a non-negotiable commercial term. It is not. Annual uplift is a contractual provision that experienced enterprise software buyers negotiate down to 3 to 5 percent, or cap as a fixed dollar amount rather than a percentage of the total contract value.

The relevance of the uplift clause to Platform licence decisions is straightforward: every dollar of overspend on misclassified licences is subject to annual uplift. If you are overspending by $315,000 per year on wrong licence types, a 9 percent uplift adds $28,350 to your overpayment in year two. Over a typical three-year enterprise agreement, the cumulative cost of the uplift applied to the misclassification base exceeds $90,000 above the base overpayment.

Salesforce's fiscal year ends January 31. The strongest negotiating window for enterprise customers is October through January, when Salesforce account teams are under maximum pressure to meet their fiscal year targets. Organisations approaching renewal in this window, and who have done the work to understand their correct licence mix, are in the strongest position to negotiate both a reduced licence count and a capped or reduced uplift rate.

Building a Platform Licence Deployment Strategy

A structured Platform licence deployment strategy involves five components: user segmentation, profile architecture, governance, application design, and renewal alignment.

Component 1: User Segmentation

Begin by segmenting every Salesforce user into one of three categories. CRM users are those who interact regularly with standard Sales Cloud or Service Cloud objects — they require full CRM licences. Platform users are those whose Salesforce interactions are limited to custom objects, Accounts, Contacts, and custom applications — they are candidates for Platform licences. Infrequent users are those who access Salesforce fewer than ten times per month for limited purposes — they are candidates for Platform Login or deprovisioning.

The segmentation should be based on actual usage data rather than self-reported job function. Pull six months of object interaction logs and identify the objects each user has actually accessed, not just the objects their profile theoretically allows them to access.

Component 2: Profile Architecture

Platform-licensed users must have profiles that do not grant access to CRM-exclusive objects. Even if a user has never accessed an Opportunity record, a profile that includes Opportunity read access creates a compliance exposure. Build dedicated Platform profiles that include only the access permissions appropriate to Platform licences, and audit existing profiles to remove CRM object permissions from users who will be migrated to Platform licences.

Component 3: Application Scoping

Every custom application that will be deployed to Platform-licensed users should be scoped and documented against the list of CRM-excluded objects. Applications that touch standard CRM objects — even as related lists or lookup fields — may trigger a compliance concern. Applications that use only Accounts, Contacts, and custom objects are cleanly within Platform licence scope.

Component 4: Data Cloud and AI Considerations

If Platform-licensed users require access to Salesforce Data Cloud functionality, a separate Data Cloud licence must be procured. Data Cloud uses a consumption-based credit model rather than per-user pricing, and credits are purchased in blocks of 100,000. Credit consumption occurs across data ingestion, profile unification, segmentation, and activation workflows. Overage charges apply when the purchased credit volume is exhausted, and these overages are a frequent source of unexpected cost in Data Cloud deployments. Planning the credit volume against expected usage — with a 30 to 40 percent buffer for growth — is essential before committing to a Data Cloud credit bundle.

Component 5: Renewal Alignment

Platform licence changes mid-contract require a formal order form amendment. Presenting a revised licence mix during the renewal negotiation cycle is operationally simpler and creates the opportunity to negotiate improved rates on the full CRM seats that remain, alongside the downgrade of misclassified users to Platform licences. Prepare the usage analysis, the revised licence allocation, and the financial business case at least six months before contract renewal to allow time for internal approval processes and Salesforce negotiation timelines.

Integration with the Broader Salesforce Cost Architecture

Platform licence optimisation does not exist in isolation. It is one component of a broader Salesforce cost management strategy that also encompasses MuleSoft integration licensing, Data Cloud credit management, and the emerging Agentforce AI cost structure.

MuleSoft is licensed on a vCore-based model where compute capacity is the billing unit. At approximately $1,250 per vCore per month, MuleSoft licensing is a significant independent cost driver in Salesforce-heavy enterprises. Right-sizing the vCore allocation — avoiding over-provisioning for development and non-production environments — can reduce MuleSoft costs by up to 30 percent without reducing production capability.

Agentforce, Salesforce's agentic AI product, introduces a per-conversation pricing model at $2 per conversation or via Flex Credits at granular per-action rates. For Platform-licensed users who are candidates for AI-assisted workflows, Agentforce credits can be provisioned independently without requiring a full CRM licence upgrade. However, the per-conversation economics must be modelled before deployment: at $2 per conversation, a deployment with 10,000 monthly conversations costs $20,000 per month, or $240,000 per year, for AI-assisted interactions alone.

Six Platform Licensing Mistakes to Avoid

Mistake 1: Assigning Platform Licences Without Auditing Profile Access. Migrating users to Platform licences without removing CRM object permissions from their profiles creates a compliance exposure that negates the cost benefit of the migration. Profile architecture must accompany the licence type change.

Mistake 2: Building Replicating Custom Objects. Using custom objects to circumvent the CRM object exclusion is a licence violation. Salesforce's compliance team identifies replication by functional intent, not object naming. Any custom object that serves the same operational purpose as a standard CRM object will be treated as unlicensed access to that object.

Mistake 3: Undersizing the Platform Login Pool. Platform Login pools sized on average monthly access patterns rather than peak access patterns will be exhausted during high-demand periods. Build a 25 to 30 percent headroom buffer above the historical peak usage level.

Mistake 4: Ignoring the Uplift Compounding Effect. Platform licence savings erode each year if the annual uplift clause is not also negotiated. Securing a Platform licence downgrade without capping the uplift rate means the saving narrows year over year as the remaining full CRM seats escalate in price.

Mistake 5: Failing to Document the Use Case. Salesforce's licence compliance review process benefits from documented business context. A clearly articulated use case — operational workflow management, internal IT tools, HR approval processes — is a stronger defence in a compliance discussion than a pattern of object access that is ambiguous without context.

Mistake 6: Treating Platform Optimisation as a One-Time Exercise. User roles evolve. New Salesforce applications get deployed. People move between teams. A licence assignment audit conducted at renewal and then ignored for three years will drift out of alignment with actual usage. Quarterly or semi-annual licence usage reviews maintain alignment between the licence type mix and actual user behaviour.

Priority Actions for Enterprise Buyers

Action 1: Commission a Licence Usage Analysis. Pull six months of Salesforce object interaction data for every active user. Map each user's actual object usage against their assigned licence type. Identify the population of users who are on full CRM licences but have not accessed CRM-exclusive objects.

Action 2: Quantify the Financial Impact. Calculate the annual saving from converting misclassified users to the appropriate Platform licence type. Include the uplift compounding effect over the remaining contract term in the financial case. Present this as a business case, not an IT request.

Action 3: Audit Profiles Before Migration. Identify all profiles assigned to Platform licence candidates. Remove CRM object permissions from those profiles before requesting the licence type change from Salesforce. Do not proceed with the migration until profiles are clean.

Action 4: Negotiate the Full Package at Renewal. Present the revised licence mix, a request to cap annual uplift at 3 to 5 percent, and any other commercial amendments as a single negotiation package at renewal. Bundled negotiation consistently delivers better outcomes than sequential point negotiations across individual contract terms.

Action 5: Engage Independent Advisors Early. Salesforce renewal negotiations are structurally adversarial. Salesforce's account team is compensated to maximise contract value; your procurement team is tasked with minimising cost. An independent advisor with no Salesforce commercial affiliation provides the benchmark data, contract redlines, and negotiation support needed to close the information asymmetry that Salesforce's commercial process relies on.