Revenue decision guide · Deal risk
Deal risk: act while the outcome can change
Turn a vague risk label into the missing condition, supporting evidence, accountable owner and next action for the live deal.
The operating question
A risk score isn't useful if the team can't see what raised it.
A deal turns red on Monday morning. The Manager sees it in the review, asks what changed and gets three possible answers: engagement fell, the close date moved and the score crossed a threshold. Nobody can see which source created the warning or what would make it clear again.
The deal is still red on Friday. Nothing happened in between because red is a description, not an action. The Seller disagreed with the score, the Manager had no condition to coach and the system had no named owner to follow up. When the deal later slips, the warning is counted as a correct prediction even though it changed nothing.
Risk has value only while somebody can still change the outcome. That requires a visible condition, its evidence, a next action and a person responsible for it.
Adding more signals treats the wrong problem
The obvious fix is a better model: more activity data, more conversation signals and a more accurate score. Better detection is useful when the existing system misses material changes.
It doesn't fix a warning the team can't inspect or act on. A model can flag every eventual loss and still create no commercial value if the warning arrives without a reason, an owner or a decision. The operating measure isn't how many risks the system found. It's how many material risks produced an appropriate action while the deal was still live.
A risk nobody owns is just a note
Name the condition in language the team can test. Budget approval missing, decision access unconfirmed and security requirements unknown are different conditions. Each needs different evidence and a different next action.
Keep the source that raised the condition and what remains unknown. A Manager should be able to agree, disagree or accept the risk with the reason recorded. Human judgment is part of the decision record, not an error for the model to hide.
Connect the warning to the next decision
A useful risk record answers five questions: what changed, what supports it, who owns the response, when the team will review it again and what happened afterwards.
That last question matters. If the action closes the gap, the team learns which response worked. If the deal still slips, the review can see whether the action was completed, whether it arrived too late or whether the original condition was not the deciding factor.
Judge the model by action and outcome
Precision and recall matter to the people building a model. A revenue team also needs an operating measure: did a material warning change what happened next?
Track whether the warning was reviewed, whether an owner accepted an action, whether the action was completed and what moved afterwards. A smaller set of inspectable conditions may create more value than a larger set of unexplained scores.
Where risk programs go wrong
Don't turn the result into surveillance. If the score becomes a judgment of the Seller, disagreement moves offline and the record gets cleaner while the decision gets worse. Keep the unit of analysis on the deal and the condition.
Don't treat correlation as cause. A condition may contribute to loss, stall or no decision without causing the outcome on its own. PROOF keeps protected condition logic and thresholds out of public material. The customer-facing record shows the many-to-one explanation the team can inspect.
The distinction worth keeping
A signal says something changed. A risk says why that change matters. An action says what somebody will do about it.
Collapsing all three into a red score is convenient for a roll-up and unhelpful for the person expected to progress the deal.
How PROOF approaches it
Keep the evidence, decision and action connected.
PROOF keeps the source, timing and accountable decision together so the team can act while the outcome can still change and learn from what happened afterwards.
See the working product