Best for
- Sales teams that need faster and better post-demo follow-up
- AEs managing multiple active opportunities
- Sales enablement teams trying to standardize demo follow-up quality
Convert one demo recording into a follow-up email, stakeholder recap, objections list, next-step notes, and buyer-specific value summary.
A complete post-demo follow-up kit that helps reps move faster while keeping the buyer's priorities, objections, and next steps clear.
Quick view
Check the audience, core tools, and access before you start the detailed steps.
Best for
Core tools
5 tools used across the workflow.
Access
Preview the open steps, then unlock the remaining implementation details and prompts.
Why this works
Demo follow-up is often rushed, generic, or dependent on a rep's memory. The call recording contains the buyer's actual priorities, objections, language, and next steps. This workflow converts that raw conversation into a structured follow-up kit that improves speed, consistency, and handoff quality.
Expected results
Time saved
1-2 hours per opportunity
AI-assisted transcript analysis reduces manual note review, recap writing, and first-draft follow-up work.
Follow-up quality
Buyer-specific recap
The workflow uses the buyer's stated priorities and objections rather than a generic demo thank-you template.
CRM hygiene
Cleaner opportunity notes
The process turns call insights into structured opportunity updates instead of leaving them buried in transcripts.
Enablement value
Reusable examples
Strong follow-up kits can be tagged and reused for coaching, objection handling, and future sales playbooks.
Step-by-step workflow
The first 3 steps are open. Pro unlocks the remaining steps, copy-paste prompts, pro tips, tool-by-tool setup guidance, and implementation details.
20-30 min
20-30 min
Scope: In Gong, open the most recent completed demo for the opportunity and confirm the recording date, meeting title, attendees, transcript language, and recording completeness before exporting anything. Export or copy the full transcript, Gong summary, questions, action items, speaker labels, and any bookmarked moments into a working Google Doc. In HubSpot, open the matching opportunity and capture the company, opportunity ID, stage, amount, close date, owner, personas involved, use case, current next step, prior activity, and existing risks.
Set up: Add links back to the Gong recording and HubSpot record so reviewers can return to the source without searching. Reconcile attendee names between Gong and HubSpot, flag unidentified speakers, and note any transcript gaps, side conversations, or audio-quality issues that could distort interpretation.
Action: Keep the raw transcript and CRM snapshot in a locked Source Packet section and put later analysis in separate sections so source evidence is never overwritten.
Output: Save the document using a consistent opportunity naming convention and record the extraction date, preparer, and source-system timestamps at the top.
A traceable demo source packet with the complete transcript, CRM snapshot, source links, attendee reconciliation, and documented data gaps.
Preserve the raw source packet unchanged. Reps and managers should be able to verify any follow-up claim against the original call and opportunity record.
25-35 min
25-35 min
QA: Review the source packet and identify the parts of the conversation where buyers describe goals, pain, success criteria, timing, stakeholders, constraints, and decision process.
Set up: Open Claude, start a new opportunity-analysis chat, and paste the prompt below into the main chat composer. Include the full transcript, CRM context, attendee-role map, known opportunity history, and transcript-quality notes as source inputs.
Action: Ask Claude to separate explicit buyer statements from seller statements, inferred context, and unresolved questions, while preserving timestamps or transcript references for important evidence. Copy the structured analysis into a Buyer Priorities section in Google Docs and save the Claude conversation link beside it.
QA: Manually verify every quoted phrase, deadline, stakeholder role, and commercial assumption against the transcript and CRM. Mark uncertain items as Needs Confirmation and do not allow inferred priorities to become buyer-facing language until the AE confirms them.
A verified buyer-priority and decision-context summary with evidence, confidence, reusable language, and open questions.
25-35 min
25-35 min
QA: Review the transcript for explicit objections, hesitation, repeated questions, budget language, technical concerns, competitor references, approval blockers, and moments where the buyer changes tone or avoids commitment. Open Claude, continue in the opportunity-analysis chat or start a focused objection-analysis chat, and paste the prompt below into the main chat composer.
Action: Include the transcript, verified buyer-priority summary, product or offer context, known competitors, approved proof library, and claims that sales may not make as source inputs.
Next action: Ask Claude to distinguish direct objections from implied concerns and to recommend the smallest useful proof, answer, or next action for each item. Copy the resulting objection-and-proof map into Google Docs and save the Claude conversation link or output reference with the opportunity kit.
Approval: Verify that every objection has transcript evidence and that every recommended proof asset actually exists, is current, and is approved for the buyer. Escalate legal, security, pricing, integration, or roadmap questions to the correct owner rather than allowing the AE to improvise unsupported answers.
A transcript-backed objection and proof map with severity, evidence, owner, approved response, and unresolved follow-up needs.
Pro workflow preview
Previewing 3 of 7 steps
Get the remaining 4 steps, copy-paste prompts, pro tips, tool-by-tool setup guidance, and ongoing workflow and prompt releases.
$9/month
Keep an explicit column for buyer-stated versus inferred. That one distinction prevents polished AI summaries from quietly turning assumptions into sales facts.
Extract the buyer priorities and decision context from this demo call.
Source inputs:
- Full call transcript with speaker labels and timestamps: {{call_transcript}}
- HubSpot opportunity context: {{crm_context}}
- Attendee and role map: {{attendee_role_map}}
- Known opportunity history: {{opportunity_history}}
- Transcript gaps or quality notes: {{transcript_quality_notes}}
Return:
1. Buyer-stated goals
2. Current pains and operational consequences
3. Success criteria and desired outcomes
4. Timeline and triggering events
5. Decision process and approval path
6. Stakeholders, roles, and influence
7. Constraints, risks, and dependencies
8. Exact buyer language worth reusing, with transcript references
9. Seller claims or assumptions that are not buyer-confirmed
10. Open questions and items requiring AE confirmation
Clearly label each item as explicit buyer statement, supported inference, or unknown. Do not invent stakeholders, dates, priorities, or commercial intent.Separate proof that can be sent immediately from proof that requires an SME or executive response. That keeps the follow-up fast without encouraging unsupported improvisation.
Analyze this demo call for objections, uncertainty, and missing proof.
Source inputs:
- Full call transcript with timestamps: {{call_transcript}}
- Verified buyer-priority summary: {{buyer_priority_summary}}
- Product or offer context: {{product_or_offer}}
- Known competitors and differentiators: {{known_competitors}}
- Approved proof and asset library: {{approved_proof_library}}
- Prohibited or unapproved claims: {{claim_constraints}}
For each item, return:
1. Objection or concern
2. Explicit, implied, or unresolved-question classification
3. Transcript evidence or timestamp
4. Business impact if unresolved
5. Recommended proof, asset, answer, or next action
6. Response owner
7. Customer-facing language suggestion
8. Claims that require verification
9. Severity and urgency
10. Confidence level
Do not invent objections or proof. State when the transcript evidence is weak or when the correct response requires a human specialist.Related workflows
Continue with workflows that share a similar GTM motion, category, or tool stack.
Create a post-call follow-up package with recap email, mutual action plan, open questions, CRM notes, and buyer-specific next steps.
A living objection handling playbook based on real sales conversations, organized by objection type, buyer persona, deal stage, and response strategy.
A system for generating tailored one-pagers for active deals based on buyer pain, industry context, deal stage, and competitive situation.