Turn a demo call into a complete sales follow-up kit

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. 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. 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. Save the document using a consistent opportunity naming convention and record the extraction date, preparer, and source-system timestamps at the top.

Review the source packet and identify the parts of the conversation where buyers describe goals, pain, success criteria, timing, stakeholders, constraints, and decision process. 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. 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. 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.

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.

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. 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. 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. 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.

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.

Select the buyer’s highest-priority outcome, the agreed next step, one concern to address, and one approved resource before drafting the email. Open Claude, start a new buyer-facing drafting chat, and paste the prompt below into the main chat composer. Include the verified buyer-priority summary, objection-and-proof map, attendee context, agreed next step, approved resource, AE voice, and prohibited claims as source inputs. Ask Claude to draft a concise email that starts with the buyer’s priority, confirms commitments and owners, addresses one important concern, and gives the recipient one easy next action. Copy the draft into Apollo or the AE’s email composer and save the approved version in the Google Docs follow-up kit with reviewer, date, and version. The AE must verify names, dates, commitments, resource access, tone, and every statement attributed to the buyer before sending. Remove extra attachments, generic gratitude, invented urgency, and any language that makes the email sound like an automated transcript summary.

Write a concise post-demo follow-up email for this opportunity.

Source inputs:
- Verified buyer priorities and language: {{buyer_priorities}}
- Objection and proof map: {{objection_proof_map}}
- Attendee names and roles: {{attendee_context}}
- Agreed next step, owner, and date: {{next_step}}
- One approved resource or proof asset: {{resource_link}}
- AE voice and relationship context: {{ae_voice}}
- Prohibited or unverified claims: {{claim_constraints}}

Requirements:
1. 120-180 words
2. Start with the buyer’s stated priority, not a generic thank-you
3. Recap only the most important agreed points
4. Address one key concern with approved proof
5. Confirm the next step, owner, and timing
6. Include one useful resource
7. End with one clear action
8. Flag any detail the AE must verify before sending

Do not invent commitments, urgency, outcomes, or buyer language. Keep the tone specific, helpful, and human.

Decide which internal audiences need the recap, such as the AE, sales manager, solutions consultant, CSM, executive sponsor, or legal and security owners. Open Claude, start a new internal-recap chat, and paste the prompt below into the main chat composer. Include the verified priority summary, objection-and-proof map, CRM context, stakeholder map, seller commitments, open questions, and desired next step as source inputs. Ask Claude to produce a concise internal recap that states the opportunity status, buyer priorities, stakeholder dynamics, risks, required proof, owner actions, and CRM updates without softening bad news. Copy the recap into the Google Docs kit and save the approved version in the appropriate internal channel or opportunity workspace. Verify that risk levels, owners, deadlines, and stakeholder roles match the call and that sensitive internal judgments are not copied into buyer-facing materials. Require each named owner to accept or correct their action before the recap is treated as final.

Create an internal opportunity recap from this demo call.

Source inputs:
- Verified buyer-priority summary: {{buyer_priority_summary}}
- Objection and proof map: {{objection_proof_map}}
- HubSpot opportunity context: {{crm_context}}
- Stakeholder and influence map: {{stakeholder_map}}
- Seller commitments made on the call: {{seller_commitments}}
- Open questions and unresolved evidence: {{open_questions}}
- Agreed next step and desired deal movement: {{next_step}}

Return:
1. Opportunity summary
2. Buyer priorities and success criteria
3. Stakeholders, roles, and influence
4. Decision process and timing
5. Main objections and missing proof
6. Risk level with evidence
7. Seller commitments
8. Recommended owner actions with dates
9. CRM fields and notes to update
10. Items that remain uncertain or require confirmation

Write for the internal account team. Preserve uncertainty, do not hide risk, and do not invent buyer intent.

Open the HubSpot opportunity and compare the existing record with the verified follow-up kit before changing any fields. Update structured fields for next step, next-step date, deal stage, stakeholder roles, primary use case, objection category, risk level, competitor, and follow-up status where those properties exist. Add a concise note that links to the Google Docs kit and summarizes the verified buyer priorities, agreed commitments, unresolved questions, and owner actions. Do not overwrite historical notes, original source fields, or seller-entered context that remains relevant; append corrections with dates and authorship instead. Create tasks for each owner with a due date and attach the correct proof asset or internal reference. Reconcile the CRM stage and close date with the actual decision process rather than leaving optimistic defaults that contradict the call. Run a final QA check for missing owners, stale next steps, unsupported stage movement, duplicate tasks, and buyer-sensitive internal language in customer-visible fields.

Assemble the final buyer email, internal recap, buyer-priority summary, objection map, proof assets, CRM link, and source packet into one clearly indexed Google Docs kit. Apply consistent tags for use case, industry, persona, deal stage, objection type, competitor, proof asset, and outcome so enablement can find comparable examples later. Remove or redact customer-confidential information before placing any version in a shared coaching or playbook library. In HubSpot, link the opportunity-specific kit to the record and record whether the example is Private to Account Team, Approved for Coaching, or Approved for Broad Reuse. Ask the sales manager or enablement owner to rate the kit for accuracy, specificity, buyer language, objection handling, next-step clarity, and CRM completeness. Save only approved examples to the reusable library and keep the original opportunity version access-controlled. Review reusable kits quarterly to remove outdated proof, retired messaging, inaccurate product details, or examples that no longer meet current standards.