Revenue Handoff Operations: Full Bow-Tie Model

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.

How to use it

Claude Code
  1. Run the line below. It pulls the whole folder into ~/.claude/skills/revops-handoffs.
  2. Describe your job in plain words. Claude Code follows the skill from there.
Claude Code — installs the whole folder, not just SKILL.md
npx degit swan-gtm/gtm-skills/skills/rutger-katz/revops-handoffs#main ~/.claude/skills/revops-handoffs

For one project only, change the path to .claude/skills/revops-handoffs.

Claude (web or desktop app)
  1. On this page open ⋯ → Download .md.
  2. Save it as SKILL.md in a folder, zip the folder, then Customize → Skills → + → Create skill → Upload a skill.
  3. Pick the file and Save. Claude shows the name and description and runs a security scan.
  4. Check the skill is switched on.
  5. Start a new chat and describe your job in plain words. The AI follows the skill from there.
ChatGPT or another app
  1. ChatGPT: make a Project and paste it into Instructions.
  2. Neither? Paste it at the top of a new chat — it works for that chat.
Not working?
  • Check which app you pasted it into — the steps above name the right one.
  • Some skills need the paid tier of Claude or ChatGPT.
Step-by-step guide with screenshots · Ask in the forum

Paste into Claude, ChatGPT or Cursor.

Source of Revenue Handoff Operations: Full Bow-Tie Model

Show the full text246 lines
nametitledescriptioncategory
revops-handoffsDesign revenue handoffsUse 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.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 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 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)
  1. Deal history and origin
  2. Customer goals with measurable success criteria (specific, not assumed)
  3. Full stakeholder map (champion, economic buyer, end users, detractors)
  4. Every commitment the AE made (explicit and implicit)
  5. Known risks and internal politics
  6. Technical requirements (integrations, migration, compliance)
  7. 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
  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 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

1---
2name: "revops-handoffs"
3title: Design revenue handoffs
4description: "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."
5category: RevOps
6---
7 
8# Revenue Handoff Operations: Full Bow-Tie Model
9 
10You 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.
11 
12**Reference files** (read before giving detailed implementation advice):
13- `references/handoff-slas-and-benchmarks.md`: SLA targets, speed-to-lead data, metrics per handoff, leading indicators of failure, measurement dashboards
14- `references/expansion-pipeline-architecture.md`: three-type expansion model, new-DMU cross-sell handling, ownership thresholds, association model, SPICED requirements
15- `references/hubspot-workflows.md`: pipeline configurations, workflow specs, property catalog, Breeze AI patterns, tier requirements
16- `references/ai-tooling.md`: AI handoff document generation, enrichment/scoring tools, predictive models, LLM middleware patterns, GDPR considerations
17 
18## The Five-Node Bow Tie
19 
20Most B2B SaaS orgs have four handoff points. Companies with implementation partners have five:
21 
22```
23Marketing → Sales → Partner/Impl → CS → Sales (expansion)
24 ↑
25 Lifecycle marketing & ABM loops back ←──┘
26```
27 
28Each 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).
29 
30## 1. Marketing to Sales
31 
32The most studied, most frequently broken transition. Speed kills competitors; delay kills deals.
33 
34### Speed-to-Lead (the non-negotiables)
35 
36| Lead Type | Response SLA | Evidence |
37|---|---|---|
38| 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) |
39| Paid ads | < 3 minutes | Highest cost-per-lead, hottest intent |
40| Partner referral | < 30 minutes | Warm but relationship-dependent |
41| Organic inbound | < 10 minutes | Moderate intent |
42| Content / webinar | 3-4 days (nurture first) | Premature outreach damages trust |
43 
44Reality 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).
45 
46### Lead Tiers
47 
48**Hand-raisers**: bypass scoring, route directly to sales. 5-minute SLA.
49**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).
50**PQLs** (hybrid PLG): usage-based triggers. Convert at 15-30%.
51 
52### Context Packet
53 
54Firmographic 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.
55 
56### Marketing-Sales SLA
57 
58Marketing: 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.
59 
60### Routing Models
61 
62Round-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.
63 
64→ For detailed benchmarks and metrics: read `references/handoff-slas-and-benchmarks.md`
65 
66## 2. Sales to Partner/Implementation
67 
68Customer excitement peaks at signature then collapses if nothing happens ("Trough of Disillusionment").
69 
70### Context Packet (7 elements)
71 
721. Deal history and origin
732. Customer goals with **measurable** success criteria (specific, not assumed)
743. Full stakeholder map (champion, economic buyer, end users, detractors)
754. Every commitment the AE made (explicit and implicit)
765. Known risks and internal politics
776. Technical requirements (integrations, migration, compliance)
787. Customer timeline including critical events from SPICED
79 
80### SLAs
81 
82| Milestone | Target |
83|---|---|
84| Internal AE to Impl briefing | 24-48 hours post-signature |
85| Customer introduction email | Within first week |
86| Kickoff scheduled | 48-72 hours post-signing |
87| First implementation meeting | 2-7 days (2 best, 7 standard) |
88 
89### Partner-Specific
90 
91Partner 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.
92 
93### Sales Involvement Model
94 
95**Warm overlay** (default): AE at kickoff, introductions, steps back, CC'd 2 weeks.
96**Pre-sale CS** (enterprise >€50K ACV): CSM in late-stage calls.
97**Clean break** (SMB <€10K): automated handoff.
98 
99## 3. Implementation to CS
100 
101Least standardised, most consequential. Early value realisation (within first 30 days) correlates with higher CLV.
102 
103### Context Packet
104 
105Scope/configuration details, training completion status and gaps, outstanding issues with workarounds, customer sentiment during implementation, updated stakeholder map, initial adoption metrics, lessons learned.
106 
107### Go-Live Readiness (5 conditions, all true)
108 
109Tasks work end-to-end. People trained. Data migrated. Support plan in place. Rollback plan exists.
110 
111### Health Scoring Starts Here
112 
113Don't wait for steady-state. Track: milestone completion rate, stakeholder engagement, customer responsiveness, admin login frequency, training attendance.
114 
115## 4. CS to Sales (Expansion)
116 
117Expansion 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%.
118 
119### Three Expansion Types: Critical
120 
121| Type | DMU | Pipeline | Discovery |
122|---|---|---|---|
123| **Upsell** | Same champion, same budget | Short: Identified → Proposal → Won | SPICED refresh |
124| **Cross-sell (warm)** | Partial overlap, champion introduces | Standard: Identified → Needs Assessment → Proposal → Negotiation → Won | Partial new SPICED |
125| **Cross-sell (new DMU)** | Completely new buying group | Full discovery stages added | Full new SPICED mandatory |
126 
127A 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.
128 
129**Litmus test**: "Would losing the contract in BU-A affect closing in BU-B?" If no → new logo with customer referral source.
130 
131### Ownership
132 
133| ACV | Owner | CS role |
134|---|---|---|
135| <€10K | CSM closes | End-to-end |
136| €10K-50K | AM/AE + CSM | Context, stays in meetings |
137| >€50K | AE full cycle | Introduces, advisory |
138 
139Define thresholds in governance. Ambiguity = nobody closes.
140 
141### Expansion Signals
142 
143Usage: 80%+ seat limits, new feature adoption, DAU increasing.
144Relationship: champion promoted, new stakeholder, positive NPS.
145Commercial: org headcount growth, new budget cycle, cross-functional interest.
146Outcomes: value ahead of schedule, ROI exceeded, new use cases.
147 
148### CS to Sales Handback Process
149 
150CSM flags signal → workflow creates deal → assigns to AE → CSM prepares brief (health, usage, stakeholders, whitespace) → joint meeting → clear rules of engagement from there.
151 
152→ For new-DMU detail, association model, and reporting payoff: read `references/expansion-pipeline-architecture.md`
153 
154## 5. Lifecycle Marketing and ABM Loops
155 
156### Five-Stage Post-Sale Marketing
157 
1581. **Onboarding**: role-based education, setup guides, in-app messaging
1592. **Adoption**: feature spotlights, best practices, certifications
1603. **Retention**: ROI reports, QBR materials, NPS surveys
1614. **Expansion**: usage-based trigger emails, cross-sell content, feature nudges
1625. **Advocacy**: case studies, review campaigns (G2, Capterra), advisory boards
163 
164### ABM for Existing Customers
165 
166Churn 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).
167 
168## 6. AI-Enabled Handoffs
169 
170Read `references/ai-tooling.md` for the full stack. Summary:
171 
172**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.
173 
174**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.
175 
176**Predictive**: Pendo Predict, ChurnZero for churn/expansion. Best models hit 85-92% accuracy 60-90 days pre-churn.
177 
178**GDPR non-negotiables**: data residency, model training opt-out, consent management, EU Data Act switching requirements.
179 
180## 7. HubSpot Implementation
181 
182Read `references/hubspot-workflows.md` for detailed specs. Architecture summary:
183 
184**Three pipelines**: New Business, Expansion (with `expansion_type` driving conditional stages), Renewals (auto-created on Closed Won).
185 
186**Deal-to-deal associations** (Professional+) link expansion → original deal for lineage and Δt7 measurement.
187 
188**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).
189 
190**Speed-to-lead tracking**: custom `first_connection_date` property + calculated `speed_to_lead_hours`. HubSpot lacks this natively.
191 
192## Measurement Framework
193 
194### Metrics by Handoff
195 
196| Handoff | Key Metrics | Targets |
197|---|---|---|
198| Mktg to Sales | Speed-to-lead, MQL-to-SQL conversion, unworked rate | <5 min (hand-raisers), 25-35% conversion, <5% unworked |
199| Sales to Impl | Time-to-kickoff, info completeness, quality score | <7 days, >90%, ≥4.0/5 |
200| Impl to CS | TTFV, go-live rate, onboarding churn | Segment-dependent, >85%, <3% |
201| CS to Sales | Expansion pipeline from CS, handoff time, expansion win rate, NRR | Growing QoQ, <48h, >40% upsell / >20% new-DMU, 110-130%+ |
202 
203### Leading Indicators of Failure
204 
205Rising 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.
206 
207### Quality Scorecard
208 
209Receiving team rates each handoff 1-5 across: information completeness, promise alignment, customer sentiment continuity, context transfer quality, stakeholder mapping. Review weekly in operating cadence.
210 
211## How to Use This Skill
212 
213**"Leads fall through the cracks"**: Speed-to-lead + routing rules. Read benchmarks reference.
214**"CS never knows what sales promised"**: SPICED-to-handoff pipeline. Gate Closed Won on completeness. Read AI tooling reference.
215**"We lose momentum after signature"**: Sales to Impl SLA. Auto-trigger on Closed Won. Read workflows reference.
216**"Nobody owns expansion"**: Ownership model + expansion pipeline. Read expansion architecture reference.
217**"Cross-sell has a different buying group"**: Three-type model. Read expansion architecture reference.
218**"How do we involve the partner?"**: Partner context packet + AE-at-kickoff + hypercare bridge.
219**"Design handoffs from scratch"**: Audit each point against SLA framework. Instrument leading indicators. Start with biggest revenue leak.
220 
221---
222 
223## References
224 
225- Dr. James Oldroyd, MIT Sloan (2007). Lead Response Management study. 15,000+ leads across 6 companies. Published via InsideSales.com.
226- Velocify (circa 2012). Responding within 1 minute increases conversion by 391%.
227- HBR (2011). "The Short Life of Online Sales Leads." 2,241 companies tested. Average B2B response: 42 hours. 23% never responded.
228- Workato (2024). Speed-to-lead study: 114 B2B companies. Only 1 sent personalised email within 5 min. Average personalised response: 11h 54m.
229- Chili Piper (2025). 2025 Benchmark Report: ~4M form submissions. Instant booking converts 66.7% vs ~30% industry average.
230- Justin Norris, RevOps FM (2025). "A Complete Guide to Speed-to-Lead." 10-min hand-raiser SLA to 40% conversion lift.
231- Optifai Pipeline Study (Q2 2025-Q1 2026, 939 companies). <5 min response = 32% close rate, 2.6x higher than 24+ hours.
232- Pacific Crest / David Skok & Matrix Partners (2016). SaaS Survey: expansion costs $0.27 per $1 ACV vs $1.16 new logos.
233- OpenView Partners (2023). SaaS Benchmarks (700+ companies): 50-60% of new ARR from expansion (best-in-class).
234- KeyBanc (2024). Expansion = 52% of new ARR.
235- Rework (2025). "Deal Handoff Protocol: Standardizing Post-Close Transitions." 45% implementation improvement, 35-40% churn reduction.
236- Forrester/SiriusDecisions. Demand Waterfall: MQL→SQL 39-40% with scoring vs 15-21% without.
237 
238## What good looks like
239 
240- Every bow-tie transition has a named owner, an SLA, and a context packet the receiving team actually reads.
241- Speed-to-lead is measured against the SLA and breaches alert someone accountable.
242- After signature, CS can see what sales promised without asking.
243- Leak indicators such as unworked leads and silent post-sale accounts sit on a dashboard, not in retrospectives.
244 
245> Built by [Neon Triforce](https://neontriforce.com)
246 

Discussion

Alternatives

Also in Process docsSee all 58 in Operations →
On call handoff patternsMaster on-call shift handoffs with context transfer, escalation procedures, and documentation. Use this skill when transitioning on-call responsibilities between engineers and ensuring the incoming responder has full situational awareness, when writing a shift summary that captures active incidents, ongoing investigations, and recent changes, when handing off mid-incident so a fresh engineer can take over the incident commander role without losing context, when onboarding a new engineer to the on-call rotation for the first time, or when auditing and improving the quality of existing handoff processes across teams.Infrastructure & ops · MITHandoffCompact the current conversation into a handoff document for another agent to pick up. Save to a user-configured location (OS temp, home folder, or per-project .handoff/), redact secrets before write, suggest skills for the next session, and auto-load the latest handoff on the next SessionStart. First-run setup asks where to save so the project folder never gets cluttered. Use when the user says 'hand this off', 'handoff doc', 'summarize this for a new session', 'compact this conversation', 'I'm ending this session', 'pick this up later', or any variation signaling intent to pass work to a fresh agent. Also trigger on implicit signals: the user announcing they're switching machines, ending the day mid-task, or context is growing long without a natural stopping point.Business & ops · MITFinancial Due Diligence SkillGenerate a financial due diligence checklist and analysis framework for any investment, acquisition, or partnership. Use when asked for a due diligence checklist, M&A financial review, investment analysis framework, or vendor financial assessment. Produces a document request list, key analytical questions, red flags checklist, and a summarised financial health assessment.Business & ops · MITOffsite Planner SkillPlan a team offsite that earns its cost — the purpose split (connection vs. decisions vs. planning, weighted on purpose), the agenda that alternates work and air, the logistics runbook, and the follow-through that makes Monday different from before. Use when asked plan our team offsite, design two days for the team, make this offsite not a waste, or what do we actually do at the offsite. Produces the purpose weighting, the day designs, the logistics checklist, and the commitments-capture that survives re-entry.Business & ops · MIT