sales_ops · saas · workflow
Flock Safety uses Pursuit to detect leadership changes and speed public-sector prospecting
Flock Safety's reps lost momentum when outreach bounced because public-sector leaders had moved on, and sales ops depended on manual LinkedIn updates to detect departures. RevOps lacked a scalable way to maintain contact coverage or leverage public records for targeted outreach.
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 · Leadership change flagged
Pursuit continuously flags silent leadership and staff changes beyond what shows up in press.
Tools used
PursuitSalesforce · partner
Outcome
Pursuit reaches sub-1% bounce rates in production, reducing dead-end outreaches, speeding prospecting through agency-specific signals, cleaning CRM data in Salesforce, and improving forecast accuracy for RevOps.
What failed first
The prior approach relied on manual feedback and LinkedIn updates to detect when key public-sector contacts had left, which slowed or stalled deals.
Results
Time saveda lot quicker
Volumesub-1%
Grounding & classification
Source type: vendor customer story
24 fields verified against source quotes, 1 dropped as unverifiable.
anomaly detectiondata extractionknowledge basemetric backednamed customerproduction runtime claimedtools describedworkflow describedsoftwarecycle time reductionemployee productivityerror reductionvendor customer storylead processingsales opssales outreachdata sync enrichmentmonitor detect alert