Objection library built from real calls (L2)
Stop writing objection handling from imagination. Pull the actual objections out of last quarter's recorded calls, cluster them, and publish the top ten with the responses that correlated with progression.
The steps
- 01
Export the raw objections
Tool: Gong
Pull transcript segments flagged as pricing, competitor, timing, and authority objections across one full quarter. Volume matters here, a dozen calls will mislead you. Owner: enablement plus RevOps. DoD: export covers at least one quarter of closed deals both ways.
- 02
Cluster and rank
Tool: Claude
Have the assistant cluster the segments into themes and count frequency. Enablement reviews and merges the clusters by hand. The model groups, the human names. Pitfall: accepting model labels unread. They drift toward generic sales language. DoD: top ten objections named by a human with frequency counts.
- 03
Attach responses that actually worked
Tool: Gong
For each objection, pull two clips from deals that progressed after the objection and one from a deal that stalled. Real clips beat written scripts. Owner: enablement. DoD: every objection entry links to three clips.
- 04
Publish and refresh quarterly
Tool: Notion
One page, ten objections, clips plus a short written frame. Refresh every quarter and archive what dropped out of the top ten. Owner: enablement. DoD: page published with a dated refresh schedule.
Tools in this playbook
Next playbooks
Unfamiliar terms are defined in the AI and Revenue Dictionary. Related frameworks live in the framework library.