sales-and-revenue-operations by manojbajaj95/claude-gtm-plugin
npx skills add https://github.com/manojbajaj95/claude-gtm-plugin --skill sales-and-revenue-operations全栈销售手册:创始人主导的销售、团队建设、企业级交易、营收运营、理想客户画像定义、买家角色以及薪酬设计。
┌─────────────────────────────┐
│ 购买中心 │ ← 所有决策相关方
├─────────────────────────────┤
│ 用户角色 │ ← 日常使用者
├─────────────────────────────┤
│ 买家角色 │ ← 最终付款人
├─────────────────────────────┤
│ 公司画像 │ ← 企业特征
└─────────────────────────────┘
公司画像: 行业/垂直领域、规模(员工数/营收)、发展阶段、地理位置、技术栈
买家角色: 职位/角色、资历、目标与关键绩效指标、决策权、关注点
用户角色: 日常工作流、痛点、技术熟练度
购买中心角色: 内部推动者、经济型买家、技术评估者、最终用户、阻碍者
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
| 因素 | 权重 |
|---|
| 问题严重性 | 25% |
| 可用预算 | 20% |
| 已识别内部推动者 | 15% |
| 技术匹配度 | 15% |
| 决策时间线 | 15% |
| 扩展潜力 | 10% |
列出50家符合条件的具体公司。在其中20家公司找到买家的姓名。联系其中10家。如果做不到这一点,说明你的理想客户画像不够具体。
关于完整的角色画布、购买中心映射图、访谈问题和匹配度评分,请参阅 references/full-guide.md
核心原则:
何时招聘: 等待至约100万美元年度经常性收入且流程可重复时。成对招聘 —— 你需要进行A/B测试。
招聘框架:
| 阶段 | 招聘对象 | 时机 |
|---|---|---|
| 创始人主导 | 不招聘 | 100万美元年度经常性收入之前 |
| 首批客户经理 | 2名销售代表 | 流程可重复性得到验证后 |
| 销售开发代表 | 1-2名 | 集客线索溢出时 |
| 销售副总裁 | 1名 | 当2名以上销售代表达成配额时 |
购买委员会角色: 内部推动者(内部倡导者)、经济型买家(签字人)、技术型买家(评估者)、最终用户(日常使用者)、阻碍者(可以否决)
应对犹豫不决的JOLT方法:
关键策略:
BANT: 预算 · 决策权 · 需求 · 时间线
MEDDIC: 指标 · 经济型买家 · 决策标准 · 决策流程 · 识别痛点 · 内部推动者
规则: 严格鉴定。"不"是一个成功的结果。如果匹配度不够,在第一次通话时就应取消资格。
开场(2分钟)→ 需求挖掘回顾(3分钟)→ 解决方案演示(15-20分钟)→ 互动 → 收尾(5分钟)
| 类别 | 回应方法 |
|---|---|
| 价格 | 投资回报率角度、付款条款 |
| 时机 | 紧迫性、延迟成本 |
| 竞争 | 差异化、独特价值 |
| 决策权 | 武装内部推动者 |
| 维持现状 | 不作为的成本 |
| 阶段 | 负责人 | 进入标准 |
|---|---|---|
| 订阅者 | 市场营销 | 选择接收内容 |
| 线索 | 市场营销 | 提供基本信息 |
| 营销合格线索 | 市场营销 | 匹配度 + 互动阈值 |
| 销售合格线索 | 销售 | 已接受,通过通话鉴定 |
| 商机 | 销售客户经理 | BANT已确认 |
| 客户 | 客户成功 | 已成交 |
营销合格线索 = 匹配度评分(他们是谁)+ 互动度评分(他们做了什么)。仅凭任何一项都不足以成为合格线索。
营销合格线索转销售合格线索的服务水平协议: 4小时内联系;48小时内鉴定或拒绝。
显性(匹配度): 公司规模、行业、职位、技术栈
隐性(互动度): 定价页面访问、演示请求、邮件点击、产品使用情况
负面: 竞争对手域名、学生邮箱、退订
| 方法 | 最适合 |
|---|---|
| 轮询 | 平等分配的销售区域 |
| 基于区域 | 区域/垂直团队 |
| 基于客户 | 指定客户/基于客户的营销 |
| 基于技能 | 复杂交易、多产品 |
线索响应速度: 5分钟内联系,转化可能性提高21倍。30分钟后,转化率下降10倍。
关于路由决策树和自动化手册,请参阅 references/routing-rules.md、references/automation-playbooks.md
| 指标 | 目标 |
|---|---|
| 线索转营销合格线索率 | 5-15% |
| 营销合格线索转销售合格线索率 | 30-50% |
| 销售合格线索转商机率 | 50-70% |
| 成交率 | 20-30% |
| 线索响应速度 | <5分钟 |
| 客户终身价值与获客成本比率 | 3:1 到 5:1 |
关于评分模型和生命周期定义,请参阅 references/scoring-models.md、references/lifecycle-definitions.md
标准结构: 50% 底薪 / 50% 浮动薪酬(目标总薪酬)。这是一个起点,并非铁律。
现代薪酬计划应与客户成果挂钩,而不仅仅是签约额。 那些签下高流失率交易的销售代表,其收入应低于签下高留存率客户的销售代表。
适应期: 中小型企业3-6个月,企业级6-12个月。在适应期内提供有保障的预支薪酬或降低配额。
简洁性规则: 如果销售代表无法立即计算出某个行动如何影响其薪酬,那么该计划就过于复杂。
常见错误:
关于详细的薪酬框架,请参阅 references/guest-insights.md
| 指标 | 说明 |
|---|---|
| 成交率 | 销售有效性 |
| 销售周期长度 | 流程效率 |
| 管道覆盖率 | 预测可靠性(目标是配额的3-4倍) |
| 线索转商机率 | 资格鉴定质量 |
| 获客成本 | 获客效率 |
| 配额达成率 | 销售代表绩效 |
outbound-email-strategy —— 冷启动邮件策略pricing-strategy —— 定价策略go-to-market-strategy —— 完整的上市规划每周安装量
101
代码仓库
GitHub 星标数
22
首次出现
2026年3月11日
安全审计
安装于
opencode101
gemini-cli27
github-copilot27
codex27
amp27
cline27
Full-stack sales playbook: founder-led sales, team building, enterprise deals, RevOps, ICP definition, buyer personas, and compensation design.
┌─────────────────────────────┐
│ BUYING CENTER │ ← All decision stakeholders
├─────────────────────────────┤
│ USER PERSONA │ ← Daily user
├─────────────────────────────┤
│ BUYER PERSONA │ ← Signs the check
├─────────────────────────────┤
│ COMPANY PROFILE │ ← Firmographics
└─────────────────────────────┘
Company Profile: industry/vertical, size (employees/revenue), stage, geography, tech stack
Buyer Persona: title/role, seniority, goals & KPIs, decision authority, what they care about
User Persona: daily workflow, pain points, tech savviness
Buying Center Roles: Champion, Economic Buyer, Technical Evaluator, End User, Blocker
| Factor | Weight |
|---|---|
| Problem severity | 25% |
| Budget available | 20% |
| Champion identified | 15% |
| Technical fit | 15% |
| Decision timeline | 15% |
| Expansion potential | 10% |
List 50 specific companies that fit. Find the buyer's name at 20 of them. Reach out to 10. If you can't do this, your ICP isn't specific enough.
For full persona canvases, buying center maps, interview questions, and fit scoring: see references/full-guide.md
Core principles:
When to hire: Wait until ~$1M ARR and a repeatable process. Hire in pairs — you need an A/B test.
Hiring framework:
| Stage | Who to Hire | When |
|---|---|---|
| Founder-led | Nobody | Before $1M ARR |
| First AEs | 2 reps | After proven repeatability |
| SDRs | 1-2 | When inbound overflows |
| VP Sales | 1 | When 2+ reps hitting quota |
Buying committee roles: Champion (internal advocate), Economic Buyer (signs), Technical Buyer (evaluates), End User (uses daily), Blocker (can say no)
JOLT method for indecision:
Key tactics:
BANT: Budget · Authority · Need · Timeline
MEDDIC: Metrics · Economic Buyer · Decision Criteria · Decision Process · Identify Pain · Champion
Rule: Qualify ruthlessly. "No" is a successful outcome. Disqualify on the first call if fit isn't there.
Opening (2 min) → Discovery Recap (3 min) → Solution Walkthrough (15-20 min) → Interaction → Close (5 min)
| Category | Response Approach |
|---|---|
| Price | ROI angle, payment terms |
| Timing | Urgency, cost of delay |
| Competition | Differentiation, unique value |
| Authority | Arm the champion |
| Status quo | Cost of inaction |
| Stage | Owner | Entry Criteria |
|---|---|---|
| Subscriber | Marketing | Opts in to content |
| Lead | Marketing | Basic info provided |
| MQL | Marketing | Fit + engagement threshold |
| SQL | Sales | Accepted, qualified via call |
| Opportunity | Sales AE | BANT confirmed |
| Customer | CS | Closed-won |
MQL = Fit Score (who they are) + Engagement Score (what they do). Neither alone qualifies.
MQL-to-SQL SLA: Contact within 4 hours; qualify or reject within 48 hours.
Explicit (fit): Company size, industry, title, tech stack
Implicit (engagement): Pricing page visits, demo requests, email clicks, product usage
Negative: Competitor domains, student emails, unsubscribes
| Method | Best For |
|---|---|
| Round-robin | Equal territories |
| Territory-based | Regional/vertical teams |
| Account-based | Named accounts / ABM |
| Skill-based | Complex deals, multi-product |
Speed-to-lead: Contact within 5 minutes = 21x more likely to qualify. After 30 minutes, conversion drops 10x.
For routing decision trees and automation playbooks: see references/routing-rules.md, references/automation-playbooks.md
| Metric | Target |
|---|---|
| Lead-to-MQL rate | 5-15% |
| MQL-to-SQL rate | 30-50% |
| SQL-to-Opportunity | 50-70% |
| Win rate | 20-30% |
| Speed-to-lead | <5 minutes |
| LTV:CAC ratio | 3:1 to 5:1 |
For scoring models and lifecycle definitions: see references/scoring-models.md, references/lifecycle-definitions.md
Standard structure: 50% base / 50% variable (OTE). This is a starting point, not a law.
Modern comp plans align with customer outcomes, not just bookings. Reps who close churny deals should earn less than those who close sticky customers.
Ramp periods: 3-6 months for SMB, 6-12 months for enterprise. Provide guaranteed draw or reduced quotas during ramp.
Simplicity rule: If reps can't instantly calculate how an action affects their pay, the plan is too complex.
Common mistakes:
For detailed comp frameworks: see references/guest-insights.md
| Metric | What It Tells You |
|---|---|
| Win rate | Sales effectiveness |
| Sales cycle length | Process efficiency |
| Pipeline coverage | Forecast reliability (target 3-4x quota) |
| Lead-to-Opportunity | Qualification quality |
| CAC | Acquisition efficiency |
| Quota attainment | Rep performance |
outbound-email-strategy — Cold outreachpricing-strategy — Pricing decisionsgo-to-market-strategy — Full launch planningWeekly Installs
101
Repository
GitHub Stars
22
First Seen
Mar 11, 2026
Security Audits
Gen Agent Trust HubPassSocketPassSnykPass
Installed on
opencode101
gemini-cli27
github-copilot27
codex27
amp27
cline27
创业转型指南:如何利用四P框架决定何时进行200%的转型
806 周安装