Leads disappear when the pipeline is only a list of statuses

Direct Answer

Use a small pipeline with a next-action rule at every stage.

A record should either move forward, move to nurture, or close. If it can sit forever with no owner, date, or next action, the pipeline is broken.

The goal is not to build enterprise CRM logic. The goal is to make sure every active lead has a visible state and a decision rule.

A Pipeline Is A Queue With Rules

A pipeline is not a memory palace for old opportunities. It is a queue that tells the team what should happen next.

Each stage should answer three questions:

Question	Why it matters
What has already happened?	Prevents duplicate outreach and confused handoffs
What must be known before the record moves?	Keeps stages from becoming vague labels
What is the next action and date?	Stops leads from aging quietly in the system

The non-obvious insight: fewer stages usually create better discipline. A pipeline with 18 micro-stages can still lose leads if no stage forces an action.

The Minimum 7 Stages

Run these in a CRM or a spreadsheet. The names are simple on purpose.

Stage	Meaning	Exit rule
New	The lead has been added and enriched but not contacted	Contact it, disqualify it, or move it to nurture
Contacted	Touch 1 has been sent	Send the next touch, receive a reply, close, or nurture
In conversation	A reply or live exchange exists	Answer the question, handle the objection, book a meeting, close, or nurture
Meeting	A meeting is scheduled or completed	Record outcome, next step, and owner
Proposal	Scope, timeline, and metric have been sent	Move to won, lost, follow-up, or nurture with a date
Won / Lost	The opportunity has a final sales outcome	Record reason and stop active selling
Nurture	The account is not active now but deserves a future touch	Set the next action date and trigger reason

Won and Lost can be separate CRM statuses if your tool supports them. In a small spreadsheet, one final outcome field is enough.

What Each Stage Must Record

The stage is only useful if the required fields are filled in. Empty fields are how leads disappear.

Stage	Required fields
New	Company, contact, role, source, ICP fit note, verified signal, owner
Contacted	Channel, message variant, date contacted, next action date, stop condition
In conversation	Reply summary, objection or question to answer, owner, next response date
Meeting	Attendees, agenda, workflow, success metric, meeting date, next step if fit
Proposal	Scope, timeline, success metric, price or package, decision owner, follow-up date
Won / Lost	Outcome, reason, date, source, lesson learned, possible future timing
Nurture	Reason for nurture, missing signal, next action date, useful content or trigger to watch

Do not let a record enter a stage without the fields that make that stage actionable. "Contacted" without next action date is just a sent-message archive.

The No-Stuck Rule

No stage should allow a lead to sit without a scheduled action.

Use this rule in every weekly review:

If the record has...	Then...
A clear next step and date	Keep it active
A reply that needs an answer	Move to In conversation and assign an owner
No response after the planned follow-up window	Send the next approved touch, close, or nurture
Missing fit evidence	Move back to research or skip it
No real reason to act now	Move to Nurture with a trigger and date
A final yes or no	Move to Won / Lost

"Stuck" is not a stage. It is a management signal that the pipeline rule failed.

Weekly Pipeline Cleanup Ritual

Once a week, review every active record and force a movement decision.

Step	Action
1	Sort by next action date and find overdue records
2	Check every New lead for minimum enrichment and ICP fit
3	Move Contacted records to next touch, In conversation, Nurture, or close
4	Confirm In conversation records have one question or objection to answer
5	Confirm Meeting and Proposal records have an owner, date, and success metric
6	Move anything without a real next action to Nurture, Won / Lost, or Skip
7	Write one lesson from the week: source quality, message variant, stage leak, or objection pattern

The ritual should be fast. If cleanup takes hours, the daily stage rules are too loose.

What To Avoid

Avoid pipeline design that creates activity without decisions.

Pattern to avoid	Better rule
Too many micro-stages	Use fewer stages with stricter required fields
"Follow up someday"	Set a next action date or move to nurture
Meetings with no success metric	Use the meeting stage only when the agenda and output are clear
Proposals with no owner	Do not send a proposal without a decision owner and follow-up date
Lost reasons that say "no response" only	Record whether the issue was fit, timing, role, price, trust, or no evidence

This keeps the pipeline from becoming a status graveyard.

First Action

Create or clean one pipeline view with these columns:

Column	Fill it with
Company and contact	Who the record is about
Stage	New, Contacted, In conversation, Meeting, Proposal, Won / Lost, or Nurture
Owner	Who moves it next
Verified signal	Why this record deserves attention
Last action	What happened most recently
Next action	What happens next
Next action date	When it happens
Missing field	What must be filled before the stage is valid

Then review the current active pipeline. Any record without a next action date moves forward, moves to nurture, or closes today.

Next Move

Use ICP scorecard qualification before adding leads to New so the pipeline does not inherit weak prospects.

When a reply becomes a possible meeting, use meeting booking checklist before moving the record to Meeting. For follow-up control, connect Contacted and In conversation records to follow-up automation framework.