sales_ops · saas · workflow

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.

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 · Product-line data ingestion into Clari
F5 pulls data into Clari at the product line level with mapping already completed.
Tools used
ClariGrooveSalesforce Sales Engagement
Outcome

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.

What failed first

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.

Results
Time saved3-5+ months
Volume100%
Source

https://www.clari.com/resources/customer-stories/f5-networks/

How we source this →

Grounding & classification
Source type: vendor customer story
18 fields verified against source quotes.
failure mode describedmetric backednamed customertools describedworkflow describedsoftwareemployee productivityvendor customer storysales opssales outreachdata sync enrichment