MARKET RESEARCH
Scrape earnings transcripts and log competitor strategy signals to Coda
Scrapes a newly published competitor earnings-call transcript, extracts strategic signals (pricing moves, new products, market entries, guidance changes), and appends them…
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled run after competitor earnings date
- ActionScrape transcript page to markdownFirecrawl
- ActionExtract strategy signals as tagged JSONOpenAI
- LogicDrop low-confidence or off-topic signals
- ActionAppend each signal as a tracker rowCoda
- OutputWrite run summary with row countCoda
What it does
Turns a long, noisy earnings-call transcript into a handful of clean, comparable rows in your competitor tracker. Each signal captures the competitor, theme, the exact quote, and a strategic interpretation — so analysts read structured intelligence instead of re-reading transcripts.
When to use it
Use it when you maintain a competitive-intelligence tracker and want every competitor earnings call distilled the same way, every quarter, without manual note-taking. Best for teams covering 5-20 public competitors where consistency matters more than depth.
How it works
- 1A scheduled run fires after a competitor's known earnings date.
- 2Firecrawl scrapes the investor-relations transcript page and returns clean markdown.
- 3OpenAI reads the transcript and extracts a JSON array of signals, each tagged with a theme (pricing, product, geo, guidance, hiring) and a confidence score.
- 4A filter drops low-confidence or off-topic items so the tracker stays signal-dense.
- 5Each surviving signal is appended as a row to the Coda competitor tracker with quote, theme, and interpretation.
- 6A short summary line is written back to confirm the run and row count.
Set it up
What you configure once, before turning it on.
- 1Connect FirecrawlCrawl, scrape, structured extract.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect CodaDocs, packs, automations.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Market Research workflows
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.
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.
Weekly Hiring-Intel Briefing for GTM
An agent reviews the week's accumulated hiring signals across all target accounts, writes a narrative briefing that infers each account's likely initiatives.
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.