Heading 1
Heading 2
Heading 3
Heading 4
Heading 5
Heading 6
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
Block quote
Ordered list
- Item 1
- Item 2
- Item 3
Unordered list
- Item A
- Item B
- Item C
Bold text
Emphasis
Superscript
Subscript
The decision on the table is how to size and structure the contract. Licences are usually committed for the full term, so seats bought ahead of the rollout are money you cannot recover if the programme slows down. Buy too little and you negotiate the extra seats from a weaker position mid-contract. Either way, the numbers get set before anyone has used the system.
The drivers that set the total
Five quantities decide most of the bill. The number of users multiplies with the licence type each one needs and the edition you choose. Add-ons sit on top of that per-user base. Usage-based products, where you pay for data processed, contacts reached or actions run, add a line that moves with activity.
These drivers behave differently over time. User numbers and usage grow with success, which is the point, but also means your cost in year three looks nothing like year one. Edition and add-ons are set at signature and are hard to reduce. Implementation is a one-off line, and ownership afterwards is permanent. The wider case for what Salesforce CRM delivers is what these costs are paying for, so keep both in the same business case.
Licence type per role is the biggest lever
Not every user needs a full CRM licence. A sales representative who manages opportunities needs Sales Cloud. A warehouse employee who only updates one custom object may need a platform licence, which covers custom apps with limited access to standard CRM functions. Customers and partners who log in to a portal need an external licence, which Salesforce used to sell as Community licences (Experience Cloud).
When we configure Sales Cloud and Service Cloud, we map every role to the lightest licence that still does the job before anyone signs. That exercise often shows a group of users who were never going to open the system. Leaving them out is the cheapest saving in the whole project. For the sales side of that mapping, our guide to Salesforce Sales Cloud covers what sales teams actually use.
Editions, add-ons and usage-based products
The edition decides what is included in each licence. Lower editions can restrict features such as integration access, automation or the number of test environments, so check the edition against the integrations you plan before comparing prices. An edition that looks cheaper can cost more once you buy back what it leaves out.
Add-ons follow their own logic. Pardot (Marketing Cloud Account Engagement) is usually bought as its own product next to Sales Cloud. Generative AI through Agentforce and the data platform Data Cloud (Data 360) can include usage-based elements, so the cost depends on how much you run through them. B2C Commerce, part of Commerce Cloud (Agentforce Commerce), has typically been priced on the revenue that runs through the storefront. Marketing products follow yet another model, set out in our piece on what Salesforce Marketing Cloud costs.
Measure cost against what it buys
Cost per licence is the flattering measure. The honest one is cost per active user, counting only people who use the system every week. If a third of your seats sit idle, your real price per user is higher than the contract says.
Then translate that into terms your business already reports. For service, that is cost per case handled and average handling time. For sales, it is time spent on admin per sales representative and forecast accuracy. For commerce, it is cost per order. Licences pay off when those numbers move.
