Sales And Revenue Operations logo

Sales And Revenue Operations

Community
manojbajaj95
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.

Overview

Publishermanojbajaj95
Repositoryclaude-gtm-plugin
Skill namesales-and-revenue-operations
Stars
109
Forks
34
Bundled files
6
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 6 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by manojbajaj95 on GitHub. Read the source before you install it.

Installation

Install the Sales And Revenue Operations AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/manojbajaj95/claude-gtm-plugin/tree/main/skills/sales-and-revenue-operations
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/manojbajaj95/claude-gtm-plugin.git /tmp/claude-gtm-plugin
mkdir -p .claude/skills
cp -r /tmp/claude-gtm-plugin/skills/sales-and-revenue-operations .claude/skills/sales-and-revenue-operations
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Sales And Revenue Operations in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Sales And Revenue Operations on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Sales And Revenue Operations is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Sales And Revenue Operations AI skill do?

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, BA...

Why use Sales And Revenue Operations on TypingMind?

Because you install it once and use it with any model. Sales And Revenue Operations is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Sales And Revenue Operations in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/manojbajaj95/claude-gtm-plugin/tree/main/skills/sales-and-revenue-operations. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Sales And Revenue Operations?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Sales And Revenue Operations?

As many as you like. As long as a model supports skills, you can use Sales And Revenue Operations with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Sales And Revenue Operations AI skill free?

Yes. It is published on GitHub by manojbajaj95 under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇