/news-signal-outreach

name: news-signal-outreach
version: 1.0.0
description: >
  End-to-end news-triggered signal composite. Takes any piece of news — an article,
  LinkedIn post, tweet, announcement, event, trend, regulation, product launch,
  acquisition, layoff, expansion, or any other public event — and evaluates whether
  the companies or people mentioned are ICP fits. If yes, identifies the connection
  between the news and your product, finds the right people to contact, and drafts
  personalized outreach using the news as the hook. Tool-agnostic. Accepts both
  company-level and person-level news triggers.

  AUTO-TRIGGER: Load this composite whenever a user shares a URL (LinkedIn post,
  article, tweet, blog post) or mentions a company/person they "came across",
  "saw", or "found" from any external source and asks about relevance, fit,
  ICP match, or whether to reach out. The user does NOT need to explicitly say
  "outreach" — any signal evaluation request from an external source triggers this.
tags: [outreach]

graph:
  provides:
    - icp-qualified-targets         # Companies/people from the news that fit ICP
    - relevance-angles              # How the news connects to your product
    - contact-list                  # People to reach out to
    - personalized-email-sequences  # Outreach drafts using the news as the hook
  requires:
    - news-input                    # The news item(s) — URL, text, or structured data
    - your-company-context          # What you sell, ICP, proof points
  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, contact-finding, email-drafting]

News Signal Outreach

The catch-all signal composite. Every other composite handles a specific signal type (funding, hiring, leadership change, champion move). This one handles **everything else** — any piece of news or public event that could create a reason to reach out.

A regulation change. A product recall. A competitor acquisition. A market expansion. A layoff. An earnings miss. A new partnership. An industry report. A conference keynote. A viral LinkedIn post. Any external event that shifts a company's priorities, creates urgency, or opens a window for your product.

**Why this composite exists:** The world generates an infinite stream of potential outreach triggers. The four structured signal composites handle the most common patterns. This composite handles the long tail — the unpredictable, opportunistic moments that often produce the best outreach because nobody else is sending a templated sequence about them.

When to Auto-Load

Load this composite when ANY of these are true:

• User shares ANY URL (LinkedIn post, article, tweet, blog, news) and asks about a company or person mentioned in it
• User says "came across", "saw this post", "found this article", "check this out", "is this relevant", "is this company a fit", "should we reach out"
• User mentions a company or person they discovered from an external source (social media, news, conference, podcast, newsletter) and asks about relevance or fit
• User asks "can we reach out to anyone based on this?"
• User says "check if this news is relevant to our prospects", "news-based outreach", "trigger-based outreach"
• User has a list of companies and wants to check recent news for outreach angles
• The news doesn't fit neatly into funding, hiring, leadership change, or champion move categories
• An upstream workflow surfaces a news item that needs evaluation

**Key principle:** If the user shares an external signal (URL, post, article, mention) and asks ANY question about the companies/people in it — load this composite. Don't wait for the word "outreach." The composite handles both evaluation-only (Steps 1-3) and full outreach (Steps 1-6).

Input Flexibility

This composite accepts three input modes:

| Mode | Input | Example | |------|-------|---------| | **News → Companies** | A news item. Extract companies/people mentioned, qualify them. | "Here's an article about new FDA regulations on telehealth" | | **Companies → News** | A list of companies. Find recent news about them, evaluate relevance. | "Check these 50 companies for any news we can use as an outreach angle" | | **Person → News** | A person or list of people. Find recent news about them or their company, evaluate relevance. | "Check if any of these prospects have been in the news" |

---

Step 0: Configuration (One-Time Setup)

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

ICP Definition

| Question | Purpose | Stored As | |----------|---------|-----------| | What does your company do? (1-2 sentences) | Relevance matching | `company_description` | | What problem do you solve? | Connection angle identification | `pain_point` | | What industries do you sell to? | ICP filter | `target_industries` | | What company sizes? | ICP filter | `target_company_size` | | What geographies? | ICP filter (optional) | `target_geographies` | | Any disqualifiers? | Hard no's | `disqualifiers` | | Who are your buyers? (titles) | Contact finding | `buyer_titles` | | Who are your champions? (titles) | Contact finding | `champion_titles` | | Who are your users? (titles) | Contact finding | `user_titles` |

Your Company Context

| Question | Purpose | Stored As | |----------|---------|-----------| | What specific outcomes does your product deliver? | Relevance angle building | `product_outcomes` | | Name 2-3 proof points (customers, metrics) | Email credibility | `proof_points` | | What categories of news are most relevant to your product? | Helps prioritize | `relevant_news_categories` |

**Examples of `relevant_news_categories`:**

# For a cybersecurity product:
relevant_ne