cadence-design

gtmagents's avatarfrom gtmagents

Use when spacing, sequencing, and pacing multi-touch email programs.

31stars🔀7forks📁View on GitHub🕐Updated Dec 23, 2025

When & Why to Use This Skill

The Cadence Design skill empowers users to architect sophisticated multi-touch email programs by optimizing the spacing, sequencing, and pacing of communications. It provides a structured framework for planning nurture sequences, auditing send frequency to prevent subscriber fatigue, and coordinating cross-channel touches to maximize engagement and conversion rates.

Use Cases

  • 1. Automated Onboarding & Nurture: Designing multi-branch sequences to guide new users through product activation and education stages.
  • 2. Subscriber Fatigue Prevention: Auditing and setting frequency guardrails to reduce unsubscribe rates and maintain high sender reputation.
  • 3. Omnichannel Strategy: Coordinating email sequences with SMS, in-app notifications, and sales team outreach for a seamless and unified customer experience.
  • 4. Signal-Based Campaigning: Implementing behavioral triggers (e.g., clicks, product events) to replace fixed-delay schedules with high-relevance, real-time timing.
namecadence-design
descriptionUse when spacing, sequencing, and pacing multi-touch email programs.

Email Cadence Design Skill

When to Use

  • Planning nurture, onboarding, or expansion sequences with multiple branches.
  • Auditing send frequency to reduce fatigue and unsubscribes.
  • Coordinating cross-channel touches (email, in-app, SMS, sales assist).

Framework

  1. Goal Alignment – map KPIs per stage (activation, education, expansion, retention).
  2. Signal-Based Timing – trigger on behavior (opens, clicks, product events), not fixed delays.
  3. Frequency Guardrails – define daily/weekly send caps per persona + lifecycle stage.
  4. Channel Mix – pair emails with supporting channels; document ownership and SLAs.
  5. Recovery Paths – add detours for inactivity, hard bounces, or sales handoffs.

Templates

  • Cadence matrix (day, trigger, message purpose, CTA, channel).
  • Fatigue model calculator (touches vs engagement trend).
  • Suppression logic checklist (recent send, opportunity stage, consent).

Tips

  • Front-load value but leave whitespace before high-ask CTAs.
  • Reuse proven send windows per persona while testing incrementally.
  • Share cadence plan with SDR/CSM teams to prevent overlap.