objection-library-builder

Objection library builder

Help sellers understand a buyer's concern, respond with supported information, and agree an appropriate next step.

The same words can express different concerns. A price objection might concern budget, perceived value, an alternative, or timing. Choose a question that distinguishes the plausible explanations before recommending a response.

Diagnose. Buyer: "It's too expensive." Seller: "What are you comparing it with?" Ask about budget or value after hearing the answer.

Rebut. "I understand. Other customers felt that way and then saw 3x ROI in the first year."

For a reusable library, establish patterns from qualified evidence. Use call-insights-to-objections if a raw call set needs analysis. A single live-deal question can proceed from the buyer's wording and the available context.

Inputs

For a live response, use the buyer's words, situation, known constraints, and available proof. Ask only a question whose answer materially changes the response. For a library, also confirm:

1. Segment, persona, and stage scope
2. Qualified objection evidence, not anecdotes treated as frequency
3. Approved proof and policy limits
4. Who owns the library and what event forces a review

Reuse supplied context or relevant sections of .enablement/context.md when needed. Do not invent quotes, counts, proof, or approval status. Draft response language is a proposal, not an approved claim.

A response for an upcoming conversation

1. Consider what the buyer might mean without presenting a list of hypotheses unless it helps the seller.
2. Start with a short acknowledgement and one neutral question. Let the buyer answer before giving more argument; avoid questions that imply they have failed to see the value.
3. Offer a brief reply based on known facts, in a separate conversational turn. If you propose a capability as a reason to choose, establish whether it matters to this buyer. A buyer-reported competitor price remains a report, not a verified comparison. Keep internal proof notes outside spoken lines unless the buyer needs that caveat.
4. Give a conditional next move that follows from the answer. If a confirmed requirement cannot be met, say so. Pricing, security, legal, and delivery exceptions need the authorised owner; do not script unneeded branches.