# Revops Handoffs

> >

- **Type:** Skill
- **Install:** `agentstack add skill-neon-rutger-b2b-revops-skills-revops-handoffs`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [NEON-Rutger](https://agentstack.voostack.com/s/neon-rutger)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [NEON-Rutger](https://github.com/NEON-Rutger)
- **Source:** https://github.com/NEON-Rutger/B2B-revops-skills/tree/main/revops-handoffs
- **Website:** https://www.neontriforce.com

## Install

```sh
agentstack add skill-neon-rutger-b2b-revops-skills-revops-handoffs
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# 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 the relevant file 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:

```
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 → 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) | €50K ACV): CSM in late-stage calls.
**Clean break** (SMB  €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 → 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 & ABM Loops

### Five-Stage Post-Sale Marketing

1. **Onboarding** — role-based education, setup guides, in-app messaging
2. **Adoption** — feature spotlights, best practices, certifications
3. **Retention** — ROI reports, QBR materials, NPS surveys
4. **Expansion** — usage-based trigger emails, cross-sell content, feature nudges
5. **Advocacy** — case studies, review campaigns (G2, Capterra), advisory boards

### ABM for Existing Customers

Churn prevention ABM (competitor intent signals → executive engagement), cross-sell ABM (content clustering → 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 → Sales | Speed-to-lead, MQL→SQL conversion, unworked rate |  90%, ≥ 4.0/5 |
| Impl → CS | TTFV, go-live rate, onboarding churn | Segment-dependent, > 85%,  40% upsell / > 20% new-DMU, 110–130%+ |

### Leading Indicators of Failure

Rising unworked leads (>10%) → SDR overload/routing failure. MQL rejection rising → ICP misalignment. Time-to-kickoff >14d → sales-CS bottleneck. Declining onboarding completion → capacity/complexity. Shrinking expansion pipeline → 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 → 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. 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 → 40% conversion lift.
- LeanData (2025).  Built by [Neon Triforce](https://neontriforce.com)

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [NEON-Rutger](https://github.com/NEON-Rutger)
- **Source:** [NEON-Rutger/B2B-revops-skills](https://github.com/NEON-Rutger/B2B-revops-skills)
- **License:** MIT
- **Homepage:** https://www.neontriforce.com

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-neon-rutger-b2b-revops-skills-revops-handoffs
- Seller: https://agentstack.voostack.com/s/neon-rutger
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.