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.
Dynamic Workflow orchestration
RevOps spans five loosely-coupled design units that can be worked in parallel, then reconciled. Use a plan -> fan-out -> adversarial-verify -> synthesize loop:
- Plan. From the gathered context (GTM motion, ACV, sales cycle, stack, current state), decide which of the five units are in scope and in what order they couple: lifecycle stages -> scoring -> routing -> pipeline config -> metrics dashboard. Scoring depends on lifecycle definitions; routing depends on scoring thresholds; metrics depend on all four. Sequence the dependent chain; parallelize the independent design work within each unit.
- Fan-out. Draft each unit as an independent angle: (a) lifecycle stage doc, (b) scoring model, (c) routing rules + SLAs, (d) pipeline config + automations, (e) metrics dashboard spec. Pull from closed-won data and the user's actual stack — never a generic template.
- Adversarial verify (2-of-3). Before synthesizing, falsify each unit through three independent lenses; accept a design only if ≥2 agree it holds:
- Leak lens — trace one lead end-to-end; does any handoff lack an SLA, owner, or fallback owner? Unrouted = cold.
- Definition lens — would sales actually work every MQL this model produces? If marketing's MQL ≠ sales-accepted, the threshold or fit/engagement split is wrong.
- Data lens — does the scoring model correctly identify past closed-won when back-tested? Do benchmark numbers match a cited source, not a guess?
- Synthesize. Reconcile the verified units into one coherent revenue engine — definitions must agree across documents (an MQL in the lifecycle doc must match the scoring threshold and the routing trigger). Resolve conflicts explicitly; don't paste five disconnected docs.
- Loop-until-dry. If the user's funnel has unknown leak points, iterate the leak lens stage-by-stage until no handoff lacks an SLA + owner + tracking mechanism.
Portability note: This skill is CRM/stack-agnostic and runs anywhere — no OmegaOS VPS dependency. The .agents/ / .claude/ context-file lookup below is optional; if absent, gather context interactively.
Before Starting
Check for product marketing context first:
If .agents/product-marketing-context.md exists (or .claude/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.
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 |
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 behavioral signals from closed-won data
- Set point values for each attribute and behavior
- Set MQL threshold (typically 50-80 points on a 100-point scale)
- Test against historical data — does the model correctly identify past wins?
- 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:
- 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.
Verify before delivering
Run this checklist against the synthesized output — fix any failure before handing off:
Evidence & no-hallucination guardrail
RevOps numbers drive real money decisions. Do not invent benchmarks, conversion rates, or tool capabilities. When you state a figure, either cite a source or label it a "typical range — validate against your own closed-won data." Prefer the user's actual historical data over any industry benchmark; when they conflict, the user's data wins. Stay in scope: design the revenue system the user asked for — don't drift into copywriting, pricing strategy, or outreach (hand off to the related skills below).
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 |
| 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 |
Related Skills
- mk-cold-email: For outbound prospecting emails
- mk-email-sequence: For lifecycle and nurture email flows
- mk-pricing-strategy: For pricing decisions and packaging
- mk-analytics-tracking: For tracking pipeline metrics and attribution
- mk-launch-strategy: For go-to-market launch planning
- mk-sales-enablement: For sales collateral, decks, and objection handling
1---2name: mk-revops3description: "Design and optimize revenue operations systems — the lead lifecycle, scoring, routing, pipeline, and marketing-to-sales handoff that connect marketing to revenue. EN triggers: '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', 'speed-to-lead', 'when should marketing hand off to sales'. FR triggers: 'RevOps', 'operations revenus', 'scoring des leads', 'routage des leads', 'qualification des leads', 'handoff marketing-ventes', 'gestion du pipeline', 'hygiène des données CRM', 'les leads n'arrivent pas aux ventes'. For cold outreach emails, see mk-cold-email. For email drip campaigns, see mk-email-sequence. For pricing decisions, see mk-pricing-strategy."4metadata:5 source: https://skillmd.com/skills/agentik-os/mk-revops6 version: 1.2.07---89# RevOps1011You 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.1213## Dynamic Workflow orchestration1415RevOps spans five loosely-coupled design units that can be worked in parallel, then reconciled. Use a plan -> fan-out -> adversarial-verify -> synthesize loop:16171. **Plan.** From the gathered context (GTM motion, ACV, sales cycle, stack, current state), decide which of the five units are in scope and in what order they couple: **lifecycle stages -> scoring -> routing -> pipeline config -> metrics dashboard**. Scoring depends on lifecycle definitions; routing depends on scoring thresholds; metrics depend on all four. Sequence the dependent chain; parallelize the independent design work within each unit.182. **Fan-out.** Draft each unit as an independent angle: (a) lifecycle stage doc, (b) scoring model, (c) routing rules + SLAs, (d) pipeline config + automations, (e) metrics dashboard spec. Pull from closed-won data and the user's actual stack — never a generic template.193. **Adversarial verify (2-of-3).** Before synthesizing, falsify each unit through three independent lenses; accept a design only if ≥2 agree it holds:20 - **Leak lens** — trace one lead end-to-end; does any handoff lack an SLA, owner, or fallback owner? Unrouted = cold.21 - **Definition lens** — would *sales* actually work every MQL this model produces? If marketing's MQL ≠ sales-accepted, the threshold or fit/engagement split is wrong.22 - **Data lens** — does the scoring model correctly identify past closed-won when back-tested? Do benchmark numbers match a cited source, not a guess?234. **Synthesize.** Reconcile the verified units into one coherent revenue engine — definitions must agree across documents (an MQL in the lifecycle doc must match the scoring threshold and the routing trigger). Resolve conflicts explicitly; don't paste five disconnected docs.245. **Loop-until-dry.** If the user's funnel has unknown leak points, iterate the leak lens stage-by-stage until no handoff lacks an SLA + owner + tracking mechanism.2526> Portability note: This skill is CRM/stack-agnostic and runs anywhere — no OmegaOS VPS dependency. The `.agents/` / `.claude/` context-file lookup below is optional; if absent, gather context interactively.2728## Before Starting2930**Check for product marketing context first:**31If `.agents/product-marketing-context.md` exists (or `.claude/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.3233Gather this context (ask if not provided):34351. **GTM motion** — Product-led (PLG), sales-led, or hybrid?362. **ACV range** — What's the average contract value?373. **Sales cycle length** — Days from first touch to closed-won?384. **Current stack** — CRM, marketing automation, scheduling, enrichment tools?395. **Current state** — How are leads managed today? What's working and what's not?406. **Goals** — Increase conversion? Reduce speed-to-lead? Fix handoff leaks? Build from scratch?4142Work 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.4344---4546## Core Principles4748### Single Source of Truth49One 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.5051### Define Before Automate52Get stage definitions, scoring criteria, and routing rules right on paper before building workflows. Automating a broken process just creates broken results faster.5354### Measure Every Handoff55Every 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.5657### Revenue Team Alignment58Marketing, 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.5960---6162## Lead Lifecycle Framework6364### Stage Definitions6566| Stage | Entry Criteria | Exit Criteria | Owner |67|-------|---------------|---------------|-------|68| **Subscriber** | Opts in to content (blog, newsletter) | Provides company info or shows engagement | Marketing |69| **Lead** | Identified contact with basic info | Meets minimum fit criteria | Marketing |70| **MQL** | Passes fit + engagement threshold | Sales accepts or rejects within SLA | Marketing |71| **SQL** | Sales accepts and qualifies via conversation | Opportunity created or recycled | Sales (SDR/AE) |72| **Opportunity** | Budget, authority, need, timeline confirmed | Closed-won or closed-lost | Sales (AE) |73| **Customer** | Closed-won deal | Expands, renews, or churns | CS / Account Mgmt |74| **Evangelist** | High NPS, referral activity, case study | Ongoing program participation | CS / Marketing |7576### MQL Definition7778An MQL requires both **fit** and **engagement**:7980- **Fit score** — Does this person match your ICP? (company size, industry, role, tech stack)81- **Engagement score** — Have they shown buying intent? (pricing page, demo request, multiple visits)8283Neither alone is sufficient. A perfect-fit company that never engages isn't an MQL. A student downloading every ebook isn't an MQL.8485### MQL-to-SQL Handoff SLA8687Define response times and document them:88- MQL alert sent to assigned rep89- Rep contacts within **4 hours** (business hours)90- Rep qualifies or rejects within **48 hours**91- Rejected MQLs go to recycling nurture with reason code9293**For complete lifecycle stage templates and SLA examples**: See [references/lifecycle-definitions.md](references/lifecycle-definitions.md)9495---9697## Lead Scoring9899### Scoring Dimensions100101**Explicit scoring (fit)** — Who they are:102- Company size, industry, revenue103- Job title, seniority, department104- Tech stack, geography105106**Implicit scoring (engagement)** — What they do:107- Page visits (especially pricing, demo, case studies)108- Content downloads, webinar attendance109- Email engagement (opens, clicks)110- Product usage (for PLG)111112**Negative scoring** — Disqualifying signals:113- Competitor email domains114- Student/personal email115- Unsubscribes, spam complaints116- Job title mismatches (intern, student)117118### Building a Scoring Model1191201. Define your ICP attributes and weight them1212. Identify high-intent behavioral signals from closed-won data1223. Set point values for each attribute and behavior1234. Set MQL threshold (typically 50-80 points on a 100-point scale)1245. Test against historical data — does the model correctly identify past wins?1256. Launch, measure, and recalibrate quarterly126127### Common Scoring Mistakes128129- Weighting content downloads too heavily (research ≠ buying intent)130- Not including negative scoring (lets bad leads through)131- Setting and forgetting (buyer behavior changes; recalibrate quarterly)132- Scoring all page visits equally (pricing page ≠ blog post)133134**For detailed scoring templates and example models**: See [references/scoring-models.md](references/scoring-models.md)135136---137138## Lead Routing139140### Routing Methods141142| Method | How It Works | Best For |143|--------|-------------|----------|144| **Round-robin** | Distribute evenly across reps | Equal territories, similar deal sizes |145| **Territory-based** | Assign by geography, vertical, or segment | Regional teams, industry specialists |146| **Account-based** | Named accounts go to named reps | ABM motions, strategic accounts |147| **Skill-based** | Route by deal complexity, product line, or language | Diverse product lines, global teams |148149### Routing Rules Essentials150151- Route to the **most specific match** first, then fall back to general152- Include a **fallback owner** — unassigned leads go cold fast and waste pipeline153- Round-robin should account for **rep capacity and availability** (PTO, quota attainment)154- Log every routing decision for audit and optimization155156### Speed-to-Lead157158Response time is the single biggest factor in lead conversion:159- Contact within **5 minutes** = 21x more likely to qualify (Lead Connect)160- After **30 minutes**, conversion drops by 10x161- After **24 hours**, the lead is effectively cold162163Build routing rules that prioritize speed. Alert reps immediately. Escalate if SLA is missed.164165**For routing decision trees and platform-specific setup**: See [references/routing-rules.md](references/routing-rules.md)166167---168169## Pipeline Stage Management170171### Pipeline Stages172173| Stage | Required Fields | Exit Criteria |174|-------|----------------|---------------|175| **Qualified** | Contact info, company, source, fit score | Discovery call scheduled |176| **Discovery** | Pain points, current solution, timeline | Needs confirmed, demo scheduled |177| **Demo/Evaluation** | Technical requirements, decision makers | Positive evaluation, proposal requested |178| **Proposal** | Pricing, terms, stakeholder map | Proposal delivered and reviewed |179| **Negotiation** | Redlines, approval chain, close date | Terms agreed, contract sent |180| **Closed Won** | Signed contract, payment terms | Handoff to CS complete |181| **Closed Lost** | Loss reason, competitor (if any) | Post-mortem logged |182183### Stage Hygiene184185- **Required fields per stage** — Don't let reps advance a deal without filling in required data186- **Stale deal alerts** — Flag deals that sit in a stage beyond the average time (e.g., 2x average days)187- **Stage skip detection** — Alert when deals jump stages (Qualified → Proposal skipping Discovery)188- **Close date discipline** — Push dates must include a reason; no silent pushes189190### Pipeline Metrics191192| Metric | What It Tells You |193|--------|-------------------|194| Stage conversion rates | Where deals die |195| Average time in stage | Where deals stall |196| Pipeline velocity | Revenue per day through the funnel |197| Coverage ratio | Pipeline value vs. quota (target 3-4x) |198| Win rate by source | Which channels produce real revenue |199200---201202## CRM Automation Workflows203204### Essential Automations205206- **Lifecycle stage updates** — Auto-advance stages when criteria are met207- **Task creation on handoff** — Create follow-up task when MQL assigned to rep208- **SLA alerts** — Notify manager if rep misses response time SLA209- **Deal stage triggers** — Auto-send proposals, update forecasts, notify CS on close210211### Marketing-to-Sales Automations212213- **MQL alert** — Instant notification to assigned rep with lead context214- **Meeting booked** — Notify AE when prospect books via scheduling tool215- **Lead activity digest** — Daily summary of high-intent actions by active leads216- **Re-engagement trigger** — Alert sales when a dormant lead returns to site217218### Calendar Scheduling Integration219220- **Round-robin scheduling** — Distribute meetings evenly across team221- **Routing by criteria** — Send enterprise leads to senior AEs, SMB to junior reps222- **Pre-meeting enrichment** — Auto-populate CRM record before the call223- **No-show workflows** — Auto-follow-up if prospect misses meeting224225**For platform-specific workflow recipes**: See [references/automation-playbooks.md](references/automation-playbooks.md)226227---228229## Deal Desk Processes230231### When You Need a Deal Desk232233- ACV above **$25K** (or your threshold for non-standard deals)234- Non-standard payment terms (net-90, quarterly billing)235- Multi-year contracts with custom pricing236- Volume discounts beyond published tiers237- Custom legal terms or SLAs238239### Approval Workflow Tiers240241| Deal Size | Approval Required |242|-----------|-------------------|243| Standard pricing | Auto-approved |244| 10-20% discount | Sales manager |245| 20-40% discount | VP Sales |246| 40%+ discount or custom terms | Deal desk review |247| Multi-year / enterprise | Finance + Legal |248249### Non-Standard Terms Handling250251Document every exception. Track which non-standard terms get requested most — if everyone asks for the same exception, it should become standard. Review quarterly.252253---254255## Data Hygiene & Enrichment256257### Dedup Strategy258259- **Matching rules** — Email domain + company name + phone as primary match keys260- **Merge priority** — CRM record wins over marketing automation; most recent activity wins for fields261- **Scheduled dedup** — Run weekly automated dedup with manual review for edge cases262263### Required Fields Enforcement264265- Enforce required fields at each lifecycle stage266- Block stage advancement if fields are empty267- Use progressive profiling — don't require everything upfront268269### Enrichment Tools270271| Tool | Strength |272|------|----------|273| Clearbit | Real-time enrichment, good for tech companies |274| Apollo | Contact data + sequences, strong for prospecting |275| ZoomInfo | Enterprise-grade, largest B2B database |276277### Quarterly Audit Checklist278279- Review and merge duplicates280- Validate email deliverability on stale contacts281- Archive contacts with no activity in 12+ months282- Audit lifecycle stage distribution (look for bottlenecks)283- Verify enrichment data accuracy on a sample set284285---286287## RevOps Metrics Dashboard288289### Key Metrics290291| Metric | Formula / Definition | Benchmark |292|--------|---------------------|-----------|293| Lead-to-MQL rate | MQLs / Total leads | 5-15% |294| MQL-to-SQL rate | SQLs / MQLs | 30-50% |295| SQL-to-Opportunity | Opportunities / SQLs | 50-70% |296| Pipeline velocity | (# deals x avg deal size x win rate) / avg sales cycle | Varies by ACV |297| CAC | Total sales + marketing spend / new customers | LTV:CAC > 3:1 |298| LTV:CAC ratio | Customer lifetime value / CAC | 3:1 to 5:1 healthy |299| Speed-to-lead | Time from form fill to first rep contact | < 5 minutes ideal |300| Win rate | Closed-won / total opportunities | 20-30% (varies) |301302### Dashboard Structure303304Build three views:3051. **Marketing view** — Lead volume, MQL rate, source attribution, cost per MQL3062. **Sales view** — Pipeline value, stage conversion, velocity, forecast accuracy3073. **Executive view** — CAC, LTV:CAC, revenue vs. target, pipeline coverage308309---310311## Output Format312313When delivering RevOps recommendations, provide:3143151. **Lifecycle stage document** — Stage definitions with entry/exit criteria, owners, and SLAs3162. **Scoring specification** — Fit and engagement attributes with point values and MQL threshold3173. **Routing rules document** — Decision tree with assignment logic and fallbacks3184. **Pipeline configuration** — Stage definitions, required fields, and automation triggers3195. **Metrics dashboard spec** — Key metrics, data sources, and target benchmarks320321Format each as a standalone document the user can implement directly. Include platform-specific guidance when the CRM is known.322323### Verify before delivering324325Run this checklist against the synthesized output — fix any failure before handing off:326327- [ ] **Definitions agree across documents** — the MQL in the lifecycle doc = the scoring threshold = the routing trigger. No drift.328- [ ] **Every handoff has an SLA + named owner + tracking mechanism** — marketing→sales, SDR→AE, AE→CS. None unrouted, none without a fallback owner.329- [ ] **Scoring model back-tests** — it would flag the user's actual past closed-won deals as MQLs; negative scoring excludes the obvious bad-fit cases.330- [ ] **Every benchmark is sourced or labelled** — each conversion-rate / speed-to-lead / LTV:CAC figure cites its origin (e.g., Lead Connect) or is explicitly marked "typical range, validate against your data". No invented numbers presented as fact.331- [ ] **Platform-specific steps are real** — only give CRM-specific setup for a platform the user named; never fabricate a feature a tool doesn't have.332333### Evidence & no-hallucination guardrail334335RevOps numbers drive real money decisions. Do not invent benchmarks, conversion rates, or tool capabilities. When you state a figure, either cite a source or label it a "typical range — validate against your own closed-won data." Prefer the user's actual historical data over any industry benchmark; when they conflict, the user's data wins. Stay in scope: design the revenue system the user asked for — don't drift into copywriting, pricing strategy, or outreach (hand off to the related skills below).336337---338339## Task-Specific Questions3403411. What CRM platform are you using (or planning to use)?3422. How many leads per month do you generate?3433. What's your current MQL definition?3444. Where do leads get stuck in your funnel?3455. Do you have SLAs between marketing and sales today?346347---348349## Tool Integrations350351For implementation, see the [tools registry](../../tools/REGISTRY.md). Key RevOps tools:352353| Tool | What It Does | Guide |354|------|-------------|-------|355| **HubSpot** | CRM, marketing automation, lead scoring, workflows | [hubspot.md](../../tools/integrations/hubspot.md) |356| **Salesforce** | Enterprise CRM, pipeline management, reporting | [salesforce.md](../../tools/integrations/salesforce.md) |357| **Calendly** | Meeting scheduling, round-robin routing | [calendly.md](../../tools/integrations/calendly.md) |358| **SavvyCal** | Scheduling with priority-based availability | [savvycal.md](../../tools/integrations/savvycal.md) |359| **Clearbit** | Real-time lead enrichment and scoring | [clearbit.md](../../tools/integrations/clearbit.md) |360| **Apollo** | Contact data, enrichment, and outbound sequences | [apollo.md](../../tools/integrations/apollo.md) |361| **ActiveCampaign** | Marketing automation for SMBs, lead scoring | [activecampaign.md](../../tools/integrations/activecampaign.md) |362| **Zapier** | Cross-tool automation and workflow glue | [zapier.md](../../tools/integrations/zapier.md) |363364---365366## Related Skills367368- **mk-cold-email**: For outbound prospecting emails369- **mk-email-sequence**: For lifecycle and nurture email flows370- **mk-pricing-strategy**: For pricing decisions and packaging371- **mk-analytics-tracking**: For tracking pipeline metrics and attribution372- **mk-launch-strategy**: For go-to-market launch planning373- **mk-sales-enablement**: For sales collateral, decks, and objection handling