跳到主要内容

sales-and-revenue-operations 标准

Comprehensive sales and revenue operations skill. Use when building a sales team, doing founder-led sales, hiring first sales reps, navigating enterprise deals, implementing product-led sales, designing sales compensation plans, defining ICP, mapping buyer personas, or optimizing the revenue engine (RevOps). Activates for: sales strategy, rev ops, revenue operations, sales enablement, sales compensation, ICP, ideal customer profile, buyer persona, sales process, deal execution, lead scoring, lead routing, lead lifecycle, MQL, SQL, pipeline management, CRM automation, sales qualification, BANT, MEDDIC, founder sales, enterprise sales, product-led sales, startup sales, SDR, AE, quota, ramp, commission plan.

在 GitHub 打开

安装方式

cp -r skills/sales-and-revenue-operations ~/.claude/skills/sales-and-revenue-operations

把该 skill 目录放进客户端 skills 目录。不同客户端的目录可能不同,Claude Code 默认是 ~/.claude/skills/

整仓一次性获取:git clone --depth 1 https://github.com/manojbajaj95/claude-gtm-plugin.git

依赖与权限

  • 无需 API Key
  • 无需联网
  • 依赖外部命令:make
  • 以上为按正文与 frontmatter 自动推断的信号,仅供参考;安装前建议先阅读原文。
触发场景
building a sales teamdoing founder-led saleshiring first sales repsnavigating enterp

SKILL.md 正文

来源 manojbajaj95/claude-gtm-plugin@0830a46 · 许可 MIT · 内容未修改

Sales & Revenue Operations

Workspace Context

Read bootstrap context before asking questions: strategy/brand.md for brand, audience, offer, channels, tools, constraints, and metrics; about/me.md for personal voice; content/ideas.md and content/calendar.md for content planning. Use legacy product-marketing context files only as fallback. Save generated drafts to content/<platform>/drafts/YYYY-MM-DD_short-topic-slug.md, and route durable learnings back to strategy/brand.md, about/me.md, or content/ideas.md.

Operating Contract

This skill is self-contained for its frontmatter scope: use its local instructions, references, scripts, and assets as the playbook; ask only for missing task-specific inputs; hand off to adjacent skills instead of expanding scope; and return an actionable artifact, decision, plan, draft, or diagnostic.

Full-stack sales playbook: founder-led sales, team building, enterprise deals, RevOps, ICP definition, buyer personas, and compensation design.


Quick Start

  1. Assess stage — Founder-led, first reps, or scaling?
  2. Define motion — Inbound, outbound, PLG, or hybrid?
  3. Build ICP — Who are you selling to?
  4. Design process — Discovery → Demo → Close
  5. Instrument RevOps — Lead lifecycle, scoring, routing

ICP & Buyer Persona

ICP Stack (build bottom-up)

┌─────────────────────────────┐
│       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

ICP Scoring

FactorWeight
Problem severity25%
Budget available20%
Champion identified15%
Technical fit15%
Decision timeline15%
Expansion potential10%

The 50-Company Test

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


Founder-Led Sales

Core principles:

  • The founder IS the product — your credibility closes deals early competitors can't
  • Your biggest competitor is indecision (40-60% of B2B purchases end in no decision)
  • Sell before you build — Figma mockups can secure first customers
  • Close the laptop — focus on diagnosis, not demos
  • Book next meeting on the current one to maintain momentum

When to hire: Wait until ~$1M ARR and a repeatable process. Hire in pairs — you need an A/B test.

Hiring framework:

StageWho to HireWhen
Founder-ledNobodyBefore $1M ARR
First AEs2 repsAfter proven repeatability
SDRs1-2When inbound overflows
VP Sales1When 2+ reps hitting quota

Enterprise Sales

Buying committee roles: Champion (internal advocate), Economic Buyer (signs), Technical Buyer (evaluates), End User (uses daily), Blocker (can say no)

JOLT method for indecision:

  1. Judge level of indecision
  2. Offer a firm recommendation
  3. Limit exploration by building trust
  4. Take risk off the table — de-risk the deal

Key tactics:

  • Identify and arm the champion — they sell internally for you
  • Address FOMU (Fear Of Making a Mistake), not just FOMO
  • Make procurement's job easy — prepare all documentation upfront

Sales Qualification

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.


Sales Enablement

Sales Deck (10-12 slides)

  1. Current World Problem, 2. Cost of the Problem, 3. The Shift Happening, 4. Your Approach, 5. Product Walkthrough (3-4 workflows), 6. Proof Points, 7. Case Study, 8. Implementation, 9. ROI/Value, 10. Pricing Overview, 11. Next Steps/CTA

Demo Structure

Opening (2 min) → Discovery Recap (3 min) → Solution Walkthrough (15-20 min) → Interaction → Close (5 min)

Objection Handling

CategoryResponse Approach
PriceROI angle, payment terms
TimingUrgency, cost of delay
CompetitionDifferentiation, unique value
AuthorityArm the champion
Status quoCost of inaction

Revenue Operations

Lead Lifecycle Stages

StageOwnerEntry Criteria
SubscriberMarketingOpts in to content
LeadMarketingBasic info provided
MQLMarketingFit + engagement threshold
SQLSalesAccepted, qualified via call
OpportunitySales AEBANT confirmed
CustomerCSClosed-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.

Lead Scoring

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

Lead Routing Methods

MethodBest For
Round-robinEqual territories
Territory-basedRegional/vertical teams
Account-basedNamed accounts / ABM
Skill-basedComplex 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

Pipeline Stage Hygiene

  • Enforce required fields per stage to block advancement with bad data
  • Flag stale deals (2x average time in stage) automatically
  • Alert on stage skips (Qualified → Proposal without Discovery)
  • Require reason codes on close date pushes

RevOps Metrics

MetricTarget
Lead-to-MQL rate5-15%
MQL-to-SQL rate30-50%
SQL-to-Opportunity50-70%
Win rate20-30%
Speed-to-lead<5 minutes
LTV:CAC ratio3:1 to 5:1

For scoring models and lifecycle definitions: see references/scoring-models.md, references/lifecycle-definitions.md


Sales Compensation

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:

  • Incentivizing only bookings without customer quality
  • Over-complicated plans with too many variables
  • No ramp protection for new hires
  • Ignoring churn in comp design

For detailed comp frameworks: see references/guest-insights.md


Sales Metrics

MetricWhat It Tells You
Win rateSales effectiveness
Sales cycle lengthProcess efficiency
Pipeline coverageForecast reliability (target 3-4x quota)
Lead-to-OpportunityQualification quality
CACAcquisition efficiency
Quota attainmentRep performance

Related Skills

  • outbound-email-strategy — Cold outreach
  • pricing-strategy — Pricing decisions
  • go-to-market-strategy — Full launch planning

质量与来源

所属仓库
manojbajaj95/claude-gtm-plugin
仓库星标
106
最近更新
25 天前
采集时间
今天
commit
0830a46f4cfb
内容指纹
sha256:1d989480ef5d9d1
文件路径
skills/sales-and-revenue-operations/SKILL.md

同仓库其它 Skill

查看全部 50 个
ab-test-setup
When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," or "hypothesis." For tracking implementation, see data-and-funnel-analytics.
manojbajaj95/claude-gtm-plugin 106 原文
Claude CodeCodex CLI
ad-campaign-management
Use when creating, managing, or optimizing paid advertising campaigns across any platform. Covers ad copy generation, ad creative strategy, campaign management, and competitive intelligence. Triggers on: ad copy, ad creative, paid ads, paid advertising, Facebook ads, LinkedIn ads, Google ads, Meta ads, ad campaign, ad strategy, ad testing, competitive ads, competitor ads, ad library, ad analysis, ad creative generation, campaign management, ROAS, CPC, CTR. Use this skill whenever the user mentions ads, paid channels, ad campaigns, ad copy, ad performance, or wants to analyze competitor advertising.
manojbajaj95/claude-gtm-plugin 106 原文
Claude CodeCodex CLI
app-store-optimization
Use this skill when optimizing app store listings, researching keywords, or tracking mobile app performance on Apple App Store and Google Play Store.
manojbajaj95/claude-gtm-plugin 106 原文
Claude CodeCodex CLI
blog-writing-specialist
Comprehensive blog writing skill that handles technical blog posts, personal voice writing, brain dump transformation, and category-aware AEO-optimized content. Use when: (1) writing, editing, or proofreading a blog article or post, (2) transforming unstructured brain dumps into polished posts, (3) writing in specific personal voices (Jarad, Nick Nisi), (4) creating category-aware technology/company/product posts, (5) building tutorials, deep dives, postmortems, benchmarks, or architecture posts, (6) writing engineering blogs, dev blogs, programming blogs, coding tutorials, or documentation posts. Triggers: blog post, blog writing, technical blog, dev tutorial, brain dump, article, content writing, developer article, engineering blog, programming blog, coding tutorial, documentation post, technical writing, blog editing, proofreading, developer content
manojbajaj95/claude-gtm-plugin 106 原文
Claude CodeCodex CLI
bootstrap
Onboard a new GTM project — run an agency-style interview, then generate CLAUDE.md, PROGRESS.md, about/me.md, strategy/brand.md, and scaffold content + assets folders. Use this skill whenever the user wants to set up a new project, onboard a brand, start from scratch, configure their marketing context, or initialize their workspace. Trigger on: bootstrap, onboard, set up my project, get started, configure my brand, initialize, new project setup, brand onboarding, set up my brand, create project structure, onboard my company, set up content folders, prepare my workspace, start a new GTM project. Also use when the user seems to be starting fresh and hasn't set up strategy/brand.md or about/me.md yet.
manojbajaj95/claude-gtm-plugin 106 原文
Claude CodeCodex CLI
brand-messaging-and-positioning
Comprehensive brand messaging, positioning, and value proposition development using proven frameworks including Peep Laja Message Layers, Osterwalder Value Proposition Canvas, Geoffrey Moore positioning, April Dunford's Five Components, StoryBrand SB7, Andy Raskin Strategic Narrative, and Messaging House. Use when developing brand identity, brand messaging architecture, positioning statements, value propositions, messaging hierarchies, brand pillars, taglines, one-liners, elevator pitches, brand guidelines, visual identity systems, or creating Positioning & Messaging Packs. Triggers include: messaging framework, brand positioning, value prop, messaging architecture, brand pillars, brand identity, StoryBrand, positioning statement, brand guidelines, design system, messaging house, corporate identity, brand voice, visual standards.
manojbajaj95/claude-gtm-plugin 106 原文
Claude CodeCodex CLI