sdr-post-call-deck

SDR Post-Call Deck Skill

Transform meeting transcripts into polished, prospect-ready decks in 4 integrated phases. Everything stays tracked within Apollo.io.

---

Workflow Overview

Phase 1: EXTRACT & ANALYZE        → Extract transcript from Apollo.io Conversations
         (Internal Notes)          → Map keyword trackers to identify key highlights
                                   → Create internal summary notes in Apollo.io contact

Phase 2: GENERATE DECK            → Build 10-12 slide PowerPoint using Gamma or pptxgenjs
         (Prospect-Facing)        → Focus on what WAS DISCUSSED (not generic company info)
                                   → Minimal text, high-impact visuals (no stock images)

Phase 3: COMPOSE EMAIL            → Write crisp, professional email summary
         (Ready to Send)          → Include deck preview in email body
                                   → Call-to-action for next steps

Phase 4: SEND & TRACK            → Send via Apollo.io email feature
         (Apollo.io Ecosystem)    → Deck auto-attached with call summary
                                   → Everything logged in contact timeline

---

Phase 1: Extract & Analyze (Internal Notes)

Input: Apollo.io Conversation

1. Locate the conversation in Apollo.io → Conversations
2. Access the transcript and summary provided by Apollo.io
3. Extract these details:
   • Prospect name & title
   • Company & context
   • Call date/time
   • SDR name & any other attendees
   • Call duration
   • Raw transcript

Keyword Tracker Mapping

Use these Apollo.io keyword trackers to identify key highlights from the transcript:

Tracker Category	Focus	Examples
CoM - Discovery	What problems/pains did they mention?	"experiencing challenges," "what tools do you," "what problems"
CoM - Value Language	What outcomes matter to them?	"increase ROI," "actionable insights," "streamline processes"
CoM - Qualify & Analyze	How did you differentiate? What metrics matter?	"current situation," "success metrics," "comparison," "KPIs"
CoM - Buying Intent	Did they research you? Any intent signals?	"researching your solution," "intent signals," "right time"
CoM - Negotiate	Did budget come up?	"budget," "price," "discount," "multi-year"
Objections	What concerns were raised?	"concern," "we can't afford," "don't see the value," "compliance"
CoM - The Mantra	How did you explain your approach?	"how we do it," "measure that," "positive business outcomes"

Create Internal Summary Notes

Add these to the Apollo.io contact (in Notes/History):

📞 CALL SUMMARY - [Date]
═══════════════════════════════════════════════════════════════

ATTENDEES:
• [Prospect Name] - [Title]
• [Other attendees]
• SDR: [Your name]

KEY PAIN POINTS IDENTIFIED:
• [Specific pain mentioned - use Discovery keywords]
• [Specific pain mentioned]

SOLUTION AREAS DISCUSSED:
• [Feature/capability discussed in context of THEIR problem]
• [Specific use case they asked about]

VALUE DRIVERS THAT RESONATED:
• [Outcome they care about - use Value Language keywords]
• [Metric/KPI they mentioned]

OBJECTIONS/CONCERNS:
• [Specific concern with context]
• [How you addressed it or deferred]

BUYING SIGNALS / INTENT:
• [Did they research you? Any timeline mentions?]
• [Budget discussion? (if applicable)]

NEXT STEPS:
• [Specific action item with owner + due date]
• [Follow-up information to send]
• [Timeline for decision]

NOTES FOR FUTURE CALLS:
• [Team structure? Who else to involve?]
• [Strategic priorities to reference]
• [Tone/style preferences]

---

Phase 2: Generate Deck (12-15 Slides)

Structure

Keep this tight. Every slide should answer: "Why does the prospect need to see this?"

Note: Prospect-focused slides come first (what WE discussed), then company context, then resources & next steps. This flow keeps them engaged with their problem before introducing your solution.

SECTION A: PROSPECT DISCUSSION (Slides 1-8)

1. Slide 1: Call Summary Cover

   • Prospect name & company
   • Call date
   • "Post-Call Summary" title
   • One relevant accent visual (icon or subtle shape - NO stock image)

2. Slide 2: What We Discussed (Overview)

   • 3-4 bullet points of main topics
   • Use minimal text; let the layout breathe

3. Slide 3: Their Current Situation

   • Their stated pain/challenge (direct quote or paraphrased)
   • What they're currently struggling with
   • One-liner on impact

4. Slide 4-6: Areas We Explored (3 slides max - pick top 3 topics)

   • Each slide: Topic header + how it solves THEIR specific problem
   • Include one relevant visual per slide (relevant diagram, icon flow, or simple graphic - NOT stock photo)
   • Minimal bullet points (2-3 max)

5. Slide 7: How We're Different (Optional - only if competitive discussion happened)

   • Key differentiator relevant to their use case
   • Proof point or capability comparison
   • Visual: side-by-side comparison or capability callout

6. Slide 8: Specific Concerns Addressed

   • List any objections raised
   • How you addressed each one
   • Keep it factual and solution-focused

SECTION B: ABOUT OUR COMPANY (Slides 9-11)

7. Slide 9: Who We Are (Company Overview)

   • Critical: This is NOT a generic "About Us" slide
   • One paragraph describing company mission/vision as it relates to solving THEIR specific problem
   • Founded year + team size (if relevant)
   • Why we exist = directly mapped to their pain point
   • Visual: Company logo + one simple icon/graphic (no stock image)

   Example (not generic):

   "Founded in 2018, [Company] helps B2B SaaS teams automate prospect research and account targeting. We built this because we saw reps spending 40% of their day on manual research instead of selling. Today, 200+ growth teams use [Company] to recover 10+ hours/week per rep."

   NOT this:

   "Founded in 2018, [Company] is a market-leading platform for sales teams. We serve customers worldwide. Our mission is to drive success."

8. Slide 10: Product Overview (What We Do - Specific to THEIR Pain)

   • Critical: Show ONLY the capabilities relevant to THEIR problems
   • Use their pain points + what they asked about as your guide
   • 3-4 core features/capabilities (only ones discussed or highly relevant to their situation)
   • For each: Feature → How it solves YOUR specific problem
   • Visual: Feature icons or simple capability flow diagram

   Example (specific):

   Automated Account Targeting You mentioned needing a unified target account list. Our platform lets you define and sync target accounts across your Salesforce instance, eliminating overlap and rep confusion.

   Research Automation Instead of manual data entry (4 hrs/day), our platform enriches prospect data automatically. You get insights in seconds, not hours.

   NOT this:

   "Features: Account targeting, Research automation, Personalization, CRM sync, Lead scoring, Email integration, Workflow automation, API access..."

   Use product portfolio memory: Agent has access to full product capabilities but shows ONLY what's relevant.

9. Slide 11: Why Trust Us (Credibility & Proof)

   • Choose ONE of these approaches (or mix them):

   Option A: Certifications + Standards

   • ISO 27001 (security)
   • SOC 2 Type II (compliance)
   • GDPR compliant
   • Industry certifications relevant to their business
   • Visual: Certification badges/logos

   Option B: Customer Social Proof

   • "Trusted by 200+ B2B SaaS companies"
   • Quick client list (3-5 company logos if notable, or by segment)
   • Quote from similar customer (if relevant)
   • Visual: Client logos or testimonial

   Option C: Results/Metrics

   • "Typical customer sees 50% reduction in research time"
   • "Average rep productivity gain: 10 hours/week"
   • "98% data accuracy"
   • Visual: Key metrics in large, readable format

   Option D: Hybrid (Recommended)

   • One certification badge (top-left)
   • One customer success metric (center)
   • One client logo or segment callout (bottom)
   • Visual: Clean, balanced layout

SECTION C: USE CASES (Slides 12-13, Optional)

10. Slide 12: How We'd Handle Your Situation (Use Case - Specific)

    • Map directly from transcript: What did they ask about? What problems did they emphasize?
    • Walk through a concrete example of how your solution would work FOR THEM
    • Reference their specific context (company size, challenges, metrics)
    • 3-4 steps showing the workflow
    • Visual: Process flow or step-by-step diagram

    Example (specific to TechStart scenario):

    How [Company] Solves TechStart's Account Targeting Challenge:

    1. Define: You upload your target account list (mid-market tech companies)
    2. Deduplicate: Platform identifies overlapping accounts across your 50 reps
    3. Distribute: Reps see assigned accounts in Salesforce (no more chasing whoever responds)
    4. Measure: Dashboard shows account coverage + rep alignment

    Expected outcome for you: 50% research time reduction + aligned targeting

    NOT this:

    "Step 1: Login. Step 2: Add data. Step 3: Run workflow. Step 4: Export results."

11. Slide 13: Use Case / Similar Customer Example (Optional - only if highly relevant)

    • One paragraph on how a SIMILAR customer (same size, industry, challenge) solved their problem
    • "Company X" reduced research time by 50% and closed $2M ARR in Q2
    • If available: How long it took (quick implementation = 2 weeks)
    • Visual: Company name (not logo—privacy) + metric callout

    Only include if: You have a genuinely similar customer AND it came up in conversation

SECTION D: NEXT STEPS & RESOURCES (Slides 14-15)

12. Slide 14: Resources for Further Review

    • Link to demo video (if you did one)
    • Case study or white paper relevant to their industry/problem
    • Technical documentation (Salesforce integration guide if applicable)
    • Security/compliance docs (if they asked about it)
    • Contact info for questions
    • Not: Generic company brochures, product pricing pages

13. Slide 15: Next Steps

    • Crystal clear action items
    • Owner (you or them) + due date
    • Timeline to decision
    • How they'll hear from you
    • One sentence on why you're excited to work together

14. Slide 16: Contact & Follow-up (Optional)

    • Your name, title, email, phone
    • Calendar link or how to schedule
    • Social media handle (optional)

    Alternative: Merge this with Slide 15 if you want to stay under 15 slides

Design Principles

• NO STOCK IMAGES: Use icons, diagrams, charts, or leave negative space. Relevant > pretty
• Minimal text: 3-5 bullets per slide max
• High contrast: Text must be readable at a glance
• One visual element per slide: Keep cognitive load low
• Color palette: Pick 2-3 colors; keep it professional but memorable
• Font pairing: One header font (distinctive), one body font (clean)

Critical: Company Slides Must Be SPECIFIC

Slides 9-11 are NOT generic "About Us" slides. They must directly address the prospect's needs:

• Slide 9 (Who We Are): Explain WHY you exist in context of THEIR problem

  • "We built this because we saw [their pain point]"
  • Not: "We're a market leader in sales technology"

• Slide 10 (Product Overview): Show ONLY capabilities relevant to THEIR discussion

  • Use the transcript as your filter: What did they ask about?
  • Reference their specific context: "You mentioned 4 hours/day on research—here's how we solve that"
  • Not: A dump of all 20 product features

• Slide 11 (Credibility): Choose proof that matters TO THEM

  • If they asked about security → show ISO/SOC 2 badges
  • If they want to know customers like them → show similar customer logos
  • If they care about results → show productivity metrics
  • Not: Everything at once

Agent Memory Note: The SDR/agent using this skill has full product portfolio knowledge and customer database access. Their job is to filter intelligently—show what matters, hide what doesn't.

Deck Generation Approach

Option A: Use Gamma API (Preferred - faster, cleaner integration)

- Call tool_search for Gamma integration
- Pass structured content (title, sections, key points) to Gamma
- Gamma generates polished deck with default theme
- Download as PPTX

Option B: Use pptxgenjs (If Gamma unavailable)

- Build deck programmatically with pptxgenjs
- Apply custom color palette + typography
- Add icons and minimal visuals
- Export as PPTX

---

Phase 3: Compose Email (Crisp Summary)

Email Structure

Subject: Post-Call Summary – [Prospect Name] – [Date]

Body (Keep it SHORT - 150-200 words max):

Hi [Prospect Name],

Thanks for the great conversation today! 

Here's a quick recap of what we discussed:

✓ Your current challenge: [1-2 sentence on their pain point]
✓ How [Company Name] can help: [Specific to THEIR use case]
✓ Next steps: [Your action item + date]

I've attached a summary deck with more details on:
• [Key area 1 discussed]
• [Key area 2 discussed]
• Resources for further review

Feel free to share this internally as you socialize this with [stakeholder/team]. Happy to answer any questions via email or a quick call.

Looking forward to [next milestone: demo/followup call/etc.] on [date].

Best regards,
[Your name]
[Your title]
[Phone] | [Email]
[Company] | [Link to calendar]

Best Practices

• Lead with their problem: Don't talk about your company
• Specific to THEIR situation: Avoid generic language
• Clear next step: Who does what by when
• Tone: Professional but conversational—like you know them
• One CTA: Either "reply with questions," "schedule a follow-up," or "share internally"

---

Phase 4: Send & Track (Apollo.io Integration)

Sending via Apollo.io Email

1. Open Apollo.io → Contact record
2. Compose Email within Apollo.io (email feature)
3. Attach the deck as PDF or PPTX
4. Paste email body from Phase 3
5. Schedule send for within 1 hour of call end (or send immediately if preferred)
6. Track in contact timeline (automatically logged by Apollo.io)

What Gets Tracked

• ✅ Email sent timestamp
• ✅ Deck attachment
• ✅ Email open + click tracking
• ✅ Prospect engagement
• ✅ Integration with contact history

If Apollo.io Email Unavailable

Fallback to Gmail:

1. Create new email in Gmail
2. Paste deck link or attach PPTX
3. Use email body from Phase 3
4. Send with subject: Post-Call Summary – [Prospect Name]
5. Manually log in Apollo.io notes: "Sent post-call summary deck on [date] via email"

---

Complete Workflow Checklist

• Phase 1: Extract

  • Access Apollo.io Conversations
  • Download/copy transcript
  • Map keyword trackers to transcript
  • Create internal notes in Apollo.io contact

• Phase 2: Generate (12-15 slides)

  • SECTION A - Prospect Discussion (Slides 1-8)

    • Slide 1: Cover with company/prospect names
    • Slide 2: What we discussed (overview)
    • Slide 3: Their current situation (problem)
    • Slides 4-6: Areas explored (3 slides, specific to their pain)
    • Slide 7: How we're different (if competitive discussion)
    • Slide 8: Concerns addressed

  • SECTION B - Company Context (Slides 9-11) ⭐ CRITICAL

    • Slide 9: Who we are (mapped to THEIR pain, not generic)
    • Slide 10: Product overview (ONLY capabilities they asked about)
    • Slide 11: Why trust us (credibility - certs/clients/metrics)

  • SECTION C - Use Cases (Slides 12-13)

    • Slide 12: How we'd handle your situation (specific workflow)
    • Slide 13: Similar customer example (if relevant to transcript)

  • SECTION D - Resources & Next Steps (Slides 14-15)

    • Slide 14: Resources for further review
    • Slide 15: Next steps & timeline

  • Verify no stock images

  • Verify company slides are specific, not generic

  • Generate deck (Gamma or pptxgenjs)

  • Review for readability + visual hierarchy

  • Export as PPTX

• Phase 3: Compose

  • Write crisp email (150-200 words)
  • Focus on prospect's problem, not your company
  • Include specific next steps
  • Proof for tone & clarity

• Phase 4: Send

  • Send via Apollo.io email feature (preferred)
  • Attach deck
  • Confirm logged in contact timeline
  • Set reminder for follow-up

---

Tips for Success

Get the Research Right

• Direct quotes from the prospect about their pain (more powerful than paraphrase)
• Their terminology: Use their words for problems, not your framework
• Specific numbers: If they mentioned team size, revenue impact, timelines—include them

Make Every Slide Count

• Delete any slide that doesn't answer: "Why does the prospect need to see this?"
• Company slides (9-11) are NOT generic "About Us" slides
  • Slide 9: Explain WHY you exist in context of THEIR problem
  • Slide 10: Show ONLY capabilities relevant to what THEY asked about
  • Slide 11: Choose credibility proof that matters TO THEM (security certs if they asked about it, customer logos if they want proof, metrics if they care about results)
• Your only job: Reflect back what they said, what they need, and how you can help THEM.

Company Slides Must Be Specific

• NOT: "Founded in 2018, we are a market leader in sales technology"

• YES: "Founded in 2018, we help B2B SaaS teams automate prospect research. We built this because we saw reps spending 4+ hours a day on manual research—like your team is experiencing now."

• NOT: List all 20 product features

• YES: "The three capabilities most relevant to your situation: [Feature 1 mapped to their pain], [Feature 2 mapped to their pain], [Feature 3 mapped to their pain]"

• NOT: Every certification and every customer logo

• YES: Show ONE proof type that matters to them—if they asked about security, show ISO/SOC 2; if they want to see customers like them, show similar logos; if they care about results, show productivity metrics

Use your product portfolio knowledge strategically: You know every feature + every customer. Filter to show only what's relevant.

Timing Matters

• Send within 1 hour of call (while context is fresh)
• If there's delay, note it in email: "Sorry for the slight delay—wanted to make sure this captured all our discussion"

Prospect-Ready Visuals

• No corporate logos scattered everywhere
• No generic "people in a meeting" stock photos
• Use: icons, diagrams, process flows, comparison tables, charts
• When in doubt, leave it blank—negative space is professional

Follow the CoM (Conversation Mapper) Keywords

• These aren't just buzzwords; they're how you identify what actually matters to this prospect
• "Pain" keyword mentioned 3x? That's your headline
• "ROI" and "metrics" came up? Include a resource on their specific value calculation
• "Timeline" keyword? Make sure next steps have dates

---

Troubleshooting

Issue	Solution
Transcript too raw/messy	Use Apollo.io's summary as primary source; use transcript for quote extraction
Not sure what to include	Ask: "Does the prospect need this to understand what we discussed?" If no, cut it
Company slides feel generic	Rewrite to map directly to THEIR pain. Use transcript as your filter. If they didn't ask about it, don't include it.
Product overview feels like a dump	You know all 20 features; they care about 3-4. Use their questions as your filter. What did they ask about? Start there.
Credibility slide unclear	Pick ONE proof type: (A) Certs if they care about security, (B) Customer logos if they want proof of similar customers, (C) Metrics if they care about results, or (D) Hybrid. Don't list everything.
Prospect didn't raise budget/timeline	Don't force it. Focus on pain, solution, resources, next steps.
Apollo.io email feature unavailable	Use Gmail; manually log outreach in Apollo.io contact notes
Getting to 15 slides and still have content	You're including too much generic info. Ruthlessly cut non-essential slides. Company slides should be 3 slides max, not 6.

---

Reference Files

The agents/ directory contains instructions for specialized subagents. Read them when you need to spawn the relevant subagent.

Main References

• keyword-trackers.md — Complete Apollo.io keyword tracker reference for identifying call highlights
• example-workflow.md — Fully worked example showing transcript → keyword mapping → internal notes → complete deck outline
• company-slides-guide.md — Detailed guide for making Slides 9-11 (company context) prospect-specific, not generic
  • How to write "Who We Are" specific to their pain
  • How to show product capabilities mapped to their needs
  • Credibility slide options (certifications vs. customer proof vs. metrics)
  • Real examples by industry

Use company-slides-guide.md whenever you're building Slides 9-11 to ensure they're specific to THIS prospect, not generic.

---

Estimated Timeline

Phase	Time	Notes
Phase 1: Extract & Notes	10-15 min	Faster if transcript is clean
Phase 2: Generate Deck	15-20 min	Faster with Gamma; slower with pptxgenjs
Phase 3: Compose Email	5 min	Short & crisp by design
Phase 4: Send & Track	2-3 min	Apollo.io email is fastest
TOTAL	~40 min	Well under 1-hour window

---

Next Steps

1. Copy the Keyword Tracker reference → bookmark for easy access during calls
2. Build a deck template with your company's color palette + fonts (reuse for all calls)
3. Create email templates for different scenarios (first call, follow-up, competitive situation)
4. Set reminders → 45 minutes after call ends, send summary deck
5. Track metrics → Monitor which decks get opened, which resources get downloaded