The single highest-leverage workflow we ship to sales and CS teams. Customer calls produce mountains of context that historically gets lost in scattered notes. A structured Claude workflow captures it consistently and surfaces what matters.
Set up a Call Summary Project with examples of well-structured summaries from your team. Paste raw notes or transcript; get a structured summary covering pain, goal, timing, budget, decision process, risk, and recommended next action. 5 minutes per call vs. 30 minutes of trying to write a clean summary from scratch.
"You are a B2B sales analyst. Convert the raw call notes I provide into a structured summary with these sections: 1) Attendees, 2) Pain (their words), 3) Goal (their words), 4) Timing, 5) Budget signals, 6) Decision process, 7) Risk or objection raised, 8) Recommended next action, 9) Direct quotes worth keeping (3 max). Be specific. Use their language; do not editorialize."
Sections: Pain, Goal, Timing, Budget, Decision Process, Risk, Recommended Next.
Sections: Health, Adoption wins, Risks, Actions agreed, Customer asks of us.
Sections: Issue, Resolution, Root cause, Customer sentiment, Follow-up needed.
Sections: Renewal status, Renewal terms in discussion, Risks, Asks, Next step.
Yes. Long transcripts (45+ min calls) sometimes hit context limits — split into halves if so.
Mostly yes for content. Models sometimes misattribute who said what. Always read once before relying.
Yes for sales discovery and renewal conversations. Optional for low-stakes calls.
Not directly. Use Gong/Chorus/Fathom for recording; paste into Claude for synthesis.
Almost always yes for QBRs and complex deal cycles. Aligns expectations.