GTM Playbooks/Objection Analyzer
For Head of Sales Intermediate

Grade how your team handles objections

Objection Analyzer reads the LinkedIn and email threads you already have, grades every reply your SDRs sent, and turns the best ones into battle cards your whole team can reuse.

Get the skill

Get started

Calls get graded. Written replies don't. Sales teams review call recordings, but the objection replies SDRs send over LinkedIn and email never get the same look, so nobody actually knows if the team answers well in writing.

Objection Analyzer reads those threads, ranks the objections, grades every reply that was sent, and hands back a battle card per objection and a reusable template for each frequent one.

It also splits the fix three ways: the copy caused it, the list caused it, or it's a real product gap. Training the team harder only helps when none of those three checks out.

  • The objections you actually get, ranked, each with its recovery rate
  • Every reply you sent, scored, with the best one promoted as the example to clone
  • A battle card per objection: what it means, what to ask, what never to say
  • A ready-to-use reply template per frequent objection, written from what worked in your threads
  • Yours to hand an SDR as-is, or to turn into the team guidelines

What it won't tell you. It only grades replies, so it says nothing about the leads who never answered at all, and that group is usually the bigger one. To trace an objection back to the exact message that caused it, use the prompts under "Fix it upstream" below. If an objection type shows up in fewer than 5 replies, its card skips the recovery rate instead of printing one from too little data, other types with enough replies still get theirs.

Why that matters: a recovery rate that is plausible and wrong sends a team to coach the wrong objection for a quarter, and the pipeline is where you find out.

Run your first objection review

1

Point it at the conversations you already have

Nothing to set up first, and nothing to tag. Name the scope the way you would say it out loud: a window, a campaign, a channel, one rep, or everything. It tells you the volume before it pulls anything, so a bulk hydrate you did not want cannot happen by accident.

Prompt to copy copy
Sweep all my conversations, categorize every objection, and give me a response template for each frequent one.
First
The thread count, so you can narrow it before anything is pulled
Then
One question: a meeting, a signup, a resource or a nurture?
Why
The objection barely changes. Where the reply points changes completely
2

It comes back ranked, graded, and written up

The ranking is the half teams expect. The grades are the half you do not have. Every reply you sent after an objection is scored on nine things a good reply does: matching their tone, actually addressing the blocker, staying as short as they were, asking one question rather than three, and never pushing. Three points each, 27 in all.

Clear 22 and the reply becomes the example to clone. The weakest comes back with one line on what it should have said. And if nothing of yours clears 22, the card says so and falls back to the best practice it ships with, rather than promoting a mediocre reply as a model.

Next to each objection sits its recovery rate: of the ones you answered and that have had a week to breathe, the share where the lead wrote back. It measures whether the thread survived, not whether the deal closed.

Objection analysisWorked example · one quarter of LinkedIn replies
Price and budget33% of objections
Top objectionPrice and budget, 33% of all objections
Caused upstream62% of them land on the first message, before any scope exists
Never answered41% of the price objections got no reply at all
Best reply27/27, promoted as the clone-this example in the card
Weakest replydefended the price and pushed a demo. Should have asked what they compare it to
Reply mixwrong fit 25%, "job seeker" dominant
Verdictprice: copy. wrong fit: targeting. Two different owners
Open the battle cards Fix these campaigns in La Growth Machine

And it writes the reply for each frequent objection, from your own best-scoring answers rather than from a manual. Hand it to a rep as it is, or use it as the raw material for the team's guidelines.

Response template · price and budget · built from 2 of your replies that scored 22+, 1 of which recovered copy
Fair enough. Expensive compared to what, out of curiosity? Asking because [their_tool] and doing [the_job] by hand cost very different things, and I would rather tell you straight whether this is worth your time.

Read the shape, not the figures. Those numbers are the worked example from the skill's own documentation, and they are here to show what a finding looks like. Yours will read differently. Every figure printed comes from your threads, carries its sample size, or does not get printed.

3

Narrow it until it is something you can act on

The first sweep is a picture of everything, which is rarely what you act on. Reply in plain words to go type by type and read the card behind any objection in the ranking. Scope by campaign or by rep is a decision to make before the first pull, not after: re-slicing a corpus you have already swept means re-reading those threads.

Prompt to copy copy
Open the price objection card: how did we answer it, what worked, and what should we have said?
High score, low recovery
The objection is real. The reply was fine.
Low score, decent recovery
The easiest win on the board.
Under five threads
It says the slice is too thin instead of answering anyway.
4

Two ways to spend the finding

The output splits along the diagnosis. Objections the verdict calls a copy problem go to whoever owns the sequence. The ones it calls handling go to the team, as material.

Give it to the team
  • One battle card per objection, with the example to clone taken from your own threads
  • The weakest reply named with one line aimed at the move, not at the person
  • A reusable template per frequent objection, with its provenance stated on it
  • It grades the objections you answered. It cannot grade the ones nobody replied to
Fix it upstream
  • Objections that arrive at first touch get traced back to the message causing them
  • Each rewrite comes back as copy you can paste straight into the sequence
  • Wrong-fit clusters point at the list, which is a targeting decision
  • It never edits a live campaign. It hands you the rewrite and you make the change

Bonus: wire it into your own routine

The skill gives you the analysis. What you do with it on a schedule is yours to wire. A review you have to remember is a review that stops happening, so if your setup has a scheduler and a Slack connector, point them at a monthly sweep and have the recap land in the team channel. Monthly rather than weekly: a reply needs a week before it counts as answered or ignored, so a seven-day window comes back with almost nothing to rate.

Prompt to copy copy
On the first Monday of each month, sweep last month's replies and post the ranked objections and the never-answered rate to our #sales channel.
A trend, not a snapshot
Every run merges into the same ledger instead of starting over.
Cards that sharpen
Each run adds real examples to the cards instead of restating the baseline.

Go further: combine it with Reply Draft Assistant

Battle cards are only worth writing if they reach the person answering the inbox on a Tuesday. Reply Draft Assistant handles your replies end to end, and at the end of a run this offers to wire your playbook into its drafting step, so an objection reply is written from your card for that type instead of a generic angle. It shows you the patch and applies it only if you say yes.

Prompt to copy copy
Wire my objection playbook into Reply Draft Assistant, then show me the diff before you change anything.

That closes the loop: the sweep tells you what to say, Reply Draft Assistant says it, and the next sweep grades how it went.

Prompts to try on your own replies

Copy one, swap in your campaign or your window, and send it to Claude. In plain English, French, any language.

Sweep and grade
Whole corpus copy
Sweep all my conversations, categorize every objection, and give me a response template for each frequent one.
Last 30 days copy
Analyze the objections in my replies over the last 30 days.
Coach one type copy
Grade how we answered the price objections last month and tell me what to coach.
Your own replies copy
Which objections do I get most on my campaigns, and how well do I answer them?
The silence copy
How many objections did we never answer at all, and on which campaigns?
Fix it upstream
Trace the copy copy
Which sequence messages are causing the objections we get, and how would you rewrite them?
One campaign copy
Why does my "Q3 Founders" campaign get so many bad-timing answers?
List or copy copy
Show me the wrong-fit replies and tell me whether the problem is the list or the message.

Make it your team's playbook

  • →Scope it however you think: a campaign, a channel, a window or a single rep, named in the same sentence
  • →Share one ledger: set OBJECTION_PLAYBOOK_DIR to a folder the team syncs, and every sweep merges into it
  • →Close the loop: wire the cards into your reply skill and let the La Growth Machine MCP pull the conversations for you

Stop guessing which fix to fund

Run it on one quarter of your own replies and get the copy-or-list answer with the numbers behind it. The first run is useful with no data and no account.

Want a new playbook like this every week?