MARKET RESEARCH

Backfill a New Competitor's Theme History

When you add a competitor to your tracked watchlist, scrapes their last four earnings-call transcripts, extracts themes from each.

CategoryMarket Research
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerCompetitor added to watchlistCodaCoda
  • LogicResolve last four transcript URLs
  • ActionScrape the four historical transcriptsFirecrawl
  • ActionExtract themes per quarterOpenAI
  • OutputBatch-write history rows to Coda boardCodaCoda

What it does

Gives a freshly added competitor instant history on your trend board. The moment a new name is added to the watchlist, it retrieves their last four earnings-call transcripts, runs each through theme extraction, and writes one row per quarter into Coda — so the new competitor isn't a blank column until their next call.

When to use it

Use it whenever your tracked set changes: a new public rival emerges, a competitor IPOs, or you expand coverage into an adjacent segment. Saves an analyst from manually digging up and tagging a year of past calls.

How it works

  1. 1An event trigger fires when a competitor is added to the watchlist table.
  2. 2A logic step resolves the company's last four transcript URLs from its investor-relations page.
  3. 3Firecrawl scrapes each of the four transcripts.
  4. 4OpenAI extracts themes, sentiment, and quotes per quarter using the same taxonomy as the live tracker.
  5. 5The flow batch-writes the four quarters of theme rows into the Coda trend board, tagged by fiscal period.

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.