objection-library-builder

name	objection-library-builder
description	Build a structured objection handling library for revenue teams with response patterns, proof, and escalation rules. Use when asked to create or improve objection handling by segment, stage, persona, or competitor context. Route one-off call coaching to call-review-coach and broader messaging strategy to value-prop-and-positioning.

Objection Library Builder

Build a reusable objection playbook that helps teams respond consistently without sounding scripted.

Confirm Inputs First

• If a current revenue-enablement-context exists, use it first for persona language, stage definitions, and approved proof boundaries.
• Confirm segment, persona, and sales stage scope.
• Confirm current objection sources (calls, notes, CRM fields, manager input).
• Confirm top objections by frequency or business impact.
• Confirm proof sources available (customer outcomes, product evidence, policy terms).
• Confirm legal, pricing, or procurement constraints that affect responses.
• If inputs are incomplete, ask for only the minimum missing items or proceed with labeled assumptions.

Read The Right Reference

• Read references/objection-library-framework.md when you need response structure, severity definitions, and escalation rules.

Default Workflow

1. Clean up the objection wording. Turn messy rep notes into a short list of clear objection statements.
2. Group by theme. Cluster objections by persona, stage, competitor, and buying concern.
3. Prioritize the list. Rank by frequency, deal risk, and how often the team can actually influence the issue.
4. Write the response path. Use a simple flow: acknowledge, diagnose, answer, prove, and confirm the next step.
5. Add diagnostic questions. Include one or two questions that help the rep uncover whether the objection is real or hiding a bigger issue.
6. Add proof and collateral. Link each response to the best proof point, case study, product fact, or policy.
7. Add do-not-say guardrails. Call out the phrases that create overpromising or confusion.
8. Add escalation rules. Make it clear when the rep should hand off to legal, security, pricing, or implementation.
9. Route adjacent work: For strategic messaging, use value-prop-and-positioning. For competitor-specific counters, use battlecard-builder. For practice drills, use roleplay-scenario-builder.

Output Contract

• Objection taxonomy with priority tiers.
• Response play cards for each tier-one objection.
• Proof and collateral map per response.
• Response governance status and owner per play card.
• Escalation matrix by objection type.
• Coaching notes for managers.
• Assumptions list when source inputs were incomplete.

What To Avoid

• Treating all objections as equal without prioritization by deal risk.
• Shipping rebuttals without diagnostic lines that uncover root cause.
• Publishing responses without ownership or approval status.

Quality Bar

• Responses are evidence-backed and commercially realistic.
• Library distinguishes diagnosis from response.
• Escalation boundaries are explicit and enforceable.
• Priority reflects business risk, not opinion volume.
• Reps can apply responses quickly in live calls.