Table of Contents
Salesforce Platform: What It Is and What It Includes
Salesforce Platform licences (formerly "Salesforce Platform" or "App Cloud") provide access to the core Salesforce development infrastructure without the pre-built CRM application features of Sales Cloud, Service Cloud, or other cloud products. Platform users can access and interact with custom applications built on Salesforce — including custom objects, Apex code, Lightning components, flows, and integrations — but cannot access standard Salesforce CRM features like Leads, Opportunities, Campaigns, or Cases.
Platform licences are available in two primary variants: Salesforce Platform ($25/user/month) and Salesforce Platform Starter ($15/user/month, with more limited capabilities). The full Platform licence supports unlimited custom objects, the full Salesforce developer toolset, AppExchange application installations, and integration with Salesforce's core platform services including Salesforce Flow, Platform Events, and the broader Salesforce ecosystem.
What Platform Licences Include
Key inclusions: access to custom objects and records built by the organisation, Salesforce mobile app access, standard Salesforce security and access controls (profiles, permission sets, roles), Salesforce Flow access for custom workflow automation, API access for integrations, custom report types built on custom objects, and access to AppExchange applications that support Platform licences. Crucially, Platform licences also include access to 10 standard Salesforce objects — including Accounts, Contacts, and a limited set of other standard objects. This is often sufficient for portal or operational use cases that need basic relationship data.
The Licence Architecture Opportunity
The commercial opportunity in Platform licensing arises from a fundamental characteristic of large enterprise Salesforce deployments: not everyone who needs to interact with a Salesforce system needs CRM functionality. Operations teams using custom workflow management applications, HR teams accessing custom employee management tools, finance teams interacting with custom approval and tracking systems — all of these user populations may have been provisioned with full CRM product licences when Platform licences would serve their actual needs at 17% of the cost.
Platform vs CRM Product: The Cost Comparison
The cost differential between Platform and CRM product licences is dramatic at any scale:
| Licence Type | List Price /user/month | Typical Negotiated Price | Platform Saving vs Enterprise |
|---|---|---|---|
| Sales Cloud Enterprise | $150 | $90–$113 | — |
| Sales Cloud Unlimited | $300 | $165–$210 | — |
| Service Cloud Enterprise | $150 | $90–$113 | — |
| Salesforce Platform | $25 | $12–$18 | 83–87% lower than Enterprise |
| Salesforce Platform Starter | $15 | $8–$12 | 89–93% lower than Enterprise |
For 500 non-CRM users who are currently on Sales Cloud Enterprise, migrating to Platform licences saves: (500 users × $125/user/month difference × 12 months) = $750,000 per year at list prices, or $450,000–$570,000 at negotiated rates. This single optimisation covers the cost of a comprehensive Salesforce advisory engagement many times over.
The Build-vs-Buy Framework
The decision to deploy users on Platform licences versus CRM product licences — or versus a purpose-built SaaS solution entirely — requires evaluating three dimensions:
Dimension 1: What Does the User Actually Need?
The first question is purely functional: what does the user need to do in Salesforce? If the answer is "access and interact with custom objects, workflows, and dashboards that our team has built" — Platform is likely sufficient. If the answer includes "manage sales pipeline, track opportunities, create leads, run campaign management" — a CRM product licence is required.
The practical test: audit the user's Salesforce activity logs. Which objects do they access? Which standard Salesforce features do they use? If the activity log shows exclusive or near-exclusive use of custom objects and custom applications, Platform is the right licence type. Many organisations discover this audit reveals 30–40% of their CRM product licence users are primarily custom application users.
Dimension 2: What Is the Cost of Building vs Buying?
Platform licensing is only cost-effective if the custom application that replaces the CRM product functionality can be built and maintained at a cost lower than the CRM product licence savings. This depends on: the complexity of the required workflow, the size of the Salesforce development team available, the maturity of existing platform capabilities, and the ongoing maintenance cost of custom code.
For simple use cases — custom approval workflows, data entry forms, basic reporting dashboards — the build cost on Platform is low and the licence savings justify the investment easily. For complex use cases — advanced analytics, sophisticated integrations, multi-channel communications — the build cost may approach or exceed the licence savings, and a purpose-built SaaS solution may deliver better value than either Platform build or CRM product licence.
Dimension 3: What Are the Lock-In Implications?
Building on Salesforce Platform deepens your Salesforce platform dependency. Custom applications built in Apex, Lightning Web Components, and Salesforce Flow represent sunk investment that is difficult to migrate to other platforms. Before committing to a Platform build strategy, assess your long-term Salesforce platform strategy: if there is any credible scenario in which you would migrate away from Salesforce in the next 5–7 years, Platform builds increase that migration cost significantly.
When Platform Licensing Wins
Platform licensing delivers the clearest commercial advantage in several recurring use cases:
Operational workflow applications: Custom applications for operations, supply chain, facilities management, or other non-CRM departments that need to interact with data models connected to the Salesforce platform but do not need CRM features. These applications are relatively simple to build, maintain well on Platform, and serve large user populations that would otherwise require CRM product licences.
Internal portals and tools: Employee-facing applications built on Salesforce for internal workflows — expense management, IT service requests, onboarding processes. These applications require access to custom data models and integration with corporate data, but no CRM product functionality.
Extended enterprise access: Non-sales users who need read-access to Salesforce data — finance teams reviewing opportunity data, marketing teams accessing campaign attribution, executive teams viewing dashboards. Platform licences with appropriate data access controls serve this use case at a fraction of Sales Cloud cost.
Partner and channel management: For some partner use cases, Platform licences combined with Experience Cloud represent lower cost than full Sales Cloud Partner Community licences. The optimal licence structure depends on the specific functionality required — assessment is necessary.
Platform Limitations: What You Give Up
Platform licences are not appropriate for every use case. Key limitations to assess:
No standard CRM objects beyond 10: Platform users cannot access Leads, Opportunities, Forecasts, Campaigns, Cases, Products, Contracts, or other standard Salesforce CRM objects beyond the 10 included in Platform. Any user who needs to interact with these standard objects — even read-only — requires a CRM product licence.
No Process Builder automation on standard objects: Platform licence users cannot trigger or be recipients of process automation based on standard CRM objects. If your custom application includes automations that reference or trigger on Opportunities, Cases, or other standard objects, Platform users may encounter limitations.
AppExchange application compatibility: Not all AppExchange applications support Platform licences. Applications that require Sales Cloud or Service Cloud user access for their operation cannot be used with Platform licences. Audit your AppExchange application portfolio against Platform compatibility before migrating users.
Reporting on standard objects: Platform users can run reports on custom objects but have limited access to standard Salesforce report types. If users need to run reports that combine custom and standard CRM data, this may require a CRM product licence.
Negotiating Platform Licence Pricing
Platform licences are priced relatively low already ($25/user/month list), but significant further negotiation is possible:
Bundle Platform into the broader Salesforce deal: Platform licences negotiated as a standalone addition to an existing contract receive minimal discount. Platform licences negotiated as part of a combined CRM renewal — where the total ACV justifies management approval of deeper discounting — regularly achieve 30–45% discounts, bringing effective pricing to $12–$18/user/month.
Use Platform volume to support overall deal economics: Adding large volumes of Platform users to a Salesforce deal increases total ACV without proportional cost — Salesforce's margin on Platform licences is high. Use this dynamic by proposing large Platform user counts in exchange for better pricing on your CRM product licences, where margin impact is larger.
Multi-year commitment for Platform pricing protection: Platform prices, like other Salesforce products, can escalate at renewal. A multi-year commitment with a contractual price cap protects against the 5–10% annual price increases that erode the economics of large Platform deployments over time.
Governance and Licence Management
Platform licence governance requires ongoing management to realise the full cost benefit:
Regular user type audits: User roles change as business processes evolve. Users who were correctly assigned Platform licences may subsequently require CRM access; users who had CRM product licences may shift to custom application-only workflows. Quarterly licence type audits maintain the optimised profile and prevent drift toward over-licensing.
Application development governance: As the organisation builds more custom applications on Platform, the risk increases of applications that inadvertently require CRM product features. Establish development governance that includes licence impact assessment before deploying new custom applications — applications that require access to standard CRM objects for Platform users force unexpected licence upgrades.
Licence capacity planning: Platform licence costs are lower but still meaningful at enterprise scale. Plan licence volumes to include reasonable buffer for new users and business growth, but do not provision speculative capacity — unused Platform licences still represent cost. Model growth projections at renewal and negotiate flexible capacity provisions where possible.
For the full Salesforce optimisation framework, see our Complete Guide to Salesforce Contract Negotiation. The Salesforce Shelfware Elimination guide covers related optimisation tactics including unused feature identification across the Salesforce portfolio. For comprehensive benchmarks and contract templates, see our Salesforce Renewal Playbook.