MARKET RESEARCH
Flag New & Changed 10-Q Risk Factors with Email Alerts
On each new competitor 10-Q, extract the risk-factor section, detect language added or removed versus the prior filing, log it to Notion.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled check for new 10-Q filings
- ActionFetch filing and isolate risk-factors sectionFirecrawl
- ActionClassify risk items as added, removed, or reworded vs priorOpenAI
- ActionLog all risk changes to Notion risk-watch databaseNotion
- LogicDetect newly added material risks
- OutputEmail alert to the watch listGmail
What it does
Focuses narrowly on the risk-factors section of competitor 10-Qs — the place where companies quietly disclose new threats. It compares each new filing's risk language to the last one, records every addition and removal in a Notion risk-watch database, and sends a targeted email when a genuinely new material risk shows up.
When to use it
Use it when emerging-risk disclosure is your early-warning signal — regulatory exposure, supply concentration, litigation, or new competitive threats a rival is forced to name. Suited to risk, legal, and strategy teams who want to be told only when something new appears.
How it works
- 1A scheduled check detects new 10-Q filings for tracked tickers.
- 2Firecrawl fetches the filing and the workflow isolates the risk-factors section.
- 3OpenAI compares it against the prior filing's risk language and classifies each item as added, removed, or reworded.
- 4Every change is logged as a row in the Notion risk-watch database.
- 5A logic gate checks for newly added material risks; when found, an email alert goes out to the watch list.
Set it up
What you configure once, before turning it on.
- 1Connect FirecrawlCrawl, scrape, structured extract.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect NotionPages, databases, comments.
- 4Connect GmailRead, draft, send, label.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Market Research workflows
Hiring Surge Detector with Slack Alert
Detects when a target account's open-role count jumps above its recent baseline and posts a ranked Slack alert to the GTM channel so reps can act on a company that is clearly…
Tech-Stack Shift Inference from Job Descriptions
Reads new job descriptions for target accounts, uses an LLM to extract named technologies and infer stack changes.
Enrich Inbound Accounts with BigQuery Firmographics and Score Fit
When a new account row lands in Airtable, joins it against BigQuery public business datasets to attach firmographic attributes.
Blend BigQuery TAM with Live Competitor Signals into a Notion Brief
On demand, sizes a chosen segment from BigQuery public data, gathers current competitor signals via Brave Search, and synthesizes a one-page market brief into Notion.
Allocate Sales Territory TAM from BigQuery Geo Data to HubSpot
When triggered by a webhook, queries BigQuery public ZIP-level business data to compute TAM per sales territory.
Discover Adjacent Segments from BigQuery and Rank Expansion Bets
On a schedule, scans BigQuery public industry data for fast-growing NAICS sectors adjacent to your core segments, scores them as expansion bets.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.