Forecast discipline reset



Forecast discipline had degraded to the point where large deals could sit open indefinitely in the 'omitted' category with no activity and nobody accountable for closing them out, the forecast looked clean precisely because the ugly deals had somewhere to hide.
SalesforceDesigned collaborative forecasting in Salesforce, surfaced inside the conversation-intelligence tool the team already worked in, with explicit written definitions for commit, best case, pipeline and omitted, so category choice becomes a claim a manager can challenge.
Added validation rules so stale deals cannot park in 'omitted' indefinitely: the category now requires the deal to be dispositioned rather than quietly left open.
Designed a contact-role qualification-scoring architecture so stage progression reflects who has actually been engaged in the buying group, rather than a rep's confidence.
After the company switched off its attribution platform, built the attribution flow and CRM specification to close the outbound blind spot, then handed the build over to the in-house team with a demo and documentation.
Kicked off opportunity-type simplification, a guided-path build and updated pipeline stages, and ran a data-hygiene review that identified account hierarchy, not duplicate records, as the underlying problem, then selected a hierarchy-management tool to fix the actual cause.
Forecast discipline reset
Commit, best case, pipeline and omitted were given explicit definitions, backed by validation rules designed to eliminate the open-forever omitted pipeline, with contact-role qualification scoring driving stage progression.



+5
7 steps
Merging two Salesforce orgs into one against a contract-expiry deadline
Cutover executed on schedule, ahead of the contract deadline
CRM migration and merge



+2
4 steps
Re-architecting a segmentation field across two CRMs, and rebuilding every report that depended on it
~195k contacts re-segmented
ERP implementation or migration

4 steps
Retiring a legacy ERP integration and answering 'what is our active ARR?'
Legacy ERP retired