/hiring-signal-outreach

name: hiring-signal-outreach
version: 1.0.0
description: >
  End-to-end hiring signal composite. Takes any set of companies, detects job
  postings that your product augments or replaces, finds relevant people
  (the hiring manager, buyers, champions, users), and drafts personalized
  outreach using the job role as the hook. Tool-agnostic — works with any
  company source, job board, contact finder, and outreach platform.
tags: [outreach]

graph:
  provides:
    - companies-with-hiring-signals  # Companies posting roles your product augments/replaces
    - contact-list                   # People at those companies to reach out to
    - personalized-email-sequences   # Outreach drafts using job posting as the hook
  requires:
    - company-list                   # Any list of companies (CSV, CRM, manual, Supabase)
    - your-company-context           # What you sell, what roles your product augments/replaces
  connects_to:
    - skill: cold-email-outreach
      when: "User wants to launch the campaign via their outreach tool"
      passes: contact-list, personalized-email-sequences
    - skill: linkedin-outreach
      when: "User wants LinkedIn outreach instead of or alongside email"
      passes: contact-list
  capabilities: [web-search, job-search, contact-finding, email-drafting]

Hiring Signal Outreach

Detects job postings at target companies where the role being hired for is one your product augments, replaces, or directly supports. Finds the right people to contact (not just the person being hired — the hiring manager, budget holder, and potential champions), then drafts personalized outreach using the job posting as the hook.

**Why hiring signals work:** When a company posts a job, they've already acknowledged the problem your product solves. They've budgeted for it (headcount is budget). They're actively evaluating how to solve it. Your email arrives at exactly the moment they're thinking about this problem — and you're offering a faster, cheaper, or complementary solution.

When to Auto-Load

Load this composite when:

• User says "check if any of these companies are hiring for roles we replace", "job posting signals", "hiring signal outreach"
• User has a list of companies and wants to find those hiring for relevant roles
• An upstream workflow (TAM Pulse, company monitoring) triggers a hiring signal check

---

Step 0: Configuration (One-Time Setup)

On first run for a client/user, collect and store these preferences. Skip on subsequent runs.

Role Mapping (Critical — This Defines What Signals Matter)

| Question | Purpose | Stored As | |----------|---------|-----------| | What does your product do? (1-2 sentences) | Match against job descriptions | `company_description` | | What job roles does your product **replace**? | Strongest signal — they're hiring for what you automate | `roles_replaced` | | What job roles does your product **augment**? | Good signal — your product makes this person more effective | `roles_augmented` | | What job roles **buy** your product? | Contact finding — who holds the budget | `buyer_titles` | | What job roles **champion** your product? | Contact finding — who feels the pain daily | `champion_titles` | | What job roles **use** your product? | Contact finding — who would operate it | `user_titles` | | What keywords in a job description indicate relevance? | Filters out false positives | `jd_keywords` |

**Example for an AI calling product:**

roles_replaced: ["BDC Representative", "Call Center Agent", "Appointment Setter"]
roles_augmented: ["Sales Manager", "BDC Manager", "Service Advisor"]
buyer_titles: ["VP Sales", "Director of Operations", "General Manager", "COO"]
champion_titles: ["BDC Manager", "Sales Manager", "Fixed Ops Director"]
user_titles: ["BDC Rep", "Service Advisor", "Sales Consultant"]
jd_keywords: ["inbound calls", "outbound calls", "appointment setting", "customer follow-up"]

Signal Detection Config

| Question | Options | Stored As | |----------|---------|-----------| | How should we find job postings? | LinkedIn Jobs / Indeed / Apollo / Google Jobs / Web search | `job_search_tool` | | How far back should we look? | 7 / 14 / 30 days | `lookback_days` |

Contact Finding Config

| Question | Options | Stored As | |----------|---------|-----------| | How should we find contacts at these companies? | Apollo / LinkedIn / Clearbit / Web search | `contact_tool` |

Outreach Config

| Question | Options | Stored As | |----------|---------|-----------| | Where do you want outreach sent? | Smartlead / Instantly / Outreach.io / Lemlist / CSV export | `outreach_tool` | | Email or multi-channel? | Email only / Email + LinkedIn | `outreach_channels` |

Your Company Context

| Question | Purpose | Stored As | |----------|---------|-----------| | What problem do you solve? | Email hook | `pain_point` | | Name 2-3 proof points (customers, metrics, results) | Email credibility | `proof_points` | | What's the cost comparison vs. a full-time hire? | ROI angle for outreach | `cost_comparison` | | How fast can you deploy vs. a new hire? | Speed angle | `deployment_speed` |

**Store config in:** `clients/<client-name>/config/signal-outreach.json` or equivalent.

---

Step 1: Detect Hiring Signals

**Purpose:** For each company in the input list, find active job postings that match roles your product replaces or augments.

Input Contract

companies: [
  {
    name: string          # Required
    domain: string        # Required
    industry?: string     # Optional
    size?: string         # Optional
  }
]
roles_replaced: string[]          # From config
roles_augmented: string[]         # From config
jd_keywords: string[]             # From config
lookback_days: integer             # From config (default: 14)

Process

For each company (or in batches):

1. **Search for job postings** using the configured `job_search_tool`:

• **LinkedIn Jobs:** Search `company_name + role_title` for each role