Loading
Pipelines with stages you define, entry criteria that must be satisfied before a deal can advance, deal records that keep every change to value, owner and close date, and weighted forecasting that shows the unweighted number beside it.
Alongside those sit the parts that make the rest legible: splits for deals with more than one owner, required win/loss reasons at close, readable scoring rules, and automation that fires on a stage change rather than on somebody remembering.
Because a pipeline starts as a shared language and ends as a filing convention. Stage names drift until two reps mean different things by "negotiation", probability is set once and never revisited, and close dates slide a fortnight at a time in increments too small for anyone to flag.
By the time the quarter is obviously wrong, the pipeline has been wrong for two months. Nobody can point at when it started, because nothing recorded the moment it did.
A stage change stops being an update to a sales system. Reaching Won opens delivery phases in Loop from the sold lines and a billing schedule in Books from the agreed terms, without a handover meeting and without anybody re-keying the sale.
It also means the forecast is arithmetic over rows the whole company can see. When a number is disputed, it can be opened to the deals underneath it, which usually ends the dispute faster than defending it does.
It will not stop a determined rep advancing a deal by filling in a field. Entry criteria make the claim explicit and auditable; they do not make it true, and a team that games them will produce a pipeline that is precisely and confidently wrong.
Nor will it price the work. What a deal is worth to you lives here; what it costs to deliver lives in Loop and Books, and margin is the comparison of the two.
Start with the stages you actually run rather than the ones a template suggests, and give each one entry criteria you are willing to enforce. A stage with no criteria is a label, and labels are what produced the forecast you are trying to replace.
Set probabilities per pipeline, not globally — a renewal at 60% and a new logo at 60% are not the same bet, and treating them alike is the most common reason a weighted forecast reads badly.
Loop opens delivery from won deals and reports variance against what was sold. Books bills from the terms and recognises the revenue. Desk sees account standing when it prioritises a ticket. Growth follows the campaign that produced the lead through to the closed number. Each reads the same deal row. None of them keeps a second copy, which is why they cannot quietly disagree about what was sold.
A stage change stops being an update to a sales system. Reaching Won opens delivery phases in Loop from the sold lines and a billing schedule in Books from the agreed terms, without a handover meeting and without anybody re-keying the sale.
It will not stop a determined rep advancing a deal by filling in a field. Entry criteria make the claim explicit and auditable; they do not make it true, and a team that games them will produce a pipeline that is precisely and confidently wrong.
Start with the stages you actually run rather than the ones a template suggests, and give each one entry criteria you are willing to enforce. A stage with no criteria is a label, and labels are what produced the forecast you are trying to replace.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.