Before signing a Salesforce contract, the same question always comes up: Sales Cloud or Service Cloud? Both are part of the same platform, both carry the Salesforce name, and in a sales presentation both look like they do roughly the same thing.
They do not. Confusing the two is one of the main sources of disappointment after go live, and it usually takes hold well before the contract is signed.
The dividing line is clear: Sales Cloud supports customer acquisition, from prospecting to signature. Service Cloud supports the post-sale relationship, from the first incident to renewal.
This is the reality Salesforce sales teams have little interest in raising up front. As soon as an organisation has both a sales team and a customer service team, it needs both products. Signing for Sales Cloud alone and telling yourself "we will look at Service Cloud later" creates implementation debt that is expensive to pay back.
Adding Service Cloud after the fact is technically possible, but it means reworking the data model, the profiles and the automations. What would have cost X in the initial implementation often costs 2X to 3X when retrofitted.
A Sales Cloud license can technically include Case objects, and a Service Cloud license can include Opportunity objects. What changes is access to the advanced native features, Omni-Channel and Einstein for Service, which are only available with Service Cloud.
The question to ask your Salesforce account executive before signing: "Which features are included in this license, and which ones require an add-on?"
Implementing Sales Cloud first makes sense for a company starting out. But if Service Cloud is already on the roadmap, the data model has to be designed for both from day one. The Account-Contact-Case model is not the Account-Contact-Opportunity model, and making them coexist cleanly takes a level of foresight many projects never apply.
A user on a Sales Cloud license has no access to Service Cloud features. In mixed organisations (sales and customer service on the same Salesforce), licenses have to be planned per user profile from the start.
The most useful question in a scoping meeting: "Who will use Salesforce day to day, and what for?" If the answer includes both sales reps and support teams, order both licenses from the start, even if Service Cloud is not implemented in the first phase.
In organisations under 50 people, the line between sales and service is often blurred. Sales Cloud with manually configured Case objects can be enough at first. Once ticket volume passes a few dozen a week, running without Service Cloud becomes painful.
The rule I apply: more than 50 tickets a week and you need Service Cloud. Below that, a properly configured Sales Cloud can hold up.
The scoping call is free and comes with no commitment. 30 minutes to define the scope and confirm feasibility.
Contact →