Salesforce

Definition: The dominant enterprise CRM platform, built on Salesforce’s own multi-tenant Lightning platform, tracking leads, opportunities, accounts, cases, and custom objects in one system that can be extended with proprietary code. Founded in 1999 by Marc Benioff and co-founders on the then-radical pitch of “no software” — CRM delivered entirely over the web instead of installed on-premise — it became one of the first big proof points for the SaaS business model and now anchors a broader suite spanning sales, service, marketing, and analytics.

Core Services & Concepts

Apex — Apex, a proprietary Java-like language for triggers, batch jobs, and business logic; runs sandboxed under “governor limits” (max SOQL queries, DML statements, and CPU time per transaction) that force careful, bulk-safe coding patterns
SOQL/SOSL — Salesforce’s own query languages for the underlying multi-tenant object model, not raw SQL against a normal relational schema
REST/SOAP/Bulk APIs — REST API, the Bulk API handles asynchronous loads/exports of millions of records without hitting per-call API limits
Connected Apps (OAuth) — OAuth 2.0, third-party app authorization; supports SAML-based SSO (Single Sign-On) for enterprise identity providers
Flow (automation builder) — Event-Driven Architecture, no-code trigger-based automation that replaced the older Workflow Rules and Process Builder tools
AppExchange — Salesforce’s marketplace of thousands of third-party apps and prebuilt integrations

How Pricing Works

Sold in per-user/month editions (Essentials, Professional, Enterprise, Unlimited), with Enterprise commonly running well over $150/user/month billed annually
Sales Cloud, Service Cloud, Marketing Cloud, and CPQ are separately licensed products, not bundled into one flat price
Add-ons like extra API call allocations, additional sandboxes, and premier support are priced incrementally on top of the base license
Larger Enterprise and Unlimited edition customers typically negotiate custom multi-year contracts rather than paying list price
Nonprofits and educational institutions get steep discounts through the Salesforce.org / Power of Us program

Pros

Extremely customizable: custom objects, fields, page layouts, and Apex triggers can model almost any business process
Dominant CRM market share means a deep talent pool of certified admins/developers and a huge integration ecosystem
Multi-tenant architecture handles enterprise scale, orgs with hundreds of thousands of users and millions of records
Granular permission model (profiles, permission sets, role hierarchy, sharing rules) supports complex org structures
Large network of certified consulting partners (Accenture, Deloitte, and thousands of smaller shops) capable of running large-scale implementations

Cons

Notoriously expensive — Enterprise edition licensing runs well over $150/user/month, with Sales Cloud, Service Cloud, CPQ, and most useful add-ons priced and sold separately
Steep learning curve; serious implementations effectively require certified admins (Salesforce Administrator) and developers (Platform Developer I/II)
Customization sprawl: years of stacked Apex triggers, workflow rules, and Flows on the same objects make orgs fragile and expensive to refactor or migrate off of
Governor limits can force awkward workarounds (bulkifying code, deferring logic to async jobs) in complex automations
Three major releases a year (Spring/Summer/Winter) mean admins must regression-test customizations against platform changes on a recurring cadence

Comparison: Salesforce vs HubSpot vs Zoho CRM vs Pipedrive

	Salesforce	HubSpot	Zoho CRM	Pipedrive
Primary strength	Deep customization and enterprise scale	Inbound marketing and CRM bundled into one product	Affordable all-in-one business suite	Simple, visual pipeline built for sales reps
Typical pricing model	Per-user/month editions; Enterprise runs well over $150/user/month, add-ons priced separately	Free core CRM; paid Hubs billed by seat (Sales/Service) or marketing-contact volume (Marketing)	Paid tiers commonly start under $20/user/month	Per-user/month, mid-tier pricing below Salesforce
Best fit	Large enterprises with complex, multi-department sales processes	SMBs wanting CRM plus marketing automation without stitching tools together	Budget-conscious small businesses wanting CRM plus back-office apps	Small sales teams wanting a focused pipeline tool
API or product style	REST/SOAP/Bulk APIs plus Apex for custom code — powerful but a steep platform to master	REST API with a CRM object-association model spanning Hubs	REST API plus Deluge scripting, most valuable paired with the wider Zoho suite	REST API (v2) plus webhooks, deliberately minimal configuration

Best For

Large sales teams and enterprises needing deep customization of their sales process, or multi-department implementations spanning sales, service, and marketing
Organizations that expect to build custom internal applications on the same platform as their CRM data, not just track deals

Real Examples

Used by most Fortune 500 sales organizations; companies like Adidas, Toyota, and Spotify run sales and service operations on Salesforce Sales Cloud and Service Cloud
Consulting giants like Accenture and Deloitte run entire practices dedicated to Salesforce implementation and customization work
Nonprofits and universities frequently run donor and alumni management on discounted Salesforce.org licenses

Use Cases

Enterprise sales pipeline management
Customer support case tracking (Service Cloud)
Marketing/sales alignment at scale via Marketing Cloud integration
Custom internal applications built directly on the Salesforce Platform (formerly Force.com)
Partner relationship management for organizations selling through resellers or channel partners

Integration Notes & Common Pitfalls

Governor limits (max SOQL queries, DML rows, CPU time per transaction) mean integrations must be written in bulk-safe patterns from day one — code that works fine against ten sandbox records can hit limits against real production volumes
Per-org daily API call limits scale with edition and user count, so high-volume syncs (e.g. every order from an e-commerce platform) often need the Bulk API rather than one-record-at-a-time REST calls
Sandbox types (Developer, Developer Pro, Partial Copy, Full) differ in data-refresh cadence and storage, and picking the wrong one is a common source of “it worked in staging” surprises
Years of stacked Apex triggers and Flows on the same object create hard-to-reason-about ordering dependencies, so auditing what already fires on save before adding new automation avoids order-of-execution bugs
API access itself is gated by edition — some lower-tier editions don’t include full REST API access at all, a surprise for teams that assumed any paid plan could integrate freely

Code Example

// Creating a Lead via the Salesforce REST API
const response = await fetch(
  'https://yourInstance.my.salesforce.com/services/data/v59.0/sobjects/Lead',
  {
    method: 'POST',
    headers: {
      'Content-Type': 'application/json',
      Authorization: `Bearer ${accessToken}`,
    },
    body: JSON.stringify({
      LastName: 'Doe',
      Company: 'Acme Corp',
      Email: 'doe@acme.com',
    }),
  },
);
// Returns { id, success, errors } — always check `success` rather than
// assuming a 2xx response means the record was created cleanly.

FAQ

Do I need a developer to use Salesforce? For basic pipeline tracking, no — declarative tools like Flow, page layouts, and validation rules cover a lot of ground. Once logic needs to span multiple objects with complex conditions or talk to external systems, most orgs bring in an Apex developer.

What’s the difference between Salesforce and the Salesforce Platform? The Platform (formerly Force.com) is the underlying application-development layer; Sales Cloud and Service Cloud are pre-built products on top of it, so custom internal apps can live alongside CRM data in the same org.

Why do Salesforce orgs get slower and more fragile over time? Years of stacked declarative automation and Apex triggers on the same objects create ordering dependencies that are hard to reason about — without regular technical-debt cleanup, one more automation can have unpredictable side effects on existing ones.

Can a small business realistically use Salesforce, or is it overkill? Technically yes via Essentials/Professional editions, but most small teams get more value per dollar from Pipedrive, HubSpot, or Zoho CRM — Salesforce’s cost and configuration overhead tend to pay off only once a sales org’s complexity actually needs it.

History

Founded in 1999 by Marc Benioff, Parker Harris, Dave Moellenhoff, and Frank Dominguez, pioneering cloud-delivered “no software” CRM when most competitors still sold on-premise installs
IPO’d in 2004, becoming one of the first major SaaS companies to go public
Grew through major acquisitions: ExactTarget/Marketing Cloud (2013), MuleSoft (2018), Tableau (2019), and Slack (2021, roughly $27.7B, its largest acquisition to date)
Has held the #1 CRM market-share position for over a decade by most third-party analyst rankings, and was among the first SaaS companies to reach $30B+ in annual revenue

Referenced by

Dig deeper

Spot an error in this note?