HANDOVER SUMMARY PROMPT — Polymorph ====================================== This prompt takes all meeting transcripts from a completed sales process — discovery calls, pitch meetings, follow-up conversations — and produces a structured handover document for the delivery team. The output gives delivery everything they need to hit the ground running: what was discussed, what was agreed, what the client expects, and what to watch out for. No context gets lost between sales and delivery. HOW TO USE ---------- 1. Copy the full prompt below (everything inside the START/END markers) 2. Paste it into your LLM of choice (Claude, ChatGPT, etc.) 3. Attach or paste all meeting transcripts — discovery, pitch, follow-up calls, and any other conversations from the sales process 4. Optionally add your own notes or context not captured in transcripts 5. Review the output, fill in gaps, and share with the delivery team before onboarding kicks off ---START PROMPT--- You are a senior sales operations specialist. Your job is to analyze meeting transcripts from a completed sales process and produce a clean, structured handover document that gives the delivery team everything they need to onboard and serve this client effectively. I will provide you with transcripts from all meetings in this sales process (discovery calls, pitch/proposal meetings, follow-up conversations, and any other discussions). There may also be additional notes or context I'll include separately. Analyze every transcript carefully. Extract specific details, exact language, and concrete commitments. Do not summarize vaguely — be precise and specific throughout. Produce the handover document using the following structure: --- # Client Handover Summary ## 1. Client Overview - **Company name:** - **Industry / sector:** - **Company size:** (team size, revenue if mentioned, stage) - **Key contacts:** (list each person with their name, role/title, and involvement level — e.g. decision-maker, influencer, day-to-day contact) - **How they found us:** (referral, inbound, outbound, event, etc.) - **Any relevant background:** (funding stage, recent changes, market position) ## 2. Core Growth Problem Describe the primary problem the client needs solved. Use their exact words wherever possible. Format as: - **In their words:** "[exact quotes from transcripts]" - **Summary:** A 2-3 sentence distillation of the core problem ## 3. Trigger & Urgency What triggered them to seek help now? - **Trigger event:** (what specifically happened or changed) - **Commercial driver:** (the business reason this is urgent) - **Timeline pressure:** (any hard deadlines or time-sensitive factors) ## 4. Personal Frustration Beyond the commercial problem, what is personally frustrating or draining for the key decision-maker? Use their exact language. - **What's draining them:** "[exact quotes]" - **Why it matters:** How this connects to the decision to engage us ## 5. Stakeholders & Decision Path - **Final decision-maker:** (name + role) - **Key influencers:** (name + role + their stance) - **Internal champions:** (who advocated for us internally) - **Decision process:** (committee, single decision-maker, procurement, etc.) - **Other stakeholders delivery should know about:** ## 6. What They've Already Tried Previous attempts to solve this problem. Critical context so delivery doesn't repeat failed approaches. For each previous attempt: - What they tried - When (roughly) - What worked - What didn't work - Why it failed or was abandoned - Their sentiment about it ## 7. Success Criteria What does the client consider a win? - **90-day goals:** - **12-month goals:** - **Specific metrics or numbers:** - **Qualitative success markers:** - **What would make this a clear, unambiguous win:** ## 8. Agreed Solution & Scope What was proposed and agreed upon. - **Service / engagement type:** (e.g. paid concept design, fixed build phase, retainer — be specific) - **Specific deliverables and activities included:** - [list each one] - **Explicitly excluded or out of scope:** - [list anything discussed but ruled out] - **Any scope nuances or conditions:** ## 9. Key Outputs & Deliverables | # | Deliverable | Details / Notes | |---|------------|----------------| | 1 | | | | 2 | | | | 3 | | | ## 10. Investment & Commercial Terms - **Total price agreed:** - **Pricing structure:** (phase fee, milestone billing, retainer, T&M — as sold) - **Payment terms:** - **Contract length / commitment:** - **Special conditions:** (discounts, trades, deferred payments, etc.) - **What was agreed verbally but may not be in the contract:** ## 11. Timeline & Expectations - **Engagement start date:** - **Onboarding period:** - **Key milestones:** - Week 1: ... - Week 2-4: ... - Month 2-3: ... - **Client's expectations on communication:** - **First deliverable expected by:** ## 12. Risks & Watch-Outs - **Client sensitivities:** (topics to handle carefully, past bad experiences) - **Internal politics:** (competing priorities, skeptical stakeholders) - **Scope creep risks:** (areas where the client may push for more than agreed) - **Execution risks:** (dependencies on client, access issues, resource constraints) - **Relationship notes:** (communication preferences, trust builders/breakers) ## 13. Onboarding Actions Immediate next steps for the first week: - **Access needed:** (tools, platforms, accounts, data) - **Materials to request from client:** (brand guidelines, existing content, analytics) - **Meetings to book:** (kickoff, team intros, stakeholder alignment) - **Internal actions:** (team briefing, resource allocation, project setup) - **First communication to client:** (what to send, when, from whom) --- RULES 1. Use the client's exact language wherever possible. Quote them directly. 2. Be specific, not vague. "They want to grow" is useless. "They want to produce 20+ social assets per month within 90 days" is useful. 3. Flag ambiguity: "⚠️ UNCLEAR — [describe what's ambiguous and why]" 4. Mark gaps: "❌ NOT DISCUSSED — [topic] was not covered. Address during onboarding." 5. Note contradictions: "⚠️ CONTRADICTION — In the discovery they said [X], but in the pitch they said [Y]." 6. Format as clean markdown with headers, bullet points, and tables. 7. Keep it concise but thorough. Readable in 10 minutes. 8. Separate facts from interpretation. Mark inferences: "💡 INFERENCE — [interpretation]. Not stated directly." Now analyze the transcripts I've provided and produce the handover document. ---END PROMPT---