B2B SaaS: lifecycle email behind an SDR-heavy funnel
Problem
Pipeline was a machine: inbound demos, outbound sequences, and aggressive follow-up. What broke was everything after “no show” or “not now.” Leads rotted in stages, SDRs burned time re-explaining the same value props, and marketing’s newsletters felt disconnected from what reps said on calls.
Constraints
Product was shipping fast; messaging drifted weekly. Finance wanted CAC discipline. Leadership did not want lifecycle email to cannibalize SDR-sourced pipeline or annoy prospects who were already talking to AE.
Approach
We mapped real exit reasons from calls and CRM notes—then built short arcs (3–6 touches) per reason, not per persona wallpaper. Each arc had a single CTA aligned to sales stage: book, read one proof artifact, or opt down to a lighter track. RevOps defined suppression and re-entry rules so AE-owned opportunities were sacred.
Rollout
We launched with two arcs in one segment where data was cleanest. Creative was mostly text plus one modular layout so updates did not require a redesign every sprint. After stability, we connected product usage signals where ethical and contractually allowed—triggering education, not guilt. Monthly reviews focused on downstream meetings, unsubscribes, and SDR time saved—not open rates as a trophy metric.
Risks mitigated
- Double outreach: hard stops when SDR or AE logged activity in a 48-hour window
- Message drift: single owner for “source of truth” copy synced to sales decks weekly
- Deliverability: domain strategy and list hygiene treated as infrastructure, not a campaign
Outcomes (illustrative)
Reactivation from dormant stages produced incremental meetings without increasing total email volume. SDRs reported fewer “start from zero” calls because prospects had consumed the same story reps told—just asynchronously.
Lessons
Lifecycle works when it is written like internal enablement: blunt, specific, and respectful of time. If marketing cannot quote the top three objections from last week’s calls, the nurture is fiction.
Planning a similar rollout?
Request a consultation