菜单
Use before pitching or demoing to a prospect or existing account — to run structured discovery that names the real problem, its cost, the decision process, and whether a human sale is even warranted.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when you need to assess whether a client account is healthy, at risk, or slipping — before renewal, after a rough patch, or on a regular cadence — and decide what to do about it.
Use when a client request is ready to become production work and you must brief creative or media — turning a vague ask into an objective, an audience, and constraints the team can build against.
Use when responding to an RFP or writing a new-business proposal — to decide whether to pursue it, shape the offer, and produce a document a client can say yes to.
Use when preparing the quarterly review a client account faces — to report results against the objective honestly, read what worked, and set what the next quarter buys.
Use when you need to write or change a statement of work — turning an agreed offer into a scope, deliverables, price, and terms that both protect the client and defend the agency's margin.
Use when reviewing compensation for a role, a team, or the whole population — checks where people sit against defensible bands, finds equity gaps, and produces a ranked, costed set of adjustments.
| name | sales-discovery |
| description | Use before pitching or demoing to a prospect or existing account — to run structured discovery that names the real problem, its cost, the decision process, and whether a human sale is even warranted. |
Discovery is the work of understanding an account's real problem before you try to solve it. In a product-led company most accounts should never need a salesperson, so discovery has a second job: qualify hard and disqualify fast, spending human time only where it genuinely unlocks value. A demo before discovery is a pitch into the dark.
Account: <name>
Problem (their words): <statement> — cost: <quantified>
People: economic buyer <who> | daily user <who> | blocker <who>
Decision: process <how> | timeline <when> | budget <reality>
Product usage signal: <what they already do>
Verdict: QUALIFIED → demo to <outcome> | DISQUALIFIED → route to self-serve because <reason>
Signal logged: <objection / stall reason → routed to Product/Growth>