# Sales Objections > A Claude skill from zubair-trabzada/ai-sales-team-claude. - **Type:** Skill - **Install:** `agentstack add skill-zubair-trabzada-ai-sales-team-claude-sales-objections` - **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior - **Seller:** [zubair-trabzada](https://agentstack.voostack.com/s/zubair-trabzada) - **Installs:** 0 - **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills) - **Latest version:** 0.1.0 - **License:** MIT - **Upstream author:** [zubair-trabzada](https://github.com/zubair-trabzada) - **Source:** https://github.com/zubair-trabzada/ai-sales-team-claude/tree/main/skills/sales-objections - **Website:** https://www.skool.com/aiworkshop ## Install ```sh agentstack add skill-zubair-trabzada-ai-sales-team-claude-sales-objections ``` Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent. ## About # Objection Handling Playbook You generate comprehensive objection response scripts that salespeople can use in real-time during calls, meetings, and email exchanges. Every objection response is word-for-word ready to use, not a summary or framework description. This playbook covers 15 universal objections, industry-specific objections, competitive objections, and pricing deep-dives. ## Invocation ``` /sales objections ``` Where `` is the prospect's industry (e.g., "SaaS", "healthcare", "e-commerce"), a specific topic (e.g., "pricing", "enterprise security"), or a prospect company name/URL for fully customized objection handling. ## Step 1: Gather Context Before generating the playbook, collect or infer: 1. **Your product/service**: What you sell and the core value proposition 2. **Target industry**: The prospect's industry or vertical 3. **Prospect company size**: SMB, mid-market, or enterprise (affects objection types and responses) 4. **Typical competitors**: The 2-3 competitors you most frequently sell against 5. **Average deal size**: Affects how pricing objections are handled 6. **Your strongest proof points**: Best case studies, metrics, and testimonials available If previous analysis files exist in the working directory (PROSPECT-ANALYSIS.md, COMPANY-RESEARCH.md, COMPETITIVE-INTEL.md), read them and automatically customize the playbook to the specific prospect. If the user provides a URL instead of a topic, fetch the website using WebFetch and determine the industry, company size, and likely objections based on the research. --- ## Step 2: Objection Handling Frameworks Every response in this playbook uses one of two frameworks. Generate both response versions for each objection so the salesperson can choose the one that fits the moment. ### Framework 1: Feel-Felt-Found (FFR) Structure: ``` "I understand how you feel about [restate their concern in your own words]. [Similar company/role] felt the same way when they were [in the same situation]. What they found was [specific positive outcome with a metric or concrete result]." ``` Rules for FFF responses: - "Feel" must genuinely acknowledge their concern — never dismiss it - "Felt" must reference a real or realistic similar company/person — be specific (industry, size, role) - "Found" must include a specific, measurable outcome — never vague ("they loved it") - Total response should be 3-5 sentences spoken aloud (approximately 15-25 seconds) ### Framework 2: Acknowledge-Bridge-Close (ABC) Structure: ``` **Acknowledge**: "[Validate their concern — show you heard them and it's a reasonable concern]" **Bridge**: "[Transition to your value — reframe the concern as a reason to move forward]" **Close**: "[Provide evidence and propose a specific next step]" ``` Rules for ABC responses: - Acknowledge must NOT start with "but" or "however" — genuinely validate first - Bridge must reframe, not dismiss — turn their concern into an advantage or learning moment - Close must include a proof point AND a specific next action (question, offer, or proposal) - Total response should be 3-5 sentences spoken aloud (approximately 15-25 seconds) --- ## Step 3: The 15 Universal Sales Objections Generate complete handling scripts for each of the following objections. For EACH objection, provide all six components listed below. --- ### Objection 1: "It's too expensive" / "We don't have the budget" **What it really means**: They either do not see enough value to justify the price, have not secured internal budget approval, or are using price as a polite way to decline. Rarely means they literally cannot afford it. **FFR Response**: "I completely understand the budget concern — [price] is a meaningful investment. [Company in their industry] felt the same way when they were evaluating this last [quarter/year]. They were spending roughly [X amount] on [current manual process / existing tool / lost opportunity cost]. What they found after implementing was [specific ROI metric] — they actually [saved/generated] [X] within the first [timeframe], which was [multiplier]x their investment. Would it help if I walked you through the ROI math specific to your situation?" **ABC Response**: "That's a fair concern, and I appreciate you being direct about it. (Acknowledge) Here's what I've seen though — the cost of NOT solving [their specific pain point] is usually much higher than the investment. Right now, based on what you shared about [their specific situation], you're likely spending [estimated cost of current approach] on [current process]. (Bridge) Let me put together a quick ROI comparison so you can see the numbers side by side — would 10 minutes on Thursday work to walk through it? (Close)" **Follow-up question**: "Just so I understand — is it that the price is higher than you expected, or that you haven't been able to secure budget for this category yet? Those are different problems, and I might be able to help with both." **Proof point to deploy**: [Generate a specific ROI case study — e.g., "Acme Corp reduced their [cost category] by 40% in 90 days, saving $150K annually on a $50K investment."] **When to walk away**: If they genuinely cannot afford it after exploring all pricing options (tiered pricing, reduced scope, payment terms), and there is no path to budget in the next 1-2 quarters, move them to a nurture sequence. --- ### Objection 2: "We're happy with our current solution" **What it really means**: Status quo bias. Switching costs feel high and the pain of change feels greater than the pain of staying. They may also not be aware of what they are missing. **FFR Response**: "That's great to hear — it means you've already solved the basics, which actually makes this conversation easier. [Similar company] felt the same way about [their current tool]. They were genuinely satisfied — it worked. What they found was that 'working' and 'optimal' are very different things. After switching, they discovered they'd been leaving [specific metric — e.g., 30% more efficiency, $200K in revenue] on the table without realizing it. I'm not suggesting you have a problem — I'm curious if there are opportunities you might not have visibility into yet." **ABC Response**: "I'd be worried if you weren't happy with your current setup — it would mean you made a bad decision, and you clearly didn't. (Acknowledge) That said, most of the companies we work with were happy with their previous solution too. The question isn't whether your current tool works — it's whether there's a significant gap between where you are and where you could be. (Bridge) What if we did a quick gap analysis — 15 minutes, no commitment — and if I can't show you at least [specific value metric] in upside, I'll be the first to tell you to stick with what you have? (Close)" **Follow-up question**: "What's the one thing you wish your current solution did better? Even small frustrations tend to compound over time." **Proof point to deploy**: [Generate a competitive displacement case study specific to the identified current solution.] **When to walk away**: If after a gap analysis they genuinely have no unmet needs and their current solution covers everything, they are not a prospect right now. Add to nurture for when their needs evolve or their contract renews. --- ### Objection 3: "We need to think about it" **What it really means**: Almost never means they will actually think about it. Usually means they have an unspoken concern, they need buy-in from someone else, or they want to avoid saying no directly. **FFR Response**: "Absolutely — this is an important decision and you should take the time you need. [Similar role at similar company] said the same thing. What they found helpful was identifying the specific criteria they needed to evaluate so the thinking time was productive rather than open-ended. Can I ask — what are the two or three factors that will drive your decision? I might be able to get you answers today that save you a week of back-and-forth." **ABC Response**: "Of course — you should absolutely think it through. (Acknowledge) In my experience, 'thinking about it' goes a lot faster when we can narrow down exactly what needs to be resolved. Most of the time, there are one or two specific questions that, once answered, make the decision clear one way or another. (Bridge) What would you need to see or know to feel confident about moving forward? Let's tackle those right now if we can. (Close)" **Follow-up question**: "Totally fair. Can I ask — is there a specific concern or question that's giving you pause? I'd rather address it now while we're both here than have it linger." **Proof point to deploy**: "Most of our customers who did decide to move forward told us their biggest regret was not doing it sooner — [specific customer] estimated they lost [metric] for every month they delayed." **When to walk away**: If they are genuinely not the decision-maker and need internal alignment, help them sell internally (provide a one-pager, offer to join a call with their stakeholder). If they repeatedly defer without specifics, they are likely a "no" — move to breakup sequence. --- ### Objection 4: "Send me more information" **What it really means**: This is the polite brush-off. 90% of the time it means "I want to end this conversation." Occasionally it is genuine — they want to review materials before committing time. **FFR Response**: "Happy to send something over. [Prospect at similar company] asked for the same thing. What they found was that a generic PDF didn't really answer their specific questions — what actually helped was a 10-minute walkthrough focused on [their specific use case]. I can put together something tailored to [their situation] — would a quick call Thursday be more useful than a brochure?" **ABC Response**: "Absolutely — I'll send that over today. (Acknowledge) I want to make sure I send you the RIGHT information though, not a generic overview that doesn't address your situation. (Bridge) What specifically would be most useful for you to see? Is it pricing, implementation, case studies, or something else? That way I can tailor it and save you time digging through a 30-page deck. (Close)" **Follow-up question**: "Sure thing. So I send the right materials — what are the two or three things that would most influence your decision? I'll make sure those are front and center." **Proof point to deploy**: Offer to send a case study specifically relevant to their industry/size instead of generic materials. **When to walk away**: If they insist on email-only communication and refuse any call or meeting after 2-3 attempts, respect it. Send the best materials you have and add to the follow-up sequence. --- ### Objection 5: "We're not ready right now" / "The timing isn't right" **What it really means**: Could be genuine (other priorities, budget cycles, leadership changes) or a soft decline. Need to determine which. **FFR Response**: "I appreciate you being upfront about timing. [Similar company] was in the same position — they had [Q4 planning / a migration / a re-org] happening and couldn't take on anything new. What they found was that starting the evaluation process now, even slowly, meant they were ready to move when the timing was right instead of starting from scratch. They saved about [X weeks/months] by doing the groundwork early. Is there a specific timeline when this would move up in priority?" **ABC Response**: "Completely understand — timing matters, and I don't want to push something when you're not ready. (Acknowledge) Here's what I've seen though: the companies that get the best results are usually the ones that start the conversation early, even if implementation is months away. It means when the timing IS right, they're not scrambling. (Bridge) What if we keep this low-touch — I'll check in with something useful once a month, and when the timing works, we can pick right up? What does your timeline look like for revisiting this? (Close)" **Follow-up question**: "Makes sense. Can you help me understand — is it that you don't have bandwidth to evaluate right now, or that you don't have bandwidth to implement right now? Those have different solutions." **Proof point to deploy**: "Companies that start their evaluation [X months] before they're ready to implement get [specific benefit — faster time to value, better pricing, smoother onboarding]." **When to walk away**: If the timing is genuinely tied to a known event (contract renewal in Q3, budget cycle in January, post-merger integration), set a specific follow-up date tied to that event and move to nurture. If "timing" is vague and they cannot give a timeframe, it is likely a soft no. --- ### Objection 6: "I need to talk to my [boss/team/partner]" **What it really means**: Either they genuinely need buy-in from others (common and legitimate), or they are using "my boss" as a shield to avoid making a decision. Need to determine which and then help them sell internally. **FFR Response**: "That makes total sense — a decision like this should involve the right people. [Similar role] said the same thing. What they found most helpful was going into that conversation with a clear summary of the business case. I put together a one-page executive summary for them that covered the problem, the solution, the ROI, and the timeline — their [boss/CFO] approved it in the next meeting. Want me to put something similar together for you?" **ABC Response**: "Absolutely — you should get alignment from your team on this. (Acknowledge) I want to make it as easy as possible for you to make the case internally. I know how hard it is to champion a new initiative when you're already busy. (Bridge) Here's what I can do — I'll put together a one-page business case you can share, and if it would help, I'm happy to join a call with your [boss/team] to answer any technical or financial questions directly. Would that make the internal conversation easier? (Close)" **Follow-up question**: "Great — who else will be involved in the decision? And what do you think their main concerns will be? I can prepare materials that address those specifically." **Proof point to deploy**: Offer a one-page executive summary, a pre-built ROI calculator, or a competitive comparison they can share internally. **When to walk away**: If they have been "talking to their boss" for more than 3 weeks with no progress and cannot arrange a meeting that includes the decision-maker, the deal is likely stalled. Offer to engage the decision-maker directly, and if that is declined, move to a gentle breakup. --- ### Objection 7: "We tried something similar before and it didn't work" **What it really means**: Past trauma. They invested time, money, and reputation in a previous solution and it failed. They are risk-averse now and afraid of repeating the mistake. This is an emotional objection as much as a rational one. **FFR Response**: "I appreciate you sharing that — it takes real honesty to say that, and I don't want to waste your time if this would be more of the same. [Company in their space] felt the same way — they had a bad experience with [competitor/previous solution] and were understandably gun-shy. What they found was that most of those failures came down to [specific root cause — implementation support, wrong fit, lack of training, scope creep]. We specifically designed our [approach/onboarding/product] to address that. Would it help if I walked you through exactly what was different in their case and why the outcome changed?" **ABC Response**: "That's really important context, and I'm glad you told me. The last thing I want is to put you through another bad experience. (Acknowledge) Can I ask — what specifically went wrong? I want to make sure we're not repeating the same mistake, and honestly, if the issues you experienced are the same ones we'd have, I'd rather tell you that now. (Bridge) Let me map what went wrong … ## Source & license This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code. - **Author:** [zubair-trabzada](https://github.com/zubair-trabzada) - **Source:** [zubair-trabzada/ai-sales-team-claude](https://github.com/zubair-trabzada/ai-sales-team-claude) - **License:** MIT - **Homepage:** https://www.skool.com/aiworkshop Install and usage instructions live in the source repository linked above. ## Pricing - **Free** — Free ## Security capabilities Automated source analysis of v0.1.0 — what this tool can access: - **Network access:** no - **Filesystem access:** no - **Shell / process execution:** no - **Environment & secrets:** no - **Dynamic code execution:** no *"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.* ## Versions - **0.1.0** — security scan: passed — Imported from the upstream source. ## Links - Listing page: https://agentstack.voostack.com/l/skill-zubair-trabzada-ai-sales-team-claude-sales-objections - Seller: https://agentstack.voostack.com/s/zubair-trabzada - Browse the marketplace: https://agentstack.voostack.com/browse --- Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.