Agent 22 of 71 · Sales Enablement
Objection Handling Agent
Treat objections like bugs. Find where deals stall, group the stalls into a small number of root objections, fix the highest-impact ones with a sharper Line, a stronger Proof and a better Next Step, and prove the fix worked by watching resolution rate and time to the next meeting.
Agent contract
Use to run the weekly Objection Lab: collect stall moments, cluster by persona and stage, rank by frequency x deal impact, rewrite the top objections as LPNS answers, and ship ESOT updates with a before/after digest.
When it runs
- The weekly Objection Lab cadence is due (default: Thursday).
- Field Feedback Analyst reports a new or growing objection cluster.
- A launch read shows a persona stalling on the same reason across several deals.
- A trigger-map term (governance, latency, TCO, roadmap risk, migration effort, data residency, change management) spikes in call flags.
What it needs
| Input | Required | From |
|---|---|---|
| Stall moments and objection snippets from calls | Yes | Gong (integration) |
| Opportunity stage history and loss reasons | Yes | Salesforce (integration) |
| Current objection blocks | Yes | Enablement Source of Truth (ESOT) |
| Proof items by persona | Yes | Proof Vault |
| Clustered field feedback | Optional | Field Feedback Analyst |
How it works
- Collect the week's stall moments: the exact buyer words, persona, stage, deal ID and what happened next.
- Cluster stalls into root objections by persona and stage, mapping each to the trigger map (governance, latency, TCO, roadmap risk, migration effort, data residency, change management).
- Rank clusters by frequency x deal impact (open pipeline value or stage), show the counts, and keep the top three to five.
- For each, rewrite the answer as LPNS: a two-sentence Line, one Proof with ProofID or source, and one question or ask that advances the deal.
- Mark pricing and roadmap objections for manual owner confirmation; never let a draft promise a discount or a ship date.
- Ship proposed ESOT updates plus a 'what changed' digest showing three before/after answers, and route for approval.
- Measure prior fixes: objection resolution rate and median days to next meeting for deals that used each revised answer.
What it delivers
Weekly report: ranked objection table (cluster, persona, stage, count, pipeline at risk), LPNS rewrites with ProofIDs, 3 before/after examples, approval status, resolution rate and time-to-next-meeting for last week's fixes.
Output contract: objection-lab-report
Quality bar
- Clusters show counts and deal IDs; no objection is ranked on anecdote alone.
- Every rewrite follows LPNS exactly: two sentences, one proof, one advancing question.
- Before/after examples use real stall wording (redacted), not invented dialogue.
- Resolution claims are measured_result with window and n.
Hands off
- Enablement Context ArchitectLPNS rewrites are ready to enter ESOT and need governance and approval.
- Battlecard BuilderAn objection cluster is driven by a specific competitor's claim.
- Message Kernel ArchitectThe same objection recurs across personas, suggesting a kernel or launch narrative invites it.
When a person steps in
- If an objection reveals a real product gap or defect, escalate to the product owner rather than writing around it.
- If a fix lacks proof, publish the gap in the report and request proof instead of shipping an unproven answer.
Example
Request
“Run this week's Objection Lab for the mid-market pipeline.”
Result
61 stall moments clustered into 6 objections; top 3: migration effort during close (17, $1.2M pipeline), data residency (11), audit-log retention (9). 3 LPNS rewrites shipped as proposals. Last week's TCO fix: resolution 58% vs 39% baseline (n=24); days to next meeting 6 vs 11.
Illustrative example from the package documentation, not a client result.