What the Follow-up Email Sequence Generator actually produces

[ { "subject": "Your CRM Demo Recap + Salesforce Integration Deep-Dive", "rationale": "Direct reference to the demo and their specific pain point (Salesforce integration), creates clarity on what's included" }, { "subject": "Jordan, here's how you can cut reporting time by 80% (for your 45-rep team)", "rationale": "Personalized with name, addresses their specific team size, quantifies a key benefit they care about" }, { "subject": "Real-time pipeline visibility—see how it works for Brightwave", "rationale": "Speaks directly to their stated pain point, company-specific, solution-focused without being generic" }, { "subject": "Quick follow-up: Your Salesforce integration questions answered", "rationale": "References their specific questions from the demo, positions email as helpful vs. salesy" }, { "subject": "Demo Recording + ROI Breakdown for Your Q3 Timeline", "rationale": "Clear value props (recording, ROI), acknowledges their stated timeline, creates urgency without pressure" } ]

EMAIL 1: POST-DEMO RECAP & RESOURCES Timing: June 12, 2025 (2 days post-demo) Subject Line Option: "Your CRM Demo Recap + Salesforce Integration Deep-Dive" Body: Hi Jordan, Thanks so much for taking the time to meet with us yesterday. I really enjoyed walking through the pipeline forecasting module with you—and I could tell your team's frustration with manual reporting resonated when we showed the real-time analytics dashboard. As promised, I've put together a few resources to keep the momentum going: • Demo Recording Link: [LINK] – You can share this with your team to see the automation and reporting features in action. Pay special attention to the 2:15 mark where we dive into the Salesforce sync capabilities you asked about. • Salesforce Integration One-Pager: [ATTACHMENT] – This breaks down exactly how we handle data mapping and bi-directional syncing (the gap you mentioned with your current tool). • ROI Calculator for 45-Rep Teams: [LINK] – I've pre-populated this with your team size. It shows the time and cost savings you could see with automated reporting alone. Most teams in your space see payback within 2-3 months. I'm also coordinating with our technical team to set up a deeper technical discussion with your IT lead around mid-next week. You mentioned Q3 as your target rollout—that timeline is totally doable, and getting IT aligned early always makes implementation smoother. Would June 18th at 2 PM work for a 45-minute technical deep-dive? I'll send a calendar invite separately, but wanted to check with you first. Looking forward to moving this forward. Best, [Your Name] [Your Title] [Company Name] [Contact Info] CTA: Click to view demo recording + confirm June 18th technical call --- EMAIL 2: VALUE-ADD NURTURE Timing: June 16, 2025 (4 days after Email 1, 2 days before technical call) Subject Line Option: "Quick insight: How SaaS leaders handle the Salesforce integration transition" Body: Hi Jordan, I was reviewing your notes from our demo and realized I didn't fully address one concern you raised—the risk of disruption during the Salesforce integration switch. I wanted to share something that might help: we recently worked with another 200-person B2B SaaS company through a similar transition. They were worried about downtime with their reps, so we set up a phased rollout where power users adopted the new pipeline forecasting module first, then we expanded team-wide. It took 3 weeks total, zero disruption to their sales cycle. I'm attaching a brief case study (Brightwave's situation is pretty similar to theirs) and a migration playbook our implementation team uses. No pressure to read through it all—I know you're busy—but it might be useful background for your IT lead before we chat on the 18th. One more thing: if you have specific Salesforce objects or workflows that are critical to your team's process, send those my way before Thursday and I'll have our technical team review them in advance. It'll make our call way more productive. Looking forward to the deep-dive. Best, [Your Name] CTA: Review attached case study + send any critical Salesforce workflows --- EMAIL 3: POST-TECHNICAL-CALL PROPOSAL MOMENTUM Timing: June 20, 2025 (2 days after technical call) Subject Line Option: "Next steps: Let's get your proposal in motion for Q3" Body: Hi Jordan, Great conversation with you and your IT lead on Wednesday. I know you both had solid questions about data governance and our sync frequency—I'm glad we could walk through those details. Based on what we discussed, I've prepared a preliminary proposal that accounts for: • Your 45-rep team size and current Salesforce setup • The phased rollout approach your team preferred • Q3 go-live with full training and support • Implementation costs plus your first-year license fees I'm attaching the proposal for your review. The ROI calculator you saw earlier is embedded in there—you'll see the payback timeline is even stronger than we initially estimated, given what we learned about your current manual reporting overhead. I'm planning to follow up on this around June 25th to see if you have questions or if we should schedule a final call to walk through the numbers with your finance or operations team. In the meantime, if anything stands out or you'd like me to adjust any assumptions, just shoot me a note. Flexibility on payment terms, implementation timeline, and even feature prioritization—we want to make this work for Brightwave. Thanks for moving quickly on this. Your team's going to love having real-time pipeline visibility. Best, [Your Name] CTA: Review attached proposal + send questions by June 25th --- TIMING SUMMARY: • Email 1 (Post-Demo Recap): June 12 — Resources, next-step confirmation, demo recording • Email 2 (Nurture/Value-Add): June 16 — Risk mitigation, social proof, pre-call preparation • Email 3 (Proposal Momentum): June 20 — Proposal review, ROI reinforcement, call-to-action on decision timeline