Revops
Design lead scoring, routing, MQL-to-SQL handoffs, and CRM hygiene so marketing spend actually reaches sales pipelines.
Overview
RevOps is an agent skill most often used in Grow (also Validate pricing, Operate iterate) that designs lead lifecycle, scoring, routing, and CRM handoffs between marketing and sales.
Install
npx skills add https://github.com/coreyhaines31/marketingskills --skill revopsWhat is this skill?
- Frames RevOps as a unified revenue engine across marketing, sales, and customer success
- Intake covers PLG vs sales-led motion, ACV, sales cycle, and current CRM stack
- Addresses lead scoring, routing, MQL/SQL definitions, and deal desk patterns
- Uses product marketing context files when present before asking discovery questions
- Points to cold-email, emails, and pricing skills for adjacent tactics
- Skill metadata version 2.0.0
Adoption & trust: 56.6k installs on skills.sh; 32.4k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Leads pile up in marketing tools while sales chases the wrong accounts because stages, scoring, and handoff rules were never defined.
Who is it for?
Hybrid or sales-assisted indie SaaS with a CRM who need MQL/SQL clarity and marketing-to-sales automation design.
Skip if: Writing individual cold emails or full pricing strategy without pipeline context—use cold-email or pricing skills first.
When should I use this skill?
RevOps, lead scoring, routing, MQL/SQL, pipeline stages, CRM automation, marketing-to-sales handoff, or leads not reaching sales.
What do I get? / Deliverables
You get documented lifecycle stages, qualification criteria, routing logic, and hygiene practices aligned to your GTM motion and CRM stack.
- Lead lifecycle and stage definitions
- Scoring and routing recommendations
- Handoff and data hygiene operating guidelines
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Grow is the canonical shelf because RevOps optimizes how captured demand moves through lifecycle stages toward revenue after you have something to sell. Lifecycle matches lead stages, qualification rules, pipeline definitions, and marketing-to-sales handoff timing the skill centers on.
Where it fits
Align qualification thresholds with ACV and packaging before scaling paid acquisition.
Define MQL/SQL criteria and routing rules so product-qualified leads reach sales at the right moment.
Audit CRM data hygiene and stage drift after a quarter of mixed PLG and outbound leads.
How it compares
Revenue operations process design—not a CRM plugin and not a launch announcement playbook.
Common Questions / FAQ
Who is revops for?
Founders and small GTM teams connecting marketing capture to sales closure who own or influence CRM stages and lead routing.
When should I use revops?
In Grow lifecycle work when defining MQL/SQL, pipeline stages, or handoffs; during Validate pricing when motion affects qualification; and in Operate when fixing data hygiene—when you mention RevOps, lead scoring, or leads not reaching sales.
Is revops safe to install?
It advises on process and may reference CRM workflows you implement yourself; review the Security Audits panel on this Prism page before granting agent access to production CRM credentials.
Workflow Chain
SKILL.md
READMESKILL.md - Revops
# RevOps You are an expert in revenue operations. Your goal is to help design and optimize the systems that connect marketing, sales, and customer success into a unified revenue engine. ## Before Starting **Check for product marketing context first:** If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. Gather this context (ask if not provided): 1. **GTM motion** — Product-led (PLG), sales-led, or hybrid? 2. **ACV range** — What's the average contract value? 3. **Sales cycle length** — Days from first touch to closed-won? 4. **Current stack** — CRM, marketing automation, scheduling, enrichment tools? 5. **Current state** — How are leads managed today? What's working and what's not? 6. **Goals** — Increase conversion? Reduce speed-to-lead? Fix handoff leaks? Build from scratch? Work with whatever the user gives you. If they have a clear problem area, start there. Don't block on missing inputs — use what you have and note what would strengthen the solution. --- ## Core Principles ### Single Source of Truth One system of record for every lead and account. If data lives in multiple places, it will conflict. Pick a CRM as the canonical source and sync everything to it. ### Define Before Automate Get stage definitions, scoring criteria, and routing rules right on paper before building workflows. Automating a broken process just creates broken results faster. ### Measure Every Handoff Every handoff between teams is a potential leak. Marketing-to-sales, SDR-to-AE, AE-to-CS — each needs an SLA, a tracking mechanism, and someone accountable for follow-through. ### Revenue Team Alignment Marketing, sales, and customer success must agree on definitions. If marketing calls something an MQL but sales won't work it, the definition is wrong. Alignment meetings aren't optional. --- ## Lead Lifecycle Framework ### Stage Definitions | Stage | Entry Criteria | Exit Criteria | Owner | |-------|---------------|---------------|-------| | **Subscriber** | Opts in to content (blog, newsletter) | Provides company info or shows engagement | Marketing | | **Lead** | Identified contact with basic info | Meets minimum fit criteria | Marketing | | **MQL** | Passes fit + engagement threshold | Sales accepts or rejects within SLA | Marketing | | **SQL** | Sales accepts and qualifies via conversation | Opportunity created or recycled | Sales (SDR/AE) | | **Opportunity** | Budget, authority, need, timeline confirmed | Closed-won or closed-lost | Sales (AE) | | **Customer** | Closed-won deal | Expands, renews, or churns | CS / Account Mgmt | | **Evangelist** | High NPS, referral activity, case study | Ongoing program participation | CS / Marketing | ### MQL Definition An MQL requires both **fit** and **engagement**: - **Fit score** — Does this person match your ICP? (company size, industry, role, tech stack) - **Engagement score** — Have they shown buying intent? (pricing page, demo request, multiple visits) Neither alone is sufficient. A perfect-fit company that never engages isn't an MQL. A student downloading every