Portfolio Management of Salesforce Products:
Sales, Service, Marketing, Commerce

The Portfolio Problem

Salesforce sells its products as a suite but prices and deploys them individually. The result is that most enterprise organisations accumulate Salesforce clouds in response to specific business requests — Sales Cloud because the sales team needed a CRM, Service Cloud because the contact centre needed case management, Marketing Cloud because the marketing team needed automation — without a portfolio view of how these clouds interact, where they share data, and whether the combined investment is justified by the combined value.

Portfolio management of Salesforce products asks three questions that individual cloud decisions do not: What is the right sequence of investment? Are the interdependencies between clouds being managed? And are we getting portfolio value — where the combined output exceeds the sum of individual cloud outputs — or just multiple independent deployments that happen to share a vendor?

Sequencing Matters: Foundation Before Extension

The most common portfolio failure is implementing multiple clouds simultaneously or in rapid succession before the foundational cloud (typically Sales Cloud) has reached meaningful adoption and data quality. Adding Marketing Cloud to a Sales Cloud org where only 40% of users are active and the pipeline data is unreliable produces a Marketing Cloud that sends messages to poorly segmented audiences based on dirty data. The second cloud amplifies the problems of the first.

The right sequence: implement the foundational cloud to high adoption and data quality first. Then extend with the next cloud that logically builds on the foundation. Sales → Service builds on the shared customer record. Service → Marketing builds on the combined customer history. Marketing → Commerce builds on campaign engagement data. Each step in the sequence is only as valuable as the data quality of the preceding step.

Cloud Interdependencies and Integration Complexity

Each Salesforce cloud carries its own data model, its own integration requirements, and its own governance surface. Adding a new cloud to an existing portfolio does not just add the cloud's own complexity — it adds the integration complexity of connecting the new cloud to all existing clouds and enterprise systems.

Sales + Service: Shared Accounts, Contacts, and customer history. The integration is relatively lightweight — both live on the core Salesforce platform and share data natively. The complexity is primarily in process design: who owns the Account record, how does the 360 view work, who sees what.

Marketing Cloud: A separate technical platform that connects to the core Salesforce org via Marketing Cloud Connect. This introduces a synchronisation architecture, data studio configurations, and a separate admin skill set. The integration is not trivial and requires ongoing maintenance.

Commerce Cloud: Salesforce's B2B and B2C commerce platforms have their own technical architectures and require significant integration work to connect product catalogs, order management, and customer data to the core CRM.

Investment Prioritisation Across Competing Clouds

When multiple business units request different Salesforce clouds simultaneously — and budgets are constrained — a structured prioritisation framework is needed. Four factors determine priority:

Foundation dependency: Does the requested cloud require capabilities that don't yet exist in the current portfolio? If the Service Cloud request requires a clean Account and Contact data model that doesn't yet exist in Sales Cloud, the Sales Cloud data quality work is a prerequisite — fund that first.

Business value per pound invested: Quantify the expected business value of each cloud investment (use the ROI framework from ENT-003) and compare on a value-per-investment basis. The cloud that delivers the most measurable business value per £ of investment should typically take priority.

Strategic alignment: Which cloud investment best supports the organisation's 3-year business strategy? A company growing through customer retention invests in Service Cloud. A company growing through new customer acquisition invests in Marketing Cloud. Cloud investments that align with strategic priorities deliver more value because the business will invest in adoption.

Internal capability readiness: Can the CoE support the additional cloud? Adding Marketing Cloud to a CoE that is already stretched by Sales Cloud and Service Cloud support produces poor outcomes from both the new cloud and the existing ones.

Portfolio Rationalisation

Portfolio management is not only about adding clouds — it is also about retiring them when they are not delivering value. Salesforce organisations that never rationalise their portfolio accumulate underutilised clouds that drain CoE capacity and licensing budget.

The rationalisation decision framework: if a cloud's adoption is below 40% 18 months after go-live, conduct a root cause analysis. If the cause is remediable (leadership engagement, training, process gap), invest in remediation with a 6-month target and clear success criteria. If the cause is structural (the cloud genuinely does not fit the use case, the business process no longer exists, the sponsoring leader has left), retire the cloud: deprovision users, export data, and reallocate the licence cost to a higher-value investment.