Salesforce Platform licenses cost roughly $25–$100 per user/month versus $165–$330 for full Sales or Service Cloud — a 60–80% saving — for users who only need custom apps, not the CRM objects. The arbitrage is legitimate when those users genuinely never touch Leads, Opportunities or Cases.
Salesforce Platform licenses (Platform Starter and Platform Plus) cost roughly $25–$100 per user/month versus $165–$330 for full Sales or Service Cloud seats — a 60–80% saving — for users who only need custom apps built on the platform, not the CRM objects. The arbitrage is entirely legitimate when those users genuinely never touch the restricted standard objects (Leads, Opportunities, Cases, Forecasts and similar). Used correctly it is one of the highest-return moves in a Salesforce estate; used carelessly it is a compliance exposure. This article sits under our Salesforce pricing pillar; see also the Salesforce practice page.
The principle: pay for CRM only where CRM is used. A claims processor, a field engineer, an internal-portal user or an HR-app user often needs custom objects and workflows but never a sales pipeline. Licensing them on Platform instead of full CRM can cut their seat cost by three-quarters. The catch is that Platform licenses restrict access to Salesforce's standard CRM objects — cross that line and you are under-licensed.
We map each user group's actual object usage and model the Platform arbitrage — the saving is often the largest single line in a Salesforce review.
The difference is object access. Platform licenses grant custom objects and a limited set of standard objects (Accounts, Contacts, Reports, Documents) but exclude the revenue-generating CRM objects. The table sets out the trade.
| Capability | Platform license | Full Sales/Service Cloud |
|---|---|---|
| Custom objects & apps | Yes | Yes |
| Accounts & Contacts | Yes (typically up to a cap) | Yes |
| Leads, Opportunities, Forecasts | No | Yes |
| Cases, Entitlements (Service) | No | Yes |
| Indicative list (user/mo) | $25–$100 | $165–$330 |
It applies when a user population's work lives entirely in custom apps. Common legitimate cases: internal operations portals, asset or inventory apps, HR and onboarding apps, field-service data capture that does not use the Service Cloud Case object, and partner or employee communities running on custom objects. The test is simple and auditable — does this group ever create, read or update a restricted standard object? If not, Platform is the correct, compliant licence. Our license optimization service runs this mapping as a standard first pass.
The Platform-vs-CRM mapping worksheet and the object-usage evidence Salesforce accepts.
Salesforce sells the Platform licence in two tiers, and the gap between them is mostly about custom-object and tab limits rather than CRM access — neither grants the restricted standard objects. The table sets out the trade so you license to the workload, not to the safer-feeling higher tier.
| Dimension | Platform Starter | Platform Plus |
|---|---|---|
| Custom objects (indicative) | Lower cap | Higher cap |
| Custom tabs / apps | Limited | Expanded |
| Best for | Single internal app, light use | Multiple custom apps, heavier internal platform |
| Indicative list (user/mo) | ~$25 | ~$100 |
Consider an organisation with 1,000 Enterprise Edition seats at an effective $120 per user/month. Suppose 300 of those users only ever work in an internal operations app built on custom objects — they never open a Lead, Opportunity or Case. Re-licensing those 300 to Platform Plus at an effective $70 per user/month saves $50 per user per month, or $180,000 a year, with no loss of function for that group. If 150 of them need even less and fit Platform Starter, the saving grows again. This is why the Platform-versus-CRM map is consistently the single largest line in the Salesforce reviews our license optimization team runs — the saving is real, recurring, and fully compliant when the object-usage evidence holds.
The evidence Salesforce expects, and that protects you in a reconciliation, is an object-usage map: for each user group, which standard and custom objects they create, read, update or delete. Pull this from field history, login and usage reports, and profile/permission-set analysis rather than from assumptions about job titles. A user's role says little about their object usage; the data says everything. Keep the map current — refresh it at each renewal — and enforce the boundary with profiles and permission sets so a Platform-licensed user cannot be granted access to a restricted object by a later configuration change. That governance is what turns the arbitrage from a risk into a durable saving.
Two mistakes turn the arbitrage into exposure. First, scope creep: a Platform-licensed app later adds a feature that touches Opportunities or Cases, and every user on it is suddenly under-licensed. Govern object access so a new field or flow cannot silently pull a restricted object into a Platform app. Second, over-correction: nervous teams license everyone on full CRM "to be safe", overpaying by 60–80% on populations that never need it. The defensible middle is an audited object-usage map, refreshed at renewal, with access controls that enforce the boundary. The discipline mirrors the consumption-versus-entitlement logic in Agentforce pricing, and the same right-sizing principle applies across platforms — see ServiceNow license types for the fulfiller-versus-requester equivalent. For the full pricing reference, return to the Salesforce pricing pillar.
Platform is not the only way to license users cheaply, and the right answer depends on who the users are. For external users — customers, partners, members — Experience Cloud (formerly Community) licenses, priced per login or per member, are usually the correct and cheaper route; putting external users on internal Platform seats is both costlier and a common compliance error. For internal users who only need custom apps, Platform is the answer. For users who need just one or two CRM objects occasionally, the maths is closer and worth modelling explicitly, because a small number of restricted-object touches can force a full CRM seat. The general rule: match the licence type to the user's actual access pattern and population (internal vs external), not to a blanket policy. Mixing these up is one of the most expensive licensing mistakes we unwind.
Turning the arbitrage into realised savings is a project, not a one-off swap. The sequence we run: (1) export object-level usage for every active user over the last ninety days; (2) cluster users into populations by access pattern; (3) for each population, determine the minimum compliant licence — Platform Starter, Platform Plus, full CRM or Experience Cloud; (4) validate with the business that the access pattern is stable, not seasonal; (5) stage the re-licensing at renewal, when quantities can be adjusted; (6) lock the boundary with profiles and permission sets so reclassified users cannot drift back across the line. Done once and governed thereafter, a reclassification typically pays for itself many times over in the first renewal cycle, and the object-usage map it produces becomes the evidence base for every subsequent Salesforce true-up. Our license optimization team runs this end to end.
We map object usage and model the Platform-vs-CRM split. We work for buyers, not Salesforce.
Weekly compliance intelligence for IT leaders.
