SEC-Filing Event Outreach
A material change in business is the most defensible outbound trigger — sequence it inside the 90-day window with a hook recipients can verify themselves.
Sample output for this workflow will appear here once it is captured.
Run the workflow in Claude, ChatGPT, or HG Insights Playground using the buttons below to see real output.
Overview
Surface accounts with a material 8-K event (M&A, exec change, restructuring, guidance shift) in the last 90 days — a public, defensible trigger for outbound. Returns the event, the firmographic context, and an opening hook that ties the filing to your product per `opening-line-discipline`.
Use cases
Outbound that quotes a public filing
Your SDR runs this on the public-company subset of their list and gets accounts with material 8-K events in last 90 days — exec changes, M&A, restructuring. The hook quotes the filing's item number and date so recipients can verify the citation in EDGAR. This is the message that gets forwarded inside the buying team.
On-topic discipline that doesn't waste a sequence slot
Not every 8-K is a buying signal. A routine dividend declaration is not a tooling decision. The workflow drops off-topic filings per the `sdr-trigger-prioritization` rubric, so the SDR doesn't open with a filing that the recipient will immediately read as 'they didn't read it either'.
View workflow prompt
# SEC-Filing Event Outreach
## Parameters
- `{{ticker_domain_pairs}}` *(required)* — Comma-separated `ticker:domain` pairs. Both halves are required — `sec_filing_section` needs the ticker; `company_firmographic` and `company_fai` need the domain. SDR managers typically pull both from CRM.. Example: `CRM:salesforce.com,NOW:servicenow.com,DDOG:datadoghq.com`
- `{{your_product}}` *(required)* — Your product or category — anchors the connection to the filing event. Example: `ServiceNow`
- `{{event_within_days}}` *(required)* — 8-K lookback window in days (default 90 per `hg-recent-signals`). Example: `90`
## Purpose
You are an SDR working public-company prospects against {{your_product}}. `sec_filing_section` is a per-ticker lookup that requires BOTH `companyTicker` AND an explicit `section` code; the 8-K item codes that signal material events are `1.01`, `2.01`, `5.02`, `7.01`, and `8.01`. Surface accounts whose recent 8-K hits one of those sections inside {{event_within_days}} days, contextualize with firmographic + function data via the domain half of the input pair, and return rows whose opening hook ties the filing to {{your_product}} per [`opening-line-discipline`](https://phoenix.hginsights.com/gtm/skills/opening-line-discipline).
## Process
1. **Filing scan** — for each `ticker:domain` pair in {{ticker_domain_pairs}}, iterate over the 8-K item codes (`1.01` Material Agreements, `2.01` Asset Acquisitions, `5.02` Exec Changes, `7.01` FD Disclosures, `8.01` Other Material Events). Call `sec_filing_section` with `companyTicker: <ticker>`, `filingType: "8-K"`, and `section: <one of 1.01/2.01/5.02/7.01/8.01>` per pass. Capture filing date, section item, and the material event text. Keep rows whose filing date falls in the last {{event_within_days}} days. Fall back to `sec_full_text_search` for keyword-driven discovery if the per-section scan returns empty.
2. **Confirm on-topic** — apply the `sdr-trigger-prioritization` 8-K-on-topic check: a CFO-departure 8-K is NOT a buying signal for a network-security product. Drop off-topic rows.
3. **Firmographic context** — `company_firmographic` per survivor's domain (taken from the input pair) for industry / employee band / revenue band.
4. **Function context** — `company_fai` per survivor's domain (`products: [{{your_product}}]` or category-matching products) for `departmentUsageShare` (drives contact-function selection).
5. **Contact pass** — `contact_search` per survivor for the suggested function's senior titles. No enrichment in this workflow (8-K named officers are usually public; surface those by name).
## Output Format
- `# 📰 SEC-Filing Event Outbound`
- `## Ranked accounts` — table: rank | ticker | company | filing date | event type | industry | employee band | suggested contact | one-line hook
- Hook quotes the filing event by name + date + ties to {{your_product}} (e.g., "Q3 8-K Item 5.02 announced new CIO Sarah Lin starting June 1 — the kind of leadership transition that puts {{your_product}}'s consolidation agenda back on the agenda")
- Per-row citation: `[sec_filing_section]` for the event, `[company_firmographic]` for industry/employees
## Quality Checklist
- Every row's filing is inside {{event_within_days}} days AND the event is on-topic for {{your_product}}
- The hook quotes the filing item number and date — not a paraphrase. Recipients can verify the citation in EDGAR.
- Off-topic 8-Ks (e.g., routine board appointments, dividend declarations) are dropped, not retained for padding
- Firmographic columns use actually-exposed fields (industry, employee band, revenue band) — no fabricated "market cap" or rank fields