What is Salesforce? - Key Products, Cloud Services, Benefits

Salesforce is a leading cloud platform used by global organizations to enhance customer relationship management (CRM).¹ It started in 1999 as one of the first CRMs delivered over the internet rather than installed on a company's own servers. Today, it has evolved into a prominent Platform as a Service (PaaS) solution, supporting businesses in managing customer relationships, operations, and data. More recently, the growing AI technology has further enhanced Salesforce’s automation capabilities and intelligence. The platform now scores leads, summarizes cases, and runs agents that answer customers, follow up leads, and update records on their own.

This article provides a detailed overview of Salesforce, focusing on its purpose, adoption by revenue teams, ownership within organizations, comparison with other CRMs, common implementation challenges, key components, and best practices for maintaining a healthy Salesforce org.

What is Salesforce?

Salesforce is a popular CRM platform that runs in the cloud and holds a company's customer data in one place, right from the first lead to the last service case. It is commonly known as Salesforce CRM.

It is more than just a CRM, though. Underneath Salesforce’s comprehensive range of products such as sales, services, and marketing, sits one platform that holds the data, the automations, and the security settings. The same platform lets an admin build a custom app without buying a separate system.

That’s why one can say that Salesforce is a CRM on the surface and a cloud platform underneath. Companies can start with one cloud and add the next one later without moving their data.

Salesforce History

Salesforce started in 1999 as one of the first CRMs delivered over the internet rather than installed on a company's own servers.² The idea gained huge popularity over the following decade, and the product grew from a sales tool into a family of clouds. Soon in 2005, it opened the AppExchange, a marketplace for apps built on the platform. In 2024, it introduced Agentforce, its layer of AI agents, and in October 2025, it placed the whole product line under the Agentforce 360 name. The individual clouds have been renamed after it since.³

Below are the main parts of Salesforce as it is sold today:

• Agentforce Sales (formerly Sales Cloud) for leads, deals and forecasts
• Agentforce Service (formerly Service Cloud) for cases, knowledge and self-service
• Agentforce Marketing (formerly Marketing Cloud), with Marketing Cloud Account Engagement (Pardot) for B2B marketing automation
• Experience Cloud for customer and partner portals
• Data 360 (formerly Data Cloud), the data layer that joins records from other systems into one customer profile
• Einstein, the AI features built into the clouds
• Agentforce, the AI agents that work across them
• The Salesforce Platform, with Flow for automation and Apex for code
• MuleSoft for integration and the AppExchange for ready-made apps

Please note that Salesforce renamed most of its clouds under the Agentforce brand in recent years. Most of the products underneath are the same, and the help documentation still shows the older names in many places, so an org that says Sales Cloud on the screen is not out of date. We cover each of these parts in the upcoming sections.

Salesforce sells the licenses, but the setup is usually done by a consulting partner, and Salesforce lists such firms under its partner program. The partner status tells you that the firm has delivered Salesforce work before; it does not tell you whether the firm also earns from the licenses it recommends. CRM-only consultancies like Vegacompass hold the Salesforce Consulting Partner status, advise on five CRM platforms without reselling any of them, and the Salesforce work we have delivered since 2014 covers audits, implementations, integrations, and migrations.

Benefits of Salesforce CRM

Every revenue team keeps a record of its customers somewhere, whether it is a ten-person startup or a bank with a thousand agents. In most companies, that record is already spread across a few places:

• Deal spreadsheet
• Newsletter tool
• Complaints inbox
• Billing software
• Salesperson's memory

One thing most important to realise here is that each of them is right about its own piece and wrong about the whole. The same customer has two names and three email addresses. The deal that closed last month is still open in the spreadsheet, and the complaint that came in on Monday is invisible to the salesperson calling on Tuesday. As such, the sales head exports the pipeline to Excel the night before the board meeting and fixes the numbers by hand, and nobody trusts the forecast, including the person who made it.

You may be wondering: a CRM adds a license, a setup project, and a new habit for every rep. So, a fair question arises: what does the company get for it?

The answer is one record that every team reads and writes, and everything else follows from it. Below are the main benefits of Salesforce CRM:

• One customer record for every team: The account, its contacts, its deals and its service cases sit on one record. As such, the salesperson sees Monday's complaint before Tuesday's call, and the service agent sees the renewal that is due next month.
• A pipeline that matches the sales process: The stages and the required fields follow the team's own selling steps, and the forecast is calculated from the records instead of data collected on a Friday call. The board number and the CRM number become the same number.
• Automation of the routine work: Lead assignment, follow-up reminders, and case routing run through Flow without a developer. That's why a rep's day has fewer copy-paste jobs in it, and a case does not wait in a queue because someone forgot to forward it.
• Reports and dashboards from live data: Every report reads the same records the reps update, so the pipeline review, the service backlog, and campaign results are ready without an export. On the other hand, a report is only as good as the fields behind it, which is a point we return to in the quick tips.
• Configuration before code: Objects, fields, and automations are changed through settings, and an admin can do most of it. As such, a company can start with one cloud and one team and grow the org as the business changes, rather than buying a new system every few years.
• A large ecosystem: The AppExchange carries thousands of ready-made apps, and the pool of Salesforce admins, developers, and consulting partners is also large. Hiring for Salesforce is easier than hiring for a niche CRM, and most common integrations already exist as connectors.^3,4
• Three releases a year, with no upgrade project: New features arrive in the spring, summer, and winter releases, applied by Salesforce, so the company is never running a five-year-old version. One thing to note is that a release can also change something an admin built, which is why it is always better to cross-check them.
• AI on top of the same record: Einstein adds lead scoring and summaries inside the clouds, and Agentforce agents can act on a case or a lead on their own within the limits set by admins.

Most companies that get the most from Salesforce treat it as the system the revenue process runs on, and not as a tool for the sales team alone. Please note that none of the benefits above arrive with the license. They arrive when the process is written down, the data is clean, and someone owns the org, which is why we have spent as much time on ownership and implementation as on the features in this article.

How does Salesforce work? (key features of Salesforce CRM)

A company's copy of Salesforce is called an org. It is a private space on Salesforce's servers with its own users, its own data, and its own settings, and no other company can see into it. Everything the company does in Salesforce happens inside that org, whether it runs one cloud or five.

Salesforce Objects

Inside the org, the data lives in objects. An object is nothing but a table with a purpose, such as Account, Contact, Lead, Opportunity, or Case. Each object has fields, and each row in it is a record. The records link to each other, so a contact belongs to an account, an opportunity belongs to an account, and a case belongs to a contact. Salesforce ships the standard objects, and an admin can add custom objects for anything the business tracks that the standard ones do not cover, such as a policy, a shipment, or a property.

The clouds are built on top of these objects. Simply put, Agentforce Sales is the set of objects, screens, and automations for selling, Agentforce Service is the set for customer service, and both read the same account record. That is what makes Salesforce a platform rather than a collection of separate tools.

Key Benefits of Salesforce CRM

• Records and Relationships: One record per customer, linked to its contacts, deals, orders, and cases, so any team can start from the account and find the rest.
• Automation: Flow lets an admin build the rules that run on their own, such as assigning a new lead, sending a reminder before a renewal, or routing a case to the right queue.
• Reports and Dashboards: Reports are built from the live records through a point-and-click builder, and dashboards put them on one screen for the sales head, the service manager, or the board.
• Security and Access: Profiles, roles, permission sets, and sharing rules decide who can see and edit which records and fields. For instance, a rep sees their own accounts, a manager sees the team's, and the finance user sees the invoice fields and nothing else.
• The Mobile App: The same records and the same permissions on a phone, so a field rep updates the deal after the meeting instead of after the week.
• Sandboxes and Releases: A sandbox is a copy of the org for building and testing, so changes are tried before they reach the users. Salesforce applies its three yearly releases to every org, as discussed previously.⁵
• The AppExchange: A marketplace of apps, components and connectors built on the platform, installed into the org rather than bought as a separate system.
• Artificial Intelligence: Einstein for the predictions and summaries inside the clouds, and Agentforce for agents that act on records within set limits. We cover both in a dedicated section below.
• Customization and Development: Most of the org is changed through settings, and code is available where the settings run out. We discuss it next.
• Integration: Salesforce connects to the ERP, the marketing tools, and the support desk through connectors, middleware, or its own APIs. We discuss it after that.

Salesforce customization and development

There are two ways to customize Salesforce: configuration and development.

Configuration

It means changing the org through its own settings:

• Adding a field
• Editing a page layout
• Writing a validation rule or building a Flow.

Development

It means writing code:

• Apex for the business logic that settings cannot express
• Lightning Web Components for screens that the standard pages cannot show

An admin does the first, and a developer does the second.

Most of what a company needs is configuration. The stages of a deal, the fields on a case, the approval that fires above a discount, the email that goes out when a lead arrives, all of it is built through settings. As such, the sensible order is to configure first and code only where a setting cannot do the job.

For example, a price calculated from three objects at once, or a step that has to call another system and wait for the answer.

As such, the code deserves a second look before it is written. A Flow is visible to the next admin and changes along with the settings. An Apex class is invisible to anyone who cannot read it, needs a developer for every change, and has to be tested against every release. Please note that most orgs older than five years carry code that nobody remembers the reason for, usually written for a manager who has since left, and such code is where the technical debt of an org usually sits.

And that’s why the difference is simple: configuration is owned by the admin, whereas code is owned by whoever wrote it.

Salesforce integration

Salesforce is seldom the only system a company runs. The orders and the invoices sit in the ERP, the campaigns in the marketing tool, the tickets in a support desk, and the website in its own stack. Integration is the work of connecting them to the org, so that a record entered in one place appears in the others without anyone typing it twice.

In general, there are three ways to connect a system to Salesforce:

• Native connectors: Ready-made links that Salesforce or the other vendor ships, often installed from the AppExchange. Quick to set up, and limited to what the vendor allows.
• Middleware: A separate tool that sits between the systems and moves the data on a schedule or in real time. MuleSoft, which Salesforce owns, is the usual choice when several systems feed one org.
• Point-to-Point Builds: Custom code on one or both sides, talking through the Salesforce APIs. The most flexible option, and the one that needs the most upkeep.

Which one fits depends on how many systems there are, how many records move, and how fresh the data has to be. A two-system company with a nightly sync needs no middleware, whereas a company with an ERP, a support desk, and a warehouse feeding one org usually does.

One thing to note is that an integration fails quietly. The sync stops on a Tuesday because someone renamed a field, nobody sees an error, and the reports drift apart for a month before anyone notices that the invoice totals no longer match the deals. That's why every integration needs an agreed direction for each field, an owner, and a log that someone actually reads.

Vegacompass has decades of MuleSoft expertise, and the integrations we build come with the field mapping and the sync schedule written down, so the client's own admin does not depend on us to keep them running, whether they go through a connector, MuleSoft, or a point-to-point build. To learn more about this service, please read our CRM Integration page.

Key Salesforce products and clouds

Salesforce has a set of products that altogether make a huge platform for CRM. Each product is built for one part of the customer relationship, and a company buys only the ones it needs. Below, we have discussed the five that most companies start with. As discussed earlier, most of them were renamed under the Agentforce brand in 2025 and 2026, so we use the current names with the older ones in parentheses. Einstein and Agentforce, the AI parts, are discussed in the next section.

1. Agentforce Sales (formerly Sales Cloud)

Agentforce Sales is the product for the sales team, and it is the one most companies buy first. It holds the leads, the accounts, the contacts, and the deals, and it calculates the forecast from them. For most companies, this is the product they mean when they say Salesforce.

A typical setup mainly includes:

• The lead object, for prospects not yet qualified
• The account and contact objects, for the companies and the people in them
• The opportunity object, with the stages and the forecast categories
• Quotes and products, where the deal is priced inside the CRM
• Activities, such as the calls, emails, and meetings logged against a record

Since the rename, the product also ships prebuilt agents, such as an SDR agent that handles outbound email follow-ups with leads and a coaching agent that prepares a rep before a call. Both work on the same records the reps already use.

Typical uses of Agentforce Sales

• Lead capture and qualification from the website, campaigns, and events
• Pipeline management with stages that match the sales process
• Forecasting by rep, team, and territory
• Ideal for any B2B sales team that runs deals through defined stages, from a five-person team to a global sales organization

2. Agentforce Service (formerly Service Cloud)

Agentforce Service is the product for the customer service team. It brings every request, whether it arrives by phone, email, chat, or social media, into one queue of cases, and it shows the agent the customer's history on the same screen. Its main goal is to resolve a case faster than the customer expects and to keep a record of how it was resolved.

Such a setup mainly includes:

• The case object, with the queues and the assignment rules
• Knowledge, the articles that agents and customers search
• Omni-channel routing, which sends each case to the right agent
• Service level agreements (SLAs), with the clock that starts when a case arrives

Salesforce also sells Agentforce Contact Center as an add-on in some regions, which brings voice calls and the AI agents into the same console.

Typical uses of Agentforce Service

• Case management across email, chat, phone, and social channels
• A knowledge base for agents and for customer self-service
• Routing and escalation against SLAs

Ideal for support teams with more than a handful of agents, and for any company where a missed case costs a customer

One thing to note is that the console does not decide the process. The routing rules, the priorities, and the SLA clocks are set by the service manager, and a case that lands in a queue nobody owns still waits, however good the software is.

3. Agentforce Marketing (formerly Marketing Cloud) and Account Engagement (Pardot)

Agentforce Marketing is the umbrella name for Salesforce's marketing products, and it covers more than one product. Below are the three that carry the marketing name today:

• Marketing Cloud Account Engagement (formerly Pardot), the B2B marketing automation tool that sits closest to the CRM
• Marketing Cloud Engagement (formerly ExactTarget), the B2C email and journey tool
• Marketing Cloud Next, the newest product, built directly on the Salesforce platform with Data 360 and Agentforce underneath.⁷

For a B2B company, Account Engagement is the one that matters most. It scores a prospect on what they read and click, runs the nurture emails, and passes the lead to the sales team once the score crosses the line, along with the campaign history that got it there.

A typical Account Engagement setup mainly includes:

• Prospects, the marketing-side record which syncs to the leads and contacts
• Forms and landing pages, where the prospect enters
• Engagement Studio, the nurture programs
• Scoring and grading, which rank the prospect's interest and fit

Typical uses of Agentforce Marketing

• Lead capture and nurture campaigns for B2B (Account Engagement)
• Email journeys and B2C personalization (Engagement and Marketing Cloud Next)
• Campaign attribution back into the CRM
• Ideal for marketing teams that need the campaign, the lead, and the deal in one report; a small team with a newsletter list rarely needs more than the CRM's own campaign object

It is worth noting that marketing and sales often keep two definitions of a lead. The prospect that marketing calls qualified is not always the lead that sales calls real, and that gap is where most marketing-to-sales handoffs break, whatever the tool.

4. Experience Cloud

Experience Cloud is the product for the people outside the company: the customers, the partners, and the members. It builds a portal on top of the org, so a customer can log in, see their own cases and orders, search the knowledge base and raise a request without emailing anyone, and a partner can register a deal. It was earlier known as Community Cloud, and many admins still call such portals communities.

Such a portal mainly includes:

• A site, built from templates, with the company's branding
• Access rules, which decide what each customer or partner can see
• The same objects as the org, such as cases, orders and knowledge articles, exposed to the outside
• Self-service, where the customer finds the answer before a case is raised

Typical uses of Experience Cloud

• Customer portals for cases, orders and account details
• Partner portals for deal registration and lead sharing
• Member and volunteer portals for non-profits
• Ideal for any company where the same questions arrive by email every day, and for businesses that sell through partners

For example, the published case studies on Vegacompass for FlexTrade and Dementia Singapore describe client portals and community portals built on Salesforce. Please note that a portal is only useful if the answers are in it. People usually launch the portal first and write the knowledge articles later, and the customers go back to email within a month.

5. Data 360 (formerly Data Cloud)

Data 360 is the data layer of the platform. It pulls in data from outside the CRM, such as website visits, app events, orders from the ERP, and records from a data warehouse, matches it to the right customer, and keeps one profile per customer that every cloud and every agent can read. It has been renamed several times, and it was called Data Cloud until October 2025.

Its job mainly includes:

• Connecting the sources, including zero-copy links to a warehouse, where the data stays where it is
• Matching records that belong to the same person across systems
• Building segments, which are lists of customers who match a rule
• Feeding the profile to the clouds and to Agentforce, which is where the agents get their context

Typical uses of Data 360

• One profile per customer across the CRM, the website, and the store
• Segments for marketing, built from behavior and not only from fields
• Grounding for Agentforce, so the agents answer from the company's own data
• Ideal for companies with customer data in three or more systems and a marketing or service use case ready for it; a company with all its data already in the CRM has little to gain from it yet

One thing to note is that Data 360 is priced on consumption rather than per seat, and it does not clean the data it receives. It matches records and applies the rule it is given; it does not know that the address in the ERP is the wrong one. That's why the source systems are cleaned before Data 360 is switched on, and not after.

Below are the other products in the Salesforce family that a company may need:

• Agentforce Commerce (formerly Commerce Cloud) for online storefronts
• Field Service for the technicians and the site visits
• Revenue Cloud for quotes, contracts and billing
• Industry clouds with prebuilt data models for financial services, healthcare, manufacturing and others
• Tableau for analytics, and CRM Analytics inside the platform
• Slack, the collaboration tool Salesforce bought in 2021, which shows CRM records inside its channels⁸
• MuleSoft for integration, as discussed above

Please note that Field Service, Revenue Cloud, and some of the industry clouds are being moved under the Agentforce name as well, so the label on the contract and the label on the website may differ for a while.

Salesforce and AI (Einstein, Data 360, and Agentforce)

AI inside a CRM does two things:

• It reads, which means it scores a lead, drafts an email, summarizes a case, or predicts the quarter from the records it can see.
• Next, since 2024, it acts, which means an agent takes a request, decides what to do from a list of allowed actions, and does it without a person clicking through the steps.

Both heavily depend on the records underneath. On a clean org with a defined process, AI removes the routine work. On a messy one, it does the wrong thing faster, and most importantly, more politely, than any rep would.

Below is the order that works:

• Refine Processes: The stages, the case priorities, and the handoffs have to mean one thing before an agent is asked to follow them. An agent cannot route a case by priority when three teams define priority differently.
• Data Cleanup: Duplicates, blank fields, and stale records are what the AI reads, and whatever it reads, it repeats.
• Deploy Agents: Start with one narrow job, such as answering order-status questions from the portal, measure it, and widen the scope only after it holds.

Einstein and Salesforce’ Promise to Data Protection

Einstein is the name Salesforce has used for the AI features built into the clouds since long before the current wave, and it still handles the predictive side:

• Lead and opportunity scoring
• Forecast predictions
• Next-step recommendations for reps
• The summaries and draft replies that appear inside a record

Such features are switched on by an admin, and they work within the cloud they belong to. In any case, they do not act on their own. Instead, they suggest, and a person decides to act on that suggestion.

Einstein Copilot, the earlier conversational assistant, was folded into Agentforce in early 2025.

Einstein Trust Layer

The Einstein Trust Layer sits between the org and the large language model, and it does four things to every prompt:

• Masks the personal data before the prompt leaves Salesforce
• Grounds the prompt in the org's own records so the answer is about the actual customer
• Filters the response for harmful or off-policy content
• Logs the whole exchange for audit

Salesforce's agreements with the model providers are meant to keep the company's data out of the models' training, as its documentation states.

One thing to note is that the trust layer protects the data; it does not correct it. A masked, grounded, and logged prompt built on a duplicate account still returns the duplicate's history.

Agentforce

Agentforce is the layer of AI agents Salesforce introduced in 2024, and since October 2025, it is also the name on most of the product line.⁹ An agent is best understood as a new kind of user in the org. It is given a job, a set of actions it is allowed to take, the records it is allowed to read, and the rules for when it must hand over to a person. It then handles requests on its own, in a chat window, a portal, an email thread, a Slack channel, or a phone call.

• Prebuilt Agents: Salesforce ships agents for the common jobs, such as a service agent that answers customer questions and updates cases, an SDR agent that follows up leads by email, and a sales coach that runs practice calls with a rep.
• Agent Builder: The tool where an admin defines an agent's jobs, actions, and guardrails in plain language rather than code, with Flows, Apex, and prompt templates as the actions it can call.
• Grounding: The agent reads the CRM records and, where the company has it, the Data 360 profile, so it answers from the company's data and not from the model's general knowledge.
• Escalation: The rules that decide when the agent stops and hands the conversation to a person, with the full transcript attached.
• Pricing by Usage: Agents are billed on conversations or usage rather than per seat, which is a different budget line from the licenses and worth understanding before the pilot.

Please note that an agent scales whatever it finds. Marketing and sales rarely define a qualified lead the same way, and an SDR agent working from the marketing definition will email a lot of people the sales team would never have called. That's why the pilot is narrow, the actions are few, and someone reads the transcripts every week for the first month.

Vegacompass, a Salesforce Consulting Partner since 2014, has built its own Salesforce agents as follows. Each of them is switched on for a client only after the process and the data behind it are in place.

• AI Agent Salesman for lead qualification and outreach
• Vega Support AI (SimCase) for ticket triage and case summaries
• Agent Casey for rule-based decisions

Who owns Salesforce in a company?

The short answer is that Salesforce belongs to whoever owns the revenue numbers. In most cases, the head of sales, the chief revenue officer, or the COO is accountable for the CRM, because the pipeline, the forecast, and the customer record are their numbers.

The ownership is shared by three roles.

• The accountable executive decides what the CRM is for.
• The process owner, usually the revenue operations (RevOps) lead where the company has one, decides what a stage means, which fields are required, and how a lead moves from marketing to sales.
• The configuration owner is the Salesforce admin, who builds what the process owner defines, manages the users, and reads the release notes three times a year. The order matters: the admin builds what the process owner decides, and not the other way around.

Where there is no RevOps lead, the role falls to the sales operations manager or to the admin, and the admin then ends up deciding the process by default. That is how an org grows a field for every manager who asked for one, and a stage that means three different things to three teams. As such, if the company is too small for a RevOps lead, the sales head should hold the process decisions personally rather than delegate them to whoever knows the settings.

In any case, two parties are not responsible for Salesforce, however much they seem to be. The partner that implemented it is not responsible for adoption. They just built what was asked and left. And Salesforce itself is not responsible for the process; its account executive sells the licenses and renews them. Neither of them attends the Monday pipeline meeting, and that is where a CRM lives or dies.

Below is how the ownership usually looks by company size:

• A Small Company (up to about 50 users): The founder or the sales head owns it, and a power user, rather than a full-time admin, maintains it in the gaps between their own job. The risk is that the power user leaves and takes the reasons for every automation with them, so even a small org needs its automations written down.
• A Mid-Size Company (50 to 500 users): A full-time admin, a RevOps lead, and a business owner on the leadership team, with a partner for the larger changes. This is the size at which a change process is needed: requests reviewed once a week against the process, rather than fields added the day someone asks.
• An Enterprise (500 users and above): A platform team with admins, developers, and an architect, a governance forum that decides what gets built, and a release calendar. Each cloud has its own business owner: the sales head for sales and the service head for service, and the admin team serves all of them. Many enterprises run more than one org, which makes ownership harder, not easier.

One more important thing to note is that a managed-services contract does not transfer ownership. A partner who administers the org for a monthly fee still builds what the company asks for. If nobody inside the company decides what a stage means, the partner decides it by default, usually in favor of whoever asked last. The fix is a name against each of the three roles, written down, and a monthly review of what changed and why.

Applications of Salesforce CRM (who uses it, and what for)

Salesforce is simply useful wherever a company has customers to keep track of, which is in fact true in the case of all companies. Below are the main applications of Salesforce CRM:

• Sales Pipeline Management: Tracking every deal from the first call to the signed contract, and forecasting the quarter from the stages.
• Customer service and support: Logging, routing, and resolving cases from every channel, with the customer's history in front of the agent.
• Marketing Automation: Capturing leads from the website and campaigns, nurturing them by email, and passing the qualified ones to sales with the campaign attached.
• Customer and Partner Portals: Letting customers see their own cases and orders, and letting partners register deals, without emailing anyone.
• Account Management and Renewals: Keeping the contract dates, the contacts, and the open issues on one record, so the renewal conversation starts before the notice period.
• Field Service: Scheduling technicians, tracking the visit, and closing the work order from the phone.
• Reporting and Analytics: Dashboards for the sales head, the service manager, and the board, built from the same records the teams update.
• Custom Applications: Anything the business tracks that has a record, an owner, and a status, such as loan applications at a lender, volunteers at a non-profit, or admissions at a university, built on the platform without a separate system.

By company size, as discussed earlier, Salesforce is used at all three levels, but not in the same way. A small company uses one cloud, a power user who is also a rep, and a handful of automations, and a small team on a clean HubSpot portal often has no reason to move. A mid-size company is where Salesforce earns its keep: two or three clouds, an ERP integration, a RevOps lead, and a forecast the board reads. An enterprise runs it across regions and business units, often in more than one org, with a platform team behind it.

Who Uses Salesforce CRM

Inside the company, the people who use it every day are:

• Sales Reps and Account Managers: The pipeline, the activities and the quotes, with the mobile app between meetings
• Sales Development Reps (SDRs): The leads, the follow-up sequences and the handoff to the closer
• Service Agents and their Supervisors: The case queue, the knowledge base and the SLA clock
• Marketers: The campaigns, the scoring, and the attribution reports
• Admins and Developers: The configuration, the code, and the release notes
• RevOps and Sales Operations: The process definitions, the reports, and the data quality
• Executives: The dashboards, which are usually the only screen they open

Industries that Can Leverage Salesforce CRM and AI Technologies

By industry, Salesforce is used in industries like financial services, retail, logistics, manufacturing, healthcare, technology, and the non-profit sector, and Salesforce sells industry clouds with prebuilt data models for several of them, as discussed above. Our own published Salesforce work spans six verticals:

• Capital Markets and Fintech: Case management for SGX and a greenfield build with trading-system integration for MaxxTrader
• Luxury and Retail: A Salesforce audit and optimization across the APAC region for Chanel, in collaboration with Keyrus
• Logistics and Shipping: Marketing analytics and sandboxes for OSM Worldwide, partnered with Coresolute LLC
• Manufacturing, Healthcare and Life Sciences, and SaaS and Technology: ERP integration, sales automation and ongoing support

As such, the question for a company is rarely whether its industry uses Salesforce; some competitor already does. The question is whether its own process is defined enough to be worth the license and the setup, which is what the next two sections are about.

Salesforce implementation

An implementation is the actual work between buying the licenses and the first day the team runs on the org. It covers the process decisions, the configuration, the data migration, the integrations, the training, and the go-live. It is usually done with a consulting partner, as discussed earlier. It comes in three forms:

• A greenfield build for a company new to Salesforce
• A re-implementation for a company whose existing org has stopped matching the business
• A migration for a company moving its data from another CRM, such as Dynamics 365, HubSpot, or an older system

Most implementations follow these four steps:

• Assess: Read the current state before anything is designed, including the process as it actually runs, the data as it actually is, and the systems that have to connect. On a new org, this is a discovery, and on an existing org it is an audit. Either way, it ends in a written document which says what to build and what to leave alone.
• Design: Turn the assessment into a plan the leadership can read: the process, the data model, which cloud handles what, and how the integrations move data. This is where the company decides what a stage means and who owns which record, before a single field is created.
• Build: Configure the org in sprints, code only where a setting cannot do the job, migrate the data after it is cleaned, connect the systems, and test with the people who will use it. The users see working screens every few weeks rather than a reveal at the end.
• Run: Go live with a period of close support, called hypercare, and then hand over to the admin or a managed-services team, with the release notes read three times a year and the measures set at the start reviewed each quarter.

How long it takes depends on the number of clouds, the volume of data to migrate, the number of integrations, and how many teams are in scope. An assessment is generally a couple of weeks. A single-cloud implementation for one team usually runs in sprints over a few months, and a multi-cloud program with integrations and years of historical data takes longer. Anyone who quotes a date before seeing the current process and the data is guessing.

The cost has two parts, and they are paid to different people. The licenses are paid to Salesforce, per user or per usage, at whatever tier the company chooses. The implementation is paid to the partner, and it follows the scope:

• The number of clouds and users, the amount of custom code
• The number of integrations
• The state of the data
• How much of the process still has to be decided during the project

The last one is the quiet cost. A company that arrives with its process written down pays for a build, whereas a company that arrives without it pays for the workshops first.

How to decide if your business needs Salesforce

Salesforce is not a game changer for every company, and the companies it fits are defined by their process rather than their size. A twenty-person company with a three-party sales cycle, partner channels, and an ERP may need it like no one else. On the other hand, a two-hundred-person company with one product, one price, and a simple funnel may not.

Below is the quick fit check:

• Who it suits: Companies with a defined, multi-step sales process; more than one team working the same customer record, such as sales and service or sales and marketing; an ERP, a support desk, or a partner channel that has to connect; and a named owner for the org. The more of these that apply, the stronger the case.
• Who should look elsewhere: A small team that lives in the inbox and needs a shared contact list with reminders; a marketing-led company with a short, simple sales cycle, which HubSpot serves with less overhead; and a company that runs on Microsoft end to end, with its ERP in Business Central or Finance and Operations and a conventional sales process, which Dynamics 365 fits with less integration work. A company with nobody to own the org should not buy any of the three yet.
• For everyone already on a CRM: The answer is an audit of the current one before a migration to a new one. Most "we need Salesforce" conversations are actually "our current CRM is a mess" conversations, and a messy portal migrated as it is becomes a messy org.

There are three popular CRM vendors: Salesforce, Microsoft Dynamics 365, and HubSpot. All of them price per user by tier, and the tiers and their limits change every year, so the vendor's own edition table is the only current source for what a tier includes. Salesforce's agents and Data 360 are priced on usage on top of the seats, as discussed above.

Salesforce vs. Microsoft Dynamics 365

Dynamics 365 is the closest competitor to Salesforce for a mid-size or enterprise company, and the two are more alike than either vendor admits.^10,12,13 Both hold the same kinds of records, both automate through settings before code (Flow and Apex on one side, Power Automate and plugins on the other), and both need a partner and an admin. The difference is where they sit. Dynamics 365 is part of the Microsoft stack, so it lives inside Outlook and Teams, shares Dataverse with the Power Platform, and connects to Business Central or Finance and Operations without middleware. Salesforce is a platform in its own right, with a larger ecosystem of apps and partners and stronger portal and marketing products.¹¹

• Dynamics 365 wins when the company runs on Microsoft end to end, its ERP is a Dynamics ERP, and the sales and service processes are conventional.
• Salesforce wins when the customer-facing process is the company's edge, when portals, partners, or marketing sit at the center of it, or when the company is not Microsoft-centric to begin with.

A company can move in either direction. For example, the published case study for FIMC describes an insurer's move from Salesforce to Dynamics 365, and it reports a 98% reduction in duplicate entries, because the data was cleaned on the way across.

Salesforce vs. HubSpot

HubSpot is not a smaller Salesforce, and treating it as one is how companies buy the wrong tool in both directions. It is a single portal with six Hubs, for marketing, sales, service, content, operations, and commerce, built to be run by the team that uses it rather than by an admin, and its AI, Breeze, follows the same idea.

A marketing-led company with a short sales cycle gets more out of HubSpot in a month than out of Salesforce in a year, because the people who own the process can change it themselves.

Salesforce wins when the process outgrows what a portal is built for: several business units on one customer record, territories and complex quoting, custom objects for things HubSpot has no shape for, many integrations, or a service operation with dozens of agents and SLAs.

Quick Comparison: Salesforce vs. Microsoft Dynamics 365 vs. HubSpot

8 Quick Tips to Keep Your Salesforce Org Healthy

At Vegacompass, we say an org does not decay because the software ages; instead, it decays because nobody is watching it.

Below are eight quick tips that keep a Salesforce org healthy, whatever its size:

1. Name the three owners and write the names down

The executive who answers for the CRM, the process owner who decides what a stage means, and the admin who builds it, as discussed earlier. Review the list every quarter, because people move, and an org whose owner left in March is unowned by June.

2. Run every change through a queue

A request for a new field or a new automation goes into a list, gets a reason and a requester, and is reviewed once a week against the process, rather than built the same afternoon. Half the requests turn out to be duplicates of a field that already exists.

3. Set the data rules before the reps set their own

Required fields at each stage, picklists instead of free text wherever a value repeats, duplicate rules on accounts and contacts, and one agreed direction for every field that syncs from another system. A rule added after a year of free text cleans nothing backwards.

4. Clean the pipeline and the duplicates every month

A monthly report of opportunities that have not moved in two months, and a monthly duplicate report, both worked through by a person rather than filed. People usually leave a dead deal in the pipeline rather than mark it lost, and the forecast carries it until someone asks.

5. Test the automations before every release

Salesforce updates the org three times a year, and a release can change the behavior of a Flow or a component an admin built. Run the important automations in a sandbox on the preview release, and read the release notes for the areas the org depends on.

6. Check the licenses before the renewal, not after

Pull the login history a quarter before the renewal date, deactivate the users who have not logged in, and rightsize the seats and the tiers to the people who use them. The renewal notice is a deadline, not a discovery.

7. Ask which setting cannot do it before writing code

When a developer proposes Apex, the first question is which configuration option has been ruled out and why. The code that stays gets a comment, an owner, and a test, because the next admin will meet it without the developer.

8. Book a Salesforce audit at the right time

An audit reads the objects, the automations, the data quality, and the license usage, and ends in one written diagnosis with the fixes ranked by the value they return. It is generally a two-week engagement. The right times are before a renewal, after a merger or an acquisition, when the admin leaves, before a migration, before switching on Agentforce, and whenever the board's number and the CRM's number disagree.

On the other hand, an org that went live six months ago with a written process and reps who use it daily does not need an audit; it needs the release notes read and the change queue kept. At Vegacompass, the senior consultant who writes the diagnosis is the one who ranks and builds the fixes. Our goal is to ensure that the report is written strictly by someone who has to make it work.

FAQs

Q. Is Salesforce a CRM or a platform?

Both. On the surface, Salesforce is a CRM that holds the customer records and the sales, service, and marketing work around them. Underneath the clouds sits one platform, with the data, the automations, and the security settings shared across all of them, and an admin can build custom apps on it without buying another system. That's why a company can start with one cloud and add the next one later without moving its data.

Q. What is Agentforce?

Agentforce is the layer of AI agents that Salesforce introduced in 2024. Salesforce ships prebuilt agents for sales and service, and an admin can build custom ones in Agent Builder. The agents are billed on usage rather than per seat, and they work only as well as the process and the data underneath them.

Q. What does Salesforce cost?

The cost has two parts. The licenses are paid to Salesforce, per user by tier, with the agents and Data 360 priced on usage on top, and since the tiers and their limits change every year, the vendor's current edition table is the only reliable source. The implementation is paid to the partner and follows the scope: the clouds, the users, the custom code, the integrations, and the state of the data.

Vegacompass: Full-Service CRM and Salesforce Consulting Partner

Vegacompass has 12+ years of experience in CRM and digital transformation. We aim to empower organizations to become the best version of themselves through new CRM and AI technologies. We are an approved Salesforce Consulting Partner.

Everything this article covers, from the objects and the clouds to the integrations, the data and the agents, is assessed, designed, and built by our senior consultants. Recently, we have developed a team to explore possibilities and build sustainable, adaptable, and flexible AI solutions for clients to ensure their CRM success.

We offer the following CRM consulting services:

• CRM Strategy (Marketing, Sales and Customer Service)
• Revenue Operations Consulting
• CRM Audit & Technical Debt
• Salesforce Implementation and Migration
• CRM Migration
• CRM Data Cleanup
• AI CRM Consulting

Get in touch

Please tell us where you are with Salesforce, whether you are still deciding on it, running an org nobody owns, facing a renewal, or weighing an Agentforce pilot, along with the seats, the integrations, and what is not working.

The note goes to a senior consultant, and after a 30-minute call, you get a written point of view on what to fix first and what it would take, and it is yours whether or not we work together. We sign an NDA first if you need one. The same consultant who writes the plan then leads the build, with our own delivery team in Pune, Palo Alto, Austin, and Singapore.

Talk to a Salesforce consultant today to find out whether Salesforce fits your revenue process, or what it would take for the org you already run to earn its licenses.

References

1. (September 20, 2021). New Study Finds Salesforce Economy Will Create 9.3 Million Jobs and $1.6 Trillion in New Business Revenues by 2026. Salesforce. https://www.salesforce.com/uk/news/press-releases/2021/09/20/idc-salesforce-economy-2021/?bc=OTH
2. (2026). Salesforce. The #1 Agentic CRM. Salesforce. https://www.salesforce.com/company/our-story/
3. (December 12, 2006). Salesforce Launches iTunes-like Store For AppExchange. TechCrunch. https://techcrunch.com/2006/12/12/salesforce-launches-itunes-like-store-for-appexchange/
4. (October 24, 2017). Salesforce Launches New AppExchange — A Faster and Smarter Way to Tap into the Power of the World’s Leading Enterprise Cloud Ecosystem. Salesforce. https://www.salesforce.com/news/press-releases/2017/10/24/
5. (2026). Salesforce upgrade release schedule FAQ. Salesforce Help. https://help.salesforce.com/s/articleView?id=005224913&language=en_US&type=1
6. (2025). Agentforce Contact Center. Salesforce Help. https://help.salesforce.com/s/articleView?id=service.support_channels.htm&language=en_US
7. Lee, M. (2026). Salesforce Marketing Cloud Next: What's Changed and How It Compares to Alternatives. Bloomreach. https://www.bloomreach.com/en/blog/salesforce-marketing-cloud-next
8. Klie, L. (August 17, 2021). Salesforce Reveals Its Plans for Slack Integration. Destination CRM. https://www.destinationcrm.com/Articles/CRM-News/CRM-Featured-Articles/Salesforce-Reveals-Its-Plans-for-Slack-Integration-148459.aspx
9. (February 24, 2025). Salesforce and Google Bring Gemini to Agentforce, Enable More Customer Choice in Major Partnership Expansion. Salesforce Newsroom. https://investor.salesforce.com/news/news-details/2025/Salesforce-and-Google-Bring-Gemini-to-Agentforce-Enable-More-Customer-Choice-in-Major-Partnership-Expansion/default.aspx
10. (2026). Dynamics 365 vs Salesforce: CRM & ERP Comparison 2026. Top Dynamics Partners. https://topdynamicspartners.com/learn/erp-comparison/d365-vs-salesforce
11. (2026). Agentforce 360 Platform – Ecosystem | Salesforce. Salesforce. https://www.salesforce.com/platform/ecosystem
12. (2026). Dynamics 365 vs Salesforce: 2026 CRM Comparison. AlphaBold. https://www.alphabold.com/microsoft-dynamics-365-vs-salesforce/
13. Sekhon, A. S. (2026). Dynamics 365 CRM vs Salesforce: Which Is Best for Your Business?. AXSource. https://www.axsource.com/blog/dynamics-365-crm-vs-salesforce/