# Salesforce Editions and Licences: Choose the Right Access at the Right Cost

Salesforce editions define the package your organization buys; user licences and permission set licences determine what each person or integration can use. Sales plans list at $25 for Starter, $100 for Pro, $195 for Core, $395 for Advanced and $550 for Max per user per month in USD. As worked examples, five Starter users cost $125 a month, while 40 Core users cost $7,800 a month before extras. [Salesforce sales prices](https://www.salesforce.com/sales/pricing/).

Canonical URL: https://www.martechdevs.com/blog/salesforce-editions

By [Jafrin Akter Alo](https://www.martechdevs.com/authors/jafrin-akter-alo)

Data Engineer and Co-founder at [Martechdevs](https://www.martechdevs.com) and [Growth and Analytics Partners](https://www.growthandanalytics.com)

[LinkedIn](https://linkedin.com/in/jafrinalo)

Last updated: 2026-11-11

Next step: [Build the full Salesforce budget](https://www.martechdevs.com/blog/salesforce-pricing). Include services, add-ons and operation beyond the licence.

## What are you billed for in a Salesforce edition?

Salesforce charges for the subscriptions and quantities on your order, with separate access entitlements underneath. An organization has one edition, each user has one user licence, and a user can hold additional permission set licences. Permissions then determine which licensed capabilities that user may actually exercise. [How Salesforce licences work](https://trailhead.salesforce.com/content/learn/modules/salesforce-licensing/understand-how-licenses-work).

Start with these distinctions before comparing a quote:

| Layer | What it decides | Example buying question |
| --- | --- | --- |
| Organization edition | Available package and platform capabilities | Does the proposed edition support the required sales process? |
| User licence | The user's underlying access entitlement | Does this operator need sales objects or only a custom application? |
| Permission set licence | Additional licensed functionality for that user | Is the extra capability purchased and assigned? |
| Profile and permission sets | Which permitted actions the user receives | Can the operator edit this field and run this action? |

These layers come from [Salesforce's licensing model](https://trailhead.salesforce.com/content/learn/modules/salesforce-licensing/understand-how-licenses-work). Buying an entitlement and granting access are separate steps. Record both in your implementation plan.

Our [CRM and lifecycle implementation work](https://www.martechdevs.com/crm-lifecycle) starts with the tasks, records and integrations each role needs. For the complete budget beyond licences, use the [Salesforce pricing guide](https://www.martechdevs.com/blog/salesforce-pricing).

## What will Salesforce licences cost a company like yours?

Count the people who need each licensed workflow, then price the applicable package. Company headcount alone cannot establish the bill: a 100-person company might have 25 CRM operators, while another needs 80. The worked examples below use explicit seat assumptions so you can replace them with your own.

USD list-price illustrations, before tax, implementation, add-ons or consumption. Starter supports monthly or annual billing; the other paid Sales editions below are billed annually. [Billing basis](https://www.salesforce.com/sales/pricing/).

| Company situation | Assumed subscription | Monthly equivalent | Annual equivalent |
| --- | --- | ---: | ---: |
| Five-person startup | 5 Starter users × $25 | $125 | $1,500 |
| 20-person SaaS, eight CRM users | 8 Pro users × $100 | $800 | $9,600 |
| 80-person B2B SaaS | 25 Core users × $195 | $4,875 | $58,500 |
| 300-person business | 40 Core users × $195 | $7,800 | $93,600 |
| Enterprise with 1,000 sales users | 1,000 Advanced users × $395 | $395,000 | $4,740,000 |

These are arithmetic examples, not recommendations to buy by company size. A five-person company with demanding integration requirements might need a different edition; a larger company can have a narrow licensed population.

For the 300-person example, adding ten Core subscriptions raises the monthly equivalent by **$1,950**. Moving the original 40-user population from Core to Advanced changes its edition subtotal by **40 × ($395 − $195) = $8,000 a month**. That is the number the extra capabilities need to justify in your operating plan.

## What makes a Salesforce licence bill jump?

The main multipliers are more paid users, a higher edition, separately licensed products and purchased usage capacity. Measure each change independently before accepting a bundle. A proposal can have a lower quoted rate per user and a larger annual commitment if it includes more users, products or years.

An important integration boundary sits at Pro: Salesforce lists its Web Services API add-on at **$25 per user per month**. Confirm the chargeable population on the order. Under an eight-user assumption, that adds $200 monthly equivalent to the $800 Pro subtotal. [API price row](https://www.salesforce.com/sales/pricing/).

Other questions that expose an incomplete quote:

- Does the support package already come with the edition? The public page includes Premier Success with Core, Advanced and Max. [Support inclusion](https://www.salesforce.com/sales/pricing/).
- Which included products will the team actually deploy, and which replace an existing renewal?
- Are integration identities counted separately from interactive users?
- Is AI capacity pooled at organization level or supplied per user, and what happens after its allowance?
- Are storage, sandbox capacity and any marketplace application separately purchased?

Ask for a subtotal for every line. A bundled product has financial value when its licensed scope replaces something you would otherwise buy and your team can use it.

## Does adding people or adding usage increase the cost?

The base Sales subscription follows purchased users, while consumption services and some add-ons have their own units. Frequent use does not turn a fixed user subscription into a pay-per-login product. Equally, an unused paid licence can remain a contractual cost until the relevant term permits a reduction. [Subscription fee rules](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/salesforce_MSA.pdf).

Separate these populations in your inventory:

| Population | Access decision | Evidence to collect |
| --- | --- | --- |
| Sellers and sales managers | CRM functionality required by the role | Lead, opportunity, forecasting and approval tasks |
| Internal custom-app operators | Whether Platform licensing covers all dependencies | Every object, report and automated action they touch |
| External partners or customers | Appropriate external access product | Login pattern and record-sharing requirements |
| System integrations | Dedicated API-only identity where supported | Connector authentication and object permissions |

Salesforce's [Platform feature comparison](https://help.salesforce.com/s/articleView?id=users_license_types_communities_lightning_platform_details.htm&language=en_US&type=0) includes accounts and contacts but leaves leads, opportunities and quotes outside the listed Platform entitlements. A Platform user should therefore be evaluated against the entire workflow, including related records. A lower price cannot solve a missing object entitlement.

## Which Salesforce edition fits which situation?

Choose the least expensive configuration that passes your real workflow and access tests. Free and Starter suit a simpler initial process; Pro adds customization and automation; the higher editions need a specific operational reason. Keep the decision anchored to required functionality, integration compatibility and cost rather than employee count.

| Situation | First candidate | What would justify a different choice? |
| --- | --- | --- |
| Two people organizing basic CRM work | Free Suite | More users or required capabilities beyond its limits |
| Small team with a straightforward process | Starter | A demonstrated integration or customization gap |
| Team requiring greater customization | Pro, with required add-ons itemized | Failed workflow tests or a better complete Core quote |
| Integrated sales organization | Core | Explicit security, resilience or broader bundle requirements |
| Broad advanced sales and AI rollout | Advanced or Max | Confirm adoption, entitlements and usage before committing |

Free Suite includes two users and requires a login at least every 60 days to remain active. Its marketing allowance is 100 emails monthly. [Free Suite limits](https://www.salesforce.com/crm/free-crm/).

Core, Advanced and Max are the newer packages corresponding to the legacy Enterprise, Unlimited and Agentforce 1 buying positions. Salesforce states that existing legacy-edition pricing remains unchanged; an old contract should be checked on its own terms. The announcement describes the bundle changes and regional/contract qualifications. [Edition changes](https://www.salesforce.com/news/stories/salesforce-simplifies-editions-2026/).

### Which licence should an integration use?

A system-to-system connection should have its own supported identity and minimum required permissions. Salesforce's integration guidance uses the Salesforce Integration user licence, the Minimum Access API Only Integrations profile and the Salesforce API Integration permission set licence. The profile restricts the identity to API use; object and field access still need assignment. [Integration-user setup](https://developer.salesforce.com/blogs/2024/02/invoke-rest-apis-with-the-salesforce-integration-user-and-oauth-client-credentials).

The guidance lists five included integration licences for legacy Enterprise, Unlimited and Performance orgs. Check **Setup → Company Information** and the current order for the actual allocation in your org. Do not assume an old edition entitlement automatically describes every new package. Test the connector's supported authentication flow before switching a working connection.

## How do you keep licence spending under control?

Maintain a role-to-task inventory and compare it with purchased and assigned licences before renewal. Test a cheaper candidate configuration with the actual records, reports and integrations required by that role. Reducing privileges is a security improvement; reducing a paid commitment requires a separate commercial action under the contract.

1. Export purchased, assigned and available licence counts from Company Information.
2. List the job each user or integration performs, including infrequent month-end work.
3. Map each job to required objects, actions, permission set licences and connected applications.
4. Test one representative user with the proposed access. Include failure, reassignment and exception handling.
5. Record the smallest configuration that passes and the corresponding renewal quantity.
6. Obtain the proposed quantities and prices in writing before the notice deadline.

Use this decision path for each role. An access failure returns to the licence and permission review rather than being bypassed with excessive permissions.

![Classify each Salesforce role as an API integration, sales user or other operator, test the matching licence and permissions, then confirm the order only when access and contract checks pass.](https://www.martechdevs.com/assets/blog/salesforce-editions.svg)

Diagram connections:

- Map required tasks and records to API-only integration?. 
- API-only integration? to Check integration licence and authentication: Yes. 
- API-only integration? to Needs sales objects?: No. 
- Needs sales objects? to Select CRM licence and edition: Yes. 
- Needs sales objects? to Check Platform or external access fit: No. 
- Check integration licence and authentication to Test required actions and denied actions. 
- Select CRM licence and edition to Test required actions and denied actions. 
- Check Platform or external access fit to Test required actions and denied actions. 
- Test required actions and denied actions to Tests and contract fit?. 
- Tests and contract fit? to Confirm quantity and renewal terms: Yes. 
- Tests and contract fit? to Map required tasks and records: No

## What should you watch for in the Salesforce contract?

Review the purchased quantity, renewal notice, payment schedule and scope of each product before signing. Salesforce's standard agreement generally bases fees on subscriptions purchased, restricts reductions during the term and renews subscriptions automatically unless notice is given. Your order can change the applicable terms, so compare its wording directly. [Main Services Agreement](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/salesforce_MSA.pdf).

The agreement's default renewal notice is at least 30 days. Promotional or one-time pricing may renew at the then-current list price unless the order says otherwise; reducing volume or term at renewal can also trigger repricing. Put those conditions in the budget instead of assuming year two repeats year one.

For example, the eight-user Pro illustration is **$9,600 per year at the stated list rate**, before other charges. If the headcount and rate stay unchanged, its second-year edition subtotal is also $9,600. A startup offer changes that assumption only when its written terms say so.

[Salesforce Launchpad](https://www.salesforce.com/launchpad/) offers free and discounted products for eligible venture-backed startups, but its public page does not promise one universal percentage. Request the applicable product, duration, renewal price and eligibility confirmation.

## How do you read the Salesforce rate card correctly?

Read the product name, billing unit and entitlement notes together. The same word can appear in different product names: Starter Suite is a CRM package, while Platform Starter is a custom-application user offering. A price comparison is useful only after the licence covers the intended work and the organization configuration supports it.

The [current Platform pricing page](https://www.salesforce.com/platform/enterprise-app-development/pricing/) lists Platform Starter at $25 and Platform Plus at $100 per user monthly, billed annually, with 10 and 110 custom-object access limits respectively. Its Platform Login & Dev Credits offer is $1,000 for 10,000 credits, equivalent to 200 logins at 50 credits each. For an occasional custom-app operator, compare the resulting $5 per billable login with a monthly seat after confirming the login-counting rules and contract term.

The [Platform rate-card PDF](https://c1.sfdcstatic.com/content/dam/web/en_us/www/documents/pricing/salesforce-platform-pricing-editions.pdf) describes organization edition separately from user subscription type. Its tables retain legacy edition names; obtain a current compatible quote for a new Core, Advanced or Max purchase.

Three annotations belong beside every quoted line:

- **Per user:** specify which population is being counted.
- **Included:** specify the quantity, period and access rights, including any separate activation.
- **Available for purchase:** add the quoted amount to the comparison before ranking options.

Never use a Platform seat to assume access to leads or opportunities that the [Platform entitlement table](https://help.salesforce.com/s/articleView?id=users_license_types_communities_lightning_platform_details.htm&language=en_US&type=0) does not grant. Ask the seller to confirm the proposed mix and retain that confirmation with the role inventory.

## What should you confirm before buying or renewing?

Finalize a tested access map, a complete subscription subtotal and the next renewal's commercial assumptions. The useful output is a list of roles with the exact licence each needs, plus the features and integrations that passed testing. That gives finance and the administrator the same basis for approving the order.

## Checklist

- [ ] Every purchased licence has an owner or a documented near-term requirement.
- [ ] Each role's required objects, actions and reports passed the proposed access test.
- [ ] Integration identities and API entitlements are confirmed for the exact edition.
- [ ] Paid add-ons, usage allowances and support inclusions are itemized.
- [ ] Year-two quantities, renewal assumptions and notice deadlines are recorded.

Use the [CRM audit skill](https://www.martechdevs.com/skills/crm-audit) to organize the access and integration inventory. Then model your quantities in the [Salesforce cost calculator](https://www.martechdevs.com/tools/salesforce-cost-calculator), compare the complete [Salesforce pricing budget](https://www.martechdevs.com/blog/salesforce-pricing), or assess the alternative process in [HubSpot vs Salesforce](https://www.martechdevs.com/blog/hubspot-vs-salesforce-startups). Our [Salesforce implementation service](https://www.martechdevs.com/salesforce-implementation) can turn the chosen licence scope into a working CRM.

## Frequently asked questions

### Can one Salesforce organization mix Core and Advanced for different sellers?

Salesforce's licensing model describes one edition per organization, with different supported user licence types and add-ons underneath it. Do not budget a Core/Advanced split inside one org without a written compatible offer. Start with the org edition, then map the permitted licence mix to the tasks each group needs. [Licensing model](https://trailhead.salesforce.com/content/learn/modules/salesforce-licensing/understand-how-licenses-work).

### Can a permission set unlock an object the user licence excludes?

An ordinary permission set grants access within the user's licensed capabilities. Additional functionality can require an appropriate permission set licence or a different user licence as well as the permission assignment. Check entitlement and assignment separately when an access test fails; granting broader administrative permissions is an unsafe substitute for fixing the underlying licence fit. [Salesforce licensing](https://trailhead.salesforce.com/content/learn/modules/salesforce-licensing/understand-how-licenses-work).

### Can Salesforce Platform licences replace every full CRM licence?

Platform licences suit supported custom-app and internal workflows, with the exact permitted objects and features determining fit. Salesforce's comparison leaves leads, opportunities, orders and quotes outside the listed Platform entitlements. Trace related records, reports and automation before changing a role's licence; the custom application's main screen alone does not establish compatibility. [Platform features](https://help.salesforce.com/s/articleView?id=users_license_types_communities_lightning_platform_details.htm&language=en_US&type=0).

### Does deactivating a Salesforce user immediately reduce the invoice?

Deactivation changes access, while the purchased subscription quantity follows the contract. Salesforce's standard agreement generally prevents quantity reductions during the term unless the order provides otherwise. Record the freed licence for an approved reassignment or renewal reduction, and obtain confirmation of the commercial change instead of assuming the next invoice will fall. [Subscription terms](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/salesforce_MSA.pdf).

### Is a free Developer org a production CRM subscription?

A Developer org is a development environment, while Free Suite is Salesforce's separate free CRM offer with two user licences. Evaluate the actual production service, limits and support model you intend to use. For a small operational team, begin with Free Suite's documented scope and move to a paid package when the required workflow outgrows it. [Developer-org definition](https://trailhead.salesforce.com/content/learn/modules/salesforce-licensing/understand-how-licenses-work), [Free Suite](https://www.salesforce.com/crm/free-crm/).

## Sources

1. [Salesforce Sales pricing](https://www.salesforce.com/sales/pricing/)

2. [Salesforce licensing model](https://trailhead.salesforce.com/content/learn/modules/salesforce-licensing/understand-how-licenses-work)

3. [Salesforce Platform licence feature comparison](https://help.salesforce.com/s/articleView?id=users_license_types_communities_lightning_platform_details.htm&language=en_US&type=0)

4. [Salesforce integration user and OAuth client credentials](https://developer.salesforce.com/blogs/2024/02/invoke-rest-apis-with-the-salesforce-integration-user-and-oauth-client-credentials)

5. [Salesforce Main Services Agreement](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/salesforce_MSA.pdf)

6. [Salesforce Platform pricing](https://www.salesforce.com/platform/enterprise-app-development/pricing/)

7. [Salesforce Platform rate card](https://c1.sfdcstatic.com/content/dam/web/en_us/www/documents/pricing/salesforce-platform-pricing-editions.pdf)

8. [Salesforce Free CRM](https://www.salesforce.com/crm/free-crm/)

9. [Salesforce Launchpad](https://www.salesforce.com/launchpad/)

10. [Salesforce Core, Advanced and Max announcement](https://www.salesforce.com/news/stories/salesforce-simplifies-editions-2026/)
