mcpField
C
cadence-design

cadence-design

github.com/gtmagentsMarketing & growth42865 installsUpdated 30w ago
Repository

About cadence-design

A skill for planning and auditing multi-stage email sequences, intended for marketing teams coordinating with sales and customer success. It combines behavior-based timing, frequency limits, channel planning, and recovery paths.

Key features

  1. 01Set goals and metrics by lifecycle stage
  2. 02Time sends using behavioral signals
  3. 03Set frequency caps by audience and stage
  4. 04Plan cross-channel touches and ownership
  5. 05Design inactivity and bounce recovery paths

Use cases

  1. 01Plan nurture, onboarding, or expansion sequences
  2. 02Review send frequency to reduce fatigue and unsubscribes
  3. 03Coordinate email, in-app, SMS, and sales touches

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/gtmagents/gtm-agents --skill cadence-design

After installing, type/cadence-designin Claude Code to confirm it loaded.

Details

From the project README

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.

Comments

Markdown supported