04
The probability problem
The number in your CRM is a guess. Every decision downstream is built on it.
Every pipeline review, every sales forecast, every revenue projection in your world includes a probability attached to each open deal. The number is in your CRM. The number drives hiring, capacity planning, cash flow projection, what you tell your accountant, what you tell your team.
The number is also a guess. The deal creator looked at the deal, thought about how the last conversation felt, typed "70%" into a field, and moved on. Every downstream decision is built on top of a number a human typed while looking at the ceiling.
Pipeline reviews are exercises in collective guessing→ observable behaviour
Forecasts are grounded in typed intuition→ engagement signal
Deals slip past recovery because nobody noticed→ decay alerts fire
Clinch's decay tracking is not "alert me when my client goes cold." It is the architectural fix to the probability problem. It monitors how each deal is actually behaving — which sections the prospect viewed, how long they spent, how many times they returned, where they paused, when they stopped opening it. The behaviour pattern is a measurable signal. Probability stops being a guess and starts being a function of what the deal is actually doing.
A deal opened three times in 48 hours with twelve minutes on pricing and two returns to scope has a measurable probability profile. A deal opened once and never touched again is a different signal entirely. The system reads both. The human typing a number cannot.
Scenario
A B2B principal walks into Monday's leadership meeting with eight open deals. Six have typed probabilities. Two are blank. Clinch shows the actual engagement reality — three "high probability" deals untouched for eleven days, and one "low probability" deal opened seven times with twenty-three minutes on the integration section. The forecast they present is no longer a collection of guesses. It is grounded in what each deal is actually doing.