In short Four big platforms quietly run most large companies. SAP is the ERP — the system of record for money and materials. Salesforce is the CRM — the system of record for customers. Workday is the HRIS — the system of record for people. ServiceNow is the ITSM — the system of record for work and requests. This article gives each one the same plain-English treatment: what it is, its flagship product, the modules you’ll hear named, and a single business process flowing through it end to end.

Walk into almost any large company and four systems are quietly running underneath everything you do. Somebody says “it has to be in SAP by Thursday,” or “did you update Salesforce?”, or “do it in Workday,” or “just raise a ticket.” Each of those sentences points at a different system, and each system owns a different slice of the truth. This article gives all four the same plain-English treatment — what it is, its flagship product, the modules people name, and one real business process flowing through it — so the names stop being noise.

If you want the conceptual version — why each system “wins arguments,” why they feel rigid, and how to read the jargon — that’s the whole Business Systems course. This article is the concrete companion: the actual products and what happens inside them.

The one idea that ties them together

Each system is the system of record for one kind of thing — the single official source of truth that overrules every spreadsheet and hallway conversation. SAP owns money and materials, Salesforce owns customers, Workday owns people, and ServiceNow owns work and requests. Keep that map in your head and the rest is detail:

  • SAP → ERP → money, inventory, orders, the general ledger
  • Salesforce → CRM → leads, customers, deals, the sales forecast
  • Workday → HRIS → your role, manager, pay, review, and time off
  • ServiceNow → ITSM → tickets: incidents, requests, and changes

SAP in Plain English

What SAP is

SAP is an ERP — Enterprise Resource Planning — which is a grand name for the company’s central record of money and stuff. Every euro the company spends or earns, and every physical item it buys, makes, or ships, eventually gets recorded here, once, correctly. It’s the system finance closes the books from, so “it’s in SAP” ends arguments. (Oracle, NetSuite, and Microsoft Dynamics are the same category.) The conceptual deep-dive lives in ERP in Plain English.

The flagship product: SAP S/4HANA

The current flagship is SAP S/4HANA, SAP’s ERP built on its fast in-memory HANA database. The older generation was SAP ECC, and a lot of companies are mid-migration — that’s what “we’re going live on S/4 next year” means. Increasingly it’s sold as cloud under the RISE with SAP and GROW with SAP banners.

Common SAP modules

SAP splits the work into modules, and the acronyms people overhear map straight to them:

  • Finance and controlling — FI (Financial Accounting, the general ledger) and CO (Controlling, cost centers and internal reporting)
  • Materials management and procurement — MM: purchase orders, suppliers, the three-way match
  • Sales and distribution — SD: customer orders, deliveries, billing
  • Production planning — PP: manufacturing and what to build when
  • Supply chain and inventory — warehouse and stock movements (EWM and related)
  • Human resources — historically HCM, though HR now usually lives in a dedicated HRIS (see Workday below)

A business process inside SAP

Watch a single customer order move through those modules end to end:

  1. Customer places an order — captured in Sales and Distribution (SD)
  2. Inventory is checked — SD asks inventory whether the stock exists
  3. Materials are purchased — if stock is short, Materials Management (MM) raises a purchase order to a supplier
  4. Product is shipped — the warehouse ships and records the stock leaving
  5. Invoice is generated — SD bills the customer
  6. Revenue appears in finance reports — the sale posts to the general ledger in FI/CO, where finance closes the quarter

One order, five modules, and every step leaves a permanent record. That’s the whole point of an ERP.

Salesforce in Plain English

What Salesforce is

Salesforce is a CRM — Customer Relationship Management — the system of record for customers. Everything the company knows about a customer is supposed to live here: who they are, who talks to them, what they’ve bought, what they might buy next, and every email, call, and complaint along the way. (Microsoft Dynamics and HubSpot are the same species.) The conceptual version is CRM in Plain English.

The flagship product: Sales Cloud

Salesforce’s core CRM is Sales Cloud — where leads, opportunities, and the pipeline live. It’s the original product, and everything else is arranged around it on the Salesforce Platform, extended with third-party apps from the AppExchange.

Common Salesforce modules (“clouds”)

Salesforce calls its modules clouds, and they all share the same accounts and contacts:

  • Sales Cloud — leads, opportunities, pipeline, forecast
  • Service Cloud — support cases and the help queue
  • Marketing Cloud — campaigns and the leads they generate
  • Commerce Cloud — online storefronts and orders
  • Data Cloud — one unified customer profile stitched from every source
  • Agentforce — Salesforce’s newer AI agents that act across all of the above

A business process inside Salesforce

Follow one deal from stranger to signed customer:

  1. A lead comes in — a web form, a trade-show scan, a cold-call bite (a maybe)
  2. The lead is qualified — a rep decides it’s real and converts it
  3. An opportunity is created — now it has a dollar value, a close date, and a stage
  4. It moves through the pipeline — qualification → proposal → negotiation, each stage carrying a probability
  5. The deal is closed won — it counts as booked revenue
  6. It’s handed to Service Cloud — support and renewals now hang off the same account
  7. The forecast updates — the rep’s number rolls up into what the CFO tells investors

Every rep’s pipeline rolls into that final forecast, which is exactly why “if it’s not in the CRM, it didn’t happen.”

Workday in Plain English

What Workday is

Workday is an HRIS — Human Resources Information System — the system of record for people. The core idea is one employee master record per person: your role, manager, level, salary, location, and start date. Every HR-shaped thing in the company reads from or writes to that record. (SAP SuccessFactors, BambooHR, and ADP play the same role elsewhere.) The conceptual version is HRIS in Plain English.

The flagship product: Workday HCM

Workday sells two flagships that share one data core — Workday HCM (Human Capital Management, the people side) and Workday Financial Management (the money side, and a genuine ERP rival to SAP). The employee record most people picture is the HCM heart.

Common Workday modules

  • Core HCM — the master record, org structure, and self-service
  • Payroll — pays exactly what the record says, every month
  • Time and Absence — hours worked and time off
  • Talent and Performance — the review cycle
  • Compensation and Benefits — the comp cycle and its fixed raise pool
  • Recruiting — job requisitions through to the hire
  • Financial Management and Adaptive Planning — the finance and budgeting side

A business process inside Workday

Follow one person from applicant to productive employee:

  1. A job requisition opens — Recruiting posts the role
  2. A candidate is hired — the offer is accepted and a hire event fires in the HRIS
  3. The employee record is created — role, manager, level, salary, start date
  4. Downstream systems provision automatically — IT opens accounts, facilities issues a badge, payroll opens a pay record, so the laptop is ready on day one
  5. Payroll runs — every month, straight from the record, no human re-checking the salary
  6. The review and comp cycle routes to their manager — using the manager field on the record

Change one field — say, the manager — and every one of those downstream steps inherits it. Accuracy here is accuracy everywhere.

ServiceNow in Plain English

What ServiceNow is

ServiceNow is an ITSM — IT Service Management — the system of record for work and requests. It runs IT’s entire workload as tickets: every problem, who owns it, what was done, and how long it took. Increasingly HR, facilities, and finance run on the same ticket machinery too. (Jira Service Management, Zendesk, and Freshservice are the same category.) The conceptual version is ITSM and the Ticket.

The flagship product: the Now Platform

ServiceNow runs on the Now Platform, a single workflow engine with product families layered on top — which is why the same ticketing shows up well outside IT.

Common ServiceNow modules

  • ITSM (IT Service Management) — incidents, service requests, and changes
  • ITOM (IT Operations Management) — the CMDB (IT’s inventory of every system) and system health
  • HR Service Delivery (HRSD) — the same tickets, for HR questions
  • Customer Service Management (CSM) — the same tickets, for customers
  • Security Operations (SecOps) and Risk (IRM) — security incidents and compliance
  • App Engine — custom workflows built on the platform

A business process inside ServiceNow

Follow one broken laptop from complaint to closed:

  1. A ticket is raised — you report the problem instead of grabbing someone in the hallway
  2. Triage labels it — is it an incident (something broke), a service request (something standard), or a change (modify a live system)?
  3. A priority is set — impact × urgency; a company-wide outage during month-end close is a P1
  4. It’s routed to a queue — the specialist lane (network, laptops, HR systems) with people who can actually fix it
  5. It’s worked against an SLA — the service level agreement is the clock, e.g. respond in 15 minutes, resolve in 4 hours
  6. It’s resolved and closed — and the record feeds reports, staffing data, and pattern-spotting

No ticket means no record, no priority, and no SLA clock — which is why “raise a ticket” is the opposite of a brush-off.

How the four connect

These systems look separate, but a single real-world event ripples across all of them. A new customer order lands in Salesforce as a closed-won deal, becomes a real order and invoice in SAP, and if something breaks during delivery it becomes a ticket in ServiceNow — while the salesperson who closed it, the finance analyst who booked it, and the support agent who fixed it are all employee records in Workday. Each system owns its own truth and passes the baton at the boundaries. The Business Systems course walks through exactly how one customer touches every system, and why the systems so often struggle to talk to each other.

Related reading: CRM in Plain English · ERP in Plain English · HRIS in Plain English · ITSM and the Ticket