Wholesaling pipeline stages: what must be true to enter and leave each one

Why do wholesaling pipelines leak?

A pipeline leaks when a stage change is a click instead of a decision. Picture a hypothetical team of six: an acquisitions rep moves a seller to "Offer made" after a phone call, the offer never goes out in writing, and the seller stops answering. Nothing in the CRM says the offer was never sent, so the deal looks alive for a month. Multiply that by forty open deals and your forecast is fiction.

Four things cause most of it:

• Stages describe the rep's activity, not the seller's situation. "Working" tells you what someone is doing, not what happens next.
• No exit rule. Anyone can move a deal forward with nothing filled in, so the data behind later stages is missing.
• No owner for the gaps. The hand-offs (cold caller to acquisitions, acquisitions to dispo) are where deals sit unclaimed.
• No clock. A deal can sit in one stage forever without anybody being told.

What are the eight stages of a wholesale or home-buying pipeline?

These are the stages I'd start a 10 to 50 person team on. Rename them to fit your shop, but keep the logic: each stage answers one question about the seller or the deal.

If your pipeline has a lot more stages than this, check whether some are really tasks or statuses. "Waiting on title" is a task. "Seller thinking about it" is a follow-up date. A stage should change what you do with a deal, not describe a to-do on it.

What are the four rules every stage needs?

1. An entry rule: one sentence a new rep could apply without asking you. "The seller signed" is an entry rule. "Looks good" is not.
2. An exit rule: the fields that must be filled in before the deal can move on. This is what makes the data usable later. If you need the offer date to measure speed to offer, the exit rule from "Appointment" has to ask for it.
3. An owner: one name or one queue, never "the team". The hand-offs need the clearest owners of all.
4. A clock: a maximum number of days before something fires: a task, an alert to the manager, a flag in the report. Choose the number from your own history, not a blog. Look at how long your closed deals took in each stage and flag anything well past that.

Write these four things for each stage on one page and review it with the team once. It takes an hour and it ends most arguments about whose deal something is.

Where do "not now" sellers go?

Not into Dead. A seller who says "call me in March" is a lead with a date, and the biggest source of reactivation deals you have. Give "Not now" its own handling:

• A required re-contact date and a reason (timing, price, another buyer, needs repairs done, probate pending).
• A task created automatically on that date, assigned to the original owner.
• A separate stage or status such as "Nurture", so it never counts in your active pipeline numbers.

Reserve Dead for sellers who bought elsewhere, listed with an agent, or said to stop. Keep the dead reason a short picklist (5 to 8 values), because that is what lets you see why deals die. The playbook for waking up parked sellers is in reactivating dead seller leads, and the cadence is in the follow-up cadence builder.

Should these be Lead statuses or Opportunity stages in Salesforce?

Both, split at the point where an inquiry becomes a real deal. Early stages (New lead, Contacted, and Nurture) usually fit the Lead record. The deal stages (Appointment set through Closed) usually fit the Opportunity. The split matters because an inquiry that never becomes a deal shouldn't clog your opportunity reports, and your forecast should only count deals. Where exactly to convert is covered in Lead, Opportunity or Property: how to model a seller in Salesforce.

How do you build this in Salesforce?

1. Path for the stages that matter

Path shows the stages as a bar at the top of the record. For each step you can pick up to five key fields and write up to 1,000 characters of guidance. Put the exit rule's must-have fields in the key fields, and put the entry rule and a two-line script in the guidance. Reps see what they need at the exact moment they move a deal.

2. Validation rules for the must-haves

Path is guidance, not enforcement. To make a field truly required, add a validation rule that blocks the move to a stage unless the fields are filled. Example: moving to "Under contract" fails with a clear message unless contract price, closing date and a signed contract link are present. Keep the messages specific ("Add the closing date before moving to Under contract") so reps know what to fix.

3. A stage-age alert

Add a date field that stamps whenever the stage changes, then a scheduled flow that finds deals past their time limit and creates a task for the owner, with a notice to the manager when it's past a second limit. A simple flow beats a dashboard nobody opens.

4. Stage history for free

Salesforce keeps a history of opportunity stage changes automatically, which is what lets you report on how long deals spend in each stage. Create a custom report type or use the "Opportunities with History" report type to see stage age and where deals get stuck.

5. Roles and permissions

Decide who can move a deal backward, who can reopen a Dead deal, and who can change a closed deal's price. Fewer people with those rights means cleaner numbers. If VAs work in the CRM, see who sees what.

Which three reports show whether the stages work?

1. Deals by stage and age: open deals grouped by stage, sorted by days in stage. The oldest rows are your first calls of the week.
2. Stage-to-stage conversion: of the deals that entered a stage, how many reached the next one, by source and by rep. This shows whether the leak is at the offer or at the contract.
3. Dead reasons: a count by reason and by source for the last 90 days. If "bought elsewhere" leads the list, the problem is speed or follow-up, not lead quality.

More report recipes are in 20 Salesforce reports for wholesalers and the five numbers I'd put in front of an owner every Monday are in the Monday 5.

What are the most common mistakes?

• Too many stages. Past eight or nine, reps skip stages and the data goes soft.
• Required fields on everything. If you require ten fields at stage one, reps will type junk to get past it. Ask for what you need at each step, no more.
• Dead as a parking lot. If nothing leaves Dead, you are throwing away your cheapest leads.
• Changing stage names without migrating history. Renaming a stage can break reports and any automation or ad-platform feed keyed to it. Plan stage changes like a small project.
• No review. Walk through the oldest ten deals in each stage once a week. It takes 15 minutes and it is the cheapest quality control you have.

If you want a second pair of eyes on your stages, this is exactly what the CRM Revenue Audit looks at first.

Questions

Related guides

Sources

Checked in October 2026. Salesforce and vendor features change with each release, so check the linked page before you rely on a detail.

1. Trailhead: Visualize Success with Path and Kanban. Up to five key fields and up to 1,000 characters of guidance per path step
2. Salesforce Help: Create or Edit Key Fields Using Sales Path. Where Path settings and key fields are configured