免费在 GitHub 公开

objection-handler

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", "they said they're happy with their current vendor". Diagnoses what the objection really means, picks the response pattern (clarify, reframe, prove, defer or walk away), writes responses for email, call and LinkedIn, and builds a reusable objection library with proof for each.

中文简介正在准备中。当前显示原文说明。

prosyo-ai/gtm-skill星标 11(GitHub 11 + cccskills 0)

集成工具LinkedIn

实测评分未实测

查看安装方法

包含的文件（2）

SKILL.md3.5 KB
references/objection-library.md2.4 KB

SKILL.md（原文）

安装前可以查看交给 AI 代理的指令内容。

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."

评价

还没有评价。欢迎分享你的使用感受。

无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

同一仓库的技能

abm-account-plan

免费

Use this skill when you run account-based marketing or sales on a short list of named accounts: "build an ABM plan", "account plan for our top 20", "how do we break into this enterprise account", "1:1 ABM program". Picks the accounts and the ABM tier (1:1, 1:few, 1:many), maps the buying group, writes the account insight and value hypothesis, plans coordinated sales and marketing plays by stage, and sets the metrics (engagement, meetings, pipeline) that show it is working.

中文简介正在准备中。当前显示原文说明。