What Is a Customer Prospect? Prospect vs Lead vs Client

What is a customer prospect, in one sentence?

A customer prospect is a person at a company that fits your ideal customer profile (ICP) and could buy from you, but has not bought yet. "Prospective customer" and "prospective buyer" mean the same thing. Take a software firm that sells to building contractors: the head of procurement at a 300-person contractor that fits its buyer profile is a prospect, even before she has heard of the firm. The day she replies, she becomes a lead.

The quickest way to keep the related words apart: a prospect is about fit, a lead is about response, a customer is about a signed deal. Before the prospect sits the suspect, a company nobody has checked yet. After the customer comes the client, a buyer you keep working with.

The word shifts a little between departments. Some teams use "prospect" for anyone on a target list, checked or not. Adobe's guide to leads vs prospects says some people use lead, prospect and opportunity interchangeably, but they describe different types of prospective customers.

Inbound-minded guides put the prospect after the lead. Adobe puts it in one line: "A prospect is a qualified lead."

I use the outbound meaning: someone whose company and title have been checked and who is worth a direct approach by name, before any contact. And I am strict about it. A name only counts as a prospect on my lists once someone has compared the company with the client's existing buyers and found the person who really signs off on that kind of purchase. Until then it is a suspect, however good the logo looks.

The trouble starts when marketing and sales share one CRM and one monthly report, and each team counts a different group under the same word. The pipeline number then means two things at once.

Why do vendors disagree on whether the prospect comes before or after the lead?

Read a few CRM guides and you will find the prospect placed before the lead in some, after it in others. The disagreement comes from which team the writer had in mind.

Inbound teams meet the lead first. Someone fills in a form, downloads a guide or starts a trial. That person is a lead the moment they act. Sales then checks whether they are worth a real conversation, and the ones who pass get called prospects or sales qualified leads.

Outbound teams meet the prospect first. You choose a company that fits and a person inside it who decides. That person is a prospect before they have ever heard of you. They become a lead only when they reply.

My team works mostly through cold email and LinkedIn outreach, so on our side the prospect always comes before the lead. I treat the first reply as the moment a prospect becomes a lead, because a reply is where a conversation starts.

The two CRMs most founders meet first show the same split. HubSpot's default lifecycle stages run Subscriber, Lead, Marketing Qualified Lead, Sales Qualified Lead, Opportunity, Customer, Evangelist and Other (HubSpot lifecycle stages).

There is no stage called prospect. The closest is the Sales Qualified Lead, which HubSpot defines as a contact or company that sales has vetted as a possible buyer. That is the inbound meaning of prospect, sitting after the lead.

Microsoft's Dynamics 365 Sales works with lead records and opportunity records. Qualifying a lead confirms it is a genuine sales opportunity, links an account and a contact to it, and creates the opportunity record.

Microsoft's own example of when to qualify is a prospect who shares their budget and a firm timeline for deciding (Microsoft Learn, Dynamics 365 Sales). In that product, "prospect" is just the person behind the lead record.

Decision rule: Any order works if it is written down. Pick one, write a one-line entry rule for each stage and map every rule to the stage names your CRM already has. If you run inbound and outbound side by side, keep one order and add a source field, so a lead from a form and a lead from a cold reply never get counted as the same thing.

Suspect, prospect, lead, opportunity, customer, client: which stage is which?

Here is the full ladder in the outbound order, with the CRM names next to each rung. Qualification sits between lead and opportunity as a gate, a quick check every lead passes through before a deal opens.

A few boundaries cause most of the arguments.

Suspect vs prospect. The only difference is the fit check, and it is easy to skip. A list bought by industry and headcount is a list of suspects. It becomes a prospect list once somebody has confirmed that each company resembles your buyers and that each name decides something.

Lead vs opportunity. A reply is a lead. A reply that says "sounds interesting, send me a time" is still a lead until it clears the gate. The four signals in the gate row do that work. Customer qualification covers the method and the questions behind each signal.

Opportunity vs customer. Booking a meeting and closing a contract are two different jobs, so on my reports a booked meeting stays an opportunity until the paperwork is done. When I review a campaign, I count booked, attended and closed as three separate numbers, because a gap between any two of them points to a different problem.

Customer vs client. A customer has bought. A client has a relationship that keeps going: a retainer, a renewal, a second project. The practical difference is who owns the record: a customer can stay with whoever closed the deal, while a client needs an owner whose job is keeping the relationship.

Is the prospect a person or a company?

Both, and in B2B each needs its own stage. The company is the account, and it either fits your ICP or it does not. The person is the contact, the one you actually write to. It is the same split that separates an ICP, which describes the company, from a buyer persona, which describes the person.

The account decides whether anyone there is worth contacting. The contact decides whether your message lands at all. A perfect account with the wrong person on the record is still a suspect. Period.

Getting the person right starts from evidence you already have:

• My starting point is the client's existing and former customers, and from there I look for similar companies.
• On every past deal I work out who actually made the buying decision.
• I search with the titles that niche really uses for that person, such as Head of Procurement or Project Director, instead of a plain "manager".
• I strip generic titles such as Assistant, Manager and Associate out of the target list entirely.

A construction company might buy through a head of procurement on one project and a project director on another. A software firm might buy through a VP of IT. A "decision maker" filter in a lead tool does not tell you which of these titles signs off on your kind of purchase.

Two more rules follow from the split. One account can hold several prospects, and each one needs its own stage and its own message, because a project director and a procurement head care about different things.

And an account can be a customer while a contact there is still a prospect. If you sold to one division, a second division with its own budget starts again at the prospect stage. Mark the account as a customer and the new contact as a prospect, or your reports will count a cold name as a warm one.

On my campaigns each account gets one owner, and nobody else on the team contacts that company.

How many prospects become customers? One labeled outbound funnel

One LinkedIn account, 30 days, 1,200 people contacted. That was one of our campaigns, and each count below carries its rung from the ladder.

The campaign data has no separate row for the fit check or the qualification gate, so read those rungs as folded into the rows above.

Mislabel the 289 replies and you fix the wrong thing next month. Call them prospects and the list looks weak. Call them pipeline and you expect dozens of deals, then kill the campaign in month two. I see founders do this all the time.

A reply count this size is why volume matters. A handful of hand-picked "perfect fit" names cannot show you whether the list is weak, because a buyer who is busy, not ready yet or simply not interested looks exactly like a bad fit. Judging a campaign on a few dozen names is a lottery ticket.

The steepest percentage drop in the table sits between the 289 replies and the 21 people who said they were interested, about 7%. A reply is only a lead, which is where prospecting ends and lead generation begins. That is why I never report replies as pipeline: I count conversations first, because meetings come out of conversations and customers come out of meetings.

The filter from suspect to prospect is what keeps the top row honest. When Gartner surveyed 632 B2B buyers in August and September 2024, 73% said they actively avoid suppliers who send irrelevant outreach (Gartner). Writing to unchecked suspects is the quickest way to become one of those suppliers, and to fill your CRM with unqualified leads.

What should a prospect record contain? A template

Copy these fields into your CRM or a shared sheet. The sample column describes one invented prospect, so you can see what a filled-in record looks like.

Do not skip the touch count. Without it you cannot tell a dead prospect from one the sequence gave up on too early. One or two messages will not do it; I plan at least 5 to 6 touches per prospect, on more than one channel where I can.

The third follow-up often brings the reply in our campaigns. That holds when real time separates it from the second. If your records show most prospects stopping at touch 2, the sequence ended before replies usually arrive.

Keep fit and engagement as two separate scores. HubSpot's lead scoring tool does the same, splitting fit, based on details such as role, firm headcount or yearly revenue, from engagement, based on actions the contact takes (HubSpot lead scoring). A high-fit prospect with no engagement needs more touches. A low-fit lead with high engagement gets a polite no.

I put every prospect in a CRM, and which one barely matters. What matters is that nobody slips through.

Are you allowed to hold and email prospect data?

The data source, lawful basis and opt-out fields in the template exist because of the rules below. Here is a short summary of official guidance for the three markets my team writes to most. It is not legal advice.

The ICO page says its B2B guidance is being reviewed after the Data (Use and Access) Act, so reread it before you build a UK process on this summary. The EU row is also why the data source field carries a date: you cannot tell someone where their data came from if nobody wrote it down.

Most of my team's outreach goes to the USA, the UK and Europe. When a prospect sits in Germany, Austria or the Czech Republic, I keep the first touches on LinkedIn, and cold email waits until a compliant basis is on the record.

If your EU basis is legitimate interests, put the reasoning in writing before the first send. You can adapt this worked legitimate interest assessment example for cold email.

What to change in your CRM tomorrow

Write one entry rule per stage. Add a fit check, so no name counts as a prospect until it passes. Get the labels right first. Then scale the list. Not the other way round. Once the labels are right, outbound prospecting is the next step.

Not sure where your CRM draws the line between prospect and lead? Book a call and share your stage names. We will map them to one entry rule per stage.