Respuesta rápida
- Qué es
- revops es una skill de Corey Haines (licencia MIT) que le enseña a Claude a diseñar las operaciones de ingresos de un negocio: etapas del lead, criterios para pasarlo a ventas, puntaje, reparto entre vendedores, pipeline y automatizaciones del CRM.
- Qué le das
- Cómo vendes, ticket promedio, duración del ciclo, tu CRM y herramientas, y dónde se te pierden los leads hoy
- Qué te devuelve
- Cinco documentos listos para implementar: etapas del ciclo de vida, modelo de puntaje, reglas de asignación, configuración del pipeline y tablero de métricas
- Autor
- Corey Haines
- Licencia
- MIT
- Repositorio
- coreyhaines31/marketingskills
- En GitHub
- 60,6 mil estrellas · actualizada el
- Revisada por Claura
Instálala en una línea para todos tus proyectos, en Claude Code, Cursor, Codex y más:
npx skills add coreyhaines31/marketingskills --skill revops -g
Funciona en
~/.claude/skills/~/.agents/skills/~/.agents/skills/~/.agents/skills/Pedidos para probarla
Con la skill instalada, copia uno y pégaselo a tu agente tal cual, o cambia los datos por los tuyos.
Define qué es un lead calificado para mi empresa de software contable y arma la puntuación con señales de encaje y de interés.
Diseña el traspaso de leads de marketing a ventas en HubSpot: quién recibe cada uno, en cuánto tiempo y qué pasa si nadie responde.
Dime qué indicadores mirar cada semana para saber si el pipeline está sano y cómo armarlos en el CRM.
#Qué hace
revops es una skill de Corey Haines (licencia MIT) para diseñar el recorrido del ingreso de punta a punta. Antes de empezar pregunta seis cosas: si vendes con producto que se prueba solo, con vendedores o mixto, el ticket promedio, los días del primer contacto al cierre, tu CRM y herramientas, cómo manejas los leads hoy y qué quieres lograr. Trabaja con lo que le des y anota qué datos mejorarían la propuesta. Sus cuatro principios: un solo CRM como fuente de verdad, definir antes de automatizar, medir cada traspaso entre equipos con un acuerdo de tiempos y un responsable, y que marketing, ventas y atención acuerden las mismas definiciones.
El núcleo son siete etapas del ciclo de vida (suscriptor, lead, MQL, SQL, oportunidad, cliente, promotor), cada una con criterio de entrada, de salida y dueño, más etapas propias para los contactos de prospección en frío. El puntaje combina quién es la persona (tamaño, rubro, cargo), qué hace (visitas a la página de precios, pedidos de demo) y señales negativas (correos personales, dominios de competidores, bajas). Para repartir leads compara cuatro métodos (rotativo, por territorio, por cuenta, por especialidad), exige un dueño de respaldo y registra cada asignación. El pipeline tiene siete etapas con campos obligatorios, alertas de negocios quietos más del doble del promedio, aviso cuando un negocio salta etapas y fechas de cierre que no se mueven sin motivo.
Suma automatizaciones del CRM (alerta de MQL, tareas en cada traspaso, seguimiento cuando alguien falta a una reunión), un circuito de aprobación de descuentos por niveles, una estrategia para limpiar duplicados y una revisión trimestral de datos, y un tablero en tres vistas: marketing, ventas y dirección. Trae cinco referencias: definiciones del ciclo de vida, modelos de puntaje, reglas de asignación, asignación de leads entrantes y recetas de automatización.
#Cómo aplicarla a tu negocio
Caso de ejemplo: una empresa de software de facturación en Colombia, con dos personas de marketing y cuatro vendedores en HubSpot. Los vendedores se quejan de que los leads «no sirven» y nadie sabe cuánto tarda el primer contacto.
- Cuenta el problema con datos. Le dices el volumen (por ejemplo, 300 leads al mes), de dónde vienen y que hoy todo entra como «lead» sin filtro.
- Acuerda qué es un MQL. La skill propone que sea encaje (empresa con más de cinco empleados, cargo de administración o finanzas) más señal (visitó precios o pidió demo), con un umbral de puntos y señales negativas para los correos personales.
- Define el traspaso. Sale el acuerdo: el vendedor asignado recibe la alerta al instante, contacta en 4 horas hábiles y califica o descarta en 48, con un código de motivo si descarta.
- Reparte por territorio con respaldo. Bogotá y Medellín a dos vendedores, el resto rotativo, y un dueño por defecto para lo que no coincide.
- Arma el tablero. Tasa de paso de lead a MQL y de MQL a SQL, tiempo hasta el primer contacto y tasa de cierre por fuente. A las cuatro semanas comparas contra los valores de referencia y ajustas el umbral.
#Cómo instalarla
Es una skill que no depende de un agente en particular: el mismo SKILL.md corre en cualquiera. Sus cinco referencias viven en la carpeta del repo, así que conviene instalarla entera.
- Con una línea, para cualquier agente:
npx skills add coreyhaines31/marketingskills --skill revops -gla deja instalada en todos tus proyectos. - A mano: copia la carpeta
skills/revops/completa a~/.claude/skills/para Claude Code, o a~/.agents/skills/para Cursor, Codex y Gemini CLI. - App de Claude: comprime la carpeta en un ZIP y súbela desde Customize, Skills, «Upload a skill».
- Qué más necesitas: nada para diseñar. Si quieres que el agente lea o cambie el CRM directamente, conecta el MCP o la API de tu CRM.
El SKILL.md completo (con la licencia y la fuente) está más abajo.
El SKILL.md completo
Skill original de Corey Haines (MIT). Fuente: github.com/coreyhaines31/marketingskills/tree/main/skills/revops.
El archivo original está en inglés y va tal cual, sin traducir. Lo de arriba de esta ficha es el resumen en español: qué hace, cómo aplicarla y cómo instalarla.
Leer el archivo (356 líneas)
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):
- GTM motion — Product-led (PLG), sales-led, or hybrid?
- ACV range — What's the average contract value?
- Sales cycle length — Days from first touch to closed-won?
- Current stack — CRM, marketing automation, scheduling, enrichment tools?
- Current state — How are leads managed today? What's working and what's not?
- 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 |
Outbound contacts follow their own stages (targeted → in sequence → replied → positive → meeting booked → meeting held → opportunity), with fields for signal, tier, sequence, and channel so meetings can be attributed. See references/lifecycle-definitions.md.
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
- Define your ICP attributes and weight them
- Identify high-intent signals from an eligible cohort with won and lost outcomes, using only features available at the qualification decision
- Set point values for each attribute and behavior
- Set MQL threshold (typically 50-80 points on a 100-point scale)
- Freeze the rule and test a later, fully observed holdout against the current routing baseline; report precision, recall, missed wins, false positives, and workload
- Pilot with monitoring and rollback; tune on development cohorts and preserve an untouched holdout for each promotion
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 form-submit enrichment, booking branches, missing-data fallbacks, and late results, load the inbound-routing playbook. Use it alongside the ownership and territory rules below.
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 |
|---|---|
| Clay | Waterfall enrichment across many providers |
| 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:
- Marketing view — Lead volume, MQL rate, source attribution, cost per MQL
- Sales view — Pipeline value, stage conversion, velocity, forecast accuracy
- Executive view — CAC, LTV:CAC, revenue vs. target, pipeline coverage
Output Format
When delivering RevOps recommendations, provide:
- Lifecycle stage document — Stage definitions with entry/exit criteria, owners, and SLAs
- Scoring specification — Fit and engagement attributes with point values and MQL threshold
- Routing rules document — Decision tree with assignment logic and fallbacks
- Pipeline configuration — Stage definitions, required fields, and automation triggers
- 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
- What CRM platform are you using (or planning to use)?
- How many leads per month do you generate?
- What's your current MQL definition?
- Where do leads get stuck in your funnel?
- 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 |
| Attio | CRM with a hosted MCP for agents | attio.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 |
Related Skills
- 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
Copiar el archivo tal cual
--- name: revops description: "When the user wants to design revenue operations, or asks when a lead is ready for sales or why sales and marketing disagree on lead quality: lifecycle stages, MQL and SQL, scoring, routing, handoff, pipeline stages, CRM automation. For outbound copy, see cold-email. For email flows, see emails." metadata: version: 2.2.4 --- <!-- Skill original: revops, de Corey Haines (https://github.com/coreyhaines31/marketingskills/tree/main/skills/revops) Licencia: MIT. Reproducida con atribución según los términos de la licencia. Copia publicada en claura-ai.com/skills. --> # 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 | Outbound contacts follow their own stages (targeted → in sequence → replied → positive → meeting booked → meeting held → opportunity), with fields for signal, tier, sequence, and channel so meetings can be attributed. See [references/lifecycle-definitions.md](references/lifecycle-definitions.md#outbound-stages). ### 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](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 signals from an eligible cohort with won and lost outcomes, using only features available at the qualification decision 3. Set point values for each attribute and behavior 4. Set MQL threshold (typically 50-80 points on a 100-point scale) 5. Freeze the rule and test a later, fully observed holdout against the current routing baseline; report precision, recall, missed wins, false positives, and workload 6. Pilot with monitoring and rollback; tune on development cohorts and preserve an untouched holdout for each promotion ### 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](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 form-submit enrichment, booking branches, missing-data fallbacks, and late results, load [the inbound-routing playbook](references/inbound-routing.md). Use it alongside the ownership and territory rules below. **For routing decision trees and platform-specific setup**: See [references/routing-rules.md](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](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 | |------|----------| | Clay | Waterfall enrichment across many providers | | 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](https://github.com/coreyhaines31/marketingskills/blob/main/tools/REGISTRY.md). Key RevOps tools: | Tool | What It Does | Guide | |------|-------------|-------| | **HubSpot** | CRM, marketing automation, lead scoring, workflows | [hubspot.md](https://github.com/coreyhaines31/marketingskills/blob/main/tools/integrations/hubspot.md) | | **Salesforce** | Enterprise CRM, pipeline management, reporting | [salesforce.md](https://github.com/coreyhaines31/marketingskills/blob/main/tools/integrations/salesforce.md) | | **Calendly** | Meeting scheduling, round-robin routing | [calendly.md](https://github.com/coreyhaines31/marketingskills/blob/main/tools/integrations/calendly.md) | | **SavvyCal** | Scheduling with priority-based availability | [savvycal.md](https://github.com/coreyhaines31/marketingskills/blob/main/tools/integrations/savvycal.md) | | **Attio** | CRM with a hosted MCP for agents | [attio.md](https://github.com/coreyhaines31/marketingskills/blob/main/tools/integrations/attio.md) | | **Apollo** | Contact data, enrichment, and outbound sequences | [apollo.md](https://github.com/coreyhaines31/marketingskills/blob/main/tools/integrations/apollo.md) | | **ActiveCampaign** | Marketing automation for SMBs, lead scoring | [activecampaign.md](https://github.com/coreyhaines31/marketingskills/blob/main/tools/integrations/activecampaign.md) | | **Zapier** | Cross-tool automation and workflow glue | [zapier.md](https://github.com/coreyhaines31/marketingskills/blob/main/tools/integrations/zapier.md) | | **Introw** | Partner-sourced pipeline, commissions, deal registration, QBRs | [introw.md](https://github.com/coreyhaines31/marketingskills/blob/main/tools/integrations/introw.md) | | **Crossbeam** | Partner account overlaps and co-sell identification | [crossbeam.md](https://github.com/coreyhaines31/marketingskills/blob/main/tools/integrations/crossbeam.md) | --- ## Related Skills - **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
Preguntas frecuentes sobre la skill revops
¿Qué es la skill revops y para qué sirve?
revops es una skill de Corey Haines (github.com/coreyhaines31/marketingskills, licencia MIT) que convierte a Claude en un especialista en operaciones de ingresos, el sistema que conecta marketing, ventas y atención al cliente. Define las etapas del lead con criterios de entrada y salida, cuándo un lead está listo para ventas (MQL) y cuándo ventas lo acepta (SQL), el puntaje, cómo se reparte entre vendedores, los campos obligatorios de cada etapa del pipeline, las automatizaciones del CRM y las métricas del tablero. Sirve cuando marketing dice que manda buenos leads y ventas dice que no.
¿Cómo la aplico si uso Pipedrive, HubSpot o Twenty?
La skill trabaja con el CRM que tengas: le dices cuál es y adapta la entrega a esa plataforma. Para HubSpot, Salesforce, Calendly, Attio, Apollo y Zapier enlaza guías propias del autor. Con Pipedrive, Zoho o Twenty el diseño es el mismo (etapas, campos obligatorios, reglas de reparto, alertas) y lo traduces a las automatizaciones de tu herramienta. Su primera regla es definir antes de automatizar: si las etapas no están claras en papel, automatizarlas solo hace que el error llegue más rápido. Si quieres que alguien lo monte por ti, mira el servicio de CRM.
¿En qué se diferencia de pedirle a Claude que me explique qué es un MQL?
Una pregunta suelta te devuelve la definición de manual. La skill te devuelve tu sistema: un MQL exige encaje con el cliente ideal y además señales de compra (ninguna de las dos alcanza sola), un acuerdo de respuesta de 4 horas para el primer contacto y 48 para calificar o descartar, y los descartados vuelven a nutrición con un código de motivo. Para el puntaje no te deja elegir números a ojo: pide armarlo con negocios ganados y perdidos, congelar la regla y probarla contra un grupo que no se usó para ajustarla, midiendo leads buenos que se escapan y falsos positivos.
¿Qué limitaciones tiene?
Está en inglés y piensa en venta B2B: los valores de referencia (de 5 a 15 % de leads que pasan a MQL, de 30 a 50 % de MQL que pasan a SQL, relación entre valor del cliente y costo de adquisición de 3 a 1) vienen de empresas de software y conviene tomarlos como orientación. Pídele las entregas en español. Diseña los documentos, pero no configura el CRM por su cuenta salvo que conectes tu CRM al agente. Para el dato de velocidad de respuesta cita un estudio de Lead Connect; si te interesa ese punto, lee qué hacer en los primeros 5 minutos con un lead.
Más skills de Ventas y CRM

email-marketing: arma newsletters, campañas y secuencias con IA (skill de Claura)
Planifica, escribe y revisa newsletters, campañas y secuencias de email con un objetivo por mail, segmentos por origen, UTMs en cada link y un control de 15 puntos antes de enviar.

ads-audit: auditar tus cuentas de anuncios con evidencia
Audita cuentas de anuncios de hasta 12 plataformas y separa lo que está bien, lo que está mal y lo que no se pudo revisar, con la evidencia de cada punto.

ads: planificar, revisar y corregir campañas en Meta y Google
Planifica, revisa y corrige campañas pagas en Google, Meta y LinkedIn, y te dice con datos si conviene cortar, mantener o escalar.
Para seguir con este tema
- Guía de Ventas y CRMEl orden para empezar y las notas de este tema.Guía
- Skills de Claude y ChatGPT para ventas y prospecciónLas skills de Claude para ventas y prospección: cliente ideal, listas, emails en frío, material de ventas y CRM. Cómo usarlas en Claude y en ChatGPT.Skill
- Velocidad de respuesta a leads: qué hacer en los primeros 5 minutosUn lead se enfría rápido y la mayoría de los negocios contesta tarde. Cómo cubrir los primeros cinco minutos con un agente de IA que responde solo.Nota
AI KID
RE/MAX Patagon
Mateo Caño