How Proposify cut its time spent on forecasting by 25% with help from Gong
Proposify's sales team lacked alignment on forecasting because data was scattered across Chorus, Salesforce, and their own tool; reps made decisions based on gut feelings and managers had no clear picture of the pipeline.
How it works
Common implementation structure
How this type of workflow is generally built, generalized across documented cases — not tied to any one vendor's stack. Click any stage to read what happens there. Specific products that implement these stages appear in “Tools commonly seen” below.
Stage 1 · Pipeline review question triggers process
The recurring pipeline review question about how teams feel about the pipeline initiates the forecasting process.
Tools used
GongGong ForecastChorus
Outcome
Proposify reduced pipeline review time by 25%, cut its sales cycle by 2.5 weeks, and raised its close rate from 23% to 30%, with the whole organization aligned on a single source of truth for revenue in Gong.
What failed first
Proposify had been using Chorus for call recording alongside Salesforce, but cross-referencing data across all three systems kept call coaching and forecast coaching separate, and reps were never properly taught to forecast.