What a CRM Is, and the Data Model Underneath

Every company has customers, and every customer relationship is a stream of interactions: emails, calls, meetings, purchases, support tickets, quotes. Left to itself, that stream scatters, across inboxes, spreadsheets, and people's heads. When a salesperson leaves, their relationships leave with them. When a customer calls support, nobody knows what sales promised. The company has the information, but it does not have it together.

A CRM (Customer Relationship Management) system solves exactly this. At its heart it is one idea: a single, shared place that holds everything about every customer relationship, so the whole company works from the same picture instead of fragments.

That is why the most useful way to think about a CRM is not "sales software." It is the memory of the business. It remembers who your customers and prospects are, everyone who has talked to them, what was said, what was bought, what is owed, and what should happen next, and it keeps that memory when individual people come and go.

This cursus builds the discipline in three parts:

• This lesson: what a CRM is, and the data model that makes it work.
• Lesson 2: pipelines, the customer lifecycle, and automation.
• Lesson 3: why most CRM projects fail, and what makes them succeed.

Start with the data model, because a CRM is, underneath all the features, a particular way of structuring customer information, and once you see that structure, every CRM, including Salesforce and HubSpot, becomes legible.

Before the structure, it is worth being clear about why centralizing customer data is transformative, because the benefits explain every design choice that follows.

• It ends knowledge silos. When customer information lives in one shared system rather than individuals' inboxes and memories, the relationship belongs to the company, not the employee. A rep can go on holiday, or leave, and the next person picks up the relationship with full context.
• It aligns departments. Sales, marketing, and support all touch the same customer. With a shared record, support can see what sales promised, and sales can see that a customer has three open complaints before pitching them an upsell. Without it, each department blunders in blind.
• It enables scale. A single founder can hold a hundred relationships in their head. A company with thousands of customers and dozens of employees cannot, and the CRM is what lets many people manage many relationships coherently.
• It creates a factual basis for decisions. Because the interactions are recorded, you can measure: how many deals are in progress, which marketing brought them, how long deals take, why they are lost. Management stops guessing.

Notice the through-line: every benefit comes from the information being structured and shared rather than scattered and private. That is the whole proposition, and it is why the structure, the data model, is the substance of a CRM, not an implementation detail. A pile of notes about customers is not a CRM. An organized model of customers, and everything connected to them, is.

Almost every CRM, whatever it calls them, is built from the same handful of objects, the types of thing it stores. Learn these five and you understand the skeleton of them all.

• Company (Salesforce calls it an Account): an organization you deal with, a customer, prospect, or partner. "Acme Corp."
• Person (Salesforce and HubSpot call it a Contact): an individual, usually one who works at a company. "Jane Smith, Head of Ops at Acme."
• Lead: a potential customer who has not yet been qualified, a raw, unvetted prospect. Someone who filled in a web form or handed over a business card. Leads are the top of the funnel, and they are kept separate on purpose (Lesson 2 explains why).
• Deal (Salesforce calls it an Opportunity): a specific potential sale being worked, with an amount, a stage, and an expected close date. "Acme, 50 licenses, 40,000 dollars, closing next quarter."
• Activity: a single interaction, a call, email, meeting, or note, logged against a person, company, or deal. Activities are the raw history, the record of what actually happened.

These are the nouns of the CRM. A company has people; a deal is with a company; activities are logged against all of them. Everything else a CRM does, pipelines, reports, automation, is built on top of these objects and the links between them.

The vocabulary differs by vendor (Account vs Company, Opportunity vs Deal), which is why moving between CRMs is mostly relearning names, not concepts. The underlying model is remarkably consistent, because it mirrors how business relationships actually work: organizations, the people in them, the deals you pursue, and the history of every touch.

The objects matter, but the relationships between them are what turn a CRM from five lists into one picture. A CRM is essentially a graph: objects connected by links, and the connections are where the value lives.

The core relationships:

• A company has many people. One Account (Acme) links to many Contacts (Jane in ops, Raj in finance, Mei the CEO). This mirrors reality, you sell to organizations, but you talk to people.
• A deal belongs to a company and usually involves specific people. The Acme opportunity is with Acme, and Jane and Raj are the contacts on it.
• Activities attach to any of them. A call is logged against Jane (the person), and it rolls up to Acme (the company) and to the open deal. So one logged call becomes visible from three angles.

The payoff of this linking is the 360-degree view: open a company record and you see, in one place, every person there, every deal open or won or lost, and every interaction anyone has ever had. That consolidated view is the thing a CRM exists to produce, and it is only possible because the objects are related, not just stored.

A concrete illustration: a support agent takes a call from Jane at Acme. In a CRM, they open Acme and instantly see that sales has a 40,000 dollar deal closing next week, and that Jane raised two complaints last month. They handle the call completely differently than if they saw only a name and a phone number. That context, assembled automatically from the linked objects, is the entire point.

So the mental model to carry is: a CRM is a connected model of your customer world, companies and people and deals and history, all wired together so that any one record shows you everything related to it.

One modeling choice confuses newcomers and is worth understanding, because it reveals how CRMs think: the separation between a Lead and a Contact.

Both are people. Why two objects? Because they represent people at very different stages, and mixing them pollutes the data.

• A Lead is an unqualified, unvetted prospect. You captured a name and email from a web form, a conference badge scan, a purchased list. You do not yet know if they are real, relevant, or interested. Leads are raw and often low-quality, many are junk.
• A Contact is a known person in a real relationship, someone connected to a Company you actually do business with or are seriously pursuing.

Keeping them separate protects the core data. If every scanned badge became a Contact linked to a Company, your clean database of real relationships would be swamped with unverified noise. So leads live in a holding area: you work them, and only when a lead is qualified, confirmed as a genuine prospect worth pursuing, is it converted, which typically creates a proper Contact (the person), often an Account (their company), and an Opportunity (the potential deal).

That conversion step is the gateway from "raw prospect" to "real relationship," and it is why the two objects exist. It is also a preview of Lesson 2's lifecycle: a person's journey through a CRM is a series of stages, and lead-to-contact is the first real threshold.

Not every CRM uses a separate Lead object, some (HubSpot's core model) treat everyone as a Contact and use lifecycle stages instead, which is a different answer to the same question: how do you keep raw prospects from contaminating known relationships? Either way, the underlying concern is real, and recognizing it is part of reading any CRM's model correctly.

Assemble it into a concrete example, following one relationship through the model.

Marketing runs a campaign. A person, Jane, fills in a form.

1. LEAD created: "Jane Smith, jane@acme.com" (raw, unqualified)

2. A rep works the lead, confirms Acme is a real prospect,
   and CONVERTS it, producing:
     - COMPANY (Account): Acme Corp
     - PERSON  (Contact): Jane Smith, linked to Acme
     - DEAL (Opportunity): "Acme - 50 licenses - $40k - Q3"

3. Over the following weeks, ACTIVITIES accumulate:
     - Call logged with Jane        -> visible on Jane, Acme, the deal
     - Demo meeting                 -> visible on all three
     - Follow-up email              -> visible on all three
     - Raj (finance) added as a second CONTACT on Acme

4. The deal moves through stages and closes.
   Acme is now a CUSTOMER, with a full history attached.

Every object and relationship from this lesson appears. The lead is the raw entry point. Conversion creates the real company, person, and deal. Activities record the history and, because everything is linked, that history is visible from every angle. A second contact joins because you sell to an organization, not one person.

And here is the result: months later, anyone at the company, sales, support, a new hire, can open Acme and instantly see the whole story, who works there, what was sold, every conversation, what is owed. The knowledge is no longer in one rep's head. It is the company's, structured and permanent.

That is a CRM. Not a feature list, but a structured, shared, connected model of your customer relationships. Everything in the rest of the cursus, and every specific product like Salesforce or HubSpot, is built on exactly this foundation. Once you can see the objects and their links, you can read any CRM ever made.

A CRM links a company to its many people, associates deals with the company and specific people, and attaches every activity to a person, company, or deal so it rolls up across all of them, producing a single 360-degree view; leads sit outside as raw prospects until converted.