Individual skill
revops-handoffs
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.
skills/rutger-katz/revops-handoffs/SKILL.md
Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Instructions only
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 237
- Repository last updated
- Oct 20, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- engineering Derived category
- marketing Derived category
- sales Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 14,986 bytesSKILL.mdcore · 14,986 bytesreferences/ai-tooling-for-revenue-handoffs-extended-vendor-guide.mddoc · 15,015 bytesreferences/expansion-pipeline-architecture.mddoc · 4,889 bytesreferences/handoff-slas-and-benchmarks.mddoc · 5,045 bytesreferences/hubspot-workflow-specifications-for-revenue-handoffs-extended.mddoc · 12,664 bytes
Read excerpt
# 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 dashboards
- `references/expansion-pipeline-architecture.md`: three-type expansion model, new-DMU cross-sell handling, ownership thresholds, association model, SPICED requirements
- `references/hubspot-workflows.md`: pipeline configurations, workflow specs, property catalog, Breeze AI patterns, tier requirements
- `references/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:
