Lead, Contact, Company, Deal: What Each One Means in a CRM

A lead is someone you know almost nothing about yet. They submitted a form, replied to a cold email, attended a webinar, or came from a list someone built. You have their name. Maybe an email address. That is usually about it.

A lead record is a holding space. It says: this person might be worth a conversation, and we have not checked yet.

Most leads turn out not to fit. The job of a lead stage is to hold the signal until someone qualifies whether it belongs in the sales process. Some teams skip leads entirely and add people directly as contacts. Others use leads as a separate inbox for unqualified names. Both approaches work, as long as the team is consistent about which one they chose.

The important thing: a lead is not yet in your sales process. It is a signal that someone might belong there.

A contact is a real person you are in a relationship with, or are trying to be. They have been qualified (or added directly because you already know them). They have a full record: name, title, company, how you met them, what you have discussed, what the relationship is like.

Contact records hold:

One person can be a contact at more than one company over time. This matters in B2B sales, where contacts change jobs but stay in your network. A well-structured CRM keeps the relationship with the person even when their employer changes.

• Interaction history (calls, emails, meetings)
• Notes and context about who they are
• A link to the company where they work
• Their role in any active deals

A company is the organization where a contact works, or the account you are managing or pursuing.

In most B2B CRMs, companies and contacts are separate records that link to each other. One company can have many contacts. One contact can move between companies.

Why keep them separate? Because the company relationship often outlasts any individual contact. If your main champion leaves, the account might still be worth pursuing. Company records hold:

Some CRMs call companies "accounts" instead. Same concept.

• All the people at that organization
• All deals tied to that account
• The overall activity history at the company level

A deal is a specific sale you are working toward. It is tied to a company, involves one or more contacts, and moves through stages until it closes or goes away.

A deal record tracks:

A company can have multiple deals over time. A single deal can involve multiple contacts at different levels. The deal record is where pipeline management happens.

• What you are selling and roughly what it is worth
• What stage it is at (discovery, proposal, negotiation, and so on)
• Who the key contacts are and who has decision authority
• What happened last and what comes next
• When you expect it to close

The basic flow goes: Lead to Contact to Company to Deal.

Someone submits a form (lead). You check if they are worth pursuing and create a contact record. You add or link their company. You open a deal tied to that company.

The contact record captures the relationship history. The deal record tracks the commercial progress. The company record sits above both and shows the whole account picture.

The common mistakes:

None of these are hard mistakes to make. They happen most often when a team has not agreed on what each record type is for.

• Logging conversations inside lead records instead of converting to a contact first
• Adding deals to a contact instead of to a company, so you cannot see all deals for one account in one place
• Creating a new company record every time a contact changes employers, instead of updating the contact link
• Having both a lead and a contact record for the same person, with relationship history split across both

Tiago once worked alongside a business development team in Lisbon where nobody had explained the distinction between leads and contacts when the CRM was set up. For two years, the team logged every conversation inside lead records because that was the first record type the system opened for new names. The actual contact records were empty. The deal records had no history. The only place anything useful existed was inside records the system was supposed to use only for unqualified signals. When a new account manager joined and tried to understand the pipeline, she had to reconstruct months of context from email threads.

"It was not anyone's fault," Tiago says. "Nobody told us what a lead was for. So we used it for everything."

Lumenbase uses the standard four record types: Leads, Contacts, Companies, and Deals. A lead can be converted to a contact and linked to a company in a single action. Deal records attach to companies and pull in the relevant contacts. The account timeline on a company record shows everything that has happened across all contacts and deals for that account, so the relationship history is always in one place.

Anyone new to using a CRM, or who has used one for a while but never felt clear on why the record types are separate. Also useful for team leads setting up a new CRM before bringing in new hires, and for anyone trying to figure out why a CRM feels messy and where the duplicates are coming from.