Marketer pack
Claude Skill
RevOps Lifecycle Designer
Designs the lead lifecycle and marketing→sales handoff — scoring, routing, stage definitions — so leads stop leaking between teams.
What it does
Designs the systems that connect marketing, sales, and customer success into one revenue engine: a single source of truth, stage definitions both teams agree on (MQL/SQL), lead scoring and routing, and measured handoffs with SLAs. Built to fix the leaks where leads stall or get dropped between teams — by defining the process on paper before automating it.
When to use
- ✓Leads aren't reaching sales, or stall and go cold at the handoff
- ✓Defining MQL/SQL and pipeline stages, or the scoring behind them
- ✓Building lead routing, or fixing CRM data hygiene
When not to use
- ✗You need the outreach itself written — that's a sales/email skill
- ✗A tiny team with no marketing-to-sales handoff yet
Install
Download the .zip, then unzip into your Claude skills folder.
mkdir -p ~/.claude/skills
unzip ~/Downloads/revops-lifecycle-designer.zip -d ~/.claude/skills/
# Restart Claude Code session.
# Skill is now available — Claude will use it when relevant.SKILL.md
SKILL.md
---
name: revops-lifecycle-designer
description: Use when designing revenue operations, lead lifecycle, or the marketing-to-sales handoff. Triggers on "RevOps", "lead scoring", "lead routing", "MQL", "SQL", "pipeline stages", "leads aren't getting to sales", "speed-to-lead", "marketing-to-sales handoff".
---
# RevOps Lifecycle Designer
RevOps is the plumbing between marketing, sales, and CS. Most leaks aren't a lead-volume problem — they're a definition and handoff problem: leads stall because no one agreed what "ready for sales" means or who owns the lead next.
## Single source of truth
One system of record (the CRM) for every lead and account. If the same lead lives in the marketing tool, a spreadsheet, and the CRM with different states, they will conflict — pick the canonical source and sync everything to it.
## Define before you automate
Get the stage definitions, scoring criteria, and routing rules right on paper, agreed by both marketing and sales, before building a single workflow. Automating a process nobody agreed on just produces broken results faster.
- **Stage definitions** — what makes a lead an MQL, an SQL, etc., in concrete, checkable terms both teams accept
- **Scoring** — the signals that qualify a lead, weighted to predict real intent (not vanity engagement)
- **Routing** — who gets the lead, on what trigger, within what time
## Measure every handoff
Instrument where leads move between teams and where they stall. Speed-to-lead matters — a lead contacted in minutes converts far better than one contacted in days. Put an SLA on the handoff and track it.
## Anti-patterns
- Automating before the process is defined and agreed
- Lead data split across systems that disagree
- MQL/SQL definitions marketing and sales never actually aligned on
- No SLA or measurement on the handoff — leads die in the gap
- Scoring on vanity engagement instead of real intent signals
Example prompts
Once installed, try these prompts in Claude:
- Leads from our demo form take days to reach a rep and half go cold. Design the routing and SLA to fix speed-to-lead.
- Define MQL and SQL for our PLG + sales hybrid motion, and the scoring behind each.