Which Objection Is Actually Costing You Deals? Auditing a Call-Tagged Export
Objective: Given a synthetic 30-row export of loan-conversation snippets tagged by objection type, competitor mentioned, and deal outcome, calculate win rate per objection and identify which single objection deserves a dedicated battle card this quarter.
You're the marketing analyst at Five-Star Business Finance, the Chennai-founded MSME secured lender that listed on the NSE/BSE in 2022. Branch relationship managers tag every loan conversation with an objection category, a competitor NBFC mentioned (if any), and the deal outcome. You've been handed the quarterly export.
Don't build a battle card for the loudest objection, build one for the objection that correlates with the most lost deals.
Before you start
What you'll need
Free path (everything below is enough to finish)
Free, handles a 30-row pivot with zero setup
Paid upgrades (optional, faster/deeper)
A real Gong/Chorus contract would auto-tag these categories from call transcripts; this exercise uses a pre-tagged export to isolate the analysis step.
Keeps the tagging system live instead of a one-off export
The process
1 step
Step 01 of 01
The lesson's 'Why Marketers Need Revenue Intelligence' section frames objection data as a pattern across hundreds of calls, not a single anecdote, and warns against trusting the objection that talks the loudest instead of the one that closes the fewest deals.
Objection A (collateral valuation delay) appears in 14 of 30 rows but only loses 3 deals. Objection B (processing time vs. competitor) appears in 8 rows but loses 6. Which gets the dedicated battle card?
Procedure
- Import the 30-row export and freeze the header row
- Pivot by objection_type, count total mentions and lost-deal count per category
- Compute loss rate = lost_deals / total_mentions for each objection
- Rank by loss rate, not by mention count
- Cross-check the top-ranked objection against competitor_mentioned to see which NBFC it's tied to
Objection audit, Five-Star Business Finance Q2 export (30 rows) OBJECTION MENTIONS LOST LOSS RATE collateral delay 14 3 21% processing time vs comp 8 6 75% interest rate 5 2 40% branch distance 3 1 33% Top competitor tied to 'processing time': Bajaj Finserv (5 of 8 mentions)
Healthy
The team builds a battle card around 'processing time vs. Bajaj Finserv' because it has the highest loss rate despite fewer total mentions.
Unhealthy
The team builds a battle card around 'collateral delay' because it's mentioned most often, even though it barely correlates with losses.
What this means
Frequency tells you what buyers talk about; loss rate tells you what actually kills the deal. Sort by the second one.
So what do I do about it?
| Symptom | Action | Effort |
|---|---|---|
| Battle card backlog is ranked by mention count | Re-rank by loss rate before greenlighting the next battle card | 5 min |
| No competitor tagged against the top objection | Ask branch RMs to tag competitor name during the loss-reason call debrief | 30 min |
Final deliverable
A one-page objection-priority ranking (by loss rate, not mention count) with the top-ranked objection's most-cited competitor flagged.
See a reference example
Bajaj Finserv comparison battle card, draft v1 OBJECTION: 'Your processing time is longer than [competitor]' LOSS RATE: 75% of calls where raised RESPONSE FRAMEWORK: 1. Acknowledge: 'Fair, we ask for physical collateral verification, they may not for smaller tickets.' 2. Reframe: cite average 4-day sanction-to-disbursal time for repeat MSME borrowers 3. Proof point: branch RM to cite 2 recent same-week disbursals DO NOT lead with rate comparison, buyers didn't raise rate as the objection.
Success criteria
You're done when you can:
- Ranks objections by loss rate, not raw mention count
- Correctly identifies the top-ranked objection's tied competitor