F5 gains pipeline visibility and replaces Salesforce Sales Engagement with Clari and Groove
F5's CRM limited deal review to one deal at a time with no pipeline overview, required IT involvement for feature changes that took 3-5+ months, and produced inaccurate forecasts based on meeting activity. Salesforce Sales Engagement lacked reporting, activity capture, and rep visibility, frustrating the workforce.
Salesforce Sales Engagement had poor activity capture, lacked reporting and visibility, and burdened reps. Outreach and Salesloft were evaluated and rejected because they rely on a separate shadow CRM database.
F5 gained confidence in quarterly forecasting and pipeline visibility with Clari, freed managers from hunting down information to spend more time coaching, and achieved 100% rep adoption with Groove as a Salesforce-native sales engagement platform.
Frequently asked questions
What did this team achieve with this AI workflow?
F5 gained confidence in quarterly forecasting and pipeline visibility with Clari, freed managers from hunting down information to spend more time coaching, and achieved 100% rep adoption with Groove as a Salesforce-na…
What tools did this team use?
Clari, Groove, Salesforce Sales Engagement, Salesforce.
What results were reported?
IT feature change lead time (pre-Clari): 3-5+ months; Groove rep adoption rate: 100%; Deal read quality (qualitative): much better read on deals; Clari implementation pace (qualitative): excessively fast (source-reported, not independently verified).
What failed first in this deployment?
Salesforce Sales Engagement had poor activity capture, lacked reporting and visibility, and burdened reps.
How is this sales ops AI workflow structured?
Product-line data ingestion into Clari → Pipeline and deal review in Clari UI → Business-unit quarterly forecast → Real-time manager visibility into rep activity → Groove replaces Salesforce Sales Engagement → Activity capture and ROI reporting.