Each Salesforce cloud answers a specific problem: Sales Cloud for the pipeline, Service Cloud for customer requests, Field Service for field operations, Marketing Cloud for campaigns, Revenue Cloud for quotes, Data 360 for scattered data, Agentforce for repetitive tasks. Our rule: name one problem, prove the value, then combine clouds on the same platform.
"Salesforce is a CRM." That was true fifteen years ago. Today the name covers a family of products, called "clouds", that span sales, customer service, field work, marketing, quoting and billing, data, AI, customer portals and several industry-specific businesses. For a business leader, the appeal is running everything on a single platform. The risk is buying building blocks before naming the problem.
So we took the opposite approach to product catalogs. We start from your problems, show the cloud that addresses each one and what it does, and we also say when it is not the right choice. Every product description links to the official Salesforce page we reread to write this article. Names change fast at Salesforce (several products have been renamed recently): we flag both names when they coexist.
01"Our reps don't know where their deals stand": Sales Cloud
The symptom is familiar: a pipeline rebuilt in a spreadsheet the night before the review meeting, forgotten follow-ups, forecasts that rely on gut feeling. Sales Cloud, Salesforce's original CRM, was built for this. Salesforce presents it as the tool that gives every sales rep the context they need to move their deals forward.
- Leads - capture, track and prioritize inbound prospects to convert them better.
- Pipeline and forecasts - a shared view of open deals and more reliable sales forecasts, instead of manual consolidation.
- AI agents - Salesforce now positions Sales Cloud as the place where sales reps and AI agents work together, with agents taking on repetitive tasks.
When it is the right choice: as soon as several people sell and leadership needs a reliable read on upcoming revenue. When it is not: if your main challenge is after-sales support or field scheduling, Sales Cloud alone will not handle it; other clouds, covered below, are designed for that. Our Sales Cloud page details how we deploy it.
02"Our customers repeat their problem on every call": Service Cloud
A customer who writes by email, calls back the next day, then follows up on chat, with nobody seeing the history: that is the problem Service Cloud tackles. Salesforce describes centralized management of interactions, requests ("cases"), incidents, the knowledge base and assets, from first contact to resolution, across every channel.
- A single work queue - every request is tracked, assigned and followed up, whatever the channel it came in through.
- Knowledge base - approved answers are captured and reused by your agents.
- Agentforce in service - the same page presents a help agent connected to your knowledge base to answer customers and employees.
Service Cloud makes sense when the volume of requests requires organizing work into queues, with deadlines to meet and several channels to reconcile. With a few requests a week handled by a single person, a simple ticketing tool is often enough, and we would rather tell you before than after. See our Service Cloud page.
03"Our technicians lose hours to scheduling": Field Service
Schedules kept on a whiteboard, unoptimized travel, paper reports retyped several days later: that is daily life for many field organizations. Field Service (historically Field Service Lightning) is now presented by Salesforce as Field Service and Operations, and the online help calls it Agentforce Field Service and Operations.
- Scheduling and optimization - a scheduling engine that automates job assignment, cuts travel time and helps meet service commitments.
- Dispatch console - dispatchers see their teams by availability or by skill, and manage absences and crews in one place.
- Offline mobile app - on Android and iOS, the app is designed to work without a network and syncs updates as soon as the connection returns.
The scheduling engine really pays off with mobile technicians and skills and territories to respect. For a few appointments a week with no routing constraints, it is oversized. Our Field Service page tells you more.
04"Our campaigns go out in bulk, with no personalization": Marketing Cloud, two generations
A single newsletter for the whole database, segments built by hand, no view of what triggers a purchase: many marketing projects start from there. First, a clarification, because it avoids a lot of misunderstandings. Salesforce currently sells two distinct generations of Marketing Cloud.
- Marketing Cloud Engagement - the original platform, which Salesforce describes as a platform for email, SMS, push notifications and multichannel journey orchestration. This is where you find Journey Builder, Content Builder and Automation Studio.
- Marketing Cloud Next - the new generation, built natively on the Salesforce platform, with AI, Data 360 and Agentforce at its core. According to the official FAQ, Growth and Advanced are editions of Marketing Cloud Next. Marketing journeys are built there in Salesforce's standard automation tool, as the help topic "Flow Builder Elements for Marketing Flows" shows.
The same FAQ states that no end of life and no end of sale have been announced for Marketing Cloud Engagement, and that the "+" editions of Engagement give access to a Marketing Cloud Next edition alongside the existing setup. So nobody is forced to migrate tomorrow, but the choice between the two generations deserves to be made with full knowledge of the facts.
Our reading: if your customer data already lives in Salesforce and you want sales, service and marketing to share the same view, Marketing Cloud Next is a natural option. If you already run Engagement with well-oiled journeys, the question is not to rebuild everything but to find out what the new generation would really bring you. When neither is the right choice: a modest database and a monthly newsletter do not call for a platform of this scale. See our Marketing Cloud page.
05"Our quotes come out of Excel": Revenue Cloud (formerly CPQ)
One pricing spreadsheet per sales rep, discounts granted with no rules, pricing errors discovered at invoicing. This is quote-to-cash territory, from quote to cash collection. Salesforce addresses it with Revenue Cloud, which the official help also calls Revenue Cloud Advanced or Revenue Lifecycle Management. The product page describes its building blocks:
- Configuration - rules that ensure a complex product is offered in a valid combination.
- Pricing - a configurable pricing engine that can be called at several steps of the process.
- Quotes - generating, updating and sending quotes, with help from Agentforce.
- Contracts and orders - tracking the contract from the initial sale to amendments, and orchestrating orders from fulfillment through to invoicing.
- Billing - offered as Revenue Cloud Billing, for all types of charges and billing schedules.
A news item for those of you using the older Salesforce CPQ: Salesforce states that it no longer sells CPQ licenses to new customers, has announced no end-of-life date, and names Revenue Cloud Advanced as its successor. Existing customers can keep using it: a migration should be decided on its value, not in a rush.
When it is the right choice: a rich catalog, pricing or discount rules, subscriptions or contracts that change over time. When it is not: a handful of fixed-price products; standard Sales Cloud quotes often cover that need. Our Revenue Cloud page details our approach.
06"Our customer data is scattered across ten tools": Data 360 (formerly Data Cloud)
Website, billing tool, line-of-business application, legacy files: each system knows a piece of the customer, none knows the whole. Data 360, formerly called Data Cloud, is presented by Salesforce as the real-time data engine that powers its entire platform. It unifies fragmented data from every source, including external data lakes, websites and legacy systems.
In practice, Data 360 is rarely a standalone project: Marketing Cloud Next, for example, puts it at the heart of its offering, alongside AI and Agentforce. It makes sense if you have several sources to reconcile and a specific use for the unified data. If your useful data already fits in your CRM, start by making it reliable instead. See our Data 360 page.
07"Our teams spend their days on repetitive tasks": Agentforce
Qualifying a request, summarizing a file, answering a question already handled a hundred times: these tasks eat up valuable time. Agentforce is Salesforce's AI agent platform. Salesforce defines these agents as autonomous, proactive applications designed to carry out specialized tasks for employees and customers, within defined guardrails.
The difference from a simple conversational assistant lies in action: an agent does not just answer, it acts in the CRM according to the rules you set for it. That is also why an agent is only as good as the data and processes it relies on. When it is the right choice: a frequent, well-described task with clean data. When it is not: a process that is still fuzzy or unreliable data; AI then amplifies the mess instead of solving it. Our Agentforce page presents our approach.
08"Our customers and partners call us for information they could find on their own": Experience Cloud
Order tracking, request status, product documentation, partner profile: many calls could be avoided if the information were available as self-service. Experience Cloud lets you build branded sites connected to your CRM: a customer portal where people find the solution to a problem themselves, a partner space to share content and training and collaborate on deals, a help forum or a support site. Several sites can coexist in the same org, each with its own purpose. Salesforce's platform page sums up the use: sites, portals and apps securely connected to Salesforce data.
Experience Cloud serves an external audience that needs to view or update data already in Salesforce. For a brochure website with no link to your customer data, a web content management tool will do a better job.
09"Our business has specifics a generic CRM ignores": Media Cloud and the industry clouds
Some industries have a vocabulary, objects and processes that standard CRM does not know: an advertising insertion order, a subscriber, a meter, a patient record. For these, Salesforce offers industry solutions: its Industries page claims more than sixteen, with applications, processes and automations designed for each business (automotive, communications, consumer goods, energy and utilities, financial services, healthcare, manufacturing, media, public sector, retail, among others).
We know Media Cloud particularly well, the name still used on the product page, while Trailhead now refers to Agentforce Media. Its applications cover two businesses: selling advertising space (Ad Sales Management) and managing the subscriber lifecycle (Subscriber Lifecycle Management), which Trailhead breaks down into four stages: attract, acquire and onboard, engage, retain.
An industry cloud is worth the investment when its data model truly fits your business and saves you from rebuilding it. If you would only use a fraction of it, a well-adapted standard CRM will often be simpler to keep alive. See our Media Cloud page.
10"Our process doesn't fit any box": the platform, Flow and custom development
Three-level approval, automatic follow-up, a business calculation specific to your activity: not everything comes in an off-the-shelf product. The Salesforce Platform is the foundation that lets you automate and extend how you use Salesforce. The central tool is Flow: automations are built in Flow Builder, with several flow types, including guided screens for the user (screen flows) and automations triggered when a record is created or updated (record-triggered flows).
Our conviction: declarative first, code second. An automation built in Flow stays readable and maintainable by an admin team; custom development is justified when the need genuinely goes beyond what the standard tool can do. This is often where the technical debt of a Salesforce org is decided.
11"Information doesn't flow well between teams": Slack and Tableau
Two products round out the setup, without being "clouds" in the strict sense.
- Slack - Salesforce presents it as the space that brings together your teams, your data, your apps and your agents. Salesforce records, the people involved and agents show up there at the right moment, without switching tools.
- Tableau - Salesforce's analytics and business intelligence platform, to help everyone solve their problems with data.
Slack becomes useful when your teams already live in it and the back-and-forth with the CRM wastes time. Tableau, when native reports are no longer enough to combine several sources. If standard dashboards cover your needs, there is no point adding another building block.
12The recap: your problem, the cloud that addresses it
| Your problem | The relevant cloud | What it brings |
|---|---|---|
| Unreliable pipeline and forecasts | Sales Cloud | Shared leads, deals and forecasts |
| Customers who repeat their request | Service Cloud | Requests tracked across every channel, knowledge base |
| Manual field scheduling | Field Service (Field Service and Operations) | Optimized scheduling, dispatch, offline mobile |
| Campaigns with no personalization | Marketing Cloud Engagement or Next | Multichannel journeys, segmentation, personalization |
| Quotes in Excel, pricing errors | Revenue Cloud | Configuration, pricing, quotes, contracts, orders, billing |
| Scattered customer data | Data 360 (formerly Data Cloud) | Unification of data from every source |
| Repetitive, low-value tasks | Agentforce | AI agents that act within defined guardrails |
| Avoidable calls from customers or partners | Experience Cloud | Portals and sites connected to the CRM |
| Industry-specific business (media, energy…) | Media Cloud (Agentforce Media) and industry clouds | Data model and processes specific to the industry |
| Specific process | Platform and Flow | Custom automations and applications |
| Poor information flow, limited reporting | Slack, Tableau | Collaboration around data, business analytics |
13How to choose: start small, combine later
The temptation to sign for everything at once is strong. Our experience leads us to argue for the opposite.
- Name one problem, just one, to start - the one that costs the most today, in time, revenue or customer satisfaction. The first cloud follows from it.
- Prove the value before expanding - a first scope adopted by the teams is worth more than a full rollout nobody uses.
- Combine on the same platform - the customer seen by sales can be the same one seen by service and by marketing. Adding a cloud means enriching an existing view, not creating a new silo.
- Save data and AI for the right moment - Data 360 and Agentforce deliver their full value on stable processes and reliable data. Rolling them out too early means automating a mess.
Already on Salesforce and wondering whether you are getting the most out of it? Our Salesforce audit takes stock of your org and how you use it. Starting from scratch or looking to add a cloud? Our offers show how we support our clients, from scoping to team adoption. Either way, we start with the same question: which problem do you want to solve first?