Sales-to-CS handoff brief in one pass

Founders and CS leaders at 10–60 person B2B SaaS companies where sales and CS are separate functions and handoff quality directly drives early churn · Assemble in ~10 min; first complete handoff brief in <5 min per closed deal.

GTMEdit flowon X● golden 87

step 1ready

Pull deal data from CRM

close-automation

step 2ready

Extract call intelligence from recordings

ai-sales-intelligence-and-outreach12 alts

step 3ready

Fetch post-call follow-up threads

post-call-followup

step 4connector

Ingest deal documents and contract terms

⚡ bring your own tool

step 5partial

Synthesize CS handoff brief

handoff

step 6ready

Append handoff log entry

handoff-log-update

step 7connector

Deliver brief to CS team

⚡ bring your own tool

Did this recipe work for you?

What you get

▸Structured CS handoff brief (markdown): account overview, stakeholder map, commitments log, onboarding risks, first-30-days guidance
▸Promises-vs-contract diff: what was said on calls vs. what is contractually binding
▸Persistent handoff log entry: transfer timestamp, CS owner, open items, audit trail
▸Delivery confirmation: brief pushed to CS team's working channel or document system

tools: Close CRM (existing subscription) · document storage (Drive/Notion — existing) · delivery channel (Slack/Notion — existing)

tokens: ~$1–3 per deal handoff (call transcripts + synthesis)

≈ $5–20/mo at 10–50 closed deals/month — dominated by call transcript length

What stays yours

· CS lead reviews the brief before the kick-off call and flags any promise-vs-contract gaps that need sales to clarify
· Sales rep confirms the 'what was promised' section is complete and accurate — AI extraction from calls can miss implicit commitments made off-recording
· First onboarding call is still human-led; the brief is the prep material, not a replacement for relationship continuity

✓ Last verified 2026-06-11claude-sonnet-4-6 (subagent, test-mode fixtures)

✓ step 1 · Pull deal data from CRM

✓ step 2 · Extract call intelligence from recordings

✓ step 3 · Fetch post-call follow-up threads

✓ step 4 · Ingest deal documents and contract terms

✓ step 5 · Synthesize CS handoff brief

✓ step 6 · Append handoff log entry

✓ step 7 · Deliver brief to CS team

view sample outputs from this run

step 1 · Pull deal data from CRM

# Deal Record — Close CRM Export

**Deal ID:** CLO-2026-04817
**Deal Name:** Meridian Analytics — DataOps Suite (Enterprise)
**Stage:** Closed Won
**Close Date:** 2026-06-02
**ARR:** $84,000
**Contract Term:** 12 months (annual prepay)
**Pricing Tier:** Enterprise — up to 50 seats
**Payment:** Wire transfer received 2026-06-04

## Account Details
- **Company:** Meridian Analytics, Inc.
- **Industry:** B2B SaaS / Business Intelligence
- **HQ:** Austin, TX
- **Employees:** 210
- **CRM Account ID:** ACC-00914

## Sales Rep
- **Name:** Jordan Patel
- **Email:** jordan.patel@vendorco.com
- **Slack:…

step 2 · Extract call intelligence from recordings

# Call Intelligence Brief — Meridian Analytics

**Source calls analyzed:** 2 (Discovery 2026-03-14, Technical Demo 2026-03-28)
**Total talk time:** ~105 minutes
**Skill applied:** ai-sales-intelligence-and-outreach

---

## Executive Summary
Meridian Analytics bought primarily on pain relief (schema drift + manual pipeline maintenance) and on lineage visualization differentiating us from Fivetran. The CTO (Tom) is a skeptical but satisfied buyer — he accepted SaaS-only and no EU region for now, but these are latent risks if their roadmap accelerates. The power user (Priya) will drive day-to-da…

step 3 · Fetch post-call follow-up threads

# Post-Call Follow-Up Threads — Meridian Analytics

**Source:** Post-call follow-up emails generated after each sales call
**Skill applied:** post-call-followup
**Contacts retrieved from:** contact-list.md

---

## Thread 1: Post-Discovery Follow-Up
**Sent:** 2026-03-14 (same day, ~6pm CT)
**From:** Jordan Patel → Marcus Chen
**Subject:** "Great connecting today — next steps for Meridian"

**Summary of email content:**
- Recapped pain: schema drift costing ~8 eng-hours/week
- Confirmed: SOC 2 Type II available on request, GDPR DPA standard
- Proposed next step: full technical demo with data te…

The problem

When a deal closes, I want an AI to automatically pull deal history, call recordings, and CRM notes and generate a structured CS handoff brief, so that customer success knows exactly what was promised and customers don't churn from onboarding mismatches.

Cybernetic layers

Memorypartial

Deal state and handoff history are written to the handoff log (step 6) — a persistent markdown file. Full CRM memory (ongoing account health, expansion signals) is not covered; that requires a CS platform (Gainsight, Vitally, ChurnZero) or a dedicated context file per account.

Backgroundbyo

Recipe runs on-demand per closed deal. A 'deal closed' CRM webhook triggering the recipe automatically is not a library artifact — wire it via Zapier, Make, or a CRM automation (Close, HubSpot) if you want fully hands-free execution at close.

Harnessready

Claude Code is the runtime. Install ready skills into ~/.claude/skills/ and invoke in sequence. The plugin (step 5) installs as a Claude plugin. Cowork supports the same flow.

Click any step to see what fills it — and the ranked alternatives you can swap in.