Objection Library Builder

Build a reusable objection response system 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. Normalize objection statements into a clean taxonomy.
2. Group objections by theme, persona, and stage.
3. Prioritize objections by frequency, deal risk, and controllability.
4. For each priority objection, draft a response path: acknowledge, diagnose, reframe, support with proof, and confirm next step.
5. Add do-not-say landmines to prevent overpromising.
6. Add escalation rules for legal, security, pricing, and implementation risks.
7. Assign governance status per response path: draft, approved, restricted, and owner.
8. Add links to supporting collateral by objection.
9. Route adjacent work: For strategic message development, use value-prop-and-positioning. For competitor-specific tactical counters, use battlecard-builder. For roleplay drill creation, 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 scripted rebuttal.
• Escalation boundaries are explicit and enforceable.
• Priority reflects business risk, not opinion volume.
• Reps can apply responses quickly in live calls.