mcpField
L
lifecycle-cadence

lifecycle-cadence

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

About lifecycle-cadence

Lifecycle Cadence Systems is a skill for designing and auditing nurture journeys across lifecycle stages. It helps marketing and revenue teams coordinate triggers, pacing, suppression, routing, and monitoring across channels.

Key features

  1. 01Align cadence with lifecycle stages
  2. 02Define entry triggers and exit rules
  3. 03Set pacing, suppression, and journey priorities
  4. 04Monitor engagement, unsubscribes, bounces, and SLAs

Use cases

  1. 01Design or refresh nurture programs
  2. 02Find fatigue and timing conflicts across journeys
  3. 03Coordinate multi-channel touches with MAP and CRM routing

Install

Copy the command and run it in a terminal.

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

After installing, type/lifecycle-cadencein Claude Code to confirm it loaded.

Details

From the project README

Lifecycle Cadence Systems Skill

When to Use

  • Designing new nurture programs or refreshing existing cadences.
  • Auditing fatigue, suppression, or timing conflicts across journeys.
  • Coordinating MAP and CRM routing for multi-channel touches.

Framework

  1. Lifecycle Stage Alignment – ensure cadence matches funnel stage (MQL, SAL, SQL, post-sale).
  2. Trigger Definition – entry signals (form fills, intent spikes, product milestones, campaign responses).
  3. Pacing Rules – waiting periods, fallback content, stop logic for engagement or conversions.
  4. Suppression & Priority – handle conflicting journeys, global caps, sales stages, manual pauses.
  5. Monitoring – alerts for high unsubscribe/bounce, low engagement, or SLA breaches.

Templates

  • Cadence planner (stage, delay, channel, CTA, exit criteria).
  • Suppression matrix (journey priority, conflicts, resolution rules).
  • Monitoring checklist (metrics, thresholds, escalation owners).

Tips

  • Reassess cadences quarterly as product/offers evolve.
  • Keep a single decision table for suppression rules to avoid MAP drift.
  • Align with sales/CS to pause nurtures when opps advance or risks arise.

Comments

Markdown supported