revops

Trigger phrases

Phrases that activate this skill when typed to Claude Code:

• RevOps
• lead scoring
• lead routing
• marketing-to-sales handoff
• pipeline stages

What it does

revops is a Claude Code skill from Corey Haines’s marketing-skills repo. It turns Claude into a revenue-operations consultant who handles lead scoring, routing rules, MQL/SQL definitions, pipeline-stage exit criteria, and the data-hygiene processes that keep CRM trustworthy. The skill activates when you mention “RevOps”, “lead scoring”, “lead routing”, “marketing-to-sales handoff”, or “pipeline stages”.

The output of a session is a RevOps spec: lead-scoring model with point allocations, routing rules (round-robin / territory / vertical), MQL/SQL definitions with rejection criteria, pipeline-stage definitions with entry/exit rules, CRM hygiene playbook, and SLA agreements between marketing and sales.

When to use it

Reach for it when:

• Sales is complaining marketing sends bad leads; marketing is complaining sales drops the good ones
• You’re standing up a CRM (HubSpot, Salesforce) and want it built right the first time
• Lead-handoff has no SLA and the loudest rep wins every dispute

When not to reach for it:

• You don’t have a sales team; RevOps without sales is overengineering
• Your lead volume is too low to need scoring — manually triage instead

Install

The skill is distributed via Corey Haines’s marketing-skills repo. Install via the repo’s recommended path — copy the revops SKILL.md into your project’s .claude/skills/revops/ directory, or use the repo’s plugin install if you’ve set it up.

Once installed, the skill activates on the trigger phrases above. The first time it runs, it will check for .agents/product-marketing-context.md (or .claude/product-marketing-context.md) — populating that file with your product context first dramatically improves output quality across all of Haines’s marketing skills.

What a session looks like

A typical session has three phases:

1. Definitions. MQL, SQL, opportunity, customer — written down with explicit entry and rejection criteria. Most marketing-to-sales fights trace to these being verbal-only.
2. Scoring + routing. Demographic + behavioral score with point allocations, routing rules, fast-lane criteria for high-fit leads, the auto-disqualify rules.
3. Pipeline + SLAs. Pipeline-stage exit criteria, marketing-sales SLAs (response time, lead-acceptance rate), data-hygiene playbook, weekly RevOps review cadence.

The discipline that makes it work: every fuzzy term gets a written definition with examples. “Qualified” without a definition is where the marketing-to-sales relationship dies.

Receipts

Honest reporting on what revops produces and where it has limits:

Where it works well:

• Written MQL/SQL definitions resolve more marketing-sales fights than any meeting
• Auto-disqualify rules catch the obviously-wrong leads before they pollute CRM
• The SLA framework gives both teams a fair fight on response and acceptance metrics

Where it backfires:

• CRM-specific implementation details vary; the spec is platform-neutral by default
• Lead scoring is only as good as the conversion data — early-stage scoring is best-guess until you have outcomes

Pattern that works: ship the definitions and SLAs first, scoring second. Most teams reverse this and end up with a sophisticated scoring model on top of a fuzzy MQL definition.

Source and attribution

Originally written by Corey Haines. The canonical SKILL.md and any supporting files live in the revops folder of his marketing-skills repository.

License: MIT. You can install, adapt, and redistribute the skill, with attribution preserved.

This page documents the skill from a practitioner’s perspective. For the formal spec and any updates, defer to the source repo.