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.
The prior approach relied on manual feedback and LinkedIn updates to detect when key public-sector contacts had left, which slowed or stalled deals.
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.
Frequently asked questions
What did this team achieve with this AI workflow?
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 tools did this team use?
Pursuit, Salesforce.
What results were reported?
Bounce rate in production: sub-1%; Dead-end outreaches: reduced bounce-backs; Time to become trusted partner: a lot quicker; Forecast accuracy: improved forecast accuracy (source-reported, not independently verified).
What failed first in this deployment?
The prior approach relied on manual feedback and LinkedIn updates to detect when key public-sector contacts had left, which slowed or stalled deals.
How is this sales ops AI workflow structured?
Leadership change flagged → Radar signal list pull → Salesforce enrichment write-back → Rep works the list.