revops – skill Marketing & SEO cho agent AI

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.

When to Use

• Use when the user needs lead scoring, routing, handoffs, or lifecycle definitions.
• Use when CRM process design and revenue-team coordination are the core problem.
• Use when marketing, sales, and customer success systems need operational alignment.

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

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.

---

Implementation boundaries

Treat all numeric thresholds/benchmarks and platform recipes as illustrative starting points. Validate current product tiers, APIs and field behavior before implementation. Planning does not authorize live CRM mutations, record merges/deletion, outbound messages, enrichment uploads or ad-audience sync. Preserve suppression/opt-out records; unsubscribes are eligibility controls, not merely negative scores. Minimize personal data, scope credentials, preview changes and preserve a rollback/export before bulk work. Calibrate with time-split validation including wins, losses and unconverted leads, avoiding post-outcome features.

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](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](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 speed can affect qualification, but its effect depends on channel, intent and business hours. Establish a measured local baseline; do not present historical vendor multipliers as universal conversion guarantees.

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](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
• **

… (nội dung đầy đủ có trong gói tải về)