Salesforce Platform vs Full CRM Licenses
Platform licenses cost a fraction of full CRM seats but withhold the standard CRM objects. This page shows which users qualify and how to right-size without crossing the compliance line.
Salesforce Platform licenses list at roughly $25 to $100 per user per month against $165 for a full Enterprise CRM seat, and 15 to 40 percent of users in a typical org never touch a standard CRM object, which means they are mispriced if they sit on full seats. The Platform license gives custom apps and custom objects but withholds Leads, Opportunities, Cases, and the rest of the CRM core. Matching each user to the cheapest license that covers their actual usage is one of the largest savings in a Salesforce estate.
What a Platform license is and is not
A Salesforce Platform license gives a user access to custom objects, custom apps, and the core platform, but withholds the standard CRM objects: Leads, Opportunities, Cases, Campaigns, Forecasts, and Contracts. That single restriction is the whole pricing argument. If a user needs to work an opportunity pipeline or manage support cases, they need a full CRM license. If they only use custom-built apps on the Salesforce platform, a Platform license does the same job for a fraction of the cost. The two main tiers, often sold as Platform Starter and Platform Plus, list around $25 and $100 per user per month against $165 for a full Enterprise CRM seat.
The reason this matters is that large numbers of internal users never touch the CRM objects. Operations staff using a custom approval app, field technicians using a custom inspection app, or finance users running a custom reconciliation tool can all sit on Platform licenses. Putting them on full CRM seats is one of the most common and largest forms of Salesforce overspend. Our complete Salesforce licensing guide maps where each license type fits, and the editions comparison covers the full-CRM tiers.
| License | Indicative list price | Standard CRM objects | Custom apps and objects |
|---|---|---|---|
| Platform Starter | $25 per user per month | No | Limited custom objects |
| Platform Plus | $100 per user per month | No | Expanded custom objects |
| Enterprise (full CRM) | $165 per user per month | Yes | Yes |
| Unlimited (full CRM) | $330 per user per month | Yes | Yes, with higher limits |
When a Platform license is the right call
The test is simple: list every app a user actually opens and check whether any of them touch a standard CRM object. If the answer is no, the user is a Platform candidate. The clearest cases are internal-operations users on custom apps, employee-facing tools built on the platform, and read-only users who consume custom-object data without working CRM records. Moving a few hundred such users from full CRM seats to Platform licenses can cut the per-user cost by 60 to 85 percent for that population, which on a large org is a seven-figure annual swing.
The discipline is in the audit. Salesforce admins can pull login and feature-usage data that shows which users have never opened an Opportunity or a Case, and those users are mispriced if they sit on full CRM seats. This usage-based right-sizing is the heart of our SaaS license optimization service, and it pairs with the shelfware analysis in our renewal strategy guide.
The full-CRM-by-default trap: The most expensive licensing habit is buying full CRM seats for every user because it is administratively simpler. Audit feature usage and you typically find 15 to 40 percent of seats never touch a standard CRM object. Those users belong on Platform licenses, and the gap between $25 and $165 per seat is the prize.
The custom object and feature limits
Platform licenses come with caps that full CRM seats do not. Platform Starter limits the number of custom objects and tabs a user can access, while Platform Plus raises those ceilings. There are also limits on certain platform features, automation volumes, and the number of custom apps. None of these are obstacles for a genuine platform-only user, but they are the reason you cannot simply downgrade every seat. The right approach matches each user population to the cheapest license that covers what they actually do, rather than forcing everyone to one tier.
Getting the mapping wrong in the other direction creates compliance exposure. A Platform-licensed user who is given access to a standard CRM object through a misconfigured profile or permission set is using functionality the license does not cover, and Salesforce can surface that in a license review. The mapping has to be enforced in profiles and permission sets, not just intended on paper, which is a point we stress in the contract red flags guide.
| User population | Likely correct license | Why |
|---|---|---|
| Sales reps working pipeline | Full CRM (Enterprise) | Uses Leads and Opportunities |
| Support agents on Cases | Service Cloud CRM | Uses Cases and entitlements |
| Ops users on a custom app | Platform Plus | Custom objects only, no CRM |
| Read-only data consumers | Platform Starter | Views custom data, no CRM |
The compliance line you cannot cross
The boundary between Platform and full CRM is also a compliance boundary. Salesforce can review how Platform-licensed users access standard objects, and granting that access through a permission set is a license violation even if no money changed hands. The most common way this happens is a well-meaning admin who clones a profile to save time and inadvertently copies access to Opportunities or Cases into a Platform user's permissions. The savings from Platform licensing are real, but they only hold if access control matches the license.
This is why Platform right-sizing is an exercise in governance as much as procurement. The license assignment and the permission model have to be reviewed together, and any change to profiles has to be checked against the license each affected user holds. Done properly, Platform licensing is one of the safest large savings in a Salesforce estate. Done carelessly, it converts a saving into an audit finding, which is the kind of exposure our Salesforce audit defense team is built to prevent.
Enforce the license in permissions, not just intent: A Platform license is only compliant if the user's profile and permission sets actually withhold the standard CRM objects. The cheapest way to lose the saving is an admin who clones a profile and copies CRM-object access into a Platform user. Review license type and permissions together, every time.
Negotiating the license mix
The license mix is a negotiation lever, not just a configuration choice. Salesforce account teams prefer to sell full CRM seats because they carry the higher price, so a buyer proposing a large Platform population will meet resistance framed as complexity or future-proofing. The counter is the usage data: when you can show that a defined set of users has never touched a CRM object, the case for Platform licensing those seats is hard to argue against. The savings then become a negotiation chip for the rest of the deal.
The mix also affects the renewal. An org that has right-sized its license types carries less shelfware into the renewal and negotiates from a cleaner baseline, which connects directly to the runway discipline in our renewal strategy guide and the firm-level work in our software licensing advisory practice.
Running the downgrade migration
Moving users from full CRM seats to Platform licenses is a project, not a switch, and the sequence matters. The first step is the usage audit that identifies the candidates, the second is confirming with the business that those users genuinely never need CRM objects, and the third is reconfiguring profiles and permission sets so the Platform license is compliant before the seat type changes. Skipping the middle step risks downgrading a user who occasionally works a Case; skipping the third risks a compliance gap. Done in order, the migration is low-risk and high-return.
The migration also has a timing dimension tied to the contract. Salesforce seat reductions usually require a renewal event and a negotiated true-down right, so the Platform migration has to be planned to land at the renewal rather than mid-term. Sequencing the audit and the reconfiguration during the renewal runway means the new, cheaper license mix is ready to become the renewal baseline, a discipline detailed in our renewal strategy guide.
Governing the license mix over time
A right-sized license mix drifts back toward over-licensing without governance. New hires get provisioned with full CRM seats by default because it is the simplest path, role changes move users between populations without a license review, and the careful mapping erodes quarter by quarter. A standing rule that every new user is provisioned to the lowest license their role requires, enforced in the joiner process, keeps the mix clean. A quarterly review catches the drift the joiner process misses.
The governance pays for itself because the price gap between Platform and full CRM is so large. Every user wrongly provisioned to a full seat is roughly $1,000 to $1,700 a year of avoidable cost, so even modest drift across a large org is material. Treating license-type assignment as a governed process rather than a one-time cleanup is the difference between a saving that holds and one that evaporates, which is why our Salesforce optimization practice builds the governance alongside the initial right-sizing.
Common Platform license questions
Can a Platform license use Opportunities or Cases?
No. Standard CRM objects including Leads, Opportunities, Cases, Forecasts, Campaigns, and Contracts are reserved for full CRM licenses. Granting Platform users access to them is a license violation.
How much cheaper is Platform than full CRM?
Indicative list pricing runs about $25 to $100 per user per month for Platform tiers against $165 for Enterprise CRM, so the saving per moved user is roughly 60 to 85 percent before discounts.
How do I find users who should be on Platform?
Pull feature-usage and login data to identify users who never open a standard CRM object. Those users are mispriced on full CRM seats and are the strongest Platform candidates.
Modeling the savings for finance
The Platform versus full CRM decision only happens if finance can see the number, and the model is simple to build. Take the count of users confirmed to never touch a CRM object, multiply by the gap between their current full-seat cost and the appropriate Platform tier, and annualize. On an org with a few thousand seats, even a 20 percent Platform-eligible population produces a six or seven figure annual saving, and presenting it that way moves the project from an IT housekeeping task to a board-visible cost initiative. The model should be conservative, counting only users with clear evidence of no CRM use, so the saving survives scrutiny.
The model also has to account for the one-time effort: the audit, the profile and permission reconfiguration, and the change management. That cost is small against the recurring saving, but including it makes the business case honest and defensible. A right-sizing case that shows both the recurring saving and the one-time cost is the kind of analysis our SaaS license optimization service builds, and it pairs naturally with the renewal timing in our renewal strategy guide.
Where this fits
The Platform versus full CRM decision is one of the largest and safest savings in a Salesforce estate, provided access control matches the license. Start with the complete Salesforce licensing guide, compare the full-CRM tiers in the editions comparison, and read the overage and limit charges guide for the allocation differences. For a usage-based license review, see our Salesforce advisory practice.