Trigger Mapping

Trigger Mapping

When to Use

• Designing event-driven outbound campaigns (vs. list-based batch sending)
• Building automation rules for when to contact a prospect
• Creating playbooks for SDRs on which events to act on and how
• Setting up n8n, Zapier, or custom workflows that fire outreach on specific triggers

Framework

Trigger-Based vs. List-Based Outbound

The hybrid approach is the gold standard. You pre-qualify the list (ICP match), then monitor for triggers that tell you WHEN to reach out. This gives you the best of both worlds: targeted copy with perfect timing.

The Trigger Map: 12 Core Business Events

Every trigger needs four components defined: the event, the detection method, the message angle, and the urgency window.

Trigger 1: New Funding Round

Trigger 2: Hiring for Target Role

Trigger 3: Leadership Change

Trigger 4: Tech Stack Change

Trigger 5: Competitor Churn

Trigger 6: Product Launch

Trigger 7: Earnings/Revenue Event

Trigger 8: Conference/Event Attendance

Trigger 9: Content Publication

Trigger 10: Award or Recognition

Trigger 11: M&A Activity

Trigger 12: Regulatory/Market Change

Trigger Prioritization Matrix

When multiple triggers fire simultaneously, prioritize by:

Building Trigger-Based Campaigns

Campaign Architecture

TRIGGER CAMPAIGN: {{triggerName}}

Trigger: {{event description}}
Detection: {{how you find out}}
Filter: {{ICP criteria that must also be true}}
Volume estimate: {{expected triggers per month}}

Sequence:
Step 1 (Day 0): Trigger-specific email
Step 2 (Day 3): New value angle (resource, case study)
Step 3 (Day 7): Social proof or different angle
Step 4 (Day 14): Breakup / referral

Personalization requirement:
- Step 1: Must reference the specific trigger + company
- Steps 2-4: Can use bucket personalization

Success metrics:
- Target reply rate: 10-20% (trigger campaigns should beat list-based by 2-3x)
- Target positive reply rate: 5-12%

Templates

Trigger Map Document

# Trigger Map: {{Company/Product Name}}
# Updated: {{date}}

| # | Trigger | Detection Source | Urgency Window | Message Angle | Target Persona | Est. Monthly Volume |
|---|---------|-----------------|----------------|---------------|----------------|---------------------|
| 1 | ___ | ___ | ___ | ___ | ___ | ___ |
| 2 | ___ | ___ | ___ | ___ | ___ | ___ |
| 3 | ___ | ___ | ___ | ___ | ___ | ___ |

Trigger Playbook (For SDR Team)

TRIGGER: {{trigger name}}

When you see this:
{{description of the event}}

Do this immediately:
1. Verify the lead passes ICP filter (size, industry, stage)
2. Find the right contact ({{suggested title}})
3. Check if they're already in an active campaign
4. If clear → Add to {{campaign name}} sequence
5. If in existing campaign → Flag for review

Template to use:
Subject: {{subject line template}}
Body: {{body template with variables}}

DON'T:
- {{common mistake 1}}
- {{common mistake 2}}

Tips

• Build trigger campaigns for your top 3 triggers first. Don't try to monitor everything. The Pareto principle applies: 3 triggers will generate 80% of your signal-based pipeline.
• Trigger-based campaigns should always outperform list-based campaigns. If they don't, either your signal detection is lagging (stale triggers) or your message doesn't connect the trigger to your value.
• The urgency window is real. A "congrats on the funding round" email 3 months after the announcement isn't relevant — it's lazy. Set up monitoring so you catch triggers within 48 hours.
• Combine trigger-based outreach with ongoing list-based campaigns. Trigger campaigns are your high-ROI sniper shots. List campaigns are your air cover. You need both.
• Track trigger-to-meeting conversion by trigger type. This data is gold — it tells you exactly which business events create the most pipeline for your specific product.

Progressive disclosure: load trigger automation workflows and integration configs only when building a specific trigger campaign.