Information Silos Between Sales and Customer Success Solved: Claude Prompts for SaaS Revenue Operations Managers (Advanced)

You are an expert revenue operations manager with 13 years of experience building sales-to-customer-success handoff systems for B2B SaaS companies scaling from $5M to $50M ARR. Help me write a process documentation guide so I can eliminate repeated meetings on the same topic and stop churn that starts at the moment a deal closes and a customer is handed to a team that knows nothing about why they bought. My situation: - Company ARR and growth stage: [e.g., "$18M ARR, Series B, growing 80% year-over-year — customer success team doubled in six months, institutional memory has not scaled with headcount"] - Current handoff process and its failure: [e.g., "AE sends a Slack message to the CSM with a link to the Salesforce opportunity — CSM has to dig through 40 fields to find why the customer bought, what was promised, and what the customer is afraid of"] - Information most commonly lost in the handoff: [e.g., "the specific business pain the customer articulated in discovery, the informal commitments made by the AE in the final negotiation, the executive sponsor's personal success metric"] - Churn pattern tied to the handoff failure: [e.g., "18% of churned customers in the last 12 months cited 'felt like we had to start over with the new team' as a reason in exit interviews"] - Tools in the current stack: [e.g., "Salesforce for CRM, Gainsight for CS health scoring, Notion for team documentation, Slack for internal communication"] - Team dynamics creating friction: [e.g., "AEs are compensated on closed ARR — they disengage after signature. CSMs are compensated on net revenue retention — they inherit risk the AE created but was not held accountable for"] - Executive priority: [e.g., "CRO has made improving net revenue retention from 108% to 115% the Q3 company priority — RevOps owns the handoff redesign"] Deliver: 1. A sales-to-CS handoff document template with nine fields — customer business pain in the customer's own words, success metric the executive sponsor stated, informal commitments made during negotiation, competitors evaluated and why they lost, champion name and political context, risk factors identified in the sales cycle, agreed implementation timeline, and the one thing that would make this customer churn in 90 days 2. A Salesforce handoff object configuration brief — specifies which of the nine fields become required Salesforce fields before a deal can be marked Closed Won, which fields sync to Gainsight automatically, and which require manual CSM review within 48 hours of handoff 3. A kickoff call preparation protocol for the CSM — a 30-minute internal session between the AE and CSM held within 24 hours of deal close, structured around four questions that cannot be answered by reading the CRM record 4. A handoff quality scoring rubric — a five-point scale applied by the CSM within one week of the kickoff call, rating the completeness and accuracy of the handoff document across four dimensions: pain documented, commitments clear, risk flagged, timeline agreed 5. A compensation alignment proposal for the CRO — a one-page brief recommending that AE variable compensation include a 90-day customer health score component, with the financial model showing the impact on AE OTE at current close rates and the projected NRR improvement 6. A process documentation guide for the full sales-to-CS handoff workflow — a step-by-step document covering the eight stages from deal verbal commit to 30-day customer health check, with the owner, the tool, the output, and the failure mode for each stage 7. A Gainsight health score configuration brief — recommends which signals to weight in the 0–90 day health score (product adoption, executive engagement, support ticket volume, NPS response) specifically for customers in their first quarter post-handoff 8. A monthly RevOps handoff review template — a 45-minute meeting held the first Monday of each month that reviews handoff quality scores, CSMs with the lowest-scoring handoffs from the previous month, and one process improvement to implement before the next review **Write every output assuming it will be reviewed by a CRO who has seen twelve RevOps process proposals fail in three companies — every framework must be specific enough to implement in the current quarter, measurable within 90 days, and defensible when presented to the board as a churn reduction initiative.**