revops

Overview of revops skill

What the revops skill is for

The revops skill helps an AI agent design and improve the operating system between marketing, sales, and customer success. In practice, that means lead lifecycle definitions, MQL and SQL criteria, lead scoring, routing logic, handoff SLAs, CRM automation, and the data rules needed to make those processes reliable.

Best-fit users and teams

This revops skill is best for operators and GTM leaders who need structure, not just ideas: RevOps managers, CRM admins, demand gen leads, sales ops, founders building their first funnel, and consultants cleaning up marketing-to-sales handoff. It is especially useful when leads are getting lost, sales rejects too many “qualified” leads, or teams disagree on stage definitions.

Real job-to-be-done

Most users do not need a generic explanation of revenue operations. They need a working model they can implement in HubSpot, Salesforce, or a mixed stack. The revops skill is strongest when you want to turn fuzzy goals like “fix lead routing” or “set up MQLs” into concrete stage definitions, score thresholds, routing rules, and automation steps.

What makes this revops skill different

The main differentiator is that it is not limited to theory. The repository includes practical reference files for:

• lifecycle stage definitions
• routing decision trees
• scoring models
• automation playbooks

That gives the skill better implementation scaffolding than an ordinary prompt, especially for revops for CRM Operations where definitions, ownership, and triggers need to line up.

When this skill is a good install decision

Install the revops skill if you want repeatable help with:

• defining lifecycle stages from subscriber to customer
• building explicit and behavioral lead scoring
• creating sales response SLAs
• routing leads by account, territory, ACV, or round-robin
• translating process design into CRM workflow logic

If you only need one-off copy, cold outreach, or pricing strategy, this is not the right skill.

How to Use revops skill

Install context for revops

This repository does not surface a skill-specific install command inside SKILL.md, so the practical pattern is to add the parent skills repo, then invoke revops from that installed collection:

npx skills add https://github.com/coreyhaines31/marketingskills --skill revops

After install, open skills/revops/SKILL.md first, then the supporting reference files.

Read these files before first real use

For a fast, high-signal revops guide through the repo, read in this order:

1. skills/revops/SKILL.md
2. skills/revops/references/lifecycle-definitions.md
3. skills/revops/references/scoring-models.md
4. skills/revops/references/routing-rules.md
5. skills/revops/references/automation-playbooks.md
6. skills/revops/evals/evals.json

That order matters because the skill assumes you define stages before scoring, and scoring before automation.

Start with business context, not tooling

The skill explicitly wants core operating context before making recommendations. Strong inputs include:

• GTM motion: PLG, sales-led, or hybrid
• ACV range
• sales cycle length
• current stack: CRM, MAP, enrichment, scheduling
• current lead process and biggest failure points

If your repo has .agents/product-marketing-context.md or .claude/product-marketing-context.md, the skill is designed to use that first. This reduces repeated discovery questions and improves fit.

What input the revops skill needs

The revops skill performs best when you provide:

• current lifecycle stages, even if messy
• example lead sources
• who owns each stage today
• what sales accepts or rejects
• current scoring fields or scoring complaints
• routing constraints like territories, named accounts, or enterprise thresholds
• target SLAs and operational limits

Without that, the output may sound reasonable but stay too generic to implement.

Turn a rough request into a strong revops prompt

Weak prompt:
“Help us with RevOps.”

Better prompt:
“We are a hybrid SaaS company using HubSpot. ACV is $18k to $40k. Marketing sends demo requests, webinars, and content leads to sales, but reps complain MQLs are weak and follow-up is inconsistent. Define lifecycle stages, propose MQL and SQL criteria, build a fit plus engagement scoring model, and suggest routing plus SLA workflows we can implement in HubSpot.”

This works better because it gives the skill enough context to choose thresholds, ownership, and automation logic.

Example prompt for CRM operations work

For revops for CRM Operations, ask for both policy and implementation:

“Use the revops skill to design a lead management system for Salesforce. We are sales-led, $60k ACV, 90-day cycle, US and EMEA territories. We need lifecycle definitions, score thresholds, routing rules for enterprise vs mid-market, rejection reasons, recycling logic, and the workflow steps an admin should build.”

That phrasing pushes the output beyond strategy into admin-ready structure.

Suggested workflow for first-time usage

A practical revops usage pattern is:

1. define lifecycle stages
2. set entry and exit criteria
3. assign owners and SLAs
4. design scoring dimensions
5. map routing logic
6. translate into CRM automation
7. test with edge cases
8. refine based on rejects, delays, and conversion quality

This mirrors the supporting references and prevents bad automation built on unclear definitions.

Use the references as implementation blocks

The best part of this revops skill is the reference set. Use each file as a building block:

• lifecycle-definitions.md for stage names, handoff criteria, and recycling
• scoring-models.md for explicit fit and implicit engagement scoring
• routing-rules.md for named account, territory, ACV, and round-robin logic
• automation-playbooks.md for HubSpot-style workflows and SLA enforcement

If you skip those files, you lose most of the practical value of the skill.

Evals show what good output should include

evals/evals.json is worth reading because it shows expected behaviors, not just topics. For example, outputs should:

• check for product marketing context first
• define all lifecycle transitions clearly
• align marketing and sales definitions
• include CRM implementation guidance
• cover scoring and handoff process together

That makes the evals a useful quality checklist for your own revops usage.

Practical constraints and tradeoffs

This skill is strongest for process architecture and CRM logic, not live system auditing. It can design a sound model, but it cannot verify your actual field schema, broken workflows, duplicate rules, or attribution data unless you provide them. It also assumes you should define before automate, which is correct for most teams but slower than patching one symptom fast.

Common use cases where it adds real value

High-value uses for the revops skill include:

• first lifecycle framework for a growing B2B SaaS team
• MQL redesign after sales trust breaks down
• routing cleanup when enterprise and SMB leads are mixed
• SLA and escalation design for inbound response
• lead recycling and rejection reason design
• score model calibration for higher-ACV motions

revops skill FAQ

Is revops better than a normal prompt?

Yes, for structured operations work. A normal prompt may suggest generic funnel advice. The revops skill has embedded patterns for lifecycle stages, scoring, routing, and automation, plus references that make outputs more implementation-oriented.

Is the revops skill beginner-friendly?

Mostly yes, if you can describe your funnel and tools. You do not need deep RevOps experience to get value, but beginners should give more business context and ask for definitions plus examples, not just “best practices.”

What CRMs and tools fit this skill best?

HubSpot is the clearest fit because the references include workflow recipes in that style, but the logic also transfers well to Salesforce and mixed GTM stacks. The real fit is not the brand of CRM; it is whether you need formal definitions, routing logic, and automation design.

When should I not use this revops skill?

Do not use it for:

• outbound copywriting
• pricing and packaging strategy
• campaign creative
• deep database debugging without system details

It is a process-design skill, not a universal GTM assistant.

Does revops cover only lead scoring?

No. Lead scoring is one part of the skill. The broader revops guide covers lifecycle stages, ownership, handoff rules, routing, SLAs, rejection and recycle flows, and automation patterns.

Is this useful for small teams?

Yes, especially when a founder or first operator is setting up CRM rules for the first time. Small teams often benefit from the stage and ownership clarity even more than large teams, because informal handoffs break quickly as volume rises.

How to Improve revops skill

Give complete operating constraints upfront

The fastest way to improve revops output quality is to provide the constraints that change design decisions:

• ACV
• sales cycle
• team structure
• GTM motion
• routing model
• lead volume
• current tools
• current conversion bottlenecks

These variables affect whether a strict MQL model, rep-based ownership, or queue-based routing makes sense.

Ask for decision criteria, not just recommendations

Good revops outputs explain why a lead becomes an MQL, why it routes to a team, and why an SLA should be 4 hours instead of 24. If the first answer is too abstract, ask:

• “Show entry and exit criteria for each stage.”
• “List rejection reasons and recycle rules.”
• “Translate this into workflow triggers and actions.”

That turns strategy into something a CRM admin can build.

Provide examples of real leads and edge cases

The skill improves significantly when you give sample records such as:

• enterprise target account with low engagement
• small inbound demo request with high intent
• webinar lead from a non-target industry
• existing customer who fills a new form

These edge cases expose weak routing and scoring rules early.

Calibrate scoring against your actual sales motion

A common failure mode is overweighting engagement and underweighting fit. For higher ACV or enterprise sales, ask the revops skill to separate:

• explicit fit score
• implicit engagement score
• high-intent override events

That usually produces better prioritization than one blended score.

Improve revops for CRM Operations with field-level detail

If your goal is revops for CRM Operations, include the actual properties and objects involved:

• contact fields
• account fields
• owner fields
• territory markers
• lifecycle stage property names
• activity fields used for SLA measurement

This lets the skill produce workflow logic that maps more directly to your CRM reality.

Watch for over-designed processes

Another common issue is asking the revops skill for a mature enterprise framework when your team cannot operate it. If you have one SDR, two AEs, and low lead volume, say so. Simpler routing, fewer stage transitions, and lighter scoring are often better.

Iterate after the first draft with rejection data

The best follow-up prompt is not “make it better,” but something like:
“Sales rejected 40% of MQLs because title fit was weak and students were getting scored too highly. Revise the scoring model, add negative scoring, and update routing rules.”

That gives the skill operational feedback it can use.

Use the reference files to pressure-test outputs

After the first answer, compare it against:

• stage templates in references/lifecycle-definitions.md
• fit and behavior examples in references/scoring-models.md
• fallback routing in references/routing-rules.md
• SLA workflows in references/automation-playbooks.md

If the output skips one of those layers, ask for that missing layer explicitly.

Ask for rollout order, not just end-state design

A practical improvement prompt is:
“Give me a 30-day rollout plan for this revops design, including what to define first, what to automate second, and what metrics to review weekly.”

This is useful because many revops failures come from launching automation before definitions are stable.

Measure whether the revops skill actually helped

Good success metrics after using the revops skill include:

• faster speed-to-lead
• fewer unowned MQLs
• lower sales rejection rate
• clearer reason codes for recycling
• better MQL-to-SQL conversion
• less manual triage in CRM

If your output does not change one of those, refine the design rather than adding more complexity.