All directories
SkillOperationsSales

Revenue Operations

When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes.

Open on GitHubBrowse more skills
01

Overview

Revenue Operations is a growth/marketing skill from Corey Haines’ Marketing Skills collection (github.com/coreyhaines31/marketingskills). When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. The skill is structured around practical workflows—covering Before Starting, Core Principles, Lead Lifecycle Framework, Lead Scoring, Lead Routing, Pipeline Stage Management—so Claude can move from context gathering to concrete artifacts (briefs, copy, checklists, or audit reports) instead of generic advice. Pair it with related skills in the same collection: `analytics`, `attribution`, `sales-enablement`.

SaaSOther

Work with LimeDock

Using this skill? LimeDock can wire it into a durable automation you own.

Skills show what's possible. LimeDock builds and runs the owned marketing, sales, and ops automations around them.

We sell owned automations for SaaS teams — live workflows that plug into Slack, CRM, and your internal platform — not just a skill list.

Book a workflow call
02

Link

https://github.com/coreyhaines31/marketingskills/tree/main/skills/revops
03

Installation guide

Option A — Install just this skill (recommended)

npx skills add coreyhaines31/marketingskills --skill revops

Option B — Install the full Marketing Skills collection

npx skills add coreyhaines31/marketingskills

That unlocks related skills like `cro`, `copywriting`, `emails`, `ads`, and `seo-audit`.

Option C — Manual install (Claude Code)

git clone https://github.com/coreyhaines31/marketingskills.git /tmp/marketingskills
mkdir -p ~/.claude/skills
cp -R /tmp/marketingskills/skills/revops ~/.claude/skills/revops

Claude.ai

Customize → Skills → Upload the `revops` folder as a zip / `SKILL.md` → enable the skill.

Always skim `SKILL.md` before first use so you know its triggers and related skills.

04

How to use it

1. **Trigger it with revenue operations language** — mention the job by name or ask for the deliverable this skill owns. 2. **Share product context up front** — ICP, offer, URL, constraints, and any metrics. If `.agents/product-marketing.md` (or `.claude/product-marketing.md`) exists, the skill will read it first. 3. **Let it run the assessment** — answer clarifying questions before asking for final copy/strategy. 4. **Request a concrete artifact** — brief, audit, page outline, sequence, scorecard, or launch checklist. 5. **Close the loop** — feed performance data back so the next iteration compounds.

**Typical sections it covers:** Before Starting, Core Principles, Lead Lifecycle Framework, Lead Scoring, Lead Routing, Pipeline Stage Management, CRM Automation Workflows, Deal Desk Processes.

If Claude does not auto-select it, say: “Use the Revenue Operations skill (`revops`)…”.

05

Example prompts

  • “Use the Revenue Operations skill to assess our current state and produce a prioritized action plan.”
  • “Walk me through how Revenue Operations would approach this step by step, then execute on our product.”
  • “Create a reusable checklist and prompt template for running Revenue Operations monthly.”
  • “Review my draft plan and improve it with Revenue Operations. Call out assumptions and risks.”
06

Use cases and examples

  • Run a full RevOps workflow on a live product or campaign
  • Produce a reusable RevOps brief/checklist for the team
  • Audit the current state and prioritize fixes for revops
  • Generate first-draft artifacts then refine with brand constraints
  • Connect RevOps output to measurement and next experiments
  • Document a playbook entry so revops learnings compound
  • Apply the “Before Starting” guidance to a current initiative
  • Apply the “Core Principles” guidance to a current initiative
07

Prerequisites

  • Claude Code, Claude.ai Skills, or another Agent Skills–compatible host
  • Product/brand context (ICP, offer, URLs, constraints) for grounded outputs
  • Optional: `.agents/product-marketing.md` or `.claude/product-marketing.md` in the repo
  • Permission to install third-party skills — audit SKILL.md first
  • Optional: analytics or ad-platform access when the task needs real performance data
08

Tips

  • Keep triggers specific so Revenue Operations fires only when that job is requested (avoids context tax).
  • Load product-marketing context (ICP, voice, offer) before asking for final copy or strategy.
  • Prefer one sharp deliverable per turn—brief, audit, or draft—then iterate with data.
  • Audit `SKILL.md` and any scripts before production use; treat community skills as code.
  • Pair with `analytics` and `attribution` when the workflow spans channels.
09

Sources