Objection Handling from Loss Data
Turn the objections that lost you deals into a handling guide — the recurring ones, the data that counters each, and the reframe that works.
Product Marketing - Enablement
The objections that lost deals — with the evidence that counters each
5
Recurring objections
Reframe + evidence
'Too expensive' -> their own reviews
cite surprise bills at scale.
'Too expensive' -> their own reviews
cite surprise bills at scale.
| Objection | Evidence |
|---|---|
| Too expensive | Their reviews: bill surprises |
| Migration risk | Common in segment (tech data) |
| Feature X gap | Route to product |
Why it lands
A scripted 'we're actually a great value' rebuttal convinces no one. 'Their own reviewers report surprise bills at scale — here's the data' answers the price objection with evidence the buyer can verify.
Overview
Take a pasted set of loss notes citing objections, cluster the recurring objections, and build a handling guide for each — pairing the reframe with supporting data (technographic, review, or intent evidence) so sales answers the objection with evidence, not a scripted rebuttal.
Use cases
Objection handling reps actually use
A guide built from the objections that really lost deals — each answered with verifiable evidence — beats a generic rebuttal sheet that reps abandon mid-call.
Honest routing of real gaps
When an objection is a genuine product gap, spinning it loses credibility. Routing it to product — and saying so — keeps the rest of the guide trustworthy.
View workflow prompt
# Objection Handling from Loss Data
## Parameters
- `{{loss_notes}}` *(required)* — Pasted loss notes with objections (deal, objection, competitor). Example: `Acme - 'too expensive vs Datadog' - lost; Beta - 'worried about migration risk' - lost`
- `{{competitor}}` *(optional)* — The competitor most objections reference. Example: `Datadog`
## Purpose
Cluster the recurring objections in {{loss_notes}} (often referencing {{competitor}}) and build a handling guide that pairs each reframe with supporting evidence — so reps answer 'too expensive' or 'migration risk' with data, not a memorized line.
## Process
1. **Cluster objections** — read {{loss_notes}}; group into recurring objection types (price, risk, feature gap, incumbent inertia).
2. **Find counter-evidence** — for each, pull supporting data: `get_product_reviews` (the competitor's own customers voice the same concern), `company_technographic` (migration is common in this segment), `company_intent` (the market is already moving).
3. **Build the reframe** — for each objection, a reframe that acknowledges the concern and answers with evidence.
4. **Flag the real ones** — objections that are genuine product gaps (not handleable with messaging) get routed to product, honestly.
5. **Format** — a rep-usable guide: objection -> reframe -> evidence -> proof point.
## Output Format
Markdown with:
- `# Objection Handling Guide`
- `## Recurring Objections` (clustered, with frequency)
- `## Handling Guide` (table: objection | reframe | supporting evidence)
- `## Route to Product` (genuine gaps, not messaging problems)
- `## Citations`
## Quality Checklist
- Objections clustered from real loss notes
- Each reframe pairs with cited supporting evidence
- Genuine product gaps are routed honestly, not spun as objections
- Reframes are human and specific, not scripted