Request a demo
Salesforce CRMOctober 22, 2026

How Does Salesforce Work? - What Salesforce Does, Data Model, Automation, AI, Lead-to-Renewal Example

Every company on Salesforce works in its own org, on infrastructure that all customers share. Inside it, admins set up the records, permissions, and flows that run sales and service. Agentforce and Einstein then work on the same records.

12 min read
How Does Salesforce Work? - What Salesforce Does, Data Model, Automation, AI, Lead-to-Renewal Example
Rakesh Kurhade
Written byRakesh KurhadeCRM Campaign Specialist
Jason Linkswiler
Reviewed byJason LinkswilerStrategy Head, US
Rakesh Kurhade
Fact-checked byRakesh KurhadeCRM Campaign Specialist
Last reviewed

Salesforce is a leading cloud-based customer relationship management (CRM) platform. Companies subscribe to it per user, and their teams open it in a web browser or a mobile app.1 2 Each company works in its own org, a secure space kept apart from every other customer's.3 The orgs sit on shared infrastructure that Salesforce manages, and every org gets three upgrades a year.4 5

Inside the org, the customer records sit in one database that the sales and service teams share.6 Admins set the rules for those records. Flow automations and Agentforce agents then act on them within those rules.7 8 That's why Salesforce works only as well as the org is set up.

What does Salesforce do?

Salesforce gives a company one system for all its customer data. The sales, service, and marketing teams track their leads, deals, cases, and campaigns in it.9

Below are the main Salesforce products today:

Companies buy these licenses from Salesforce, and many hire a consulting partner to set up the org. Vegacompass is one such partner, a CRM-only consultancy and Salesforce Consulting Partner. We earn nothing from licenses on any platform, so our advice starts with your sales and service process.

How does Salesforce work?

Salesforce works in layers. The org holds the records, and the admins decide who sees them and what happens to them. The teams work on those records through apps, reports, and dashboards.6 It comes down to five parts.

1. The Org

The org is a company's own Salesforce, with its records, its users, and every setting the admins have made.3 The teams do their daily work in the production org.3

The admins can also create sandboxes, which are copies of the org for building and testing changes. A Developer sandbox copies only the setup, while a Full sandbox copies all the data as well.10

Note that a change made straight in production reaches every user at once, mistakes included. That's why changes are best built in a sandbox first.

2. Objects, Fields, and Records

Salesforce stores its data in objects. An object works like a table, where each field is a column and each record is a row.11

Below are the main standard objects:

  • Lead for someone who has shown interest
  • Account for a customer company
  • Contact for a person at an account
  • Opportunity for a deal in progress
  • Case for a customer's question or problem12

Admins add custom objects for anything else the business tracks, such as projects or subscriptions.11

Records connect through relationships. In a lookup, one record points to another, such as a contact to its account.13 In a master-detail relationship, deleting the master record deletes its detail records too.13 As such, an account page can show all its contacts, deals, and cases.

3. Users, Permissions, and Sharing

Salesforce controls what each user can reach at four levels:

  • Org: Who can log in, under which password rules, and at what hours and places.14
  • Object: Which types of records a user can create, view, edit, or delete.
  • Field: Which fields on those records a user can see or change.
  • Record: Which individual records a user can open.

Profiles and permission sets decide what each user can do. Salesforce recommends permission sets and permission set groups for most access.14 It also advises setting the org-wide defaults to the most restrictive level. The role hierarchy, sharing rules, and manual sharing then open access where it is needed.14

Please note that loosening an org-wide default for one user opens that object's records to the whole org.

4. Automation with Flow

Flow is the main automation tool in Salesforce. Admins build flows in Flow Builder, mostly without writing code.7

Below are the main types of flows:

  • Record-Triggered Flow: Runs when a record is created, edited, or deleted.
  • Screen Flow: Walks a user through a form or a set of steps.
  • Schedule-Triggered Flow: Runs at a set time and frequency.
  • Autolaunched Flow: Runs when something else starts it, such as a button or another flow.7

Salesforce ended support for Workflow Rules and Process Builder at the end of 2025. The old automations still run, but they get no fixes, so Salesforce advises moving them to Flow.15 Where a flow cannot do the job, developers write Apex, Salesforce's own programming language.16

5. Apps, Reports, and Dashboards

Users work in Lightning Experience in a web browser, or in the Salesforce mobile app.17 2 Each app groups the objects and pages for one job, such as sales or service.6 Admins design those pages with Lightning App Builder, a point-and-click tool.18

Reports list the records that match a set of filters.19 Dashboards turn those reports into charts, and they show the data as of their last refresh.20 So, it is worth checking the refresh time before a pipeline review.

Every screen reads the same database, so a new field can appear on the record, in reports, and in the mobile app.6

How does Salesforce connect with other systems?

A Salesforce org usually works next to other systems, such as the website and the enterprise resource planning (ERP) system.

Below are the main ways Salesforce connects with them:

  • APIs: Other systems read and write Salesforce records through the REST, SOAP, and Bulk APIs.21
  • Events: The Pub/Sub API streams events, such as record changes, to the systems that subscribe to them.21
  • Salesforce Connect: Shows data from another system, such as orders in an ERP, inside Salesforce without copying it.22
  • MuleSoft: Salesforce's integration platform for building and managing connections across many systems.23
  • AgentExchange: The Salesforce marketplace for ready-made apps, agents, and components.24

Note that a failed sync rarely raises an alarm, and the records just stop updating. To learn more about integrations, please read our CRM Integration page.

How Salesforce works day to day: one customer from lead to renewal

Consider a software company that sells to other businesses. Its sales, service, and customer success teams all work in one org.

Below is how one of its customers moves through Salesforce, from the first form to the renewal:

  • Web Form: The buyer fills in a demo form on the website, and Web-to-Lead turns it into a lead record.25
  • Assignment: A lead assignment rule sends the lead to a sales rep or a queue, based on criteria such as region.25
  • Conversion: The rep qualifies the lead and converts it. Salesforce creates an account, a contact, and an opportunity from it.26
  • Products: The rep adds products from a price book, and the deal amount updates from their prices.27
  • Forecast: Each stage of the opportunity maps to a forecast category, and the numbers roll up to the sales manager.28
  • Close: The buyer signs, and the rep moves the opportunity to Closed Won.
  • Onboarding: The stage change starts a record-triggered flow, which creates the onboarding tasks for the customer success team.7
  • Support Case: Weeks later, the customer emails the support address with a problem, and Email-to-Case turns the email into a case.29
  • Routing: Omni-Channel sends the case to an available agent with the right skills.30 The agent finds the answer in a Knowledge article and attaches it to the case.31
  • Renewal: Before the contract ends, a scheduled flow creates a renewal opportunity, and the cycle starts again.7

Please note that none of these steps happens on its own. Each one is a form, a rule, a flow, or a setting that someone built into this org. That's why two companies on the same Salesforce edition can work in very different ways.

For example, the published case study on Vegacompass for MaxxTrader, a subsidiary of Singapore Exchange, covers both sales and service.* It describes greenfield case management and a sales process for broker-dealer operations, from onboarding to account closure.

*Delivered as Vegacompass.

How does Salesforce cloud architecture work?

Salesforce is a multitenant cloud CRM. As the name implies, many customers, or tenants, share the same servers and database, and each org sees only its own data.4 3 Each company's setup is stored as metadata, kept apart from Salesforce's own core.4 This lets Salesforce change its core and each company change its setup, without one getting in the way of the other.4

Salesforce releases new features three times a year, in spring, summer, and winter.5 Sandboxes can get each release four to six weeks before production.5 This gives the admins time to test their main flows and reports first.

Hyperforce, Salesforce's infrastructure for the public cloud, runs on Amazon Web Services (AWS).32 It lets a customer choose the region where its data is stored.32

How Salesforce AI works: Einstein, Data 360, and Agentforce

Salesforce's AI reads the same records that the teams keep. A clean org gets useful answers, and a messy one gets confident wrong ones.

Below is what each part does:

  • Einstein: Gives each lead and opportunity a score based on the company's own past deals, and shows the top factors behind it.33
  • Data 360: Brings data from other systems into unified customer profiles, in some cases without copying it.34
  • Agentforce: Runs AI agents that answer questions and take actions on their own. The Atlas Reasoning Engine plans the steps, and admins set each agent's job and guardrails in Agent Builder.8

Agentforce runs on the Einstein Trust Layer. It masks sensitive data before a prompt reaches the AI model, and the model providers keep none of it.35

In practice, the AI goes in last. The records, the process, and the permissions are fixed first. Then come the platform's own AI features, and a custom agent only where nothing built in does the job. To learn more about planning AI in Salesforce, please read our AI CRM Consulting page.

What to set up before Salesforce works for your team

At Vegacompass, we say the process should be written down before the first field is created.

Below is the usual order of a Salesforce implementation:

  • Process: How a lead becomes a customer and how a case gets solved.
  • Data Model: The objects and fields that the process needs.
  • Access: The org-wide defaults, roles, and permission sets for each team.
  • Automation: The flows that take over the repeat work.
  • Data and Integrations: Clean records loaded, and the other systems connected.
  • Training: Each team shown its own pages, reports, and dashboards.

On the other hand, if your team already runs Salesforce, a CRM audit shows which of these steps were skipped. It generally takes two weeks, and the findings come back in one written diagnosis.

Vegacompass: Salesforce Consulting Partner for Setup, Integration, and AI

Vegacompass has spent 11+ years, since 2015, doing nothing but CRM. That work adds up to 120+ CRM projects. For Salesforce work, we hold Salesforce Consulting Partner status.

Our consultants plan, build, audit, and connect Salesforce orgs, and do the same on Microsoft Dynamics 365, HubSpot, ServiceNow, and open-source CRM. Agentforce and other AI come in once the records and the rules are sound.

We offer the following CRM consulting services:

  • CRM Sales Strategy
  • CRM Customer Service Strategy
  • CRM Audit
  • Salesforce Implementation
  • CRM Integration
  • CRM Data Cleanup
  • AI CRM Consulting

Get in touch

Please tell us where you are with Salesforce, whether you are choosing it or fixing an org that drifted, along with the systems it must connect to.

You will speak with a senior consultant first, in a 30-minute call. That person stays on to lead the work, supported by our delivery team in Pune, Palo Alto, Austin, and Singapore.

Talk to a Salesforce consultant today to find out whether your org is set up the way your teams really work.

Authorship

Rakesh Kurhade (Written by)

Rakesh is a technical content writer. For the past 8+ years, he has been writing practical, plain-language guides on CRM, revenue operations, and AI in CRM for sales, marketing, and RevOps leaders at mid-size and enterprise companies.

Jason Linkswiler (Reviewed by)

Revenue Operations and CRM expert with 20+ years of experience. Jason focuses on Salesforce-driven GTM and revenue systems for mid-market and PE-backed firms.

References

  1. (September 21, 2026). Salesforce Sales Pricing. Salesforce. https://www.salesforce.com/sales/pricing/
  2. (2026). Salesforce Mobile App: Getting Started Guide. Salesforce Trailhead. https://trailhead.salesforce.com/content/learn/modules/lex_salesforce1_basics/lex_salesforce1_basics_getting_started
  3. (2026). Salesforce Glossary. Salesforce Help. https://help.salesforce.com/s/articleView?id=glossary.htm&language=en_US&type=5
  4. (2026). Platform Multitenant Architecture. Salesforce Architects. https://architect.salesforce.com/fundamentals/platform-multitenant-architecture
  5. (2026). Salesforce Release Process and Transitioning Tips. Salesforce Trailhead. https://trailhead.salesforce.com/content/learn/modules/sf_releases/sf_releases_start
  6. (2026). Unlock Business Success with Salesforce Data Platform. Salesforce Trailhead. https://trailhead.salesforce.com/content/learn/modules/starting_force_com/starting_intro
  7. (2026). Enhance Business Processes with Salesforce Automation. Salesforce Trailhead. https://trailhead.salesforce.com/content/learn/modules/flow-basics/get-started-with-flows
  8. (October 20, 2026). Agentforce: The AI Agent Platform. Salesforce. https://www.salesforce.com/agentforce/
  9. (October 15, 2026). Complete Salesforce Products & Software Suite. Salesforce. https://www.salesforce.com/products/
  10. (2026). Sandbox Types and Templates. Salesforce Help. https://help.salesforce.com/s/articleView?language=en_US&id=platform.create_test_instance.htm&type=5
  11. (2026). Optimize Customer Data with Standard and Custom Objects. Salesforce Trailhead. https://trailhead.salesforce.com/content/learn/modules/data_modeling/objects_intro
  12. (2026). Case. Object Reference for the Salesforce Platform, Salesforce Developers. https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_case.htm
  13. (2026). Object Relationships: Create & Manage. Salesforce Trailhead. https://trailhead.salesforce.com/content/learn/modules/data_modeling/object_relationships
  14. (2026). Overview of Data Security. Salesforce Trailhead. https://trailhead.salesforce.com/content/learn/modules/data_security/data_security_overview
  15. (September 29, 2026). Salesforce Workflow Rules & Process Builder End of Support. Salesforce Help. https://help.salesforce.com/s/articleView?id=001096524&language=en_US&type=1
  16. (2026). Salesforce Coding Languages Guide. Salesforce Trailhead. https://trailhead.salesforce.com/content/learn/modules/platform-development-basics/code-with-salesforce-languages-01
  17. (2026). Salesforce Lightning Experience Getting Started Guide. Salesforce Trailhead. https://trailhead.salesforce.com/content/learn/modules/lex_salesforce_basics/lex_salesforce_basics_getting_started
  18. (2026). Master Lightning App Builder for Custom Pages. Salesforce Trailhead. https://trailhead.salesforce.com/content/learn/modules/lightning_app_builder/lightning_app_builder_intro
  19. (2026). Boost Your Business Insights with Lightning Reports. Salesforce Trailhead. https://trailhead.salesforce.com/content/learn/modules/lex_implementation_reports_dashboards/lex_implementation_reports_dashboards_overview
  20. (2026). Dashboards. Salesforce Help. https://help.salesforce.com/s/articleView?language=en_US&id=sf.rd_dashboards_overview.htm&type=5
  21. (2026). Which API Do I Use? Salesforce Help. https://help.salesforce.com/s/articleView?id=platform.integrate_what_is_api.htm&language=en_US&type=5
  22. (2026). Salesforce Connect. Salesforce Help. https://help.salesforce.com/s/articleView?id=sf.platform_connect_about.htm&language=en_US&type=5
  23. (August 20, 2026). MuleSoft Anypoint Platform. Salesforce. https://www.salesforce.com/mulesoft/anypoint-platform/
  24. (2026). What Is AgentExchange? Salesforce Developers. https://developer.salesforce.com/docs/platform/appexchange-install-guide/guide/appexchange-install-whatis.html
  25. (April 16, 2025). A Step-by-Step Guide to Creating Web-to-Lead Forms in Salesforce. Salesforce Ben. https://www.salesforceben.com/a-step-by-step-guide-to-creating-web-to-lead-forms-in-salesforce/
  26. (2026). What happens when I convert leads? Salesforce Help. https://help.salesforce.com/s/articleView?language=en_US&id=sales.faq_leads_what_happens_when.htm&type=5
  27. (2026). Create an Opportunity and Add Products to It. Salesforce Trailhead. https://trailhead.salesforce.com/content/learn/projects/manage-products-prices-quotes-orders/create-opportunity-add-products
  28. (2026). Configure Forecasting in Salesforce. Salesforce Trailhead. https://trailhead.salesforce.com/content/learn/modules/sales-forecasting/configure-sales-forecasting-in-salesforce
  29. (2026). Create Basic Service Channels. Salesforce Trailhead. https://trailhead.salesforce.com/content/learn/modules/service_lex/service_lex_channels
  30. (2026). Understand Skills-Based Routing. Salesforce Trailhead. https://trailhead.salesforce.com/content/learn/modules/omni-channel-lex/understand-sbr
  31. (2026). Close Cases with Articles. Salesforce Trailhead. https://trailhead.salesforce.com/content/learn/modules/lightning-knowledge-setup-and-customization/close-cases-with-articles
  32. (August 4, 2026). Salesforce Hyperforce - General Information, FAQ, Migration Guide, and Security Overview. Salesforce Help. https://help.salesforce.com/s/articleView?id=000388902&language=en_US&type=1
  33. (2026). Close More Deals. Salesforce Trailhead. https://trailhead.salesforce.com/modules/ai_sales/units/ai_sales_deals
  34. (2026). About Salesforce Data 360. Salesforce Help. https://help.salesforce.com/s/articleView?language=en_US&id=data.c360_a_data_cloud.htm&type=5
  35. (2026). Secure Agents with the Einstein Trust Layer. Salesforce Trailhead. https://trailhead.salesforce.com/content/learn/modules/conversational-marketing-fundamentals-for-marketing-cloud-next/secure-agents-with-the-einstein-trust-layer
salesforce crmsalesforce aicrm automationhow salesforce workssalesforce data model
Rakesh Kurhade
Rakesh Kurhade

Rakesh is a technical content writer. For the past 8+ years, he has been writing practical, plain-language guides on CRM, revenue operations, and AI in CRM for sales, marketing, and RevOps leaders at mid-size and enterprise companies.

More from Rakesh Kurhade →
Beyond the reading

This article comes from client work. See the services behind it.

CRM strategy consulting and delivery across Salesforce, MS Dynamics, HubSpot, ServiceNow and open-source CRM.

Explore our servicesSee case studies

Leave a comment

Have a question about this, or seen it play out differently? Add your take.

Never published.

Your name and comment are published once reviewed.

Keep reading

All articles →