home / skills / gtmagents / gtm-agents / outbound-plays

This skill helps craft channel-specific outbound plays aligned to detected signals to optimize multi-channel outreach and messaging relevance.

npx playbooks add skill gtmagents/gtm-agents --skill outbound-plays

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
1.6 KB
---
name: outbound-plays
description: Use to craft channel-specific outreach sequences that tie directly to
  detected intent signals.
---

# Signal-Aligned Outbound Plays Skill

## When to Use
- Launching targeted SDR/AE campaigns triggered by specific topics or product usage events.
- Coordinating multi-channel waves (email, phone, social, executive outreach) rooted in current buying triggers.
- Ensuring messaging references the exact signals that activated the play.

## Framework
1. **Trigger Mapping** – list top signals/topics and the matched play archetype (e.g., “security spike → exec briefing”).
2. **Persona Customization** – define copy blocks, value props, and proof points per persona activated by the signal.
3. **Channel Sequencing** – outline cadence (email → call → social) with timing guidelines based on signal freshness.
4. **Measurement Plan** – capture metrics per channel (reply rate, meeting rate, pipeline impact) and feedback loops.
5. **Escalation Paths** – specify when to escalate to exec sponsor, ABM pod, or customer marketing for references.

## Templates
- Trigger-to-play matrix (signal, persona, playbook, assets needed).
- Outreach sequence script referencing signal language and talk tracks.
- Retro doc capturing performance vs control cohorts.

## Tips
- Reference the exact topic or behavior detected in the first touch to prove relevance.
- Pair with `suppression-logic` to avoid conflicting outreach when customer success or support is active.
- Refresh playbooks quarterly to align with evolving product stories and personas.

---

Overview

This skill helps craft channel-specific outbound sequences that map directly to detected intent signals or product behaviors. It provides a repeatable framework for turning signals into targeted plays, with persona-specific copy, channel cadence, and measurement. Use it to increase relevance, accelerate responses to buying intent, and convert signals into pipeline impact.

How this skill works

The skill inspects incoming intent signals and maps each to a play archetype using a trigger-to-play matrix. For each activated play it generates persona-customized messaging blocks, a multi-channel sequence with timing guidance, and an associated measurement plan. It also defines escalation paths and suppression checks to avoid conflicting outreach.

When to use it

  • Launching SDR/AE campaigns tied to a recent product usage spike or topic signal
  • Coordinating multi-channel waves (email, call, social, executive outreach) around a specific buying trigger
  • Aligning messaging so the first touch references the exact detected signal
  • Rolling out timed sequences when signal freshness affects outreach cadence
  • Creating controlled experiments comparing signal-aligned plays vs baseline outreach

Best practices

  • Open the first touch by referencing the exact topic or behavior that triggered the play to prove relevance
  • Define copy blocks, value props, and proof points per persona before scaling sequences
  • Pair with suppression logic to prevent conflicting outreach when support or CS is active
  • Set clear metrics per channel (reply rate, meeting rate, pipeline impact) and run retro analyses
  • Refresh playbooks quarterly to reflect evolving product stories and buyer personas

Example use cases

  • Detect a security-related spike and launch an exec-briefing play with CISO-targeted messaging and account exec escalation
  • User adopts premium feature: trigger an upsell sequence combining product-led email, AE call, and LinkedIn touch
  • Inbound content interest on compliance topics kicks off an ABM pod sequence prioritizing enterprise personas
  • Multiple behavioral signals across accounts trigger a high-touch escalation to customer marketing for references
  • A/B test two cadence variations to measure meeting rate lift from signal-aligned messaging

FAQ

How do I avoid over-contacting accounts when multiple signals fire?

Use suppression logic and a priority matrix in the trigger mapping so higher-priority plays suppress lower-priority waves and coordinate with CS/support windows.

What metrics should I track to prove play effectiveness?

Track channel-level reply rate, meeting rate, conversion to opportunity, and pipeline contribution; compare against control cohorts in the retro doc.