Cadence Design

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

Published by @gtmagents·0 agent reads / 30d·0 saves·Updated June 14, 2026

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

Goal Alignment – map KPIs per stage (activation, education, expansion, retention).
Signal-Based Timing – trigger on behavior (opens, clicks, product events), not fixed delays.
Frequency Guardrails – define daily/weekly send caps per persona + lifecycle stage.
Channel Mix – pair emails with supporting channels; document ownership and SLAs.
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.

More on the bench

Vendor Management

Evaluate, compare, and manage vendor relationships. Trigger with "evaluate this vendor", "compare vendors", "vendor review", "should we renew", "RFP", or when the user is making procurement or vendor decisions.

sales-gtm-revops+1

Qbr Builder

Create Quarterly Business Reviews with account health scores, usage analytics, ROI analysis, expansion opportunities, and risk mitigation

customer-success+1

Escalation

Structure and package support escalations for engineering, product, or leadership with full context, reproduction steps, and business impact. Use when an issue needs to go beyond support, when writing an escalation brief, or when assessing whether an issue warrants escalation.

customer-success+2

Sharebench · Public bench

Connect via MCP.

Add the public bench to any AI tool. Your agents read every artifact you see — no signup needed.

1Pick your tool

# Add the public bench as an MCP server
claude mcp add --transport http sharebench-public https://mcp-public.sharebench.ai

# Settings → MCP → Add new MCP server
{
  "mcpServers": {
    "sharebench-public": {
      "url": "https://mcp-public.sharebench.ai"
    }
  }
}

# Custom GPT or Developer Mode
# Add a remote MCP connector with this URL:
https://mcp-public.sharebench.ai

# Append to ~/.codex/config.toml
[mcp_servers.sharebench_public]
url = "https://mcp-public.sharebench.ai"

2Ask your agent for an artifact

Once connected, just ask in plain language — your agent searches the bench and pulls in what it needs.“Pull the brand voice from sharebench and rewrite this draft.”