earnings-signal-play v1.0.0A

Immutable. This exact content is served forever at /api/v1/blob/aa852933d281b8f5.

---
name: earnings-signal-play
description: >-
  Outbound play triggered by public company earnings calls — strategic priority
  mining, new-initiative alignment, urgency creation. Triggers on: "earnings signal",
  "earnings play", "public company outbound", "10-K outreach".
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, earnings, public-companies, trigger-based, enterprise]
  frameworks:
    - "Signal-Based Selling"
    - "Gartner Strategic Account Planning"
    - "Winning by Design — SPICED"
---

# Earnings Call Signal Play

## Overview
Public company earnings calls are the richest source of enterprise buying signals.
In 45 minutes, executives reveal: strategic priorities for the next 12 months,
budget allocations, headwinds they're fighting, headcount plans, and specific
initiatives. This play mines earnings calls for outbound triggers.

## 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.
- **Gartner Strategic Account Planning** — used as the named operating framework for this playbook.

## When to Use
- "Mine earnings calls for signals"
- "Earnings-based outbound"
- "Enterprise trigger outreach"
- "Public company prospecting"

## Core Principle
> Earnings calls are legally required strategy documents delivered quarterly.
> When the CFO says "we're investing heavily in X this year," that's a buying
> signal. When the CEO says "Y is a headwind," that's a pain point your product
> might solve.

## Step-by-Step Process

### Phase 1: Signal Mining
Scrape and analyze target account earnings calls. Listen for:

**Buying Signals:**
- "Investing in..." / "Doubling down on..." → Budget allocated
- "Digital transformation..." → Tech stack overhaul
- "Hiring [X] headcount..." → Team scaling, new tools needed
- "Acquisition of..." → Integration needs, new buying center
- "New [product line / geography / segment]..." → Initiative with supporting budget

**Pain Points (your solution fit):**
- "Margin pressure in..." → Need for efficiency tools
- "Customer churn..." → Need for retention/CS tools
- "Competitive pressure..." → Need to move faster/cheaper
- "Operational inefficiency..." → Process automation opportunity

**Timing Markers:**
- "By end of fiscal year..." → Deadline
- "In the next two quarters..." → Active buying window
- "We've already begun..." → Urgency, in-flight initiative

### Phase 2: Signal-to-Value Mapping
For each signal, map to your product's value:
- Signal: "Hiring 50 SDRs next quarter"
  → Your value: SDR efficiency tools, ramp time reduction, sequencing platform
- Signal: "Customer retention is top priority"
  → Your value: Health scoring, CS automation, churn prediction

### Phase 3: Executive Outreach Sequence
Target: VP or SVP referenced in the earnings call (owner of the initiative).

Subject: "Your Q3 call — [specific quote]"
Body: Quote their earnings call. "You mentioned [strategic priority] is a
focus. The teams I work with at similar scale find [X insight]. Curious how
you're thinking about the [specific domain] piece of this."

### Phase 4: Multi-Level Engagement
- **C-suite:** Strategic alignment email (1 per quarter — don't spam)
- **SVP/VP:** Initiative-specific outreach referencing the earnings call
- **Director:** Operational connection — "your SVP mentioned X, here's how
  teams like yours execute on that"

### Phase 5: Quarterly Cadence
- Earnings week: Mine the call, prepare outreach drafts
- Week 1 post-earnings: Send executive outreach
- Week 2: Follow up to non-responders
- Week 3: Expand to Director level
- Maintain: Add to nurturing cadence with quarterly touch

## Output Format
Earnings play playbook with: signal mining framework, signal-to-value mapping,
executive outreach templates, and quarterly cadence calendar.



## 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, meeting-prep, pipeline-management, account-selection, competitive-intel