Revops
sickn33/agentic-awesome-skills
Design and improve revenue operations, lead lifecycle rules, scoring, routing, handoffs, and CRM process automation.
A skill your agent uses when revenue leaks between teams: leads go dark after handover to sales, promised commitments disappear after signature, expansion signals stay invisible, CS never learns…
MITAuto-check passed
Install Revops Handoffs
$ npx skills add swan-gtm/gtm-skills --skill revops-handoffs -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install swan-gtm/gtm-skills revops-handoffs --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/swan-gtm/gtm-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/rutger-katz/revops-handoffs .claude/skills/revops-handoffs && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "revops-handoffs" agent skill from https://github.com/swan-gtm/gtm-skills/tree/main/skills/rutger-katz/revops-handoffs into .claude/skills/revops-handoffs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "revops-handoffs", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/swan-gtm/gtm-skills/tree/main/skills/rutger-katz/revops-handoffsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add swan-gtm/gtm-skills --skill revops-handoffs -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install swan-gtm/gtm-skills revops-handoffs --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/swan-gtm/gtm-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/rutger-katz/revops-handoffs .agents/skills/revops-handoffs && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "revops-handoffs" agent skill from https://github.com/swan-gtm/gtm-skills/tree/main/skills/rutger-katz/revops-handoffs into .agents/skills/revops-handoffs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "revops-handoffs", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add swan-gtm/gtm-skills --skill revops-handoffs -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install swan-gtm/gtm-skills revops-handoffs --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/swan-gtm/gtm-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/rutger-katz/revops-handoffs .cursor/skills/revops-handoffs && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "revops-handoffs" agent skill from https://github.com/swan-gtm/gtm-skills/tree/main/skills/rutger-katz/revops-handoffs into .cursor/skills/revops-handoffs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "revops-handoffs", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/swan-gtm/gtm-skills.git --path skills/rutger-katz/revops-handoffs--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add swan-gtm/gtm-skills --skill revops-handoffs -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install swan-gtm/gtm-skills revops-handoffs --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/swan-gtm/gtm-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/rutger-katz/revops-handoffs .gemini/skills/revops-handoffs && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "revops-handoffs" agent skill from https://github.com/swan-gtm/gtm-skills/tree/main/skills/rutger-katz/revops-handoffs into .gemini/skills/revops-handoffs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "revops-handoffs", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install swan-gtm/gtm-skills revops-handoffsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add swan-gtm/gtm-skills --skill revops-handoffs -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/swan-gtm/gtm-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/rutger-katz/revops-handoffs .github/skills/revops-handoffs && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "revops-handoffs" agent skill from https://github.com/swan-gtm/gtm-skills/tree/main/skills/rutger-katz/revops-handoffs into .github/skills/revops-handoffs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "revops-handoffs", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add swan-gtm/gtm-skills --skill revops-handoffs -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install swan-gtm/gtm-skills revops-handoffs --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/swan-gtm/gtm-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/rutger-katz/revops-handoffs .opencode/skills/revops-handoffs && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "revops-handoffs" agent skill from https://github.com/swan-gtm/gtm-skills/tree/main/skills/rutger-katz/revops-handoffs into .opencode/skills/revops-handoffs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "revops-handoffs", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
revops-handoffs- GitHub stars
- 172
- Token cost
- ~3.7k tokens
- SKILL.md length
- 1,707 words
- Files
- 5 (incl. references)
- Skills in repo
- 32
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when revenue leaks between teams: leads go dark after handover to sales, promised commitments disappear after signature, expansion signals stay invisible, CS never learns…
- Works in 7 steps: Marketing to Sales → Sales to Partner/Implementation → Implementation to CS → …
- Revenue leaks between teams: leads go dark after handover to sales
- SKILL.md covers The Five-Node Bow Tie, 1. Marketing to Sales, 2. Sales to… and 3. Implementation to CS, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Revops Handoffs is an agent skill from swan-gtm/gtm-skills. Use this skill when revenue leaks between teams: leads go dark after handover to sales, promised commitments disappear after signature, expansion signals stay invisible, CS never learns what sales committed. Designs handoff protocols across the full revenue bow-tie (marketing to sales, sales to customer, customer to expansion) with speed-to-lead SLAs, context-packet architecture, ownership models, and leading indicators of failure. Produces handoff playbooks per transition, context templates, SLAs with…
Its SKILL.md is about 3.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/ai-tooling-for-revenue-handoffs-extended-vendor-guide.md`, `references/expansion-pipeline-architecture.md` and `references/handoff-slas-and-benchmarks.md`).
The repository describes itself as: Open, production-grade GTM skills for AI agents. The licence is MIT.
When your agent uses it
- Revenue leaks between teams: leads go dark after handover to sales
- Promised commitments disappear after signature
- Expansion signals stay invisible
- CS never learns what sales committed
Example prompts
- “/revops-handoffs”
Workflow steps
7 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 67abd04. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
neontriforce.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Revops Handoffs loads about 3.7k tokens when it runs, and up to ~13k if it reads all its reference files. Until then it costs about 194 tokens; SKILL.md has 1,707 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from swan-gtm/gtm-skills at commit 67abd04, republished under its MIT licence (© swan-gtm). 1,707 words, ~3,728 tokens.
Download SKILL.mdSave it as
.claude/skills/revops-handoffs/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- revops-handoffs
- description
- Use this skill when revenue leaks between teams: leads go dark after handover to sales, promised commitments disappear after signature, expansion signals stay invisible, CS never learns what sales committed. Designs handoff protocols across the full revenue bow-tie (marketing to sales, sales to customer, customer to expansion) with speed-to-lead SLAs, context-packet architecture, ownership models, and leading indicators of failure. Produces handoff playbooks per transition, context templates, SLAs with measurement dashboards, and detection rules for leaking revenue. Rule: handoffs are where revenue leaks. Trigger phrases: leads fall through the cracks, closed-won handoff, CS-to-sales handback, speed-to-lead, SLA between teams, nobody owns expansion.
- title
- Design revenue handoffs
- category
- RevOps
Revenue Handoff Operations: Full Bow-Tie Model
You are a revenue handoff architect. Handoffs are where revenue leaks. Standardised handoff protocols improve implementation success by ~45% and cut first-year churn by 35-40%. Your job: design the SLAs, context packets, routing rules, ownership models, and automation for every transition in the bow tie.
Reference files (read before giving detailed implementation advice):
references/handoff-slas-and-benchmarks.md: SLA targets, speed-to-lead data, metrics per handoff, leading indicators of failure, measurement dashboardsreferences/expansion-pipeline-architecture.md: three-type expansion model, new-DMU cross-sell handling, ownership thresholds, association model, SPICED requirementsreferences/hubspot-workflows.md: pipeline configurations, workflow specs, property catalog, Breeze AI patterns, tier requirementsreferences/ai-tooling.md: AI handoff document generation, enrichment/scoring tools, predictive models, LLM middleware patterns, GDPR considerations
The Five-Node Bow Tie
Most B2B SaaS orgs have four handoff points. Companies with implementation partners have five:
Marketing → Sales → Partner/Impl → CS → Sales (expansion)
↑
Lifecycle marketing & ABM loops back ←──┘Each node has: an owner, a context packet (what must transfer), an SLA (time + quality), a trigger (what fires the handoff), and measurement (how you know it's working or failing).
1. Marketing to Sales
The most studied, most frequently broken transition. Speed kills competitors; delay kills deals.
Speed-to-Lead (the non-negotiables)
| Lead Type | Response SLA | Evidence |
|---|---|---|
| Hand-raisers (demo, pricing) | < 5 minutes | 21× more likely to qualify vs 30 min (Dr. James Oldroyd, MIT Sloan, 2007; foundational research, predates AI automation and channel saturation; 15,000+ leads across 6 companies) |
| Paid ads | < 3 minutes | Highest cost-per-lead, hottest intent |
| Partner referral | < 30 minutes | Warm but relationship-dependent |
| Organic inbound | < 10 minutes | Moderate intent |
| Content / webinar | 3-4 days (nurture first) | Premature outreach damages trust |
Reality check (historical baseline, 2011): average B2B response is 42 hours, 23% never get a reply. Modern context (2025): instant booking converts 66.7% of qualified submissions vs ~30% industry average (Chili Piper, 4M submissions); <5-minute response closes at 32% rate (Optifai Pipeline Study, 939 companies).
Lead Tiers
Hand-raisers: bypass scoring, route directly to sales. 5-minute SLA. MQLs: firmographic fit + behavioural intent + third-party intent. Common starting split: 40/40/20 (operational template; optimise through conversion analysis against your closed-won data). Route to SDR/AE by territory. Scoring drives 39-40% MQL-to-SQL vs 15-21% without (Forrester/SiriusDecisions Demand Waterfall). PQLs (hybrid PLG): usage-based triggers. Convert at 15-30%.
Context Packet
Firmographic context, full engagement history, lead score breakdown (fit vs intent), buying group context (other contacts from same account), qualification data (SPICED/BANT if SDR-qualified). Auto-enrich before routing to eliminate research delay.
Marketing-Sales SLA
Marketing: X qualified MQLs, pipeline contribution at 4x coverage. Sales: respond within SLA, 5-10 follow-up attempts, CRM disposition within deadline. Enforce: auto-escalation, auto-reassignment at 24h, weekly compliance reporting.
Routing Models
Round-robin (early stage), territory-based (scale), capacity-based (mature). Account-based override is non-negotiable: leads from known accounts route to account owner, never rotation. For EU: route by language of form submission as first-pass filter: DACH, Nordics, UK/IE, Western Europe, Southern Europe, CEE.
→ For detailed benchmarks and metrics: read references/handoff-slas-and-benchmarks.md
2. Sales to Partner/Implementation
Customer excitement peaks at signature then collapses if nothing happens ("Trough of Disillusionment").
Context Packet (7 elements)
- Deal history and origin
- Customer goals with measurable success criteria (specific, not assumed)
- Full stakeholder map (champion, economic buyer, end users, detractors)
- Every commitment the AE made (explicit and implicit)
- Known risks and internal politics
- Technical requirements (integrations, migration, compliance)
- Customer timeline including critical events from SPICED
SLAs
| Milestone | Target |
|---|---|
| Internal AE to Impl briefing | 24-48 hours post-signature |
| Customer introduction email | Within first week |
| Kickoff scheduled | 48-72 hours post-signing |
| First implementation meeting | 2-7 days (2 best, 7 standard) |
Partner-Specific
Partner receives: full SPICED brief + technical requirements + stakeholder map + timeline + promises log. AE attends partner kickoff. Partner reports milestones to vendor CRM. Hypercare (2-4 weeks post go-live) bridges to CS.
Sales Involvement Model
Warm overlay (default): AE at kickoff, introductions, steps back, CC'd 2 weeks. Pre-sale CS (enterprise >€50K ACV): CSM in late-stage calls. Clean break (SMB <€10K): automated handoff.
3. Implementation to CS
Least standardised, most consequential. Early value realisation (within first 30 days) correlates with higher CLV.
Context Packet
Scope/configuration details, training completion status and gaps, outstanding issues with workarounds, customer sentiment during implementation, updated stakeholder map, initial adoption metrics, lessons learned.
Go-Live Readiness (5 conditions, all true)
Tasks work end-to-end. People trained. Data migrated. Support plan in place. Rollback plan exists.
Health Scoring Starts Here
Don't wait for steady-state. Track: milestone completion rate, stakeholder engagement, customer responsiveness, admin login frequency, training attendance.
4. CS to Sales (Expansion)
Expansion costs $0.27/$1 ACV vs $1.16 new (Pacific Crest, 2016, historical baseline); modern data shows 50-60% of new ARR from expansion sourced from existing customers (OpenView 2023, KeyBanc 2024), up from historical 35-40%.
Three Expansion Types: Critical
| Type | DMU | Pipeline | Discovery |
|---|---|---|---|
| Upsell | Same champion, same budget | Short: Identified → Proposal → Won | SPICED refresh |
| Cross-sell (warm) | Partial overlap, champion introduces | Standard: Identified → Needs Assessment → Proposal → Negotiation → Won | Partial new SPICED |
| Cross-sell (new DMU) | Completely new buying group | Full discovery stages added | Full new SPICED mandatory |
A cross-sell with a completely new DMU is a new-logo sale inside a known company. Trust is with the account, not the buying group. Forcing it into the short pipeline poisons win rate and velocity data.
Litmus test: "Would losing the contract in BU-A affect closing in BU-B?" If no → new logo with customer referral source.
Ownership
| ACV | Owner | CS role |
|---|---|---|
| <€10K | CSM closes | End-to-end |
| €10K-50K | AM/AE + CSM | Context, stays in meetings |
| >€50K | AE full cycle | Introduces, advisory |
Define thresholds in governance. Ambiguity = nobody closes.
Expansion Signals
Usage: 80%+ seat limits, new feature adoption, DAU increasing. Relationship: champion promoted, new stakeholder, positive NPS. Commercial: org headcount growth, new budget cycle, cross-functional interest. Outcomes: value ahead of schedule, ROI exceeded, new use cases.
CS to Sales Handback Process
CSM flags signal → workflow creates deal → assigns to AE → CSM prepares brief (health, usage, stakeholders, whitespace) → joint meeting → clear rules of engagement from there.
→ For new-DMU detail, association model, and reporting payoff: read references/expansion-pipeline-architecture.md
5. Lifecycle Marketing and ABM Loops
Five-Stage Post-Sale Marketing
- Onboarding: role-based education, setup guides, in-app messaging
- Adoption: feature spotlights, best practices, certifications
- Retention: ROI reports, QBR materials, NPS surveys
- Expansion: usage-based trigger emails, cross-sell content, feature nudges
- Advocacy: case studies, review campaigns (G2, Capterra), advisory boards
Show full SKILL.md (695 more words)Show less
ABM for Existing Customers
Churn prevention ABM (competitor intent signals to executive engagement), cross-sell ABM (content clustering to product nurture), multi-threading ABM (new departments via LinkedIn + role-specific content), renewal ABM (customer-specific ROI reports 90-120 days pre-renewal), usage-based expansion ABM (in-app + email on product signals).
6. AI-Enabled Handoffs
Read references/ai-tooling.md for the full stack. Summary:
Production-ready now: AskElephant ($99/mo) for auto-generated SPICED handoff docs. Clay ($149-800/mo) for enrichment + scoring. HubSpot Breeze for native intent scoring. Gong/Avoma for conversation intelligence.
LLM middleware pattern: deal stage change → pull CRM data + transcripts → structured prompt → output to CRM/workspace. Works with GPT-4 or Claude via Zapier/Make/n8n.
Predictive: Pendo Predict, ChurnZero for churn/expansion. Best models hit 85-92% accuracy 60-90 days pre-churn.
GDPR non-negotiables: data residency, model training opt-out, consent management, EU Data Act switching requirements.
7. HubSpot Implementation
Read references/hubspot-workflows.md for detailed specs. Architecture summary:
Three pipelines: New Business, Expansion (with expansion_type driving conditional stages), Renewals (auto-created on Closed Won).
Deal-to-deal associations (Professional+) link expansion → original deal for lineage and Δt7 measurement.
Key workflows: MQL routing (5-min SLA, Breeze AI summary, Slack notify, 24h escalation), Closed-Won handoff (validate completeness → create onboarding ticket + renewal deal), expansion signal (company property → auto-create deal → assign + notify), renewal automation (date-triggered at T-90).
Speed-to-lead tracking: custom first_connection_date property + calculated speed_to_lead_hours. HubSpot lacks this natively.
Measurement Framework
Metrics by Handoff
| Handoff | Key Metrics | Targets |
|---|---|---|
| Mktg to Sales | Speed-to-lead, MQL-to-SQL conversion, unworked rate | <5 min (hand-raisers), 25-35% conversion, <5% unworked |
| Sales to Impl | Time-to-kickoff, info completeness, quality score | <7 days, >90%, ≥4.0/5 |
| Impl to CS | TTFV, go-live rate, onboarding churn | Segment-dependent, >85%, <3% |
| CS to Sales | Expansion pipeline from CS, handoff time, expansion win rate, NRR | Growing QoQ, <48h, >40% upsell / >20% new-DMU, 110-130%+ |
Leading Indicators of Failure
Rising unworked leads (>10%) signals SDR overload/routing failure. MQL rejection rising signals ICP misalignment. Time-to-kickoff >14d signals sales-CS bottleneck. Declining onboarding completion signals capacity/complexity issue. Shrinking expansion pipeline signals CS not surfacing signals.
Quality Scorecard
Receiving team rates each handoff 1-5 across: information completeness, promise alignment, customer sentiment continuity, context transfer quality, stakeholder mapping. Review weekly in operating cadence.
How to Use This Skill
"Leads fall through the cracks": Speed-to-lead + routing rules. Read benchmarks reference. "CS never knows what sales promised": SPICED-to-handoff pipeline. Gate Closed Won on completeness. Read AI tooling reference. "We lose momentum after signature": Sales to Impl SLA. Auto-trigger on Closed Won. Read workflows reference. "Nobody owns expansion": Ownership model + expansion pipeline. Read expansion architecture reference. "Cross-sell has a different buying group": Three-type model. Read expansion architecture reference. "How do we involve the partner?": Partner context packet + AE-at-kickoff + hypercare bridge. "Design handoffs from scratch": Audit each point against SLA framework. Instrument leading indicators. Start with biggest revenue leak.
References
- Dr. James Oldroyd, MIT Sloan (2007). Lead Response Management study. 15,000+ leads across 6 companies. Published via InsideSales.com.
- Velocify (circa 2012). Responding within 1 minute increases conversion by 391%.
- HBR (2011). "The Short Life of Online Sales Leads." 2,241 companies tested. Average B2B response: 42 hours. 23% never responded.
- Workato (2024). Speed-to-lead study: 114 B2B companies. Only 1 sent personalised email within 5 min. Average personalised response: 11h 54m.
- Chili Piper (2025). 2025 Benchmark Report: ~4M form submissions. Instant booking converts 66.7% vs ~30% industry average.
- Justin Norris, RevOps FM (2025). "A Complete Guide to Speed-to-Lead." 10-min hand-raiser SLA to 40% conversion lift.
- Optifai Pipeline Study (Q2 2025-Q1 2026, 939 companies). <5 min response = 32% close rate, 2.6x higher than 24+ hours.
- Pacific Crest / David Skok & Matrix Partners (2016). SaaS Survey: expansion costs $0.27 per $1 ACV vs $1.16 new logos.
- OpenView Partners (2023). SaaS Benchmarks (700+ companies): 50-60% of new ARR from expansion (best-in-class).
- KeyBanc (2024). Expansion = 52% of new ARR.
- Rework (2025). "Deal Handoff Protocol: Standardizing Post-Close Transitions." 45% implementation improvement, 35-40% churn reduction.
- Forrester/SiriusDecisions. Demand Waterfall: MQL→SQL 39-40% with scoring vs 15-21% without.
What good looks like
- Every bow-tie transition has a named owner, an SLA, and a context packet the receiving team actually reads.
- Speed-to-lead is measured against the SLA and breaches alert someone accountable.
- After signature, CS can see what sales promised without asking.
- Leak indicators such as unworked leads and silent post-sale accounts sit on a dashboard, not in retrospectives.
Built by Neon Triforce
© swan-gtm, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files (references) in skills/rutger-katz/revops-handoffs of swan-gtm/gtm-skills.
- SKILL.md
- references/ai-tooling-for-revenue-handoffs-extended-vendor-guide.md
- references/expansion-pipeline-architecture.md
- references/handoff-slas-and-benchmarks.md
- references/hubspot-workflow-specifications-for-revenue-handoffs-extended.md
Open the folder on GitHubat commit 67abd04
Compare with similar skills
Revops Handoffs next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Revops Handoffs this skillswan-gtm/gtm-skills | 172 | — | ~3.7k | Automated safety check: Pass | MIT | |
| Revopssickn33/agentic-awesome-skills | 47k | 2 repos | ~3.8k | Automated safety check: Pass | MIT | |
| Session Handoff Documentthedotmack/claude-mem | 99k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Handoffnexu-io/open-design | 100k | — | ~547 | Automated safety check: Pass | Apache-2.0 | |
| Handoffalirezarezvani/claude-skills | 28k | — | ~2.5k | Automated safety check: Notes | MIT | |
| Handoffalirezarezvani/claude-skills | 28k | — | ~532 | Automated safety check: Pass | MIT |
Similar skills
Session Handoff Document
thedotmack/claude-mem
Writes a HANDOFF.md capturing goal, state, files, failed attempts and next steps so a fresh agent session can continue exactly where this one stopped.
Handoff
nexu-io/open-design
Push the run's accepted artifact to a downstream collaboration surface (cli, other code agents, cloud, desktop) and stamp the artifact manifest with the export target.
Handoff
alirezarezvani/claude-skills
Compact the current conversation into a handoff document for another agent to pick up.
Handoff
alirezarezvani/claude-skills
Compact the current conversation into a handoff document for another agent to pick up.
Session Handoff Writer
codewhale-hq/Codewhale
Writes a compact handoff note from real git and CI state so the next session or a teammate can pick up the work without rebuilding the context.
More from swan-gtm/gtm-skills
All 32 skills in this repoRevops Revenue Planning
swan-gtm/gtm-skills
Annual and quarterly revenue plan construction, top-down vs bottoms-up reconciliation, plan versioning, stretch goal handling, and FP&A-RevOps collaboration for B2B revenue teams.
AI Personalization Prompts
swan-gtm/gtm-skills
A skill your agent uses when setting up AI-powered personalization, building Clay or lemlist workflows, or automating prospect research — 6 AI personalization prompts (lemlist style) plus 2 email…
Audience Icp Filter
swan-gtm/gtm-skills
A skill your agent uses when a list of people already exists and someone needs to know who on it is worth contacting — event or webinar attendees, registrants, a prospecting export, a CRM segment, a…
Brand Mention Monitor
swan-gtm/gtm-skills
A skill your agent uses when you need to know what people are saying about a brand across the web and social — "monitor brand mentions", "what are people saying about [brand] this week", "run a…
Bridge Before Cold
swan-gtm/gtm-skills
Use this skill before staging a prospect and before drafting any first touch, when a segment has gone silent, and when deciding whether an account is genuinely cold.
Champion Move Detection
swan-gtm/gtm-skills
Use this skill on a monthly cadence to detect champions and heavy users of your paying customers who changed jobs, verify the move against live LinkedIn data, score the new company, and surface…
Questions about Revops Handoffs
What does Revops Handoffs do?
A skill your agent uses when revenue leaks between teams: leads go dark after handover to sales, promised commitments disappear after signature, expansion signals stay invisible, CS never learns…. Revops Handoffs is an agent skill from swan-gtm/gtm-skills. Use this skill when revenue leaks between teams: leads go dark after handover to sales, promised commitments disappear after signature, expansion signals stay invisible, CS never learns what sales committed.
When should I use Revops Handoffs?
Revops Handoffs fits situations like: revenue leaks between teams: leads go dark after handover to sales; promised commitments disappear after signature; expansion signals stay invisible; CS never learns what sales committed.
How do I install Revops Handoffs in Claude Code?
Run `npx skills add swan-gtm/gtm-skills --skill revops-handoffs -a claude-code`. Or copy the skill folder (skills/rutger-katz/revops-handoffs in swan-gtm/gtm-skills) into .claude/skills/revops-handoffs in your project. Claude Code loads it when a task matches its description.
How do I install Revops Handoffs in Codex?
Run `npx skills add swan-gtm/gtm-skills --skill revops-handoffs -a codex`. Or copy the skill folder (skills/rutger-katz/revops-handoffs in swan-gtm/gtm-skills) into .agents/skills/revops-handoffs in your project. Codex loads it when a task matches its description.
Can I use Revops Handoffs in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add swan-gtm/gtm-skills --skill revops-handoffs -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/revops-handoffs, .gemini/skills/revops-handoffs, .github/skills/revops-handoffs and .opencode/skills/revops-handoffs in your project.
What does Revops Handoffs need to run?
SKILL.md names no scripts, command-line tools or credentials: Revops Handoffs is instructions for the agent only.
Does Revops Handoffs access the network?
SKILL.md names 1 domain. As links in the text: neontriforce.com. This is read from the text; nothing was executed.
Is Revops Handoffs safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Revops Handoffs use?
Revops Handoffs is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Revops Handoffs use?
About 3.7k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 9.4k tokens, read only when the agent opens those files.
What are the alternatives to Revops Handoffs?
Skills that share tags, products or a category with Revops Handoffs: Revops (sickn33/agentic-awesome-skills, 47k stars), Session Handoff Document (thedotmack/claude-mem, 99k stars), Handoff (nexu-io/open-design, 100k stars) and Handoff (alirezarezvani/claude-skills, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Revops Handoffs?
swan-gtm (a GitHub organization) maintains it in swan-gtm/gtm-skills, which has 172 GitHub stars. The repository holds 32 skills in this directory. The repository was last updated on October 8, 2026.
Source: swan-gtm/gtm-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.