Five objections. Five honest answers. Written down once.
A set of prepared responses to the pushbacks your deals actually stall on, built from your own lost and stuck deals instead of a generic list.
Most people improvise their answer to 'too expensive' or 'send me details' differently every time, and lose the deal at the same moment without noticing. Generic objection scripts do not help: they are rebuttals, and a buyer can hear a rebuttal coming.
Objection Handling starts from the objections you list, ranks them, and works out what each one really asks. For each of the five that matter it drafts an acknowledgment, a diagnostic question, an evidence-based response, and a line for when the concern is fair.
What it produces.
- →A ranked list of your five most costly objections in the buyer's words
- →An acknowledgment and diagnostic question for each
- →Responses built only from evidence you can back up
- →A walk-away line for when the objection is legitimate
- ✦Founders who hear the same pushbacks every week
- ✦Salespeople onboarding to a product with known sticking points
- ✦Teams whose answers differ from call to call
- →objection-handling.zip: a native Claude Skill. Upload to Settings → Skills in Claude, or unzip to
~/.claude/skills/ - →objection-handling-skill.md: plain markdown. Works in ChatGPT Custom GPTs, Gemini, Claude Projects, agent system prompts, anywhere
- →A README inside the zip with install steps for Claude, ChatGPT, and Gemini
What it does with a real question.
I'm the sales manager for a 12-person team selling payroll software to restaurants with 20 to 100 employees. Since January, 14 of our last 30 stalled deals died on the same five pushbacks: price versus our competitor, switching hassle, a long contract, weak reporting, and "we'll revisit next quarter." Our reps all answer differently. Can we write honest responses before our March training?
Start with what each pushback really means. Your five are not equal. Price versus the competitor and "we'll revisit next quarter" are usually symptoms, not the objection. A restaurant owner who says "next quarter" is typically telling you the pain is not yet worse than the effort of switching, which makes it a switching-hassle problem in disguise. Likewise, "weak reporting" often hides one specific report a manager needs, so ask which one before defending the whole product.
My position: write responses that acknowledge, ask one diagnostic question, and only then offer evidence. For switching hassle, the honest answer is the one your reps can prove. If a 40-person restaurant can run its first payroll in parallel with the old system and you have a customer who did exactly that, say so. If migration really takes three weeks, say three weeks. Overpromising here kills trust faster than the objection does.
For the long contract, do not rebut it. Ask what they are protecting against. If it is fear of being stuck, a termination clause or shorter initial term answers it. If you cannot offer one, tell the rep to say "that is a real limit of what we do" and let the buyer decide.
Next move: this week, pull the 14 lost deals and have reps write the buyer's exact words for each objection, not softened versions. Bring those to training and draft one agreed answer per objection, including a walk-away line for buyers whose concern is legitimate.
The full Playbook runs the whole procedure and writes the complete deliverable, not this excerpt.
Written by claude-sonnet-5-5 with this Playbook loaded, 2026-10-11. Checked automatically for length and for copied framework text.
No subscription · free updates within v1.x
Works as a Claude Skill (.zip) and as a plain .md for ChatGPT, Gemini & every LLM
Delivered to your email within 60 seconds · Secured by Stripe
Price includes UK VAT where applicable
Before you buy.
How is this different from just asking Claude directly?
Asked cold, Claude produces a stock list of common objections with polished rebuttals. This works from your actual stalled deals, asks what each objection might really mean, and writes answers that ask first and prove second.
How is this different from a Tool?
Playbooks are systematically produced to a fixed template and priced accordingly ($12.99). Tools are hand-built, one at a time, and go deeper ($39 to $199). A Playbook gives you a reliable method for routine work; a Tool is for when the judgment matters more than the format.
Will this work with ChatGPT, Gemini, and other LLMs?
Yes. You get a native Claude Skill (.zip) that auto-invokes in Claude, plus a plain .md you can paste into a ChatGPT Custom GPT, a Gemini system prompt, or any LLM. The procedure travels with the file.
Can I share this with my team?
It's licensed for your own personal and professional use. The output it produces is yours to circulate. To put the Playbook itself in the hands of a whole team, email hello@authority.md about team licensing.
What if it doesn't work for me?
If the file hasn't been delivered, or arrives defective or empty, we refund in full: see our refund policy.