---
name: pmm-outreach
description: Draft founder-led or PMM-led outreach, cold email, LinkedIn DM, warm intro requests, follow-up cadences, and signal-triggered prospecting messages grounded in positioning, persona, and account context.
---

# PMM Outreach

You draft outreach grounded in positioning, persona, and account context — cold email, LinkedIn DMs, warm intros, and follow-up cadences that earn a reply.

## Workflow

1. Read product context, persona, positioning, and proof.
2. Identify recipient, why this person, why now, channel, warmth level, and desired next step.
3. Draft the hook, bridge, proof, and one CTA.
4. Produce channel-specific variants and a follow-up cadence.
5. Route to `gtm-signal-campaign` when this is a campaign, not a single message.

## Output

Create `outreach-pack.md` with:

- Primary message
- Subject lines
- LinkedIn DM variant
- Warm intro request if relevant
- Follow-up cadence
- Reply handling notes
- Claims needing proof

## Quality bar

Specific person, specific reason, specific ask. If one is missing, ask or mark the risk before drafting.

## Hand off to

PMM OS is a chain, not a menu — don't dead-end at advice. Pass the work on:

- [`gtm-signal-campaign`](../gtm-signal-campaign/SKILL.md) — scale outreach off signals
- [`pmm-battlecard`](../pmm-battlecard/SKILL.md) — handle objections in-thread
- [`gtm-account-research`](../gtm-account-research/SKILL.md) — personalize with account intel
- [`pmm-coach`](../pmm-coach/SKILL.md) — review before anything customer- or exec-facing.

## Depth

Apply the [PMM OS output-depth standard](../product-marketing-os/references/output-depth-standard.md): every section must be **specific** (named alternatives, segments, numbers — not "competitors"/"users"/"better"), **complete** (the real dimensions, not just the first), **reasoned** (the why and the trade-off), and **evidenced** (a proof or a named proof-gap). Depth is not length — do not pad, but never reduce a section to one generic line. Self-check each section before returning.

## Frameworks & deep references

Read and apply the deep frameworks below before you produce output — they carry the methodology, templates, and worked examples behind this skill (from the PMM OS framework library). Read the ones relevant to the request and *apply* them; don't paste them verbatim.

- [`sales-enablement/06-sales-playbooks.md`](../product-marketing-os/references/library/sales-enablement/references/core/06-sales-playbooks.md) — sequence as a playbook
- [`sales-enablement/09-sales-methodologies.md`](../product-marketing-os/references/library/sales-enablement/references/core/09-sales-methodologies.md) — qualify within the methodology