Objection Rebuttal Matrix

Context

Use this when prospects understand value but stall at trust, complexity, or risk objections.

Procedure

1. Collect objections from sales and support logs.
2. Cluster objections by theme (risk, effort, cost, fit).
3. Draft acknowledgment line and rebuttal line for each objection.
4. Attach proof or policy support to each rebuttal.
5. Add fallback offers (trial, guarantee, implementation support).

Output Format

# Objection Rebuttal Matrix

| Objection | Root Concern | Rebuttal | Proof Artifact | Risk Reversal |
| --------- | ------------ | -------- | -------------- | ------------- |
|           |              |          |                |               |

## Reusable Snippets

- Pricing page snippet:
- Sales call snippet:
- Email snippet:

QA Rubric (scored)

• Diagnostic depth (0-5): addresses root concern, not surface wording.
• Proof quality (0-5): concrete evidence linked to rebuttal.
• Tone quality (0-5): respectful and confidence-building.
• Reusability (0-5): adaptable to multiple channels.

Examples (good/bad)

• Good: “We know migration risk is real; here’s our 14-day assisted onboarding plus rollback plan.”
• Bad: “That objection isn’t valid, trust us.”

Variants

• Enterprise procurement variant.
• Self-serve PLG pricing-page variant.