revops

Name: revops
Author: LeoYeAI

1.1kstars405forks

How to install revops?

leoyeai/openclaw-marketing-skills/revops

$npx -y skills add LeoYeAI/openclaw-marketing-skills --skill revops

Installs into the current project.

Summary

When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'm

Files · 1

View on GitHub

SKILL.md

1	# RevOps
2
3	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.
4
5	## Before Starting
6
7	Check for product marketing context first:
8	If `.agents/product-marketing-context.md` exists (or `.agents/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
9
10	Gather this context (ask if not provided):
11
12	1. GTM motion — Product-led (PLG), sales-led, or hybrid?
13	2. ACV range — What's the average contract value?
14	3. Sales cycle length — Days from first touch to closed-won?
15	4. Current stack — CRM, marketing automation, scheduling, enrichment tools?
16	5. Current state — How are leads managed today? What's working and what's not?
17	6. Goals — Increase conversion? Reduce speed-to-lead? Fix handoff leaks? Build from scratch?
18
19	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.
20
21	---
22
23	## Core Principles
24
25	### Single Source of Truth
26	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.
27
28	### Define Before Automate
29	Get stage definitions, scoring criteria, and routing rules right on paper before building workflows. Automating a broken process just creates broken results faster.
30
31	### Measure Every Handoff
32	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.
33
34	### Revenue Team Alignment
35	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.
36
37	---
38
39	## Lead Lifecycle Framework
40
41	### Stage Definitions
42
43	\| Stage \| Entry Criteria \| Exit Criteria \| Owner \|
44	\|-------\|---------------\|---------------\|-------\|
45	\| Subscriber \| Opts in to content (blog, newsletter) \| Provides company info or shows engagement \| Marketing \|
46	\| Lead \| Identified contact with basic info \| Meets minimum fit criteria \| Marketing \|
47	\| MQL \| Passes fit + engagement threshold \| Sales accepts or rejects within SLA \| Marketing \|
48	\| SQL \| Sales accepts and qualifies via conversation \| Opportunity created or recycled \| Sales (SDR/AE) \|
49	\| Opportunity \| Budget, authority, need, timeline confirmed \| Closed-won or closed-lost \| Sales (AE) \|
50	\| Customer \| Closed-won deal \| Expands, renews, or churns \| CS / Account Mgmt \|
51	\| Evangelist \| High NPS, referral activity, case study \| Ongoing program participation \| CS / Marketing \|
52
53	### MQL Definition
54
55	An MQL requires both fit and engagement:
56
57	- Fit score — Does this person match your ICP? (company size, industry, role, tech stack)
58	- Engagement score — Have they shown buying intent? (pricing page, demo request, multiple visits)
59
60	Neither alone is sufficient. A perfect-fit company that never engages isn't an MQL. A student downloading every ebook isn't an MQL.
61
62	### MQL-to-SQL Handoff SLA
63
64	Define response times and document them:
65	- MQL alert sent to assigned rep
66	- Rep contacts within 4 hours (business hours)
67	- Rep qualifies or rejects within 48 hours
68	- Rejected MQLs go to recycling nurture with reason code
69
70	For complete lifecycle stage templates and SLA examples: See [references/lifecycle-definitions.md](references/lifecycle-definitions.md)
71
72	---
73
74	## Lead Scoring
75
76	### Scoring Dimensions
77
78	Explicit scoring (fit) — Who they are:
79	- Company size, industry, revenue
80	- Job title, seniority, department
81	- Tech stack, geography
82
83	Implicit scoring (engagement) — What they do:
84	- Page visits (especially pricing, demo, case studies)
85	- Content downloads, webinar attendance
86	- Email engagement (opens, clicks)
87	- Product usage (for PLG)
88
89	Negative scoring — Disqualifying signals:
90	- Competitor email domains
91	- Student/personal email
92	- Unsubscribes, spam complaints
93	- Job title mismatches (intern, student)
94
95	### Building a Scoring Model
96
97	1. Define your ICP attributes and wei

People who liked this also viewed

6 picks

Type

revops

1.1kstars405forks

View on GitHub

How to install revops?

leoyeai/openclaw-marketing-skills/revops

$npx -y skills add LeoYeAI/openclaw-marketing-skills --skill revops

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# RevOps
2
3	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.
4
5	## Before Starting
6
7	Check for product marketing context first:
8	If `.agents/product-marketing-context.md` exists (or `.agents/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
9
10	Gather this context (ask if not provided):
11
12	1. GTM motion — Product-led (PLG), sales-led, or hybrid?
13	2. ACV range — What's the average contract value?
14	3. Sales cycle length — Days from first touch to closed-won?
15	4. Current stack — CRM, marketing automation, scheduling, enrichment tools?
16	5. Current state — How are leads managed today? What's working and what's not?
17	6. Goals — Increase conversion? Reduce speed-to-lead? Fix handoff leaks? Build from scratch?
18
19	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.
20
21	---
22
23	## Core Principles
24
25	### Single Source of Truth
26	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.
27
28	### Define Before Automate
29	Get stage definitions, scoring criteria, and routing rules right on paper before building workflows. Automating a broken process just creates broken results faster.
30
31	### Measure Every Handoff
32	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.
33
34	### Revenue Team Alignment
35	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.
36
37	---
38
39	## Lead Lifecycle Framework
40
41	### Stage Definitions
42
43	\| Stage \| Entry Criteria \| Exit Criteria \| Owner \|
44	\|-------\|---------------\|---------------\|-------\|
45	\| Subscriber \| Opts in to content (blog, newsletter) \| Provides company info or shows engagement \| Marketing \|
46	\| Lead \| Identified contact with basic info \| Meets minimum fit criteria \| Marketing \|
47	\| MQL \| Passes fit + engagement threshold \| Sales accepts or rejects within SLA \| Marketing \|
48	\| SQL \| Sales accepts and qualifies via conversation \| Opportunity created or recycled \| Sales (SDR/AE) \|
49	\| Opportunity \| Budget, authority, need, timeline confirmed \| Closed-won or closed-lost \| Sales (AE) \|
50	\| Customer \| Closed-won deal \| Expands, renews, or churns \| CS / Account Mgmt \|
51	\| Evangelist \| High NPS, referral activity, case study \| Ongoing program participation \| CS / Marketing \|
52
53	### MQL Definition
54
55	An MQL requires both fit and engagement:
56
57	- Fit score — Does this person match your ICP? (company size, industry, role, tech stack)
58	- Engagement score — Have they shown buying intent? (pricing page, demo request, multiple visits)
59
60	Neither alone is sufficient. A perfect-fit company that never engages isn't an MQL. A student downloading every ebook isn't an MQL.
61
62	### MQL-to-SQL Handoff SLA
63
64	Define response times and document them:
65	- MQL alert sent to assigned rep
66	- Rep contacts within 4 hours (business hours)
67	- Rep qualifies or rejects within 48 hours
68	- Rejected MQLs go to recycling nurture with reason code
69
70	For complete lifecycle stage templates and SLA examples: See [references/lifecycle-definitions.md](references/lifecycle-definitions.md)
71
72	---
73
74	## Lead Scoring
75
76	### Scoring Dimensions
77
78	Explicit scoring (fit) — Who they are:
79	- Company size, industry, revenue
80	- Job title, seniority, department
81	- Tech stack, geography
82
83	Implicit scoring (engagement) — What they do:
84	- Page visits (especially pricing, demo, case studies)
85	- Content downloads, webinar attendance
86	- Email engagement (opens, clicks)
87	- Product usage (for PLG)
88
89	Negative scoring — Disqualifying signals:
90	- Competitor email domains
91	- Student/personal email
92	- Unsubscribes, spam complaints
93	- Job title mismatches (intern, student)
94
95	### Building a Scoring Model
96
97	1. Define your ICP attributes and wei

People who liked this also viewed

6 picks

Type