---
name: funding-signal-play
description: >-
  Trigger-based outbound play when a target account raises funding — urgency
  messaging, use-of-funds alignment, 7-14 day window. Triggers on: "funding signal",
  "funding play", "raised money outreach", "funding announcement outbound".
license: MIT
compatibility: Claude Code, Cursor, Codex, Hermes, Windsurf, OpenCode, Gemini CLI, Copilot, Zed, VS Code, Goose
metadata:
  version: "1.0.0"
  author: LeadMagic
  category: sales-plays
  tags: [sales-plays, trigger-based, funding, signals, outbound]
  frameworks:
    - "Signal-Based Selling"
    - "ColdIQ Trigger Selling Framework"
    - "Winning by Design — SPICED"
---

# Funding Signal Outbound Play

## Overview
A funding event is the strongest B2B buying signal that exists: budget unlocked,
growth mandate activated, and vendor evaluation starting. This play executes
a coordinated outbound motion within 7-14 days of a funding announcement.

## Frameworks Referenced

This skill is grounded in named GTM frameworks and operator methodologies, not generic advice:

- **Signal-Based Selling** — used as the named operating framework for this playbook.
- **ColdIQ Trigger Selling Framework** — used as the named operating framework for this playbook.

## When to Use
- "Run a funding signal play"
- "Outreach to recently funded companies"
- "Trigger-based outbound on funding announcements"
- "Series A/B/C outbound cadence"

## Core Principle
> A funding round is a time-bound window where decision-makers are actively
> buying. The money is allocated, the hiring plans are set, and the pressure
> to show results is high. Your window: 7-14 days post-announcement before
> 50 competitors have already reached them.

## Step-by-Step Process

### Phase 1: Signal Detection (Day 0)
Monitor funding announcements via:
- Crunchbase API / alerts
- PitchBook / CB Insights
- TechCrunch / VentureBeat coverage
- LinkedIn posts from VCs announcing portfolio raises
- Twitter/X posts from founders
- SEC Form D filings (US companies)

### Phase 2: Rapid Account Research (Day 0-1)
Within 24 hours of signal detection:
- Round size, lead investor, use of funds from press coverage
- Current team size and open roles (LinkedIn jobs)
- Current tech stack (BuiltWith)
- Founder/CEO LinkedIn profile and recent activity
- Identify which use of funds your product maps to

### Phase 3: Urgency-Based Outreach Sequence (Day 1-14)
7-day, 5-touch sequence:

**Day 1 — Email Touch 1 (Congrats + Hypothesis):**
Subject: "Congrats on the [Series X]"
Body: Reference their raise, connect their stated use of funds to a problem
you solve, share a quick data point from another recently-funded company.

**Day 2 — LinkedIn Connection:** Connect with the CRO, VP Sales, or RevOps
lead (whoever just got budget). Reference their LinkedIn post about the raise.

**Day 4 — Email Touch 2 (Proof Point):**
Subject: "[Similar company] after their [Series X]"
Body: Case study of a company at similar stage who used your product to hit
the metrics their board just set.

**Day 7 — Email Touch 3 (Direct Ask):**
Subject: "Question about [their use of funds area]"
Body: Direct, peer-to-peer. "Most teams post-[Series] face [X problem].
How are you thinking about this? Worth a 15-min call?"

**Day 10-14 — LinkedIn DM + Breakup Email:**
DM: Reference your emails, add value (industry report, benchmark data).
Email: "Closing your file" — sometimes the delayed response comes here.

### Phase 4: Multi-Thread Expansion
If no reply from primary contact, expand within the org:
- VP Engineering (if product-led)
- Head of Growth (if demand-gen focused)
- The VC who led the round (warm intro through network)

### Phase 5: Measurement
Track per funding event: contacts reached, reply rate, meeting rate, opportunity
rate, deal size. Compare against non-trigger outbound: funding signal plays should
have 2-3x higher reply rates due to timing relevance.

## Output Format
Funding play playbook with: signal monitoring setup, research template, 5-touch
sequence with templates, and measurement dashboard.



## Quality Check

Before delivering, verify:
- [ ] All required sections are complete
- [ ] Output matches the user's stated need
- [ ] Named frameworks are cited for key recommendations
- [ ] No vague claims — every recommendation has a specific action
- [ ] Deliverable is ready for operational use, not just conceptual

## Common Pitfalls

1. **Skipping research.** Building output without understanding the specific context. Fix: always gather required inputs before producing deliverables.
2. **Generic output.** "Improve your process" without concrete steps. Fix: every recommendation must include a specific action, timeline, and owner.
3. **Missing framework citations.** Advice without named authorities. Fix: ground every recommendation in a cited framework from a recognized authority.

## Related Skills
- cold-email-strategy, cold-email-copywriting, signal-scoring, list-building, multi-channel-outreach