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.
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.
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.
Frequently asked questions
What did this team achieve with this AI workflow?
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 tools did this team use?
Gong, Gong Forecast, Chorus, Salesforce.
What results were reported?
Pipeline review time: 25%; Sales cycle length: 2.5 weeks; Close rate: from 23% to 30% (source-reported, not independently verified).
What failed first in this deployment?
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 fo…
How is this sales ops AI workflow structured?
Pipeline review question triggers process → Centralize deal data across platforms → Proposal activity pulled into Gong → Leaders call accurate forecast numbers → Coach reps based on forecasting patterns.