Lead, prospect, client: what actually changes between them
Lead, prospect, client. Three words that get swapped around in the same meeting by the same people, and nobody stops to ask whether they mean the same thing. They don't, and the difference is not a vocabulary nicety. It decides who you chase this week, what you say to them, and whether your pipeline number means anything at all.
I have sat in pipeline reviews where a rep called something a prospect because they felt good about it. No reply, no call booked, no stated problem. Just vibes and a LinkedIn connection. That deal was never going to close, and the forecast said it was 40% likely, because the label was doing the lying.
This is the version I actually use.
The ladder is about evidence, not enthusiasm
Each step up costs the other person something. A lead costs them nothing: they exist and they look like they might have the problem. A prospect has spent time on you, answered something, told you a fact about their situation. A client has spent money.
That is the whole model. You move someone up when they give you evidence, not when you get excited. If you cannot name the specific thing they did that moved them, they have not moved.
A lead is a name with a reason to exist
A lead is someone who fits the shape of a buyer and has done nothing yet, or almost nothing. They downloaded a guide. They came in from a form. You pulled them off a list because their job title and company size match the people who buy from you.
The crucial part is the reason. A name with no reason attached is not a lead, it is a row in a spreadsheet, and treating a purchased list as a pile of leads is how teams end up with a pipeline that is 90% fiction. If you cannot finish the sentence "this person is on my list because...", delete them. I have written more about how to define that shape properly in what an ideal prospect looks like.
Leads are cheap and plentiful and almost worthless individually. Their value is in volume and in the fact that some fraction will answer.
A prospect is a lead you have checked for fit
This is the step everyone fudges. A prospect is a lead you have qualified, which means you know at least something real about them that you could not have guessed from the outside: what they are using today, what is broken, who signs off, roughly when they might act.
Not all of it, but enough to check fit: roughly the right size, a real need and a plausible timeframe. An answer alone is not enough, because a contact can reply and still be a poor fit. The evidence has to meet those criteria, and it has to have come out of their mouth or their keyboard, not your assumption. BANT, MEDDIC, whatever framework you like, they all boil down to the same thing: has this person told you enough that you can predict what happens next.
Sales tooling blogs mostly agree on the shape of this, and Close's breakdown of lead versus prospect versus opportunity is a decent sanity check if your team is arguing about definitions. What matters more than which framework you pick is that one person owns the definition and applies it the same way every Friday. I have gone into the mechanics of that in prospect and qualify.
A client has paid, and most teams stop caring at exactly the wrong moment
A client has signed and paid. That is it. No asterisk.
What I find odd is how much effort goes into the lead-to-prospect step and how little goes into the fortnight after someone becomes a client. That is where churn is decided, where the second contract is either obvious or a fight, and where referrals come from. The first onboarding call is worth more attention than the fifth follow-up email, and almost nobody resources it that way.
Getting the labels wrong quietly wrecks your forecast
Two things break when the definitions drift.
Your forecast inflates, because prospects are counted by feel. And your messaging goes generic, because if you cannot tell a lead from a prospect you end up writing one email that tries to serve both, which means it introduces yourself to someone who already knows you and pitches a solution to someone who has not admitted a problem. That email gets ignored by everybody, fairly.
The fix is boring. Write the definition down, stick a required field in the CRM behind the stage change, and audit it monthly. If you want a starting structure, the prospect tracker template covers the fields worth making mandatory, and client prospecting walks the whole path end to end.
The stage where people stall is the one nobody instruments
This is the part of the ladder I got wrong for years, and the one I keep coming back to.
Most of the movement from prospect to client happens inside a document. You send the proposal, the scoping doc, the deck, the pricing sheet. Then you wait. And in that gap you have no idea whether they read page four, where the pricing sits, or whether they forwarded it to a finance person who has never heard of you and read only the number.
I spent years in growth roles at DataBees and WaterFull sending exactly those documents and guessing. The stage name in the CRM said "proposal sent" and I treated that as progress, which it is not. A sent document is not a read document.
That gap is why I ended up building LiveDocument with my co-founder Joe. You attach a recorded video walkthrough to the PDF or image, share it as one link instead of an attachment, and see which pages someone actually spent time on. It is not a CRM, it will not qualify anyone for you, and it does not do watermarking or NDA walls, so if that is your requirement look at DocSend instead. What it does do is turn "proposal sent" into something you can read. If you want the tracking side specifically, that is PDF tracking software, and the wider sales picture sits on our sales use case page.
Questions people ask about this
Is a prospect always a lead first?
In a clean process, yes. Someone becomes a lead the moment they enter your world with a reason attached, and a prospect once they have given you real information. Referrals feel like an exception because they arrive half-qualified, but they still have to be qualified before you can forecast them.
What is the difference between a prospect and an opportunity?
An opportunity is a prospect with a deal attached: a defined scope, a number and a rough date. Some teams collapse the two, which is fine as long as everyone collapses them the same way.
Where do MQL and SQL fit into lead, prospect, client?
MQL is a lead that marketing thinks is warm. SQL is a lead sales has agreed to work. Both sit inside the lead-to-prospect step, and they exist mainly so marketing and sales can argue with a shared vocabulary.
Can someone go backwards?
Yes, and you should let them. A prospect who goes quiet for a quarter is a lead again. Pretending otherwise is how a pipeline fills up with ghosts.
If you take one thing from this: move people up the ladder on evidence they gave you, not on how the call felt. And if the evidence you are missing is what happened after you sent the document, that is fixable, which is roughly why livedocument.com exists.
About the Author
Cameron JamesCameron is the founder of LiveDocument. He writes about sharing documents, PDFs, decks and contracts, and why pairing a video walkthrough with a document beats sending it cold.