If you’re a CFO or Salesforce admin, you’ve probably asked yourself this:
“How many of our Salesforce licenses are actually being used?”
Did you know 40% of Salesforce customers overspend because they choose the wrong or unused licenses? At first, Salesforce licenses may seem straightforward. However, many types and pricing models make it complicated.
Many companies waste money on Salesforce CRM because some users are inactive.
It's not essential to consider just how valuable Salesforce is. Instead, we should focus on whether each license is worth it.
That's where Salesforce license management comes in. Without a solid system, you may be paying for seats you don't use.
Choosing the right Salesforce license is not simply about picking the cheapest option. Each license controls what a user can access, which Salesforce features they can use, and how much your organization ultimately pays.
Quick Answer: Salesforce license types generally fall into four major categories: full CRM licenses for sales and service teams, Platform licenses for custom apps and limited CRM access, Experience Cloud licenses for customers and partners, and specialized licenses for products such as Marketing Cloud, Identity, and integrations.
The right choice depends on who needs access, what they need to do in Salesforce, and which objects and features they actually require.
For example, a sales representative managing leads, opportunities, and forecasts may require a full Salesforce license. An internal employee who only works with custom applications may be better suited to a Salesforce Platform license, while customers and channel partners typically need an Experience Cloud license.
Choosing incorrectly can mean paying for functionality employees never use—or assigning a cheaper license that prevents users from completing essential tasks.
In this guide, we compare the major Salesforce license types, pricing models, features, limitations, and use cases to help you determine which licenses make sense for your organization.
| Business Need | Typical Salesforce License | Best For |
|---|---|---|
| Full sales CRM access | Salesforce / Sales Cloud | Sales reps managing leads, accounts, opportunities, and forecasts |
| Customer service operations | Service Cloud | Support agents managing cases and customer interactions |
| Custom apps and limited CRM access | Salesforce Platform | Internal users who don't require full Sales or Service Cloud functionality |
| Customer self-service | Experience Cloud | Customers accessing portals, knowledge, and support |
| Partner collaboration | Experience Cloud partner licenses | Resellers, distributors, and channel partners |
| Marketing automation | Marketing Cloud | Marketing teams managing campaigns, journeys, and customer engagement |
| System-to-system connectivity | Integration User | Applications and integrations that primarily require API access |
| Authentication and identity | Identity | Users who need identity and access capabilities rather than full CRM functionality |
Important: Salesforce licensing and pricing can vary by product, edition, contract, user volume, billing model, and negotiated agreement. Always confirm current entitlements and pricing with Salesforce before making a purchasing decision.
A Salesforce license defines the baseline functionality a user can access within a Salesforce organization. It determines which products, standard objects, platform capabilities, and features are available to that user.
Every Salesforce user must be assigned an appropriate license. However, not every employee needs the same level of access.
For example:
A sales representative who works with leads, opportunities, accounts, and forecasts may need a full Sales Cloud license.
A support agent handling customer cases may require Service Cloud capabilities.
An employee who primarily uses custom Salesforce applications may be able to work with a Salesforce Platform license.
Customers and partners accessing a portal typically use an appropriate Experience Cloud license rather than a full internal Salesforce license.
This distinction matters because assigning full CRM licenses to users who need only limited functionality can unnecessarily increase Salesforce costs.
These terms are related, but they are not interchangeable.
| Term | What It Determines | Example |
|---|---|---|
| Salesforce Edition | The overall features and limits available to the Salesforce org | Starter, Professional, Enterprise, Unlimited |
| User License | The baseline functionality available to an individual user | Salesforce, Salesforce Platform, Identity |
| Permission Set | Additional permissions granted within the boundaries of the user's license | Access to specific objects, fields, apps, or system permissions |
| Permission Set License | Access to additional licensed functionality that can then be enabled through permissions | Product-specific capabilities purchased for selected users |
The simplest way to understand it: your Salesforce edition defines what your organization has purchased, the user license establishes what a particular user can potentially access, and profiles and permission sets determine what that user is actually allowed to do within those licensing boundaries.
A permission set cannot generally be used to give a user functionality that their underlying license does not support.
Choosing the right Salesforce license type affects more than subscription cost. It can influence:
which CRM objects users can access;
the Salesforce products and applications available to them;
reporting and automation capabilities;
API and integration access;
customer or partner portal functionality; and
your overall Salesforce licensing spend.
For this reason, start license selection with user roles and required functionality, rather than assigning the same license to everyone.
Salesforce licensing can feel complicated because no single license fits every user. The right license depends mainly on who will use Salesforce, which products they need, and what they need to do in the platform.
For most organizations, Salesforce licenses can be understood across four practical categories:
Full CRM licenses are designed for employees who need broad access to Salesforce's core sales or customer service functionality.
These licenses are commonly used by:
Sales representatives
Sales managers
Customer service agents
CRM administrators and power users
For example, a sales rep who needs to manage leads, accounts, contacts, opportunities, and forecasts will generally require access to the relevant full CRM functionality rather than a limited platform license.
Salesforce Platform licenses are intended for internal users who need Salesforce-based applications but do not require the full set of standard Sales Cloud or Service Cloud capabilities.
They can be suitable for teams using Salesforce for processes such as custom application workflows, operations, approvals, or other internal business processes built on the Salesforce Platform.
The key question is not simply whether a Platform license costs less, but whether its available objects and capabilities match the user's actual responsibilities.
External licenses are designed for people outside your organization who need controlled access to Salesforce-powered experiences.
Depending on the use case, Experience Cloud licenses can support:
Customers using self-service portals
Partners collaborating on sales opportunities
Distributors and resellers
Members accessing digital communities
Other external stakeholders
External licensing may use different access and consumption models, so organizations should estimate both the number of users and how frequently they will access the experience.
Salesforce also offers licenses tied to specific products or access requirements rather than traditional full CRM usage.
Examples can include:
Marketing Cloud products
Identity capabilities
Integration users
Industry-specific Salesforce products
Add-on functionality and permission set licenses
Evaluate these licenses separately because their pricing, entitlements, and usage models may differ from standard CRM user licenses.
A simple way to narrow down your options is to ask:
Does the user need full CRM functionality, limited internal platform access, external portal access, or access to a specialized Salesforce product?
Start with that answer, then compare the specific features, object access, limitations, and pricing of the licenses available for that use case.
Codleo Tip: Avoid assigning licenses based only on job titles. Two employees with similar titles may use Salesforce very differently. Mapping required objects, features, integrations, and workflows to each user role can help identify where full licenses are necessary and where more limited options may be sufficient.
One of the first decisions in Salesforce licensing is whether a user is an internal employee or an external user such as a customer, partner, reseller, or distributor.
Internal users typically need licenses that provide access to Salesforce applications used by employees, while external users generally access selected CRM data and processes through Salesforce Experience Cloud.
| Factor | Internal Salesforce Licenses | External Salesforce Licenses |
|---|---|---|
| Typical users | Employees and internal teams | Customers, partners, resellers, distributors |
| Common use cases | Sales, service, operations, custom business apps | Customer portals, partner portals, self-service, channel collaboration |
| Access level | Based on the assigned internal user license | Restricted to the capabilities available through the selected external license |
| Common license options | Salesforce, Salesforce Platform and product-specific internal licenses | Experience Cloud license options |
| Best suited for | Users working directly inside Salesforce | Users who need controlled access to Salesforce-powered digital experiences |
| Licensing consideration | Required features and objects per employee | User type, required data access, and expected login/usage pattern |
An internal Salesforce license is generally appropriate when an employee needs to perform day-to-day work directly within Salesforce.
For example, a sales representative managing leads and opportunities may require broader CRM functionality, while an operations employee working primarily with custom applications may be able to use a Salesforce Platform license, depending on the required objects and features.
The important point is that not every internal user automatically needs a full Salesforce license.
External licenses are intended for users outside your organization who need access to specific Salesforce-powered processes.
For example:
A customer checking support information may need customer-focused Experience Cloud access.
A reseller collaborating on leads or opportunities may require a partner-focused license.
A large customer base accessing a portal occasionally may require a different licensing model than a smaller group of users accessing it frequently.
This makes external licensing particularly dependent on what users need to access and how often they are expected to log in.
The better question is whether the user's requirements justify internal CRM access.
In most customer and partner portal scenarios, organizations should first evaluate the appropriate Experience Cloud license rather than automatically purchasing full internal CRM licenses. The correct option depends on the user's relationship with the organization, required Salesforce objects, permissions, and usage pattern.
Codleo Recommendation: Create separate license requirements for employees, customers, and partners before purchasing Salesforce licenses. This makes it easier to identify users who genuinely need full CRM functionality and reduces the risk of paying for unnecessary access.
Salesforce Experience Cloud licenses provide external users—such as customers, partners, resellers, and distributors—controlled access to Salesforce-powered portals, communities, and digital experiences.
The right license depends on three main factors: who the external users are, what Salesforce data they need to access, and how frequently they will use the portal.
| License Type | Best For | Typical Use Case | Access Level |
|---|---|---|---|
| Customer Community | Large customer populations with relatively simple access needs | Self-service, knowledge, basic case-related experiences | Basic external access |
| Customer Community Plus | Customers requiring more advanced sharing and administration capabilities | Advanced customer portals and delegated administration | More advanced than Customer Community |
| Partner Community | Partners, resellers and distributors participating in sales processes | Partner relationship management, channel sales and collaboration | Broader CRM access for partner use cases |
| External Identity | High-volume external users primarily requiring authentication | Login, registration and identity-driven experiences | Identity-focused rather than full community functionality |
Salesforce product names, entitlements, packaging, and availability can change. Confirm the capabilities included in your Salesforce agreement before selecting a license.
Customer Community licenses are generally designed for high-volume customer-facing experiences where external users need relatively limited access.
Common scenarios include:
Customer self-service
Accessing knowledge resources
Viewing relevant account information
Participating in support-related processes
This option can make sense when customers need a Salesforce-powered portal but do not require the broader CRM functionality associated with partner collaboration.
Customer Community Plus is intended for more complex customer experiences that require additional sharing, reporting, or administrative capabilities.
It may be appropriate when your portal requires:
More advanced record-sharing requirements
Delegated external-user administration
Greater visibility across relevant customer data
More sophisticated customer collaboration
The decision between Customer Community and Customer Community Plus should therefore be based on required functionality and sharing complexity, rather than simply choosing the lower-cost license.
Partner Community licenses are designed for organizations that collaborate with channel partners, resellers, distributors, or other external sales participants.
Typical use cases can include:
Lead and opportunity collaboration
Partner account management
Deal registration
Channel sales processes
Sharing relevant CRM information with partners
If external users actively participate in your sales process, a partner-focused Experience Cloud license will generally be more relevant than a basic customer portal license.
External Identity is designed primarily for scenarios where organizations need to manage the identity and authentication of large external user populations.
It can be useful for experiences involving registration, login, profile management, and secure access where users don't need the functionality of a full customer or partner community license.
A practical starting point is:
Basic customer self-service: evaluate Customer Community.
Advanced customer access and sharing: evaluate Customer Community Plus.
Partner or reseller collaboration: evaluate Partner Community.
Primarily authentication and identity: evaluate External Identity.
However, the lowest-priced option is not automatically the most cost-effective. A license that doesn't support your required objects, sharing model, or business processes can lead to extra configuration work or require a licensing change later.
Codleo Tip: Before purchasing Experience Cloud licenses, create a simple matrix of external user type → required Salesforce objects → required actions → expected login frequency. This makes it easier to compare license options based on actual usage, not assumptions.
Salesforce Experience Cloud licensing can use different consumption models depending on the product and contract. Two important models to understand are member-based licensing and login-based licensing.
The better option depends largely on how many external users you have and how frequently each user accesses your Experience Cloud site.
| Factor | Member-Based Licensing | Login-Based Licensing |
|---|---|---|
| How it works | Access is assigned to specific external users | Usage is based on logins or login capacity |
| Best for | Users who access the portal regularly | Users who access the portal occasionally |
| Typical scenario | Active partners or customers returning frequently | Large customer population with infrequent access |
| Cost planning | Easier when the active user population is predictable | Useful when many registered users log in only occasionally |
| Main consideration | You may pay for assigned users even if some rarely log in | Heavy or unpredictable usage can consume login capacity faster |
Member-based licensing is generally worth evaluating when you have a relatively predictable group of external users who access the portal frequently.
For example, imagine a company has 200 channel partners, and most of them use its partner portal every week to collaborate on sales activities. Assigning access to those known, active users may be easier to forecast than relying on a login-consumption model.
Login-based licensing can be worth evaluating when you have a much larger external audience, but individual users access the portal only occasionally.
For example, an organization might have 20,000 registered customers, but only a small percentage log in during a typical month to check information or use a self-service experience.
In such a scenario, purchasing member-based access for every registered customer may not align with actual usage.
Don't compare the models using the number of registered users alone.
Estimate:
Active external users × average login frequency × expected growth
Then consider whether usage is consistent throughout the year or spikes during particular periods.
For example, a customer portal may experience significantly more activity during renewals, enrollment periods, product launches, or seasonal service demand. Include those peaks when estimating licensing requirements.
Frequent access by a predictable group of users → evaluate member-based licensing.
Occasional access by a large user population → evaluate login-based licensing.
This is a starting point, not a universal rule. Actual availability, entitlements, usage calculations, and commercial terms depend on the specific Salesforce product and agreement.
Codleo Tip: Review historical portal usage before renewing Experience Cloud licenses. Comparing registered users with monthly active users and login frequency can reveal whether your current licensing model still matches actual customer or partner behavior.
The main difference between a Salesforce license and a Salesforce Platform license is the level of CRM functionality available to the user.
A full Salesforce license is generally appropriate for users who need broad access to standard CRM functionality, while a Salesforce Platform license is designed for internal users who primarily work with custom apps and platform-based business processes.
| Factor | Full Salesforce License | Salesforce Platform License |
|---|---|---|
| Best for | Sales, service and other CRM-intensive users | Internal users working mainly with custom apps and processes |
| Core CRM functionality | Broader access based on the purchased Salesforce product and edition | More limited access to standard CRM functionality |
| Custom objects/apps | Yes, subject to edition and permissions | A major Platform use case, subject to license entitlements |
| Leads & opportunities | Suitable when the purchased product provides access | Generally not the right choice when users need full lead and opportunity functionality |
| Sales processes | Suitable for sales teams requiring core CRM capabilities | Limited for traditional sales-user requirements |
| Custom workflows and applications | Supported | Strong use case |
| Typical users | Sales reps, service users, CRM power users | Operations, back-office and custom-app users |
| Cost consideration | Paying for broader CRM capabilities may be justified for CRM-heavy roles | Can be worth evaluating for users who don't require full CRM functionality |
A full Salesforce license is generally the better fit when a user's responsibilities depend heavily on standard CRM processes.
For example, a sales representative who regularly needs to manage leads, accounts, contacts, opportunities, activities, and forecasts should be evaluated for the appropriate full CRM license.
Trying to reduce licensing costs by assigning an overly restrictive license can create operational problems if users cannot access the objects or features required for their jobs.
A Salesforce Platform license can be worth considering when an employee uses Salesforce primarily as a platform for internal applications rather than as a complete sales or service CRM.
Common scenarios can include:
Internal approval applications
Operations workflows
Employee or back-office applications
Custom object-based processes
Internal request-management applications
Other custom applications built on the Salesforce Platform
For example, an operations employee who updates custom project records and approves internal requests may not require the same CRM functionality as an account executive managing an opportunity pipeline.
Potentially—but only when the user's actual requirements fit the license.
The goal should not be to move as many users as possible to a lower-cost license. Instead, organizations should identify users who are paying for CRM capabilities they don't actually need.
A practical license review can follow this process:
User role → Required objects → Required features → Required integrations → Appropriate license
This approach is safer than choosing a license based purely on subscription price.
Before assigning a Platform license, verify whether the user requires:
Standard sales objects and processes
Service-related functionality
Advanced product-specific features
Specific reporting capabilities
API or integration functionality
Add-ons or permission set licenses
A Platform license cannot simply be expanded with permissions to provide functionality that the underlying license does not entitle the user to access.
Codleo Recommendation: Before changing full Salesforce licenses to Platform licenses, perform a role-based license audit. Review actual object usage and business processes for each user group so that cost optimization doesn't come at the expense of functionality.
Salesforce Developer Edition and Salesforce Platform licenses serve fundamentally different purposes. Developer Edition provides a separate Salesforce environment for learning, development, and testing, while Salesforce Platform licenses provide users access to supported functionality within an organization's Salesforce production environment.
In other words, businesses should not treat Developer Edition as a cheaper alternative to a Salesforce Platform or full CRM user license.
| Factor | Salesforce Developer Edition | Salesforce Platform License |
|---|---|---|
| Primary purpose | Learning, building, testing, and experimentation | Running internal business applications on Salesforce |
| Typical user | Developers, learners, architects, administrators | Employees and internal business users |
| Production use | Not intended as a replacement for production user licensing | Designed for eligible production business use |
| Environment | Separate development environment | User access within an organization's Salesforce org |
| Custom development | Useful for testing Salesforce development capabilities | Supports custom applications subject to purchased entitlements |
| CRM use case | Development and experimentation | Limited CRM/platform business use cases |
| Commercial model | Developer environment rather than a standard production seat | Commercial user licensing |
| Best choice when | You need an environment to learn or develop | Employees need ongoing access to Salesforce-based internal apps |
Salesforce Developer Edition is a Salesforce environment intended for development, testing, learning, and experimentation.
Developers can use it to explore platform capabilities, build prototypes, test customizations, and practice Salesforce development without treating the environment as a production CRM deployment.
It is particularly useful for:
Learning Salesforce development
Building proof-of-concept applications
Testing Apex and Lightning components
Exploring platform functionality
Practicing configuration and administration
A Salesforce Platform license is designed for business users who need ongoing access to eligible Salesforce platform capabilities and custom applications inside their organization's Salesforce environment.
For example, a company may build an internal application for project approvals, vendor management, employee requests, or operational workflows. Employees using that application may be candidates for Platform licensing if the required functionality falls within the license entitlements.
No—not as a substitute for licensing users in a production Salesforce implementation.
Developer Edition is useful for development and learning, but organizations deploying Salesforce for real business users should select production licenses based on the products, objects, features, and access those users require.
If the objective is reducing Salesforce licensing costs, evaluate whether some users qualify for Salesforce Platform or another appropriate license type rather than trying to replace production licensing with Developer Edition.
Codleo Tip: Separate your development-environment strategy from your user-licensing strategy. First determine what employees need to accomplish in production, then map those requirements to the appropriate Salesforce licenses.
Salesforce license pricing varies widely by product, edition, user type, add-ons, and contract terms. A small sales team using core CRM functionality will have a very different licensing structure from an enterprise running Sales Cloud, Service Cloud, Experience Cloud, and additional Salesforce products.
The table below provides a quick view of common Salesforce licensing options and their typical use cases.
| Salesforce Product / License | Starting or Listed Price* | Best For |
|---|---|---|
| Salesforce Starter Suite | $25/user/month | Small teams requiring core CRM capabilities |
| Salesforce Pro Suite | $100/user/month | Growing businesses requiring greater customization and automation |
| Sales Cloud Core | $195/user/month | Sales teams requiring advanced CRM, AI and related capabilities |
| Sales Cloud Advanced | $395/user/month | Organizations requiring greater AI, security and data capabilities |
| Sales Cloud Max | $550/user/month | Organizations requiring Salesforce's broadest Sales Cloud package |
| Service Cloud Starter Suite | Starting at $25/user/month | Smaller teams getting started with CRM and service capabilities |
| Service Cloud Core | $195/user/month | Customer service teams requiring core service functionality |
| Service Cloud Advanced | $395/user/month | Advanced service organizations requiring additional AI and security capabilities |
| Service Cloud Max | $550/user/month | Complex service and contact-center environments |
| Partner Relationship Management | $25/member/month | Partners, resellers and channel collaboration |
| Partner Ecosystem Management | $50/member/month | Organizations managing more advanced partner ecosystems |
| External Apps | $35/member/month or $15/login/month | External applications requiring broader customization |
Prices shown are publicly listed Salesforce USD prices checked in September 2026 and may be billed annually depending on the product. Salesforce pricing, packaging, regional availability, contract terms, minimum purchases, and product names can change. Confirm current pricing directly with Salesforce before purchasing.
There is no single price for a Salesforce license.
For basic CRM requirements, Salesforce currently lists Starter Suite from $25 per user per month, while more advanced Sales Cloud and Service Cloud packages can cost several hundred dollars per user per month.
The subscription price is also only one part of the overall Salesforce cost.
Organizations may also need to budget for:
Additional Salesforce products and add-ons
Experience Cloud users
Data or storage requirements
Integrations
Implementation and customization
User training
Ongoing administration and support
This is why comparing Salesforce licenses purely on the monthly per-user price can be misleading.
Consider two employees:
User A: An account executive manages leads, opportunities, forecasts, and customer relationships every day.
User B: An operations employee mainly reviews custom records and approves internal requests.
Giving both users the same license may be unnecessary if their Salesforce requirements differ significantly.
Instead, evaluate:
User role → Required objects → Required features → Usage frequency → Appropriate license
This role-based approach can help organizations avoid both over-licensing and under-licensing.
The cheapest option depends on what the user actually needs to accomplish.
A lower-cost license isn't a saving if it prevents a user from accessing required objects or completing an essential business process. Likewise, assigning broad CRM functionality to users who only require limited platform access may create unnecessary recurring costs.
The objective should therefore be to find the lowest-cost license that fully supports the user's required business functionality, rather than simply selecting the lowest advertised price.
Codleo Recommendation: Before purchasing or renewing Salesforce licenses, map users into functional groups such as sales, service, operations, executives, partners, customers, and integration users. Compare each group's required functionality with your current license assignments to identify potential licensing gaps or unnecessary spend.
Each user gets a core Salesforce license, which provides the basic features they need.
Salesforce user licenses include permission sets that offer additional access to features beyond the basic options. Permission set licenses also provide access to additional features not included in the main user license.
The right Salesforce license depends on what each user needs to do, not simply their department or job title. Start by identifying the Salesforce objects, features, applications, and level of access required for each user group.
| User Type | License to Evaluate | Why |
|---|---|---|
| Sales representative | Sales Cloud | Designed for users working with leads, accounts, contacts, opportunities, activities, and sales processes |
| Sales manager | Sales Cloud | Supports pipeline management, forecasting, reporting, and team-level sales processes |
| Customer service agent | Service Cloud | Built for case management and customer service workflows |
| Operations or back-office user | Salesforce Platform | Worth evaluating when the user primarily works with custom apps and doesn't require full sales or service functionality |
| Customer | Experience Cloud customer-focused license | Provides controlled external access for self-service and customer experiences |
| Partner or reseller | Experience Cloud partner-focused license | Designed for external users participating in channel and partner processes |
| Developer | Developer environments plus the appropriate production access | Development requirements should be separated from production user licensing |
| System integration | Integration-focused license/access | Appropriate when a system primarily needs API-based rather than normal end-user access |
| Marketing user | Relevant Marketing Cloud product | Designed for marketing automation, journeys, engagement, and related marketing use cases |
| Identity-only external user | External Identity | Worth evaluating when authentication and identity are the primary requirements |
These are starting points, not universal license recommendations. Actual entitlements depend on the Salesforce product, edition, contract, and required functionality.
Before assigning a license, answer these questions for each user group:
Which Salesforce objects does the user need?
Identify whether they need leads, opportunities, cases, custom objects, or other records.
What actions will they perform?
Viewing data and actively managing sales or service processes can require very different access levels.
Does the user need standard CRM or mainly custom apps?
Users primarily working with custom applications may have different licensing requirements from full CRM users.
Is the user internal or external?
Evaluate customers and partners separately from employees.
How frequently will the user access Salesforce?
This is particularly important when evaluating applicable Experience Cloud licensing models.
Consider a company with 100 people who interact with Salesforce in different ways.
Its account executives may need full Sales Cloud functionality, while an operations team may primarily use custom Salesforce applications. Customer service representatives may require Service Cloud, partners may access an Experience Cloud portal, and an integration may need dedicated system access.
Buying the same type of Salesforce license for all of these requirements could result in either unnecessary spending or insufficient functionality.
The better approach is:
Segment users → document required functionality → compare eligible licenses → validate limitations → estimate total cost
License selection becomes more complex when an organization has multiple Salesforce clouds, custom applications, large external-user populations, integrations, or hundreds of internal users.
In these situations, an experienced Salesforce consulting partner can review business requirements and current license utilization before you purchase additional licenses.
Codleo's Salesforce consulting services can help organizations map user roles and business processes to appropriate Salesforce capabilities, identify potentially underused licenses, and evaluate licensing requirements alongside the broader Salesforce architecture.
The objective of a license assessment should not simply be to buy fewer licenses. It should ensure each user has the functionality required to perform their role without paying for unnecessary access.
The right Salesforce license depends on what each user needs to do, not simply their department or job title. Start by identifying the Salesforce objects, features, applications, and level of access required for each user group.
| User Type | License to Evaluate | Why |
|---|---|---|
| Sales representative | Sales Cloud | Designed for users working with leads, accounts, contacts, opportunities, activities, and sales processes |
| Sales manager | Sales Cloud | Supports pipeline management, forecasting, reporting, and team-level sales processes |
| Customer service agent | Service Cloud | Built for case management and customer service workflows |
| Operations or back-office user | Salesforce Platform | Worth evaluating when the user primarily works with custom apps and doesn't require full sales or service functionality |
| Customer | Experience Cloud customer-focused license | Provides controlled external access for self-service and customer experiences |
| Partner or reseller | Experience Cloud partner-focused license | Designed for external users participating in channel and partner processes |
| Developer | Developer environments plus the appropriate production access | Development requirements should be separated from production user licensing |
| System integration | Integration-focused license/access | Appropriate when a system primarily needs API-based rather than normal end-user access |
| Marketing user | Relevant Marketing Cloud product | Designed for marketing automation, journeys, engagement, and related marketing use cases |
| Identity-only external user | External Identity | Worth evaluating when authentication and identity are the primary requirements |
These are starting points, not universal license recommendations. Actual entitlements depend on the Salesforce product, edition, contract, and required functionality.
Before assigning a license, answer these questions for each user group:
Which Salesforce objects does the user need?
Identify whether they need leads, opportunities, cases, custom objects, or other records.
What actions will they perform?
Viewing data and actively managing sales or service processes can require very different access levels.
Does the user need standard CRM or mainly custom apps?
Users primarily working with custom applications may have different licensing requirements from full CRM users.
Is the user internal or external?
Evaluate customers and partners separately from employees.
How frequently will the user access Salesforce?
This is particularly important when evaluating applicable Experience Cloud licensing models.
Consider a company with 100 people who interact with Salesforce in different ways.
Its account executives may need full Sales Cloud functionality, while an operations team may primarily use custom Salesforce applications. Customer service representatives may require Service Cloud, partners may access an Experience Cloud portal, and an integration may need dedicated system access.
Buying the same type of Salesforce license for all of these requirements could result in either unnecessary spending or insufficient functionality.
The better approach is:
Segment users → document required functionality → compare eligible licenses → validate limitations → estimate total cost
License selection becomes more complex when an organization has multiple Salesforce clouds, custom applications, large external-user populations, integrations, or hundreds of internal users.
In these situations, an experienced Salesforce consulting partner can review business requirements and current license utilization before you purchase additional licenses.
Codleo's Salesforce consulting services can help organizations map user roles and business processes to appropriate Salesforce capabilities, identify potentially underused licenses, and evaluate licensing requirements alongside the broader Salesforce architecture.
A license assessment should not simply aim to buy fewer licenses. It should ensure each user has the functionality needed to perform their role without paying for unnecessary access.
Salesforce Marketing Cloud licensing differs from traditional Salesforce CRM licensing. Instead of choosing only a user license, organizations may need to consider the specific Marketing Cloud product, customer or contact volumes, messaging usage, data requirements, and the marketing capabilities they need.
This means a company running basic email campaigns may have very different licensing requirements from an enterprise managing millions of customer interactions across email, SMS, advertising, and personalized journeys.
Marketing Cloud is a portfolio of marketing products, not a single universal license.
Depending on the solution, pricing and packaging can be influenced by factors such as:
Marketing product or edition
Number of contacts or customer records
Email and messaging volume
Marketing automation requirements
Data and segmentation needs
AI and personalization capabilities
Additional channels or add-ons
For this reason, businesses should define their marketing use case before comparing Marketing Cloud packages.
| Marketing Requirement | Product to Evaluate | Typical Use Case |
|---|---|---|
| B2C customer journeys and engagement | Marketing Cloud Engagement | Email, mobile messaging, journeys, segmentation, and cross-channel engagement |
| B2B marketing automation | Marketing Cloud Account Engagement | Lead nurturing, scoring, B2B campaigns, and sales-marketing alignment |
| Customer data activation | Data Cloud | Unifying and activating customer data across Salesforce experiences |
| Advanced personalization | Salesforce personalization capabilities | Delivering more relevant experiences based on customer behavior and data |
| Marketing analytics | Relevant Salesforce marketing analytics capabilities | Campaign measurement, marketing performance, and customer insights |
Salesforce product names, packaging, entitlements, and commercial models evolve over time. Confirm the current product offering and contract terms with Salesforce.
One of the most common licensing mistakes is assuming these products solve the same marketing problem.
Marketing Cloud Engagement is generally evaluated for B2C and high-volume customer engagement scenarios involving journeys and multiple communication channels.
Marketing Cloud Account Engagement focuses on B2B marketing automation, where organizations need capabilities such as lead nurturing, scoring, campaign automation, and alignment between marketing and sales teams.
The better choice therefore depends on your marketing model and required capabilities, not simply which product has the lower starting price.
Before selecting a Marketing Cloud product or package, estimate:
How many marketable contacts or customers will you manage?
Which channels will you use—email, SMS, mobile, advertising, or others?
How many messages do you expect to send?
Do you operate primarily in B2B, B2C, or both?
Do you need advanced journeys, personalization, analytics, or AI?
Which CRM, ecommerce, data, and third-party systems must be integrated?
These factors can affect both your initial licensing decision and the total cost of operating Salesforce Marketing Cloud.
A common mistake is purchasing Marketing Cloud based on current campaign requirements without considering contact growth, messaging volume, additional channels, integrations, and future automation requirements.
For example, a company may initially require only email automation but later introduce SMS, more sophisticated customer journeys, additional business units, or deeper customer-data activation.
Planning these requirements before purchasing can reduce the risk of selecting a package that becomes unsuitable as the marketing operation grows.
Codleo Tip: Build a 12–24 month estimate covering contact growth, messaging volumes, channels, integrations, and planned marketing use cases before finalizing Marketing Cloud licensing. This provides a more useful cost picture than comparing package prices alone.
Eligible nonprofit organizations can access donated Salesforce licenses and discounted products through the Salesforce Power of Us Program, making Salesforce more accessible for organizations managing donors, fundraising, programs, volunteers, and other mission-driven operations.
Yes. Eligible nonprofits can receive 10 donated Salesforce licenses through the Power of Us Program.
According to Salesforce, approved organizations can currently request one of these license bundles:
10 Agentforce Nonprofit – Enterprise Edition licenses (formerly Nonprofit Cloud), or
10 Sales and Service – Enterprise Edition licenses
Organizations requiring more than the donated licenses may also qualify for nonprofit discounts on additional Salesforce products and licenses.
For organizations requiring additional licenses, Salesforce currently lists the following Nonprofit Cloud pricing:
| Nonprofit Cloud Edition | Listed Price* | Best For |
|---|---|---|
| Nonprofit Cloud – Enterprise | $60/user/month | Nonprofits requiring fundraising, program, outcome, volunteer, and nonprofit-specific capabilities |
| Nonprofit Cloud – Unlimited | $100/user/month | Organizations requiring greater storage, automation, support, and sandbox capabilities |
| Nonprofit Cloud Agentforce 1 for Sales | $135/user/month | Nonprofits combining CRM, nonprofit functionality, AI, Data Cloud, Slack, and related capabilities |
| Nonprofit Cloud Agentforce 1 for Service | $135/user/month | Nonprofits requiring advanced service, AI, Data Cloud, Experience Cloud, and related capabilities |
Salesforce currently lists these USD prices with annual billing. Pricing, packaging, eligibility, and product names can change, so organizations should verify current terms directly with Salesforce before purchasing.
Depending on the selected products and configuration, nonprofits can use Salesforce to support processes such as:
Donor and constituent management
Fundraising
Program management
Outcome tracking
Volunteer management
Case or participant management
Reporting and analytics
Stakeholder engagement
The right Salesforce setup therefore depends on more than the number of users. Nonprofits should also consider the processes they need to manage and the functionality each team requires.
No. Nonprofit Cloud and the Nonprofit Success Pack (NPSP) are not the same product.
NPSP is not a Salesforce user license. It is a set of managed packages that can run on top of eligible Salesforce licenses.
Salesforce continues to support NPSP, but it is no longer receiving direct feature development or enhancements. Salesforce refers to this status as “End of Innovation.” Existing NPSP organizations are not required to migrate immediately and can continue using the product while evaluating Salesforce's newer nonprofit offerings.
This distinction matters when comparing Salesforce nonprofit licensing because an organization using NPSP may have a different architecture and migration path than one starting directly with the current Nonprofit Cloud offering.
Start with three questions:
Check eligibility before purchasing licenses because qualifying organizations may receive donated licenses.
Organizations managing fundraising, programs, outcomes, volunteers, and related nonprofit processes should evaluate the current Nonprofit Cloud capabilities.
Existing NPSP organizations should assess their current configuration, integrations, customizations, and future requirements before deciding whether a migration makes business sense.
Codleo Tip: Don't treat the 10 donated licenses as the entire Salesforce budget. Implementation, data migration, integrations, additional users, training, apps, and ongoing administration can still contribute to the total cost of ownership.
The cheapest Salesforce license isn't necessarily the most cost-effective. A lower-cost license can become a problem if users later discover that they cannot access the objects, applications, APIs, or business processes required for their roles.
Before purchasing or changing licenses, evaluate both what a Salesforce license includes and what it restricts.
| License Type | Good Fit For | Important Limitation to Check |
|---|---|---|
| Full Salesforce / CRM license | Users requiring broad CRM functionality | Higher cost may be unnecessary for users with limited requirements |
| Salesforce Platform | Internal users working primarily with custom apps | Does not provide the same access to standard CRM functionality as a full Salesforce license |
| Experience Cloud customer licenses | Customers accessing portals and self-service experiences | External-user access and sharing differ from internal Salesforce users |
| Experience Cloud partner licenses | Resellers, distributors, and channel partners | Access is designed around external partner use cases rather than unrestricted internal CRM usage |
| External Identity | Authentication and identity-focused experiences | Not a replacement for broader Experience Cloud or CRM functionality |
| Identity Only | Employees primarily requiring identity services such as SSO | Very limited Salesforce application/object access |
| Salesforce Integration | System-to-system integrations | Designed around API access rather than normal interactive Salesforce use |
| Developer Edition | Development, learning, and testing | Not a substitute for production user licensing |
A Salesforce Platform license can be a good option for employees who primarily use custom applications, but it should not automatically be treated as a cheaper version of a full Salesforce license.
Platform users can work with custom apps and supported platform functionality, but access to standard CRM objects and capabilities is more restricted.
For example, Salesforce states that standard Platform users aren't entitled to standard CRM objects such as leads, opportunities, campaigns, and forecasts.
Therefore, moving a sales user from a full CRM license to Platform purely to reduce cost could prevent them from performing essential sales activities.
A common misconception is that administrators can purchase a lower-level user license and then use permission sets to unlock anything the user needs.
That's not how Salesforce licensing works.
Permission sets determine what a user is allowed to access within the functionality supported by their licenses. If the underlying licenses don't support a particular permission or capability, adding it to a permission set doesn't automatically make that functionality available.
Permission Set Licenses and feature licenses can extend functionality in supported scenarios, but organizations should verify required entitlements before assuming permissions alone can solve an access issue.
External Identity is primarily designed around identity and authentication requirements for external users.
It can support scenarios such as:
User registration
Authentication
Profile management
Secure access to connected experiences
However, organizations requiring broader customer or partner processes should compare the appropriate Experience Cloud licensing rather than assuming External Identity provides equivalent functionality.
Identity Only licenses are designed for employees who primarily need Salesforce identity services, such as single sign-on.
Do not select them for employees who need to perform normal sales, service, or CRM activities.
If an employee needs Salesforce primarily as an identity provider for accessing another application, Identity Only may be worth evaluating. If they need to work with CRM records and business processes, they'll likely need another license.
A Salesforce Integration user license is intended for system-to-system integrations and supports a least-privilege approach to integration access.
Do not treat it as an inexpensive license for employees who need to use Salesforce through the normal user interface.
For integrations, organizations should also consider creating dedicated users for individual systems or integration use cases rather than sharing credentials across multiple integrations.
Not every license, feature, add-on, or permission is available with every Salesforce edition.
Your actual options can depend on:
Salesforce edition
Products purchased
Add-ons and feature licenses
Permission Set Licenses
Contract terms
Region
Existing Salesforce architecture
That is why you should treat online Salesforce license comparisons as a starting point, not a replacement for reviewing your organization's actual Salesforce agreement and entitlements.
Before upgrading or downgrading a Salesforce user license, review:
Objects the user currently accesses
Apps and tabs required for their role
Permission sets and Permission Set Licenses assigned
Reports, dashboards, and workflows they depend on
Integrations or API requirements
Custom applications and objects they use
Sales, service, or other product-specific functionality required
Then compare those requirements with the proposed license.
Codleo Recommendation: Don't downgrade licenses based only on login frequency or apparent inactivity. Review actual feature, object, and business-process usage first. A user who logs in infrequently may still depend on functionality that isn't available under a lower-level license.
A Salesforce license audit helps you determine whether you're paying for the right number and type of licenses—and whether users actually need the functionality assigned to them.
A useful audit should go beyond counting unused licenses. It should connect license allocation, user activity, required functionality, and business roles.
| Audit Area | What to Check | What It May Reveal |
|---|---|---|
| Purchased licenses | Total licenses purchased by type | Overall licensing commitment |
| Assigned licenses | Licenses currently allocated to users | Unallocated capacity |
| Active users | Users who still require Salesforce access | Former employees or unnecessary accounts |
| Login activity | Last login and usage patterns | Potentially inactive or infrequent users |
| User roles | What each group actually does in Salesforce | Users who may have mismatched licenses |
| Object usage | Leads, opportunities, cases, custom objects, etc. | Whether full CRM functionality is required |
| Permission assignments | Profiles, permission sets and Permission Set Licenses | Additional functionality being consumed |
| External users | Customer and partner usage | Experience Cloud licensing requirements |
| Integration users | APIs and connected systems | Shared or incorrectly licensed integrations |
| Upcoming requirements | New users, products, portals and projects | Future licensing demand |
Start by documenting what your organization currently owns.
In Salesforce Setup, review your company and user-license information to understand the licenses available and how many are assigned.
Capture:
License type
Purchased quantity
Assigned quantity
Available quantity
Associated products or add-ons
Renewal date, where available from your commercial records
Don't rely only on Salesforce Setup for commercial analysis. Your Salesforce contract, order forms, and renewal documentation can provide important information about what you're actually paying for.
Review active Salesforce users and their recent login activity.
Look for accounts associated with:
Former employees
Contractors who no longer require access
Duplicate users
Test accounts
Users who have changed roles
Employees with very limited Salesforce usage
An inactive user doesn't automatically mean you should remove the license. Confirm whether the person still has a legitimate business requirement before changing access.
Instead of auditing users one by one initially, group them by business function.
For example:
Sales reps → Service agents → Operations → Executives → Administrators → Integration users → Partners → Customers
Then document the functionality required by each group.
A simple framework is:
User group → Required objects → Required actions → Required features → Current license → License to evaluate
This makes license mismatches much easier to identify.
Over-licensing occurs when users have broader Salesforce capabilities than their roles require.
For example, an employee may have a full CRM license while primarily working with custom objects and an internal application.
That doesn't automatically mean you should downgrade the license. Instead, it signals that you should evaluate a Salesforce Platform or another appropriate license against the user's full requirements.
Cost reduction shouldn't be the only goal.
Under-licensing can create equally serious problems when users lack the functionality they need to do their work.
Look for:
Workarounds caused by restricted access
Users sharing accounts
Manual processes outside Salesforce
Missing object access
Teams exporting data because they cannot perform required activities inside Salesforce
Integrations using inappropriate user accounts
These issues may indicate that the current licensing structure does not align with the Salesforce solution.
User licenses are only one part of Salesforce licensing.
Review paid add-ons, feature licenses, and Permission Set Licenses to identify functionality that is assigned but rarely used.
Ask:
Who has it? → Who uses it? → Who needs it? → What business outcome does it support?
This can uncover optimization opportunities that a basic user-license count may miss.
Don't wait until a Salesforce renewal is already being finalized.
Before renewal, compare:
Current licenses + actual utilization + expected hiring + planned Salesforce projects + new product requirements
This gives your organization a stronger basis for deciding what to renew, add, reduce, or restructure.
A useful license audit should produce a clear action plan, not just a spreadsheet of users.
Your final output should identify:
Licenses that are actively required
Unused or unassigned licenses
Potentially over-licensed users
Potentially under-licensed users
Add-ons requiring review
External-user licensing requirements
Integration-user issues
Expected future license demand
Actions to evaluate before renewal
At minimum, consider reviewing licenses before a major renewal, after significant hiring or restructuring, and when Salesforce usage changes substantially.
Large or complex Salesforce environments may benefit from more frequent reviews.
If your organization operates multiple Salesforce products or has hundreds of users, experienced Salesforce consultants can also help connect licensing decisions to your Salesforce architecture and business processes.
Codleo Tip: Don't start a license audit with the question, “Which licenses can we remove?” Start with, “What does each user group need Salesforce to do?” Cost optimization should follow business requirements—not the other way around.
Reducing Salesforce licensing costs doesn't necessarily mean buying fewer licenses. The bigger opportunity is often making sure each user has the right license for the work they actually perform.
Organizations can overspend when inactive accounts remain licensed, employees receive broader CRM access than they require, paid add-ons go unused, or external users are placed on an unsuitable licensing model.
Here are practical ways to evaluate your Salesforce license spend.
Start with users who have left the organization, changed roles, completed temporary projects, or no longer require Salesforce.
Review inactive accounts carefully before renewal so you don't maintain licenses simply because nobody has revisited the assignment.
However, low login frequency alone isn't enough reason to remove or downgrade a license. Always verify the user's business responsibilities first.
Not every employee interacting with Salesforce necessarily requires the same level of CRM functionality.
For each user group, document:
Required objects → Required actions → Required features → Appropriate license
For example, an operations employee who primarily works with custom applications may have different licensing requirements from a salesperson who manages leads, opportunities, and forecasts.
Where requirements permit, evaluate whether an appropriate Platform or other license could meet the user's needs without paying for unnecessary functionality.
Base user licenses aren't the only source of Salesforce licensing costs.
Organizations may also pay for additional products, features, and Permission Set Licenses purchased for a project or assigned historically but no longer widely used.
Review:
Who has each paid entitlement?
Who actively uses it?
Which business process requires it?
Is that requirement still valid?
Will it be needed after the next renewal?
An entitlement should have a clear business reason for remaining in the licensing footprint.
For customer and partner portals, review the applicable external-user licensing models against actual usage.
A portal with a large number of registered customers who log in occasionally may have different licensing needs from a partner portal with a smaller population of users who access Salesforce frequently.
Analyze:
Registered users → Monthly active users → Login frequency → Seasonal peaks → Expected growth
Then compare those patterns with the Experience Cloud options available under your Salesforce agreement.
Review integrations that rely on employee accounts or unnecessarily broad Salesforce access.
Where appropriate, evaluate dedicated integration users and the relevant integration licensing so system-to-system connections follow a more controlled access model.
Dedicated integration identities can also make access management, auditing, troubleshooting, and security easier than sharing human-user credentials across systems.
Avoid purchasing licenses solely on projected headcount without considering when users will actually need Salesforce.
Build a forecast covering:
| Question | Why It Matters |
|---|---|
| How many users need Salesforce today? | Establishes current demand |
| How many users are expected in 6–12 months? | Supports growth planning |
| Which teams will use Salesforce? | Helps determine license mix |
| What functionality will each team require? | Prevents one-license-fits-all purchasing |
| Are new Salesforce products being introduced? | Identifies future licensing requirements |
| When is the next renewal? | Creates a timeline for optimization decisions |
The best time to identify licensing changes is before you finalize renewal discussions.
Compare your current contract against:
Active users
Actual usage
User-role changes
Required functionality
Paid add-ons
Planned hiring
New Salesforce projects
External-user growth
Integration requirements
This creates a fact-based view of what your organization will likely need during the next contract period.
No single license change reduces costs for every Salesforce customer.
The most common areas worth investigating are:
Inactive users + over-provisioned licenses + unused paid entitlements + unsuitable external-user licensing + outdated integration access + inaccurate future license forecasts.
The potential financial impact depends on your existing contract, number of users, products, and actual usage.
Aggressive license reduction can create hidden costs if employees lose required functionality and teams compensate with manual processes, spreadsheets, workarounds, or additional applications.
A better objective is:
Lowest appropriate licensing cost + required functionality + room for expected growth.
For complex Salesforce environments, a Salesforce consulting partner can help evaluate licensing requirements alongside user roles, integrations, custom applications, and the overall Salesforce architecture.
Codleo's Salesforce consulting services can support license and utilization assessments to identify areas to review before purchasing additional licenses or entering a renewal discussion.
Codleo Recommendation: Treat Salesforce license optimization as an ongoing governance activity rather than a one-time cost-cutting exercise. Reassess your license mix whenever user roles, Salesforce products, integrations, or business processes materially change.
To understand the financial impact of Salesforce licensing, consider a growing B2B company with 75 employees, where different teams use Salesforce for different purposes.
The company has:
25 account executives managing leads and opportunities
8 sales managers overseeing pipeline and forecasting
12 customer service agents handling support
20 operations employees working primarily with custom Salesforce applications
5 Salesforce administrators and power users
5 employees who don't require Salesforce access
A common licensing mistake is assuming all 70 Salesforce users need the same full CRM license.
They don't necessarily have the same requirements.
| User Group | Users | Primary Salesforce Requirement | License Approach to Evaluate |
|---|---|---|---|
| Account executives | 25 | Leads, accounts, opportunities, and sales activities | Sales Cloud |
| Sales managers | 8 | Pipeline, forecasting, reporting and sales management | Sales Cloud |
| Service agents | 12 | Cases and customer service processes | Service Cloud |
| Operations | 20 | Custom apps, workflows and internal records | Salesforce Platform |
| Admins/power users | 5 | Broad administration and CRM access | Appropriate full Salesforce access |
| No Salesforce requirement | 5 | No CRM responsibilities | No user license required |
This doesn't mean you should automatically purchase these licenses. It provides a starting point for validating each group's requirements against Salesforce's current license entitlements.
Suppose the company gave all 70 Salesforce users a $195/user/month full CRM package simply for easier administration.
The illustrative subscription calculation would be:
70 users × $195 × 12 months = $163,800 per year
Now assume the company performs a license assessment and discovers that the 20 operations users don't require full sales or service functionality.
Instead of automatically renewing the same license mix, the company can evaluate whether an appropriate Salesforce Platform license supports those users' required objects, applications, automation, reporting, and integrations.
The potential difference can be calculated as:
20 operations users × (full CRM price − eligible alternative license price) × 12
This is a more useful way to estimate license optimization than assuming every organization can achieve a fixed percentage saving.
The annual subscription calculation doesn't reflect the total cost of Salesforce ownership.
The company may also need to budget for:
Salesforce implementation or configuration
Integrations with other business systems
Data migration and data quality work
Experience Cloud licenses
Additional Salesforce products and add-ons
Training and user adoption
Administration and ongoing support
Future user growth
For example, choosing a lower-cost license that cannot support an essential business process may eventually cost more through workarounds, additional tools, or reconfiguration.
The key lesson isn't that Salesforce Platform licenses are always cheaper or that every company should downgrade users.
It is that Salesforce licensing should be based on user requirements rather than employee count alone.
For a 500-user organization, even a relatively small mismatch across dozens of users can materially affect annual subscription spend. At the same time, aggressive downgrading can create productivity and access problems.
The goal is to find the right balance between:
Required functionality + appropriate license + actual utilization + total cost
Codleo Consultant's View: Start license planning with business roles, not Salesforce products. Once you know what each user group needs to view, create, approve, automate, and report on, it becomes much easier to determine which Salesforce license options deserve evaluation.
Salesforce licensing problems often arise not because organizations buy too few licenses, but because they assign licenses without mapping them to actual business requirements.
Here are seven mistakes to watch for when purchasing, assigning, or renewing Salesforce licenses.
A sales representative, operations employee, administrator, and integration user may all interact with Salesforce, but they don't necessarily need the same functionality.
Assigning a full CRM license to every user can mean paying for capabilities that some employees rarely or never use.
Better approach: Segment users by role and document the objects, features, applications, and actions each group requires before selecting licenses.
A lower subscription cost doesn't automatically mean a lower total cost.
If a cheaper license prevents employees from accessing required CRM functionality, teams may resort to spreadsheets, manual processes, additional applications, or workarounds.
Instead of asking:
“Which Salesforce license is cheapest?”
Ask:
“What is the lowest-cost license that fully supports this user's required business processes?”
Permission sets can extend a user's permissions, but only within the capabilities supported by the underlying licenses and entitlements.
They should not be treated as a way to purchase a limited user license and then unlock unrestricted Salesforce functionality.
Before changing licenses: review the user's license, Permission Set Licenses, permission sets, required objects, and product-specific functionality together.
Organizations can accumulate unnecessary licenses as employees leave, change departments, complete projects, or stop using Salesforce.
Before renewal, compare:
Purchased licenses → Assigned licenses → Active users → Actual requirements → Future demand
Don't use login frequency alone to make the decision. An infrequent user may still require important functionality at specific points in a business process.
Customer and partner portals have different licensing considerations from internal Salesforce users.
A business with thousands of occasional customer users may need a very different model from a company with a smaller group of partners accessing Salesforce frequently.
Review:
External user type
Required records and functionality
Expected active users
Login frequency
Seasonal usage
Future growth
Then evaluate the applicable Experience Cloud licensing options.
Connecting business systems through individual employee accounts can create licensing, security, ownership, and continuity problems.
If that employee changes roles or leaves the company, the integration can also become harder to manage.
Where appropriate, evaluate dedicated integration users and relevant integration access based on the system's actual requirements.
License optimization shouldn't begin when a renewal deadline is days away.
Organizations should review licensing whenever there is a significant change such as:
Rapid hiring or downsizing
Department restructuring
A new Salesforce implementation
New integrations
Experience Cloud rollout
Acquisition or consolidation
Introduction of additional Salesforce products
A pre-renewal review should then confirm whether the existing license mix still matches the organization's expected Salesforce usage over the next 12–24 months.
Rather than starting with Salesforce products and asking who should receive them, reverse the process:
Business role → Required processes → Required objects and features → Usage pattern → Eligible license options → Cost
This helps balance functionality and cost without making licensing decisions purely on price.
Codleo Consultant's View: License optimization is most effective when it is reviewed alongside Salesforce architecture and business processes. A license that appears unused may support an important workflow, while a heavily used account may still have more functionality than the role requires. Validate the business requirement before changing access.
The right Salesforce license isn't necessarily the one with the most features or the lowest monthly price. It is the license that provides the functionality a user actually needs without paying for unnecessary access.
Start by grouping users according to their responsibilities. Identify the objects, applications, integrations, and Salesforce features each group requires, then compare those requirements with the available license options.
For most organizations, the decision can be simplified to:
Full CRM functionality → evaluate Sales Cloud or Service Cloud
Custom internal applications → evaluate Salesforce Platform
Customer or partner access → evaluate Experience Cloud
System-to-system connectivity → evaluate integration-focused access
Marketing automation → evaluate the appropriate Marketing Cloud product
And don't treat licensing as a one-time purchasing decision. User roles, Salesforce products, integrations, and business processes change over time, so your license mix should be reviewed periodically—particularly before renewal.
If you're unsure whether your organization has the right Salesforce license mix, Codleo can help assess your existing environment before you purchase additional licenses or finalize a renewal.
As a Salesforce consulting partner, Codleo's Salesforce consultants can review:
Current license allocation and utilization
User roles and required Salesforce functionality
Potentially over- or under-provisioned users
Salesforce Platform vs. full CRM requirements
Experience Cloud licensing requirements
Integration-user access
Paid add-ons and Permission Set Licenses
Future licensing requirements based on planned Salesforce initiatives
The objective isn't simply to reduce license count. It is to build a Salesforce licensing structure that balances functionality, utilization, scalability, and cost.
Planning a Salesforce purchase or renewal? Talk to Codleo's Salesforce consultants to review your licensing requirements before making your next licensing decision.
Review Your Salesforce Licensing Requirements
Publish date: 15th September, 2026