Explainer
Lead, contact, company, deal: what each one means in a CRM
CRM software uses four terms that should be simple. They are not, because different tools define them differently, and teams often inherit setups without anyone explaining the logic. This article explains what each record type is for and how they relate to each other.
Why this matters more than it seems
Tiago has worked with several B2B teams in Lisbon and Porto where the CRM was technically "set up" but practically useless. The reason, more often than not, came down to record type confusion. Leads were in the contacts table. Deals had no company attached. Notes were on records nobody checked. The data existed but told no coherent story.
When a team does not agree on what each record type means, everyone develops their own interpretation. One salesperson logs calls on the contact. Another logs them on the deal. A third puts everything in a note on the lead and never converts it. After a year, the CRM holds information about your customers, but you cannot actually use it to understand your customers.
The good news is that the logic behind leads, contacts, companies, and deals is not complicated. You just need to know what each one is actually for.
The four record types, defined
Lead
An unqualified prospect. You have a name, maybe an email or a LinkedIn profile. You have not confirmed this person fits your target customer profile or has any interest in what you sell. A lead is a placeholder, not a relationship.
Contact
A qualified person. You have spoken to them, confirmed their role, and established some kind of exchange. A contact is a real relationship that deserves tracking. They may or may not be part of an active deal right now, but you want to maintain a history with them.
Company
The organization a contact belongs to. Companies outlive individual contacts. People change jobs, but the account remains. Deals, invoices, and relationship history all attach to the company, not just to the individual people who work there.
Deal
A specific commercial opportunity with a company. It has a stage, a value, and an expected close date. One company can have multiple deals at once, and deals from years ago stay in the history even after they close.
What is a lead?
A lead is a name you have not yet qualified. You might have picked it up at a trade show, pulled it from a website, received it in an inbound form submission, or imported it from a list. You do not yet know if this person is a real prospect for your business.
The purpose of the lead stage is to hold unverified information separately from your real contact database. When you qualify a lead and confirm they are worth pursuing, you convert them: the lead becomes a contact, and usually a company record is created or linked at the same time.
Some teams skip the lead stage entirely. If everyone who comes into your CRM is already qualified because they came through referrals or a very specific inbound source, there is no value in a separate lead queue. The lead stage exists to manage the gap between "we have a name" and "we have a real prospect."
What is a contact?
A contact is a person you have a real relationship with, or at least a relationship you intend to maintain. They are in your CRM because they matter to your business: they are a current client, a past client, a prospect you are actively talking to, or someone whose relationship you want to preserve for the future.
Contacts belong to companies, but they are not the same as companies. You track a contact because you have a relationship with a person. That relationship has history: calls, emails, meetings, notes. It follows the person, not the organization. If a contact moves from one company to another, they remain a contact in your CRM. The company link changes, but the person and their history stays.
Multiple contacts can belong to one company. In a typical B2B deal, you might have the decision-maker, a technical evaluator, a finance contact, and a day-to-day implementation person. Each is a separate contact record, all linked to the same company.
What is a company (or account)?
A company is the organization. This is where the long-term account history lives: every deal you have ever had with that organization, every contact who works there, every invoice, every note about the relationship as a whole.
Companies outlive individual contacts. The person who signed your first contract may have left. Three more people may have come and gone since then. The company relationship continues regardless. If you log everything at the contact level and never at the company level, you lose the account view the moment someone leaves.
Some CRMs call this record an "account" instead of a company. The concept is the same. It is the organizational entity that your commercial relationships belong to.
What is a deal (or opportunity)?
A deal is a specific commercial opportunity. It belongs to a company and involves one or more contacts, but it is a distinct record because it has its own properties: a stage, a value, an expected close date, and a history of activity related to that sales process.
One company can have multiple deals at different stages. A client you sold to two years ago might have three closed deals in history and one open opportunity in the pipeline right now. Keeping deals as their own records means you can review the pipeline without mixing it up with account management, and you can look at a single account's commercial history without sifting through your entire deal list.
Some CRMs call this record an "opportunity." Again, the concept is the same: a defined commercial transaction with a company, tracked through stages from open to closed.
How the four connect
The standard flow goes like this. A new name arrives as a lead. You qualify them: the lead converts to a contact, and a company record is created or linked. Once the commercial conversation starts, you open a deal on the company. The deal moves through stages. It closes won or lost. The contact and company stay in your CRM for the long term, even after the deal is closed.
Lead to contact: a one-time conversion, with the lead record archived or merged into the new contact.
Contact to company: an ongoing link. One contact belongs to one company at a time, but the link updates when someone changes jobs.
Company to deals: a company can have many deals, past and present. Each deal is its own record with its own history.
Contacts to deals: contacts are linked to deals as participants. The deal belongs to the company, not to any one contact. If your main contact leaves mid-deal, you link in the replacement without losing the existing deal history.
Where teams go wrong
Logging notes on the wrong record
Notes written on a contact but not connected to a deal get lost when the deal is reviewed. Notes on a deal that never mention who said what become hard to act on. Put context about people on contact records and context about the commercial transaction on the deal.
Confusing contacts with leads
Some teams put every new name into contacts regardless of qualification. Others push everyone through a lead stage even when the relationship is already established. Either way, you end up with a list that mixes real relationships with speculative names and no clear way to tell them apart.
Deals with no company attached
When a deal floats without a company record, you lose the account view. You cannot see past deals, other contacts at the same organization, or whether a colleague already has a relationship there. A handful of orphaned deals is a minor inconvenience. Several hundred is a corrupted history.
Duplicate records from different entry points
A contact imported from LinkedIn, created manually by a salesperson, and added from a form submission can easily become three separate records. Without deduplication, the history splits. Conversations logged against one version are invisible when someone looks at another.
How Lumenbase handles this
Lumenbase is built around the same four-record model, with a few decisions that keep the structure clean by default.
- Clear separation between leads and contacts. Leads stay in their own queue until converted. Once converted, the contact record carries the full history forward, including what came in during the lead stage.
- Contacts linked to companies automatically. When you add a contact and their company, the system creates or matches the company record and links them. No manual association step required.
- Deals tied to both companies and contacts. Every deal record shows the company it belongs to and the people involved. If a contact changes companies, the deal stays with the organization it was about.
- Duplicate detection on import. When you import contacts or companies from a spreadsheet or integration, Lumenbase flags likely duplicates before they enter the database.
- Full timeline per company. The company record shows all contacts, all deals (open and closed), all emails and meetings, and all notes, regardless of which team member created them.
Who this is for
Anyone setting up a CRM for the first time, anyone inheriting a CRM that is a mess, or anyone trying to explain to their team why the records are organized the way they are. If you have ever looked at a CRM and thought "I know there is information in here somewhere, I just cannot find it," there is a good chance record type confusion is part of the problem. This article also helps when onboarding a new team member who has never used a CRM before and needs to understand why things are structured the way they are.