CRM playbook: pipelines that match how you sell

BF

The BrokerFold Team — Product + Engineering

Last reviewed

On this page
Sketching a sales process on a whiteboard before building it

Your CRM runs two funnels, and confusing them is where most pipeline frustration starts. Leads move through a fixed intake funnel — new, contacted, qualified, closed or lost — that you do not customize. Deals live on a separate Kanban board whose stages are entirely yours. The distinction, and why it exists, is covered in what are CRM pipelines and stages; this lesson is about designing the board so it tells the truth.

Step 1: write your real process down first

Before touching a setting, list what actually happens between “this person is serious” and “keys change hands” in your practice. Not the idealized version — the observable one. Most agents find five to eight genuine checkpoints. That paper list is your pipeline; the software just renders it.

Step 2: apply the evidence rule

A stage must mark something that verifiably happened: a showing booked, an offer drafted, a condition waived. “Thinking about it” and “very interested” are moods, not stages — a card sitting in a mood tells you nothing next Monday. If you cannot name the event that moves a deal into a stage, the stage does not belong on the board.

Step 3: start from the defaults and rename

The board seeds six stages on first use — New Lead, Contacted, Qualified, Showing, Offer, Closed — which is a sound skeleton. Rename them into your own language, reorder to match your sequence, and add at most one or two of your own. Renaming matters more than it seems: a board written in your vocabulary gets used; one written in generic-CRM gets ignored.

Step 4: put value and a close date on every card

The board’s KPI strip totals pipeline value and won value — numbers that are only as honest as the cards beneath them. A deal without a dollar value and an expected close date is a sticky note, not a deal. Fill both at creation, revise them when reality moves, and the weekly ops review inherits a board it can actually read.

Step 5: prune with the guardrails, not against them

A stage that still holds deals refuses deletion — you move the deals first, deliberately. That friction is the product protecting your history. Use it as a design check: if emptying a stage feels arbitrary, the stage never meant anything. Keep the board lean the same way you keep routing rules lean — every element earns its place or goes.

What done looks like

Anyone on your team can look at the board cold and answer two questions for any card: what happened to put it here, and what has to happen next. Column totals you would defend to your accountant.

The mistake that costs the most

Stages that describe paperwork instead of commitment. Five flavours of “waiting” spread deals into columns that all mean the same thing, and the board stops answering the only question it exists for: how close is the money, and where is it stuck.

Frequently asked questions

Should buyers and sellers get separate pipelines?

You run one deal board, so design stages around commitment rather than deal type — Showing and Offer describe both sides of a transaction honestly. Let the deal title carry the side (buyer or listing) and the card's value carry the economics; the board's job is telling you how close each deal is to closing.

How many stages is too many?

The board allows up to twenty, but a working pipeline usually reads best at six to eight. If two adjacent stages always move together, they are one stage. If a stage has held the same deals for a month, it is probably describing a waiting room, not a commitment.

Keep reading

Fold your stack into one.

14 days free. No credit card. Your data stays yours.