Real Estate Pipeline Management for Teams, Starting With the Deals Nobody Has Touched
Open your team's pipeline right now and sort by "last activity." We'll wait.
If your team looks like most teams we've worked with, the bottom of that list is a graveyard. Buyers who were "actively showing" in April. A seller who was "thinking about spring" two springs ago. A lead marked "hot" by an agent who left the team in August. Every one of those records is still counted in your pipeline total, which means the number you look at every Monday is wrong.
Good real estate pipeline management makes that number honest again. When you say the team has forty active buyers, you actually have forty people who want to buy a house and an agent who's working with each of them.
Start by agreeing what each stage means
Most messy pipelines have the same root problem. Every agent uses the stages differently.
One agent moves a buyer to "active" after the first phone call. Another waits until there's a signed buyer agreement. A third moves people to "active" when they feel good about them. Then you add it all up and call it a team pipeline. It isn't. It's three different pipelines that happen to share column names.
So before you clean anything, write down the rule for entering each stage. Keep it to things you can verify, not feelings. For a buyer pipeline it might look something like this (an example, adjust it to how your team works):
| Stage | A buyer belongs here when... |
|---|---|
| New lead | They've come in and haven't been contacted yet |
| Contacted | An agent has actually spoken with them (a voicemail doesn't count) |
| Appointment set | A consultation is on the calendar |
| Active | A buyer agreement is signed and they're seeing homes |
| Under contract | An offer is accepted |
| Closed | Keys handed over and the deal is funded |
Your listing pipeline needs its own stages, because listings don't move like buyers do. Wholesale deals, if you do them, need a third. Jamming all of them into one generic pipeline with a dropdown is where a lot of the confusion starts. We wrote more about that in our piece on repeatable workflows.
Once the definitions are written, share them in the team meeting and stick them somewhere agents will see them. Then enforce them. If a buyer is in "active" without a signed agreement, they go back a stage. No arguments.
Give each stage a time limit
Here's the part most teams skip. Every stage should have a rough maximum, the point where a deal sitting there stops being normal and starts being a problem.
You don't need a study to set these. Look at your own closed deals from the last year and see how long they usually spent in each stage. Then set the limit a bit past that. For example (made up numbers, use your own):
- Contacted with no appointment for more than 14 days
- Appointment set but the appointment date has passed and the stage hasn't changed
- Active buyer with no showing logged in 21 days
- Listing appointment held with no signed listing after 10 days
When a deal blows past its limit, someone should hear about it. Not in next month's review. That week. That's the whole idea behind alerts for missed follow ups: the system notices the stall so you don't have to scroll through a board looking for it.
The monthly cleanup
Once a month, set aside an hour and go through every record that's past its time limit. Do it with each agent, or ask each agent to do theirs before the team meeting. Either way, every stale record gets one of four outcomes:
- Still real. The agent has a next step and a date. Write both down on the record.
- Moved back. The buyer went quiet but hasn't said no. Move them back to an earlier stage (or into long term nurture) so they stop counting as active.
- Reassigned. The agent can't or won't work it. Give it to someone who will, today.
- Closed out as lost. Record the reason. "Bought with another agent," "decided not to move," "couldn't qualify." Those reasons are worth more than you'd think when you look at them across a year.
The first cleanup is painful. You might lose a third of your "active" pipeline on paper. That's fine. Those deals weren't really there.
After two or three months it gets fast, because there's less junk building up and agents know the records will get looked at.
What to look at in the weekly pipeline review
The monthly cleanup keeps the pipeline honest. The weekly review is where you use it. We'd keep it short and look at a few things only:
Movement, not totals. How many deals moved forward a stage this week, and how many moved backward? A pipeline that holds steady at forty buyers can be healthy or completely stuck. The total won't tell you which.
Conversion between stages, by agent. If one agent sets plenty of appointments but few turn into signed agreements, that's a coaching conversation about the consultation. If another agent signs almost everyone they meet but barely sets appointments, the problem is earlier. Same team, same lead sources, totally different fix. This is a great thing to take into an agent's one on one.
Deadlines in the next two weeks. Anything under contract with an inspection, appraisal, financing or closing date coming up. Those belong on a contract to close checklist with reminders, but the leader should still see the list.
Where the revenue comes from. Tie pipeline stages back to the lead source. It's useful to know you have twelve buyers under contract. It's more useful to know nine of them came from past client referrals and one came from the source you spend the most on every month. Our guide to lead source ROI goes deeper on that.
Pipeline management mistakes that undo all of this
Letting agents keep private lists. If an agent tracks their "real" deals in a notebook or a spreadsheet and leaves the CRM half updated, your pipeline is fiction no matter how clean the stages are. The fix is making the CRM the place where things actually happen (calls, texts, appointments, documents), so it's updated as a side effect of work instead of as extra homework.
Adding stages every time something goes wrong. Someone loses a deal at the appraisal and suddenly there's an "appraisal pending" stage. Then "appraisal received." Then "appraisal disputed." Six months later you have fourteen stages and nobody uses half of them. Keep stages for big changes in the deal, and handle the details with tasks and checklists inside the stage.
Reviewing the pipeline only when things feel slow. By the time it feels slow, the slowdown started six weeks ago. A short weekly look catches it while you can still do something.
Counting a deal twice. When a buyer is also selling, you've probably got two records. That's correct. But make sure your reporting doesn't count the same commission twice when you forecast.
How much of your pipeline management should be automatic
Defining stages and doing the monthly cleanup take judgment. That part is yours.
Almost everything else can run without anyone thinking about it: stamping the date a deal entered each stage, flagging deals past their time limit, logging calls and texts against the record, rolling up the pipeline by agent and by source. If your team is doing any of that by hand, it'll stop happening the first busy month. It always does.
Where BILLIONS fits
BILLIONS comes with separate buyer, seller and wholesale pipelines already built, so you aren't designing stages from scratch, and you can still adjust them to match how your team works. Activity is captured without manual data entry, deadlines and milestones trigger automated reminders, and real-time reporting shows pipeline by stage, by agent and by lead source. When something stalls, the right person gets an alert.
If you'd like to see what your own pipeline looks like on a real estate platform built for teams, schedule a demo. Bring a screenshot of your current board, stale deals and all.
See BILLIONS in action
The all-in-one CRM for real estate teams, built on Salesforce. Zero build-out required.
Schedule a Demo →