Replies & MeetingsPopular
Reply handler
Outbound replies need triage and answers.
You get Classified replies · Priority and next action · Draft responses
Objection handler Claude skill
Use this when a buyer pushes back. Most objections are questions in disguise; the response that works first finds out which question.
- 4-step play
- 4 guardrails
- 2 files
- Human approval built in
Use it when a prospect raises an objection in a reply, on a call or in a deal.
Then just ask your agent
“Prospect replied 'we're happy with our current vendor'. Draft a response.”
Watch it work
One request in, expert work out
What happens when you ask your agent with this skill installed. Every step below comes straight from the skill.
You
Prospect replied 'we're happy with our current vendor'. Draft a response.
Loaded skill
objection-handler- Diagnose before answering
- Choose the pattern
- Write the response
- Log it
Diagnosis · Response per channel · Objection library entry
Ready for your review. Nothing is sent or changed until you approve.
- 4Steps in the play
- 4Guardrails
- 2Files in the skill
- 4 minTo read it all
What good looks like
- The first response is usually a question.
- Proof matches the objection: a security concern gets a security document, not a ROI story.
- Bad-fit objections are accepted, not "overcome".
What you bring
- The objection in their words
- Context and stage
- Proof points
What you get
- Diagnosis
- Response per channel
- Objection library entry
name:objection-handler
description:Use this skill when a prospect raises an objection in a reply, on a call or in a deal: "how do I respond to 'too expensive'", "handle this objection", "build an objection handling guide",…
Use this when a buyer pushes back. Most objections are questions in disguise; the response that works first finds out which question.
Inputs
- The objection, in the buyer’s exact words.
- Context: cold reply, discovery call, late-stage deal; who said it.
- Proof available: customer stories, numbers, documents.
The play
1. Diagnose before answering
| Surface objection | Often really means |
|---|---|
| "Too expensive" | Value not clear yet, wrong package, budget timing, or a competitor quote |
| "We already have a solution" | Switching feels risky; current pain not acknowledged |
| "Not a priority" | Problem not tied to something they are measured on |
| "Send me some info" | Polite exit, or genuinely busy |
| "I need to talk to my team" | Not the decision-maker, or not convinced enough to champion |
| "We tried something like this" | Past failure; fear of repeating it |
2. Choose the pattern
- Clarify: ask a question that surfaces the real concern. Default first move.
- Reframe: change the comparison (cost of the problem vs the price; risk of doing nothing).
- Prove: a peer who had the same concern and what happened.
- Defer: agree a specific later moment when the condition changes.
- Walk away: when the objection reveals a genuine bad fit, say so. It builds trust and saves time.
3. Write the response
Acknowledge in a few words (no "I totally understand"), then the pattern. Keep email responses under 80 words. On calls, ask and then stop talking.
Read references/objection-library.md for responses to the 12 most common B2B objections, by stage.
4. Log it
Every objection goes into the library with the response that worked. Patterns across deals feed messaging and product.
What good looks like
- The first response is usually a question.
- Proof matches the objection: a security concern gets a security document, not a ROI story.
- Bad-fit objections are accepted, not "overcome".
- The common mistake is arguing: answering a price objection with a list of features.
Rules
- MUST clarify before rebutting when the real concern is unclear.
- MUST use only approved proof points and real pricing.
- NEVER pressure with fake deadlines or "this price ends Friday" unless it is true.
- NEVER disparage a competitor the buyer uses.
Example prompts
- "Prospect replied ‘we’re happy with our current vendor’. Draft a response."
- "Build an objection library for our sales team from these 20 call notes."
- "On calls I freeze at ‘it’s too expensive’. Give me a talk track."
Objection library
Early stage (cold replies, first calls)
| Objection | Response |
|---|---|
| "Not interested." | "Fair enough. Is that because <problem> isn’t an issue for you, or just not a priority right now?" |
| "We already use <tool>." | "Good to know. How is it handling <specific weak spot>? If it’s working, I’ll leave you be." |
| "Send me some info." | "Happy to. So it’s relevant: are you mostly looking at <outcome A> or <outcome B>?" |
| "No budget." | "Makes sense. When does planning start for next year? I’d rather be useful then." |
| "Not the right person." | "Thanks. Who owns <problem> on your team?" |
| "Bad timing." | "When would be better, and what changes then?" Book the date. |
Mid stage (discovery, demo)
| Objection | Response |
|---|---|
| "Too expensive." | "Compared to what? … What does <problem> cost you today in hours or lost deals?" Then show the maths with their numbers. |
| "We tried something like this and it failed." | "What happened? … The two most common reasons are <x> and <y>; here’s how <peer> avoided them." |
| "I need to talk to my team." | "Of course. Who’s involved, and what will they ask you that I can help answer? Want me to join for 15 minutes?" |
| "We’ll build it ourselves." | "Could be the right call. How many engineering weeks, and what does maintaining it cost per year?" |
Late stage (proposal, procurement)
| Objection | Response |
|---|---|
| "Your competitor is cheaper." | "They may be. Can we compare line by line? Teams usually find the difference in <onboarding, limits, support>. If they’re a better fit, I’ll tell you." |
| "Security has concerns." | "Which ones? I’ll send the security pack today and can set up a call with our security lead this week." |
| "Can you do a bigger discount?" | Trade, don’t give: "I can look at that if we can <sign by date / commit annually / be a reference>." |
| "Legal needs more time." | "Understood. Which clauses? We have pre-approved alternatives for the common ones." |
Proof matching
| Concern type | Best proof |
|---|---|
| Value | Peer result with numbers; their own maths |
| Risk of switching | Migration plan, timeline, a reference who switched |
| Security and compliance | Documents, certifications, data-flow diagram |
| Adoption | Usage numbers from a similar team, onboarding plan |
| Price | Cost-of-problem calculation, packaging options |
Try it
Ask your agent like this
Once the skill is installed, plain requests like these load it automatically. Swap in your own company, buyer and numbers.
-
“Prospect replied 'we're happy with our current vendor'. Draft a response.”
-
“Build an objection library for our sales team from these 20 call notes.”
-
“On calls I freeze at 'it's too expensive'. Give me a talk track.”
What does the Objection handler skill do?
Use this when a buyer pushes back. Most objections are questions in disguise; the response that works first finds out which question. You get: diagnosis, response per channel, objection library entry.
When should I use the objection handler skill?
Use it when a prospect raises an objection in a reply, on a call or in a deal.
How do I install Objection handler in Claude Code?
Run /plugin marketplace add prosyo-ai/gtm-skill and then /plugin install gtm-skills@prosyo to add the whole library, or run npx skills add prosyo-ai/gtm-skill –skill objection-handler for this skill alone. In Claude.ai, download the .zip from this page and upload it under Settings, Capabilities, Skills.
What do I need to give the agent?
Have these ready: the objection in their words, context and stage, proof points. If something is missing, the skill tells the agent to ask for it rather than guess.
Does it work with ChatGPT, Codex, Cursor or Gemini?
Yes. The skill is a plain SKILL.md file with no vendor lock-in. Agents that load skills natively (Claude Code, Claude.ai, Codex, Cursor, Gemini CLI and others) pick it up automatically; anywhere else, paste the file into the conversation as instructions.
Will it send emails or messages on its own?
No. Every skill in the library drafts, researches and analyses, and waits for a person to approve anything that sends, schedules or changes records in bulk. Your inbox, CRM and accounts stay under your control.
Is it free, and can I change it?
Yes. It is free and MIT-licensed. Copy it, adapt it to your market and voice, and if you improve it, open a pull request so everyone gets the better version.
Keep going
Browse all 69 skills
Skills that pair well with this one
Discovery call prep
You have a discovery or first sales call coming up and want to run it well.
You get One-page call plan · Question list · Next-step ask
Meeting booking reply
A prospect shows interest and you need to turn it into a booked, confirmed meeting.
You get Booking reply · Calendar invite · Confirmation
No-show recovery
A prospect misses a booked meeting or keeps rescheduling.
You get No-show sequence · Rebooking message · Diagnosis and fixes
Open source
Have a play that works? Share it as a skill.
Paste this into Claude, Codex or any agent. It interviews you about your play, writes the skill in the house format, checks it and opens the pull request. Once it is merged, it shows up here with your name on it.
Prompt for your agent
Fetch https://raw.githubusercontent.com/prosyo-ai/gtm-skill/main/AGENTS.md and follow its submission flow. Interview me about my GTM play (the real numbers, rubrics and examples), draft it in their format with reference pages, validate it and open the pull request.
Two ways to run it
Run it yourself, or put it on autopilot
The skill gives your agent the playbook. Penny, the Prosyo AI SDR, runs plays like this for you every day across LinkedIn and email.
Free · this skill
You and your agentBest for trying the play and one-off work
- Your agent follows the objection handler playbook step by step
- You bring the inputs and run it when you need it
- Works in Claude, Codex, Cursor and 40+ agents
- You review every draft before it goes anywhere
Prosyo AI SDR
Penny runs it for youBest for a pipeline that grows every day
- Finds the right buyers for your ICP every day
- Writes from what each prospect actually posted
- Follows up on LinkedIn and email at a safe, human pace
- Every reply lands in one inbox with an answer drafted
- You approve what goes out
Skills draft the play. Penny runs it.
Penny, the Prosyo AI SDR, finds your buyers, writes from what they actually posted, follows up on LinkedIn and email and lands every reply in one inbox with an answer ready. 7 days free, no card.
- 7 days free
- No card required
- Cancel in two clicks
