Salesforce Experience Cloud

Formerly Salesforce Community Cloud

Well suited for companies that have partners or end users that like to self-service. Easy to publish content and knowledge articles for them to learn if they are new, and to post announcements and important updates on the homepage so they don't miss anything. It's hard to customize it to look like your main website unless you have resources that can write code. The templates have some flexibility in how you can lay things out, but you're really limited unless you go beyond the out of the box templates or have people on the team that can put together custom components for you.

Community Cloud is great for an employee Intranet where data needs to be segmented to all company users. It is also great for partners who need some access to your database for pipeline or visibility, but not a full CRM license. It can also be utilized for hosting forms and surveys where full access isn't needed, but syncing back to the system is required.

Salesforce Experience Cloud is well-suited for organizations that have clients who periodically or routinely need to access historical data or documents. The product also offers an exceptionally effective tool to engage with customers around support/service issues and the entire Case management functionality built into the Salesforce platform. The product might be less well-suited in environments where there is exceptionally high staff turnover within customer accounts, or where there is a substantial lack of very basic computer skills.

We can keep all content in one place. The idea to combine many Salesforce services into one is not bad, but sometimes this monstrosity gets in the way. Now we are looking toward WordPress, but earlier we created a website based on Salesforce. I liked the built-in templates, the intuitive constructor, and the speed of the builder.

It's a good product if you are going to leverage Salesforce for a lot of applications. The product is well suited to serve as a collaboration portal with internal or external customers. It's likely less appropriate for fully public-facing websites where the importance is purely on look and feel vs. substantive content or collaboration.