MARKET RESEARCH

Earnings Transcript Harvester to Coda Tracking Brief

On a schedule, crawls competitor earnings-call transcripts, extracts strategy shifts and product mentions, and writes a structured row into a Coda tracking doc with citations.

CategoryMarket Research
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule fires
  • ActionCrawl IR transcript pagesFirecrawl
  • ActionExtract signals to structured JSONOpenAI
  • LogicSkip competitors with no new transcript
  • OutputAppend cited row to tracking briefCodaCoda

What it does

Keeps a living competitive-intelligence brief in Coda by mining the latest competitor earnings-call transcripts. Each run pulls the freshest transcripts, isolates statements about strategy changes, pricing moves, and named products, and appends a clean, cited row to your tracking table.

When to use it

Run it during earnings season (or weekly) when you track 3-10 public competitors and want a single source of truth instead of reading 40-page transcripts by hand. Ideal for product marketing, strategy, and competitive-intel teams who need durable, searchable records.

How it works

  1. 1A weekly schedule fires the run.
  2. 2Firecrawl crawls each competitor's investor-relations transcript page and returns clean text.
  3. 3OpenAI extracts strategy shifts, product mentions, and guidance into a structured JSON object with verbatim quotes.
  4. 4A logic step drops any competitor where no new transcript was found since the last run.
  5. 5Coda appends one row per competitor (company, quarter, signals, quotes, source URL) to the tracking brief.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect FirecrawlCrawl, scrape, structured extract.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect CodaDocs, packs, automations.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.