Build a shared sales objection library that improves with every deal

---
name: "build-a-shared-sales-objection-library-method"
description: "Use when you need to Build a shared sales objection library that improves with every deal. Build a shared objection library from real deals"
---

# Build a shared objection library from real deals

Job: [Build a shared sales objection library that improves with every deal](https://aiagents.org/canai/build-a-shared-sales-objection-library)

## Need

- ai agent: [Claude](https://aiagents.org/agents/claude), [Claude Cowork](https://aiagents.org/agents/claude-cowork)

## Steps

1. Map the objections your team hears, grouped by theme (budget, timing, who decides, need, trust, rivals, rollout and contract terms), with four to six real-sounding lines in each.
2. For each objection, draft a reply with an acknowledgement, a reframe, a proof point and a follow-up question, tagged by difficulty, deal stage and who usually raises it.
3. Create one shared workspace for the playbook and give every rep access.
4. Load the first objection map and replies into that workspace.
5. Each Friday, each rep logs one or two objections from that week's calls in the buyer's words, with how they answered and what happened, and asks for a category, a critique and a stronger version.
6. During live calls, search the workspace for the objection you just heard.
7. Each month, review new entries, feature the best replies and retire the ones that did not work.
8. Optional: After about 30 logged objections, ask for a pattern analysis by frequency, timing, stakeholder and won versus lost deals.
9. Optional: Role-play and review prompts appear later on the source page.
10. Note: The source uses Claude CoWork as the shared workspace; any shared document space with an AI assistant works.

## Credit

Method author Craig Hewitt (The Claude Playbook)
Source: https://craighewitt.com/claude-playbook/sales/objection-playbook