← ClaudeAtlas

gtm-signal-campaignlisted

When the user wants account research, ICP scoring, signal-based outbound, campaign sequences, sales outreach triggered by events, target account research, signal library design, GTM engineering, or revenue-system workflows. Turns signals into account research, sequence copy, suppression rules, and measurement plans.
buildingwithai/pmm-os · ★ 0 · AI & Automation · score 65
Install: claude install-skill buildingwithai/pmm-os
# GTM Signal Campaign You turn market and account signals into revenue actions. ## Inputs - Company profile - ICP tiers and anti-ICP - Signal library - Persona files - Competitive radar - Offer or campaign goal - Suppression rules If those do not exist, create lightweight versions under `.agents/marketing-os/context/`. ## Workflow 1. Define trigger logic - Single signal or signal combination. - Minimum score. - Recency window. - Suppression conditions. 2. Segment target accounts - ICP tier. - Persona. - Account status. - Competitive context. 3. Research accounts - Company snapshot. - Funding and growth. - Recent hires. - Tech stack. - Stakeholders. - Active signals. - Why now, why us, first hook. 4. Design sequence - Touches, timing, channels, personalization level. - Tier 1 gets more manual personalization. - Tier 3 stays efficient and templated. 5. Write copy - Use permissionless value: the message should be useful even without the CTA. - Include signal hook, insight, connection, CTA. 6. Measurement - Reply rate. - Meeting rate. - Pipeline per account. - Signal-triggered lift. - Review at 2 weeks and 6 weeks. ## Output folder ```text .agents/marketing-os/outputs/campaigns/YYYY-MM-DD-[campaign-name]/ ├── brief.md ├── account-research.md ├── sequences/ │ ├── tier1.md │ ├── tier2.md │ └── tier3.md ├── metrics.md └── results.md ``` ## MCPs Use read-only research first. Recommended MC