Customer Success Handover Doc

Template Overview

The transition from closed-won sales deal to active customer success represents the most vulnerable moment in an enterprise relationship. The Customer Success Handover Doc transfers deep stakeholder context, operational requirements, implementation timelines, and executive commitments from the account executive to the customer success team.

Markdown Template Structure

Copy the block below or click Download .md File to add this template directly to your personal vault:

---
title: "Account Handover: [Client Organization Name]"
date: [YYYY-MM-DD]
account_executive: "[[Account Executive]]"
customer_success_manager: "[[Customer Success Manager]]"
client_name: "[Client Organization Name]"
tier: "Enterprise Tier (450 Seats)"
contract_arr: "$64,800"
kickoff_date: "[YYYY-MM-DD]"
tags: [customer-success, account-handover, onboarding, enterprise]
---

# Customer Success Handover — [Client Organization Name]

## 1. Commercial Baseline & Contract Scope
- **Contract Signed Date:** [YYYY-MM-DD].
- **Contract Terms:** 2-Year Committed Agreement, 450 macOS user seats, priority technical support.
- **Primary Business Driver:** CISO mandate to replace cloud meeting bots with on-device local transcription before audit deadline.

## 2. Key Stakeholder Directory & Decision Hierarchy
| Name | Title / Role | Stance & Orientation | Preferred Communication |
|---|---|---|---|
| **[[Executive Buyer]]** | Chief Information Officer | Strong Sponsor; focused on ROI & audit reports | Monthly executive email update |
| **[[Technical Lead]]** | Mac Fleet Admin (Jamf) | Pragmatic; concerned with silent MDM installer deployment | Slack Connect channel |
| **[[Day-to-Day Champion]]**| Head of Product Strategy | Enthusiastic power user; loves Markdown vault integration | Weekly onboarding check-in |

## 3. Technical Implementation Prerequisites
- [x] Client IT confirmed Jamf Pro management across 100% of employee macOS laptops.
- [x] Custom mobileconfig profile generated granting ScreenCaptureKit permissions.
- [ ] Staging fleet pilot with 25 lead engineers scheduled for next Tuesday.

## 4. Key Promises & Agreed Expectations
- **Promise 1:** Guaranteed sub-24h support SLA for technical questions during onboarding.
- **Promise 2:** Dedicated custom Markdown template package created for their research division.

## 5. Transition Action Items
- [ ] [[Account Executive]] Introduce CSM to client executive sponsors via warm introductory email.
- [ ] [[CSM]] Schedule official Client Onboarding Kickoff call for next Thursday.
- [ ] [[CSM]] Set up dedicated Slack Connect channel with client Mac fleet admins.

Filled Real-World Example

Here is a realistic example demonstrating how this template captures actual deliberations:

---
title: "Handover: BioGen Research Labs"
date: 2026-10-06
account_executive: "[[Rachel Adams]]"
customer_success_manager: "[[Priya Patel]]"
client_name: "BioGen Research Labs"
tags: [customer-success, account-handover]
---

# Handover: BioGen Research Labs

## 1. Account Summary
Rachel Adams completed the formal account transition to Priya Patel for BioGen Labs (300 seats). All contract documents executed cleanly. Primary onboarding goal is distributing the application via Jamf Pro to clinical researchers by month end.

When to Use and When to Avoid

When to Use

• Use immediately upon closing an enterprise or mid-market software contract.
• Use during formal account handover meetings between Sales and Customer Success.
• Use to align onboarding milestones, promised deliverables, and stakeholder maps.

When to Avoid

• Avoid using for pre-close sales pipeline opportunities.
• Avoid using for annual renewal negotiations with tenured accounts.

On-Device AI Integration

Summarize your recording in Oyma with this local instruction:

Analyze the sales-to-customer-success handover recording:
1. Extract client business objectives, signed contract details, and seat counts.
2. Outline key stakeholder personas, technical deployment hurdles, and sales promises made.
3. List customer onboarding milestones and transition action items into clean Markdown.

Your data remains securely on your Mac with zero cloud exposure.