Lifecycle stages look like a settings problem. They are actually the contract between marketing, sales and customer success, and most companies never signed it.
Pick five open records at random. Send them to a rep and to whoever owns marketing reporting, separately, and ask what stage each should be in. Count the disagreements. Two or more out of five and every stage based metric you report is noise.
A stage needs a condition that is either true or false. "Had a meaningful conversation" is not one. "Confirmed budget exists and named the person who approves it" is. The moment a stage requires interpretation, two honest people will interpret it differently, and your conversion rates become a measure of rep optimism.
Every extra stage is another place for a deal to sit and another judgment call. Most mid market pipelines work better with five or six stages that mean something than with eleven that describe an idealised process nobody follows.
Conversion by stage, time in stage, and stage based forecasting are the three things executives ask for most, and all three are built directly on top of a definition nobody agreed to. That is why the forecast argument never resolves: the disagreement is two layers below where people are arguing.
Usually five or six for a mid market B2B motion. The number matters far less than whether each stage has a condition that is objectively true or false.
The specific, checkable condition that must be met before a deal moves to the next stage. Without them, stage data measures how optimistic each rep is.
Revenue operations, with sign off from sales, marketing and customer success, because all three report on the same stages and all three are affected when they drift.
The writing takes a workshop. The harder part is migrating existing records and retraining the reporting built on the old definitions.
Leave an email and I will reply myself, usually the same day. No sequence, no newsletter, and no calendar link unless you ask for one.
Would rather just book time? Here is the calendar.
We use cookies to run the site and to understand how it is used. You can accept all or necessary only. See our privacy notice.Privacy notice