Following One Customer Through Every System

What you'll learn

Follow a single order across all eight systems the course has covered
Name the system category — and a famous example — at every step of a customer journey
See why one company runs many specialized systems stitched together, not one big one

You have met all eight systems now — the CRM, the ERP, the HRIS, the ITSM tool, and the identity and integration plumbing that ties them together. Here is the last move, and the one that makes the map stick: instead of touring the systems one at a time, we follow a single customer and a single order straight through every one of them, in a row. Meet Acme Bakery. They want to buy one commercial oven from your company. Watch everything their order touches.

From stranger to signed order — the CRM

It starts with Priya, a sales rep. Acme Bakery fills in a form on your website, and Priya enters them into the CRM — the customer relationship management system, the place that owns the truth about customers and deals. Salesforce is the famous example. In the CRM, Acme first shows up as a lead: a maybe, a name and an email and a flicker of interest. Priya calls them, learns they run three shops and need a bigger oven, and promotes the lead to an opportunity — a real deal worth chasing, with a value and a close date attached. She works it for two weeks, sends a quote, and Acme says yes. Priya marks the opportunity Won. That single click is the hinge of the whole story: a “maybe” has just become a promise your company has to keep.

Across the wire, into operations — the ERP

A promise means work: an oven has to be reserved, packed, and delivered, and money has to change hands. None of that lives in the CRM. It lives in the ERP — enterprise resource planning, the system of record for money, stock, and operations. SAP is the famous example. So the won opportunity has to become a real order inside the ERP — and here is the quiet miracle you learned to see in module 7: nobody retypes it. The order crosses from Salesforce to SAP through an API (application programming interface) — the software front desk one system offers another — as an integration running automatically. The deal closes in the CRM, and an order simply appears in the ERP.

The first thing the ERP does is check inventory: is there actually an oven on the shelf to promise Acme? The ERP is the system of record for that answer — module 1’s spine concept, showing up right on cue. If the CRM and a spreadsheet disagree about stock, the ERP wins, by definition.

Ship it, then bill it — the warehouse and finance

There is an oven in stock, so the order flows to the warehouse floor, where Marcus picks it, crates it, and books the freight. This is fulfilment — the operations side, and in most companies it runs inside the ERP too, or a warehouse module bolted onto it. Marcus scans the crate, stock drops by one, and a truck leaves.

Then the money. Finance raises an invoice in the ERP — the formal “you owe us” document — and sends it to Acme. Two weeks later Acme pays, and the payment is recorded against that invoice. Now the order is closed on every axis: promised, shipped, billed, paid. One customer, and we have already crossed the CRM, an integration, the ERP, the warehouse, and finance.

When the oven acts up — support and the ticket

Three weeks in, Acme’s new oven runs hot; the thermostat is faulty. Acme contacts support, and a ticket opens in the ITSM tool — IT service management, the system that owns requests and incidents. ServiceNow is the famous example (the ticket ritual from module 5). Dana, a support agent, picks up the ticket, arranges a replacement part, and closes it when Acme confirms the fix. The customer’s whole life with you — sold, shipped, billed, and repaired — has now been recorded across four different system categories.

The people behind every step — HR and identity

Now look underneath the whole story. Priya, Marcus, and Dana are themselves records in the HRIS — the human resources information system that owns the truth about employees. Workday is the famous example (module 4). And the reason each of them could even open their system on day one — Priya into Salesforce, Marcus into SAP, Dana into ServiceNow — is SSO / identity, the single sign-on layer that provisions one login to open many systems, fed straight from that HR record (module 6). Hire someone in Workday, and access flows outward; offboard them, and it flows back.

So here is the shape of it. Every arrow in that journey — CRM to ERP, ERP to warehouse, HRIS to identity — is an API / integration, the pipes moving information between systems so humans do not have to. The exact software will be different at your company; maybe it is HubSpot instead of Salesforce, Oracle instead of SAP. But the categories and the flows are universal. Learn the shape once and every company reads the same.

The words that matter

CRM: Customer relationship management — the system of record for customers and deals. Salesforce is one famous example.
ERP: Enterprise resource planning — the system of record for orders, inventory, invoices, and payments. SAP is one famous example.
HRIS: Human resources information system — the system of record for employees. Workday is one famous example.
ITSM: IT service management — the system that owns tickets, incidents, and requests. ServiceNow is one famous example.
API / integration: The software “front desk” one system offers another, and the automatic pipe that moves data between them so nobody retypes it.
SSO / identity: Single sign-on — one login, fed from the HR record, that opens many systems and is switched off when someone leaves.
System of record: The one official source of truth for a given kind of data. When copies disagree, this one wins by definition.

One customer crosses five system categories along the top; the HR and identity systems underneath supply the people and the logins that make every step possible.

Text description of this diagram

The flow moves left to right along the top row. Acme Bakery, the customer, enters at the far left. Their record moves first into the CRM (Salesforce), where a lead becomes a won order. An arrow labelled API carries the order into the ERP (SAP), which checks stock. From there it reaches the Warehouse / Operations, where the oven ships; then Finance (inside the ERP), where an invoice is raised and payment is recorded; then Customer Support (ServiceNow), where a reported fault becomes a ticket. Every connector between systems is an API / integration — the blue dots animate along them to show data moving with no one retyping it. Underneath sits a supporting layer: the HRIS (Workday), which holds the sales rep, warehouse staff, and support agent as employee records, and the Identity / SSO system, which gives each of them one login that opens every system above. Dashed amber arrows rise from that layer into the chain, showing that HR and identity feed the people and the access into every step of the journey.

Put the journey in order

Drag each event into the stage where it belongs — or tap an event, then tap a stage. Hit Check placement when you are done.

1 · SellCRM

2 · FulfilERP / Warehouse

3 · BillFinance

4 · SupportITSM

5 · Behind the scenesHRIS / Identity

Tip: drag with a mouse, or tap an event then tap a stage on touch screens. Get one wrong and the answer key appears.

Spot it: which system is this?

Common misunderstanding

“It’s all one big system.” It isn’t. What looks like a single smooth journey is really five or six specialized systems — a CRM, an ERP, a warehouse module, a finance ledger, an ITSM tool, plus HR and identity underneath — each bought for a different job and stitched together with integrations. When someone says “just check the system,” the honest question is always which system, because each one owns a different slice of the truth.

Quick check

1. The won deal in the CRM becomes an order in the ERP with nobody retyping it. What moved it?

2. Which system is the system of record for whether an oven is in stock?

3. The support agent could open the ticketing tool on day one because…

Answers explained

A is correct — an API/integration is the automatic pipe that carries the order from Salesforce to SAP so no human retypes it. (If you picked B: swivel-chair work is exactly what the integration replaces — a person is the fallback when the pipe doesn’t exist. If you picked C: “system of record” names where truth lives, not how data moves.)
C is correct — the ERP owns inventory, so it is the system of record for stock; if two sources disagree, it wins. (If you picked A: the CRM owns customers and deals, not warehouse counts. If you picked B: the ITSM tool owns tickets, not stock.)
B is correct — her access came from single sign-on, provisioned automatically from her Workday record when HR onboarded her. (If you picked A: real access never depends on guessing. If you picked C: every business system requires a login — that’s the whole point of identity.)

Try this at work

Pick one real thing your company sells or delivers — an order, a claim, a booking, a request. This week, trace it out loud across systems: where is it entered, where does it become real, where does it get billed, and where would a complaint about it land? You have just drawn your own company’s version of this diagram.

Key takeaway

A customer’s journey isn’t one system doing everything — it’s a handful of specialized systems, each owning one slice of the truth, wired together by integrations, with HR and identity underneath supplying the people and their access.

Why it matters

You started this course nodding along when someone said “that has to go through SAP.” Now you can follow an entire customer — from a stranger filling in a form to a paid, shipped, and supported order — and name the system, and a famous example, at every single step. That is not trivia. It is the difference between feeling lost in a company and knowing exactly where the truth about any topic lives, who owns it, and which system wins when two disagree. You will ask sharper questions, land in the right team faster, and never again mistake a broken pipe for a broken business. The systems will keep changing names; the shape you now carry will not.

The whole course in one picture

Hold all eleven modules in one frame:

Different systems do different jobs. No single tool runs a company — each one is the right answer to one department’s problem.
One company runs many interconnected platforms, not one big system, and knowing which is which is half the battle.
CRM owns customer relationships and sales — leads, opportunities, deals (Salesforce).
ERP owns operations and finance — orders, inventory, invoices, payments (SAP).
HRIS owns employee information and HR — people, titles, reporting lines (Workday).
ITSM owns technology services, incidents, and requests — the ticket (ServiceNow).
Identity systems control access — one login in, provisioned from HR, switched off on exit (SSO / MFA).
APIs and integrations move the information between all of them so humans don’t retype it.
Test versus production keeps changes safe — you try things in a copy before they touch the live system.
Business and technical teams share ownership — the people who use a system and the people who run it are partners, not opposites.
And you don’t need to be a software expert to see how it all fits together — you just need the map, and now you have it.