Salesforce Platform Licence vs
Full CRM Licence: When Platform Is Sufficient

What a Salesforce Platform Licence Actually Includes

Salesforce Platform licences — previously called Force.com licences — give users access to custom applications built on the Salesforce platform, as well as a limited set of standard Salesforce objects: Accounts, Contacts, Tasks, Events, and custom objects. What Platform licences explicitly exclude is access to Salesforce's core CRM objects: Leads, Opportunities, Campaigns, Cases, and Work Orders. This distinction is where most enterprises run into trouble. If a Platform-licensed user needs to view or update an Opportunity, you have a Salesforce licence compliance problem.

Salesforce currently offers three Platform licence tiers: Salesforce Platform (from $25/user/month), Platform Plus (from $100/user/month), and the legacy Force.com Light App licence (from $15/user/month) still in some older contracts. The jump from Platform to Sales Cloud Enterprise represents a price increase of 560% per user — from $25 to $165. For a 500-user organisation where 200 employees genuinely only need access to custom internal apps, right-sizing to Platform licences represents approximately $1.68M in savings over a three-year term. Download our Salesforce licence optimisation guide for the exact methodology we apply in client engagements.

Which Users Qualify for Platform Licences

The question of whether a user qualifies for Platform over full CRM is answered by one rule: does that user need to access CRM-specific objects (Leads, Opportunities, Campaigns, Cases, Work Orders)? If the answer is no, Platform is legally sufficient and commercially advantageous. The users who most commonly qualify include internal portal and extranet users who interact only with custom objects, HR and Finance employees who use Salesforce for custom workflow applications, operations staff who access custom service or logistics objects, and light users who receive reports and dashboards but never update records.

Salesforce resists downgrading at renewal. Account Executives will argue that "most organisations find they need the flexibility of full CRM licences" — which is a commercial argument dressed as technical advice. The contractual reality is that Salesforce's licence terms permit Platform licences for any user whose access pattern fits the criteria. Before your next renewal, run a Salesforce permission set and profile audit to identify users who have never accessed Leads, Opportunities, or Cases in the past 12 months. In our experience at Redress, working across 500+ enterprise engagements, 30–50% of full CRM users in large organisations meet the criteria for downgrade to Platform. The opportunity to book a confidential advisory call to quantify your specific savings is available at any stage of your renewal cycle.

Platform Plus: The Middle Ground Most Enterprises Overlook

Platform Plus licences at $100/user/month occupy a useful middle tier that most enterprises never consider. Platform Plus adds access to Service Cloud's standard Case object and the Communities feature set — meaning users can manage customer-facing cases without needing a full Service Cloud licence. For support triage staff, community managers, and back-office teams who handle escalations but don't run full agent workflows, Platform Plus represents a $65/user/month saving versus Service Cloud Enterprise ($165/user/month). Across a 200-person support operations team, that saving is $1.56M over three years.

The caveat with Platform Plus is that it does not include access to Salesforce's Knowledge Base, Entitlements, or Service Console beyond basic Case management. Organisations running complex service workflows — like those using Salesforce Field Service Lightning for field technician management — need full Service Cloud licences for those users. The Platform Plus sweet spot is the internal help desk or partner portal environment where Case resolution is straightforward and the advanced features of Service Cloud are never opened.

Negotiating the Downgrade: What Salesforce Will and Won't Accept

Salesforce treats downgrade requests during mid-contract periods as essentially non-negotiable — the standard Salesforce Order Form includes "no reduction" provisions that prevent reducing licence counts or tiers before contract end. At renewal, however, everything is on the table. The negotiation strategy that works is to arrive at renewal discussions with a completed licence audit showing the exact number of users who qualify for Platform, the specific profiles and permission sets evidence, and a prepared counter-proposal that reduces full CRM licences while increasing Platform licences at the correct ratio.

Salesforce will typically resist with two arguments: minimum seat requirements (usually 25–50 full CRM licences regardless of usage), and claims that certain integrations require full CRM licences for all connected users. Challenge both assertions. The minimum seat requirement is negotiable at any contract value above £200,000 ACV, and the integration argument is almost always technically incorrect — Salesforce APIs use named credentials and OAuth, not per-user CRM licence checks. Organisations managing complex CPQ or Revenue Cloud workflows alongside standard CRM are the exception, as CPQ-specific objects do require appropriate permissions that may necessitate higher-tier licences for certain roles.

Avoiding the Compliance Trap After Downgrade

The most common mistake after negotiating Platform licences is failing to implement the corresponding permission set restrictions in Salesforce. If Platform-licensed users retain permission sets that grant them access to Opportunities or Campaigns — even if they never use those features — you are in technical breach of your licence agreement. Salesforce's licence compliance checks focus on active users in the past 30 days, but a formal audit scope extends to permission sets assigned, regardless of usage. Before committing to a Platform downgrade, conduct a full permission set and profile review in your Salesforce org and remove CRM object access from Platform-licensed users. The same review process applies when considering whether add-ons like Salesforce Shield are correctly scoped across your Platform versus full CRM user population.