Tell us how leads reach your team today and you get back

Build a system for handling sales leads

by coreyhaines31 · MIT license · ★ 51,120 on GitHub · updated Sep 5

Build a system for handling sales leads cover

Tell us how leads reach your team today and you get back a written playbook for scoring, routing, and following up on every lead fast.

---
name: revops
description: "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,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,' or 'when should marketing hand off to sales.' Use this for anything involving the systems and processes that connect marketing to revenue. For cold outreach emails, see cold-email. For email drip campaigns, see emails. For pricing decisions, see pricing."
metadata:
  version: 2.0.0
---

# 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):

Overview

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.

What you get

  • Lifecycle stage documentStage definitions with entry/exit criteria, owners, and SLAs
  • Scoring specificationFit and engagement attributes with point values and MQL threshold
  • Routing rules documentDecision tree with assignment logic and fallbacks
  • Pipeline configurationStage definitions, required fields, and automation triggers
  • Metrics dashboard specKey metrics, data sources, and target benchmarks
Manual install (npx, ZIP)
Claude Codenpx skills add coreyhaines31/marketingskills --skill revops -g -a claude-code
Claude Code (manual)mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/coreyhaines31/marketingskills/tar.gz/5b2c0007766c \ | tar -xz -C ~/.claude/skills --strip-components=2 marketingskills-5b2c0007766c/skills/revops
Windows (PowerShell)New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/a57b3ada2c731aa0d73d/revops.zip" -OutFile "$env:TEMP\revops.zip"; Expand-Archive "$env:TEMP\revops.zip" -DestinationPath "$HOME\.claude\skills" -Force
Claude.ai / desktopDownload the ZIP and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md15.0 KB
  • evals/1 file · 6.0 KB
  • references/4 files · 31.4 KB
Read the files here
coreyhaines31/5b2c0006 files
Shared references11SKILL.md reads these from elsewhere in the repo. Not in the ZIP.Get them on GitHub ↗
SKILL.md
Show the full text346 lines

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 ebook isn't an MQL.

MQL-to-SQL Handoff SLA

Define response times and document them:

  • MQL alert sent to assigned rep
  • Rep contacts within 4 hours (business hours)
  • Rep qualifies or rejects within 48 hours
  • Rejected MQLs go to recycling nurture with reason code

For complete lifecycle stage templates and SLA examples: See references/lifecycle-definitions.md


Lead Scoring

Scoring Dimensions

Explicit scoring (fit) — Who they are:

  • Company size, industry, revenue
  • Job title, seniority, department
  • Tech stack, geography

Implicit scoring (engagement) — What they do:

  • Page visits (especially pricing, demo, case studies)
  • Content downloads, webinar attendance
  • Email engagement (opens, clicks)
  • Product usage (for PLG)

Negative scoring — Disqualifying signals:

  • Competitor email domains
  • Student/personal email
  • Unsubscribes, spam complaints
  • Job title mismatches (intern, student)
Building a Scoring Model
  1. Define your ICP attributes and weight them
  2. Identify high-intent behavioral signals from closed-won data
  3. Set point values for each attribute and behavior
  4. Set MQL threshold (typically 50-80 points on a 100-point scale)
  5. Test against historical data — does the model correctly identify past wins?
  6. Launch, measure, and recalibrate quarterly
Common Scoring Mistakes
  • Weighting content downloads too heavily (research ≠ buying intent)
  • Not including negative scoring (lets bad leads through)
  • Setting and forgetting (buyer behavior changes; recalibrate quarterly)
  • Scoring all page visits equally (pricing page ≠ blog post)

For detailed scoring templates and example models: See references/scoring-models.md


Lead Routing

Routing Methods
Method How It Works Best For
Round-robin Distribute evenly across reps Equal territories, similar deal sizes
Territory-based Assign by geography, vertical, or segment Regional teams, industry specialists
Account-based Named accounts go to named reps ABM motions, strategic accounts
Skill-based Route by deal complexity, product line, or language Diverse product lines, global teams
Routing Rules Essentials
  • Route to the most specific match first, then fall back to general
  • Include a fallback owner — unassigned leads go cold fast and waste pipeline
  • Round-robin should account for rep capacity and availability (PTO, quota attainment)
  • Log every routing decision for audit and optimization
Speed-to-Lead

Response time is the single biggest factor in lead conversion:

  • Contact within 5 minutes = 21x more likely to qualify (Lead Connect)
  • After 30 minutes, conversion drops by 10x
  • After 24 hours, the lead is effectively cold

Build routing rules that prioritize speed. Alert reps immediately. Escalate if SLA is missed.

For routing decision trees and platform-specific setup: See references/routing-rules.md


Pipeline Stage Management

Pipeline Stages
Stage Required Fields Exit Criteria
Qualified Contact info, company, source, fit score Discovery call scheduled
Discovery Pain points, current solution, timeline Needs confirmed, demo scheduled
Demo/Evaluation Technical requirements, decision makers Positive evaluation, proposal requested
Proposal Pricing, terms, stakeholder map Proposal delivered and reviewed
Negotiation Redlines, approval chain, close date Terms agreed, contract sent
Closed Won Signed contract, payment terms Handoff to CS complete
Closed Lost Loss reason, competitor (if any) Post-mortem logged
Stage Hygiene
  • Required fields per stage — Don't let reps advance a deal without filling in required data
  • Stale deal alerts — Flag deals that sit in a stage beyond the average time (e.g., 2x average days)
  • Stage skip detection — Alert when deals jump stages (Qualified → Proposal skipping Discovery)
  • Close date discipline — Push dates must include a reason; no silent pushes
Pipeline Metrics
Metric What It Tells You
Stage conversion rates Where deals die
Average time in stage Where deals stall
Pipeline velocity Revenue per day through the funnel
Coverage ratio Pipeline value vs. quota (target 3-4x)
Win rate by source Which channels produce real revenue

CRM Automation Workflows

Essential Automations
  • Lifecycle stage updates — Auto-advance stages when criteria are met
  • Task creation on handoff — Create follow-up task when MQL assigned to rep
  • SLA alerts — Notify manager if rep misses response time SLA
  • Deal stage triggers — Auto-send proposals, update forecasts, notify CS on close
Marketing-to-Sales Automations
  • MQL alert — Instant notification to assigned rep with lead context
  • Meeting booked — Notify AE when prospect books via scheduling tool
  • Lead activity digest — Daily summary of high-intent actions by active leads
  • Re-engagement trigger — Alert sales when a dormant lead returns to site
Calendar Scheduling Integration
  • Round-robin scheduling — Distribute meetings evenly across team
  • Routing by criteria — Send enterprise leads to senior AEs, SMB to junior reps
  • Pre-meeting enrichment — Auto-populate CRM record before the call
  • No-show workflows — Auto-follow-up if prospect misses meeting

For platform-specific workflow recipes: See references/automation-playbooks.md


Deal Desk Processes

When You Need a Deal Desk
  • ACV above $25K (or your threshold for non-standard deals)
  • Non-standard payment terms (net-90, quarterly billing)
  • Multi-year contracts with custom pricing
  • Volume discounts beyond published tiers
  • Custom legal terms or SLAs
Approval Workflow Tiers
Deal Size Approval Required
Standard pricing Auto-approved
10-20% discount Sales manager
20-40% discount VP Sales
40%+ discount or custom terms Deal desk review
Multi-year / enterprise Finance + Legal
Non-Standard Terms Handling

Document every exception. Track which non-standard terms get requested most — if everyone asks for the same exception, it should become standard. Review quarterly.


Data Hygiene & Enrichment

Dedup Strategy
  • Matching rules — Email domain + company name + phone as primary match keys
  • Merge priority — CRM record wins over marketing automation; most recent activity wins for fields
  • Scheduled dedup — Run weekly automated dedup with manual review for edge cases
Required Fields Enforcement
  • Enforce required fields at each lifecycle stage
  • Block stage advancement if fields are empty
  • Use progressive profiling — don't require everything upfront
Enrichment Tools
Tool Strength
Clearbit Real-time enrichment, good for tech companies
Apollo Contact data + sequences, strong for prospecting
ZoomInfo Enterprise-grade, largest B2B database
Quarterly Audit Checklist
  • Review and merge duplicates
  • Validate email deliverability on stale contacts
  • Archive contacts with no activity in 12+ months
  • Audit lifecycle stage distribution (look for bottlenecks)
  • Verify enrichment data accuracy on a sample set

RevOps Metrics Dashboard

Key Metrics
Metric Formula / Definition Benchmark
Lead-to-MQL rate MQLs / Total leads 5-15%
MQL-to-SQL rate SQLs / MQLs 30-50%
SQL-to-Opportunity Opportunities / SQLs 50-70%
Pipeline velocity (# deals x avg deal size x win rate) / avg sales cycle Varies by ACV
CAC Total sales + marketing spend / new customers LTV:CAC > 3:1
LTV:CAC ratio Customer lifetime value / CAC 3:1 to 5:1 healthy
Speed-to-lead Time from form fill to first rep contact < 5 minutes ideal
Win rate Closed-won / total opportunities 20-30% (varies)
Dashboard Structure

Build three views:

  1. Marketing view — Lead volume, MQL rate, source attribution, cost per MQL
  2. Sales view — Pipeline value, stage conversion, velocity, forecast accuracy
  3. Executive view — CAC, LTV:CAC, revenue vs. target, pipeline coverage

Output Format

When delivering RevOps recommendations, provide:

  1. Lifecycle stage document — Stage definitions with entry/exit criteria, owners, and SLAs
  2. Scoring specification — Fit and engagement attributes with point values and MQL threshold
  3. Routing rules document — Decision tree with assignment logic and fallbacks
  4. Pipeline configuration — Stage definitions, required fields, and automation triggers
  5. Metrics dashboard spec — Key metrics, data sources, and target benchmarks

Format each as a standalone document the user can implement directly. Include platform-specific guidance when the CRM is known.


Task-Specific Questions

  1. What CRM platform are you using (or planning to use)?
  2. How many leads per month do you generate?
  3. What's your current MQL definition?
  4. Where do leads get stuck in your funnel?
  5. Do you have SLAs between marketing and sales today?

Tool Integrations

For implementation, see the tools registry. Key RevOps tools:

Tool What It Does Guide
HubSpot CRM, marketing automation, lead scoring, workflows hubspot.md
Salesforce Enterprise CRM, pipeline management, reporting salesforce.md
Calendly Meeting scheduling, round-robin routing calendly.md
SavvyCal Scheduling with priority-based availability savvycal.md
Clearbit Real-time lead enrichment and scoring clearbit.md
Apollo Contact data, enrichment, and outbound sequences apollo.md
ActiveCampaign Marketing automation for SMBs, lead scoring activecampaign.md
Zapier Cross-tool automation and workflow glue zapier.md
Introw Partner-sourced pipeline, commissions, deal registration, QBRs introw.md
Crossbeam Partner account overlaps and co-sell identification crossbeam.md

  • cold-email: For outbound prospecting emails
  • emails: For lifecycle and nurture email flows
  • pricing: For pricing decisions and packaging
  • analytics: For tracking pipeline metrics and attribution
  • launch: For go-to-market launch planning
  • sales-enablement: For sales collateral, decks, and objection handling
1---
2name: revops
3description: "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,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,' or 'when should marketing hand off to sales.' Use this for anything involving the systems and processes that connect marketing to revenue. For cold outreach emails, see cold-email. For email drip campaigns, see emails. For pricing decisions, see pricing."
4metadata:
5 version: 2.0.0
6---
7 
8# RevOps
9 
10You 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.
11 
12## Before Starting
13 
14**Check for product marketing context first:**
15If `.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.
16 
17Gather this context (ask if not provided):
18 
191. **GTM motion** — Product-led (PLG), sales-led, or hybrid?
202. **ACV range** — What's the average contract value?
213. **Sales cycle length** — Days from first touch to closed-won?
224. **Current stack** — CRM, marketing automation, scheduling, enrichment tools?
235. **Current state** — How are leads managed today? What's working and what's not?
246. **Goals** — Increase conversion? Reduce speed-to-lead? Fix handoff leaks? Build from scratch?
25 
26Work 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.
27 
28---
29 
30## Core Principles
31 
32### Single Source of Truth
33One 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.
34 
35### Define Before Automate
36Get stage definitions, scoring criteria, and routing rules right on paper before building workflows. Automating a broken process just creates broken results faster.
37 
38### Measure Every Handoff
39Every 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.
40 
41### Revenue Team Alignment
42Marketing, 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.
43 
44---
45 
46## Lead Lifecycle Framework
47 
48### Stage Definitions
49 
50| Stage | Entry Criteria | Exit Criteria | Owner |
51|-------|---------------|---------------|-------|
52| **Subscriber** | Opts in to content (blog, newsletter) | Provides company info or shows engagement | Marketing |
53| **Lead** | Identified contact with basic info | Meets minimum fit criteria | Marketing |
54| **MQL** | Passes fit + engagement threshold | Sales accepts or rejects within SLA | Marketing |
55| **SQL** | Sales accepts and qualifies via conversation | Opportunity created or recycled | Sales (SDR/AE) |
56| **Opportunity** | Budget, authority, need, timeline confirmed | Closed-won or closed-lost | Sales (AE) |
57| **Customer** | Closed-won deal | Expands, renews, or churns | CS / Account Mgmt |
58| **Evangelist** | High NPS, referral activity, case study | Ongoing program participation | CS / Marketing |
59 
60### MQL Definition
61 
62An MQL requires both **fit** and **engagement**:
63 
64- **Fit score** — Does this person match your ICP? (company size, industry, role, tech stack)
65- **Engagement score** — Have they shown buying intent? (pricing page, demo request, multiple visits)
66 
67Neither alone is sufficient. A perfect-fit company that never engages isn't an MQL. A student downloading every ebook isn't an MQL.
68 
69### MQL-to-SQL Handoff SLA
70 
71Define response times and document them:
72- MQL alert sent to assigned rep
73- Rep contacts within **4 hours** (business hours)
74- Rep qualifies or rejects within **48 hours**
75- Rejected MQLs go to recycling nurture with reason code
76 
77**For complete lifecycle stage templates and SLA examples**: See [references/lifecycle-definitions.md](references/lifecycle-definitions.md)
78 
79---
80 
81## Lead Scoring
82 
83### Scoring Dimensions
84 
85**Explicit scoring (fit)** — Who they are:
86- Company size, industry, revenue
87- Job title, seniority, department
88- Tech stack, geography
89 
90**Implicit scoring (engagement)** — What they do:
91- Page visits (especially pricing, demo, case studies)
92- Content downloads, webinar attendance
93- Email engagement (opens, clicks)
94- Product usage (for PLG)
95 
96**Negative scoring** — Disqualifying signals:
97- Competitor email domains
98- Student/personal email
99- Unsubscribes, spam complaints
100- Job title mismatches (intern, student)
101 
102### Building a Scoring Model
103 
1041. Define your ICP attributes and weight them
1052. Identify high-intent behavioral signals from closed-won data
1063. Set point values for each attribute and behavior
1074. Set MQL threshold (typically 50-80 points on a 100-point scale)
1085. Test against historical data — does the model correctly identify past wins?
1096. Launch, measure, and recalibrate quarterly
110 
111### Common Scoring Mistakes
112 
113- Weighting content downloads too heavily (research ≠ buying intent)
114- Not including negative scoring (lets bad leads through)
115- Setting and forgetting (buyer behavior changes; recalibrate quarterly)
116- Scoring all page visits equally (pricing page ≠ blog post)
117 
118**For detailed scoring templates and example models**: See [references/scoring-models.md](references/scoring-models.md)
119 
120---
121 
122## Lead Routing
123 
124### Routing Methods
125 
126| Method | How It Works | Best For |
127|--------|-------------|----------|
128| **Round-robin** | Distribute evenly across reps | Equal territories, similar deal sizes |
129| **Territory-based** | Assign by geography, vertical, or segment | Regional teams, industry specialists |
130| **Account-based** | Named accounts go to named reps | ABM motions, strategic accounts |
131| **Skill-based** | Route by deal complexity, product line, or language | Diverse product lines, global teams |
132 
133### Routing Rules Essentials
134 
135- Route to the **most specific match** first, then fall back to general
136- Include a **fallback owner** — unassigned leads go cold fast and waste pipeline
137- Round-robin should account for **rep capacity and availability** (PTO, quota attainment)
138- Log every routing decision for audit and optimization
139 
140### Speed-to-Lead
141 
142Response time is the single biggest factor in lead conversion:
143- Contact within **5 minutes** = 21x more likely to qualify (Lead Connect)
144- After **30 minutes**, conversion drops by 10x
145- After **24 hours**, the lead is effectively cold
146 
147Build routing rules that prioritize speed. Alert reps immediately. Escalate if SLA is missed.
148 
149**For routing decision trees and platform-specific setup**: See [references/routing-rules.md](references/routing-rules.md)
150 
151---
152 
153## Pipeline Stage Management
154 
155### Pipeline Stages
156 
157| Stage | Required Fields | Exit Criteria |
158|-------|----------------|---------------|
159| **Qualified** | Contact info, company, source, fit score | Discovery call scheduled |
160| **Discovery** | Pain points, current solution, timeline | Needs confirmed, demo scheduled |
161| **Demo/Evaluation** | Technical requirements, decision makers | Positive evaluation, proposal requested |
162| **Proposal** | Pricing, terms, stakeholder map | Proposal delivered and reviewed |
163| **Negotiation** | Redlines, approval chain, close date | Terms agreed, contract sent |
164| **Closed Won** | Signed contract, payment terms | Handoff to CS complete |
165| **Closed Lost** | Loss reason, competitor (if any) | Post-mortem logged |
166 
167### Stage Hygiene
168 
169- **Required fields per stage** — Don't let reps advance a deal without filling in required data
170- **Stale deal alerts** — Flag deals that sit in a stage beyond the average time (e.g., 2x average days)
171- **Stage skip detection** — Alert when deals jump stages (Qualified → Proposal skipping Discovery)
172- **Close date discipline** — Push dates must include a reason; no silent pushes
173 
174### Pipeline Metrics
175 
176| Metric | What It Tells You |
177|--------|-------------------|
178| Stage conversion rates | Where deals die |
179| Average time in stage | Where deals stall |
180| Pipeline velocity | Revenue per day through the funnel |
181| Coverage ratio | Pipeline value vs. quota (target 3-4x) |
182| Win rate by source | Which channels produce real revenue |
183 
184---
185 
186## CRM Automation Workflows
187 
188### Essential Automations
189 
190- **Lifecycle stage updates** — Auto-advance stages when criteria are met
191- **Task creation on handoff** — Create follow-up task when MQL assigned to rep
192- **SLA alerts** — Notify manager if rep misses response time SLA
193- **Deal stage triggers** — Auto-send proposals, update forecasts, notify CS on close
194 
195### Marketing-to-Sales Automations
196 
197- **MQL alert** — Instant notification to assigned rep with lead context
198- **Meeting booked** — Notify AE when prospect books via scheduling tool
199- **Lead activity digest** — Daily summary of high-intent actions by active leads
200- **Re-engagement trigger** — Alert sales when a dormant lead returns to site
201 
202### Calendar Scheduling Integration
203 
204- **Round-robin scheduling** — Distribute meetings evenly across team
205- **Routing by criteria** — Send enterprise leads to senior AEs, SMB to junior reps
206- **Pre-meeting enrichment** — Auto-populate CRM record before the call
207- **No-show workflows** — Auto-follow-up if prospect misses meeting
208 
209**For platform-specific workflow recipes**: See [references/automation-playbooks.md](references/automation-playbooks.md)
210 
211---
212 
213## Deal Desk Processes
214 
215### When You Need a Deal Desk
216 
217- ACV above **$25K** (or your threshold for non-standard deals)
218- Non-standard payment terms (net-90, quarterly billing)
219- Multi-year contracts with custom pricing
220- Volume discounts beyond published tiers
221- Custom legal terms or SLAs
222 
223### Approval Workflow Tiers
224 
225| Deal Size | Approval Required |
226|-----------|-------------------|
227| Standard pricing | Auto-approved |
228| 10-20% discount | Sales manager |
229| 20-40% discount | VP Sales |
230| 40%+ discount or custom terms | Deal desk review |
231| Multi-year / enterprise | Finance + Legal |
232 
233### Non-Standard Terms Handling
234 
235Document every exception. Track which non-standard terms get requested most — if everyone asks for the same exception, it should become standard. Review quarterly.
236 
237---
238 
239## Data Hygiene & Enrichment
240 
241### Dedup Strategy
242 
243- **Matching rules** — Email domain + company name + phone as primary match keys
244- **Merge priority** — CRM record wins over marketing automation; most recent activity wins for fields
245- **Scheduled dedup** — Run weekly automated dedup with manual review for edge cases
246 
247### Required Fields Enforcement
248 
249- Enforce required fields at each lifecycle stage
250- Block stage advancement if fields are empty
251- Use progressive profiling — don't require everything upfront
252 
253### Enrichment Tools
254 
255| Tool | Strength |
256|------|----------|
257| Clearbit | Real-time enrichment, good for tech companies |
258| Apollo | Contact data + sequences, strong for prospecting |
259| ZoomInfo | Enterprise-grade, largest B2B database |
260 
261### Quarterly Audit Checklist
262 
263- Review and merge duplicates
264- Validate email deliverability on stale contacts
265- Archive contacts with no activity in 12+ months
266- Audit lifecycle stage distribution (look for bottlenecks)
267- Verify enrichment data accuracy on a sample set
268 
269---
270 
271## RevOps Metrics Dashboard
272 
273### Key Metrics
274 
275| Metric | Formula / Definition | Benchmark |
276|--------|---------------------|-----------|
277| Lead-to-MQL rate | MQLs / Total leads | 5-15% |
278| MQL-to-SQL rate | SQLs / MQLs | 30-50% |
279| SQL-to-Opportunity | Opportunities / SQLs | 50-70% |
280| Pipeline velocity | (# deals x avg deal size x win rate) / avg sales cycle | Varies by ACV |
281| CAC | Total sales + marketing spend / new customers | LTV:CAC > 3:1 |
282| LTV:CAC ratio | Customer lifetime value / CAC | 3:1 to 5:1 healthy |
283| Speed-to-lead | Time from form fill to first rep contact | < 5 minutes ideal |
284| Win rate | Closed-won / total opportunities | 20-30% (varies) |
285 
286### Dashboard Structure
287 
288Build three views:
2891. **Marketing view** — Lead volume, MQL rate, source attribution, cost per MQL
2902. **Sales view** — Pipeline value, stage conversion, velocity, forecast accuracy
2913. **Executive view** — CAC, LTV:CAC, revenue vs. target, pipeline coverage
292 
293---
294 
295## Output Format
296 
297When delivering RevOps recommendations, provide:
298 
2991. **Lifecycle stage document** — Stage definitions with entry/exit criteria, owners, and SLAs
3002. **Scoring specification** — Fit and engagement attributes with point values and MQL threshold
3013. **Routing rules document** — Decision tree with assignment logic and fallbacks
3024. **Pipeline configuration** — Stage definitions, required fields, and automation triggers
3035. **Metrics dashboard spec** — Key metrics, data sources, and target benchmarks
304 
305Format each as a standalone document the user can implement directly. Include platform-specific guidance when the CRM is known.
306 
307---
308 
309## Task-Specific Questions
310 
3111. What CRM platform are you using (or planning to use)?
3122. How many leads per month do you generate?
3133. What's your current MQL definition?
3144. Where do leads get stuck in your funnel?
3155. Do you have SLAs between marketing and sales today?
316 
317---
318 
319## Tool Integrations
320 
321For implementation, see the [tools registry](../../tools/REGISTRY.md). Key RevOps tools:
322 
323| Tool | What It Does | Guide |
324|------|-------------|-------|
325| **HubSpot** | CRM, marketing automation, lead scoring, workflows | [hubspot.md](../../tools/integrations/hubspot.md) |
326| **Salesforce** | Enterprise CRM, pipeline management, reporting | [salesforce.md](../../tools/integrations/salesforce.md) |
327| **Calendly** | Meeting scheduling, round-robin routing | [calendly.md](../../tools/integrations/calendly.md) |
328| **SavvyCal** | Scheduling with priority-based availability | [savvycal.md](../../tools/integrations/savvycal.md) |
329| **Clearbit** | Real-time lead enrichment and scoring | [clearbit.md](../../tools/integrations/clearbit.md) |
330| **Apollo** | Contact data, enrichment, and outbound sequences | [apollo.md](../../tools/integrations/apollo.md) |
331| **ActiveCampaign** | Marketing automation for SMBs, lead scoring | [activecampaign.md](../../tools/integrations/activecampaign.md) |
332| **Zapier** | Cross-tool automation and workflow glue | [zapier.md](../../tools/integrations/zapier.md) |
333| **Introw** | Partner-sourced pipeline, commissions, deal registration, QBRs | [introw.md](../../tools/integrations/introw.md) |
334| **Crossbeam** | Partner account overlaps and co-sell identification | [crossbeam.md](../../tools/integrations/crossbeam.md) |
335 
336---
337 
338## Related Skills
339 
340- **cold-email**: For outbound prospecting emails
341- **emails**: For lifecycle and nurture email flows
342- **pricing**: For pricing decisions and packaging
343- **analytics**: For tracking pipeline metrics and attribution
344- **launch**: For go-to-market launch planning
345- **sales-enablement**: For sales collateral, decks, and objection handling
346 
View all files on GitHub →

Details

Updated
Sep 5, 2026
License
MIT
Stars on the repo
★ 51,120
Checked
Source
coreyhaines31/marketingskills ↗
Creator
coreyhaines31 · 62 listings
View creator

Similar skills

See all →
SkillAct as a comprehensive AI sales intelligenceAI Sales Team — Main Orchestratorzubair-trabzada/ai-sales-team-claude · by zubair-trabzadaYou are a comprehensive AI sales intelligence and outreach system for Claude Code. You help founders, sales teams, agency owners, and…★ 1.4k GitHub starsSkillAutonomous cold email campaign launcherAuto research publicgrowthenginenowoslawski/coldoutboundskills · by growthenginenowoslawskiAutonomous cold email campaign launcher. Takes one target company domain, scrapes their website, generates an ICP with Claude, pulls matching leads via Prospeo, enriches emails + company descriptions, personalizes each lead with parallel Claude Code Task sub-agents (A/B/C variants), and uploads as a live Smartlead campaign. Uses local JSON files for state (no database required). Use for automated daily campaign launches after you have an initial `client-profile.yaml` from /icp-onboarding. Triggers on "auto-research", "launch an automated campaign", "daily campaign", "run the research loop".★ 736 GitHub starsSkillRun a full Account-Based Marketing campaign end-to-endABM Campaign — DIY Playbookexplorium-ai/gtm-skills · by explorium-aiABM campaign skill for Claude Code: run a full Account-Based Marketing campaign end-to-end — from ICP definition to live LinkedIn Ads. Builds targeted account lists with Vibe Prospecting, enriches and scores companies with real-time B2B data, generates personalized ad creatives with Claude Code and Figma, pushes matched audiences to LinkedIn Ads, and monitors campaigns daily at scale. The complete GTM skill for AI-driven account-based marketing in Claude Code, Codex, Hermes-Agent, and OpenClaw. No agency needed.★ 197 GitHub starsSkillContact data skill for Claude Code and Codex: build a rankedAccount contact shortlistexplorium-ai/gtm-skills · by explorium-aiContact data skill for Claude Code and Codex: build a ranked shortlist of decision-makers and contacts at a target company for outbound prospecting, deal acceleration, or renewal/expansion plays. Returns verified contact data including email, phone, LinkedIn profile, title, seniority, and department. Provide a company name or domain plus optional seniority focus or use case. Use for contact data enrichment, LinkedIn profile lookup, and building outbound contact lists. Works in Claude Code, Codex, Hermes-Agent, and OpenClaw.★ 197 GitHub starsSkillLead scoring and buying signals skill for Claude CodeAccount fit rankexplorium-ai/gtm-skills · by explorium-aiLead scoring and buying signals skill for Claude Code and Codex: rank a list of accounts by ICP fit, buying intent, real-time trigger events, and workforce momentum. Returns composite score (0-100), tier (A/B/C), and a 'why now' signal per account. Use for account-based selling, ABM list prioritization, territory planning, signal-based selling, and buyer-intent ranking. Triggers on 'score these accounts', 'rank by ICP fit and intent', 'prioritize this account list', 'which accounts have the strongest buying signals', 'ICP scoring', 'account prioritization'. Works in Claude Code, Codex, Hermes-Agent, OpenClaw, and Claude Cowork.★ 197 GitHub starsSkillRun end-to-end B2B cold-email outreach through the Hyper MCPhyperfx-ai/marketing-skills · by hyperfx-aiRun end-to-end B2B cold-email outreach through the Hyper MCP — enrich prospects with Apollo, scrape per-prospect signals from company sites and LinkedIn, draft personalized emails using proven hook frameworks, send via Gmail with safe defaults, and route replies into labeled folders. Use when the user wants to write cold emails, run an outbound sequence, prospect a list, build a follow-up cadence, "reach out to leads," or asks why nobody is replying to their cold emails.★ 90 GitHub stars

More from coreyhaines31

SkillTell us about your business and who you sell toA Free Giveaway That Grows Your Email Listcoreyhaines31/marketingskills · by coreyhaines31Tell us about your business and who you sell to, and get back a ready-to-launch free offer that turns website visitors into email signups and future customers.★ 51.1k GitHub starsSkillPlan, design, or implement an A/B test or experimentA/B Test Setupcoreyhaines31/marketingskills · by coreyhaines31When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.★ 51.1k GitHub starsSkillGenerate, iterate, or scale ad creativecoreyhaines31/marketingskills · by coreyhaines31When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising platform. Also use when the user mentions 'ad copy variations,' 'ad creative,' 'generate headlines,' 'RSA headlines,' 'bulk ad copy,' 'ad iterations,' 'creative testing,' 'write me some ads,' 'Facebook ad copy,' 'Google ad headlines,' 'LinkedIn ad text,' 'static ads,' 'ad templates,' 'iMessage ad,' 'chat reveal ad,' 'ChatGPT ad,' 'Apple Notes ad,' 'AirDrop ad,' 'creative strategy,' 'creative roadmap,' 'creative retro,' 'hook writing,' 'creative review page,' 'present ad creative for approval,' 'motion video ad,' 'faceless video ad,' 'UGC ad,' 'greenscreen ad,' 'TikTok/Reels ad format,' 'which ad format to make,' 'Meta ad format tier list,' or 'creative format taxonomy.' Use this whenever someone needs to produce ad copy at scale or iterate on existing ads. For campaign strategy and targeting, see ads. For landing page copy, see copywriting.★ 51.1k GitHub starsSkillBusiness-brainstorm — Pressure-test a business ideacoreyhaines31/makerskills · by coreyhaines31When you want to pressure-test a potential new business, product, or side project against the serial-founder filter. Not "marketing ideas for a product" (that's marketing-skills:marketing-ideas) — this is "should this business exist + can you win it." Runs the idea through a structured framework (problem, audience, wedge, monetization, moat, portfolio fit, distribution, energy fit, opportunity cost), checks domain availability via /domain, optionally triggers /deep-research for market validation, and outputs a viability brief: build / sleep on it / pass. Archives every idea to ~/.config/makerskills/business-brainstorm/archive/ so past work is searchable. Triggers on "/business-brainstorm," "/brainstorm," "new business idea," "should I build X," "pressure test this idea," "validate this idea," "is X a good business," "what about a [type] for [audience]."★ 855 GitHub starsSkillYour team's shared, AI-ready knowledge base/company-brain — Team-shared AI-ready knowledge basecoreyhaines31/makerskills · by coreyhaines31Your team's shared, AI-ready knowledge base — people, companies, meetings, SOPs, and decisions structured so an agent can answer on your team's behalf. Team-scope sibling to second-brain. Modes — capture, compile (wiki pages + INDEX.md), query (trust-weighted, saved to outputs/), review (verify / deprecate / supersede stale captures), lint, connect, search. Structured raw dirs (people/, companies/, meetings/, sops/, decisions/, customer-language/, sales-objections/). Every capture stamps author, timestamp, and trust status. Optional sync from call transcripts, Slack/email exports, CRM. Vault at ${COMPANY_BRAIN_VAULT:-$HOME/Documents/CompanyBrain}/. Triggers on "/company-brain," "/cb," "capture this into the team brain," "log this meeting," "save this SOP," "compile the company wiki," "query the team brain," "what does the team know about X," "review the company brain," "lint the company brain," "who's the internal expert on X.★ 855 GitHub starsSkillMonthly CFO workflow for a company or agency/company-cfo — Monthly company CFO workflowcoreyhaines31/makerskills · by coreyhaines31Monthly CFO workflow for a company or agency — pull raw data from bank + payment processor + payroll + expense management, categorize and reconcile, compute end-of-month cash via transaction-sum method, update a scenario projector for forward forecasting, write the monthly snapshot report, surface decisions to leadership. Modes — monthly (default; the standing report), weekly (thin cash pulse), scenario (ad-hoc modeling in the projector), pickup (resume where the prior run left off). Anonymized team-scope sibling to personal-cfo (which handles personal household finances). Composes with company-brain (report gets stored + wiki-indexed there), toolify (wire company-specific data sources), loopify (schedule the monthly + weekly runs). Triggers on "/company-cfo," "/cfo," "monthly cash report," "do the CFO snapshot," "CFO monthly," "let's run CFO," "cash projection," "runway forecast," "monthly financials," "cash pulse.★ 855 GitHub stars