Your pipeline is only as honest as your stages

Open a CRM nobody agreed on and you find the same thing every time. A dozen stages. Half of them mean the same deal. A “status” field fighting the stage for the same job. And three teams, each certain their version is the real one.

That CRM can’t tell you anything. Not because the data is missing — because the data disagrees with itself. Every report is an average of four definitions, and an average of nonsense is nonsense with a decimal point.

A stage is a promise, not a bucket

A stage should answer one question: how close is this deal to becoming money? Prospecting, qualified, proposal, negotiation, closed. Each one is a promise that specific things are true and specific things have happened before a deal is allowed to sit there.

When stages stop meaning that, they turn into buckets — somewhere to drop a deal so it’s off your list. “Nurturing” becomes the graveyard. “On hold” becomes the other graveyard. And the pipeline number the board sees is built out of graveyards.

Stage and status are two different questions

People collapse stage and status into one field and then wonder why nothing reconciles. They answer different questions. Stage is where the deal sits on the path to closed. Status is what’s happening to it right now — active, stalled, waiting on the customer, waiting on us.

Salesforce makes the split obvious if you let it. A Lead has a Status: Open, Working, Nurturing, then Qualified or Unqualified. An Opportunity has a Stage, and each stage carries a probability and a forecast category behind it. Different field, different object. A Lead becomes a Contact, an Account and an Opportunity the moment it converts. Treat Lead Status like an Opportunity Stage and you’re reporting on two things through one number — which is reporting on neither.

Nothing lives in a temporary stage forever

Every stage needs a shelf life. Not a rule for its own sake — a smoke alarm.

A lead that’s been “qualified” for ninety days isn’t qualified; it’s a decision nobody made. A deal parked in “proposal” for a quarter isn’t a proposal, it’s a no that hasn’t been said out loud. The temporary stages are the worst offenders — “on hold,” “follow up later,” “nurturing” — because they feel like progress, and they’re where deals go to quietly die.

Put a clock on each stage. When a deal sits longer than the stage should ever take, something moves it: a task, a flag, a demotion back to reality. The automation isn’t the point. The point is that stuck becomes visible instead of invisible. A forecast built on deals that haven’t moved in months is just optimism with a date attached.

Agree where it came from before you argue who gets credit

Attribution fights are never really about data. They’re about credit. Marketing says the webinar sourced it. Sales says they’d been working the account for months. Same deal, two stories, no way to settle it after the fact.

The only fix is to agree the model before the deal exists, not after it closes. First touch, last touch, or weighted across the whole path — pick one, write it down, and make the CRM record it the same way every time. Salesforce will run multi-touch with Campaign Influence if you set it up. It will also happily let a rep overwrite Lead Source with whatever they typed last. One of those is a model; the other is a guess wearing a field name. And the source has to be captured where it happens — on the Lead, carried through conversion to the Opportunity — or it’s gone. A deal that can’t tell you where it came from can’t tell you what to do more of.

Design it for the people who live in it

None of this holds if the people in the CRM every day don’t recognise it as theirs. A stage model built in a strategy meeting and handed down gets ignored by the reps clicking it forty times a day.

So you watch how they actually work first. Where they hesitate. What they skip. Which field they fill with junk because it’s mandatory and means nothing to them. Then you design the stages, the statuses and the source fields so filling them in correctly is the easy path, not a tax on top of the real job. That’s the difference between a CRM people actually use and one they work around.

Adoption isn’t training people to use a system. It’s building a system people don’t need training to use. Everyone in the cycle — marketing, SDRs, AEs, success — has to read the same stage and picture the same thing.

A CRM doesn’t give you insight. A CRM everyone agreed on does.