MARKET RESEARCH

Quarter-over-Quarter Product Mention Diff Tracker

On a schedule, extracts every product named in a competitor's latest earnings call, compares it against the prior quarter stored in Airtable.

CategoryMarket Research
Enginesim
Difficultyadvanced
Triggerschedule
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerMonthly schedule fires
  • ActionFetch latest transcriptsFirecrawl
  • ActionExtract normalized product mentionsOpenAI
  • LogicDiff against prior-quarter baselineAirtableAirtable
  • OutputWrite deltas and update baselineAirtableAirtable

What it does

Tracks how a competitor's product narrative changes between earnings calls. It pulls all product and feature mentions from the newest transcript, diffs them against the last quarter's record in Airtable, and writes the deltas: which products appeared for the first time and which quietly disappeared from the script.

When to use it

Use it when you want to spot a competitor's emphasis shifts and roadmap signals over time, for example a product that suddenly gets called out (a new bet) or one that stops being mentioned (possible deprioritization). Built for product and competitive-intel analysts.

How it works

  1. 1A monthly schedule starts the run.
  2. 2Firecrawl retrieves the latest transcript for each tracked competitor.
  3. 3OpenAI extracts a normalized list of product and feature names with mention counts.
  4. 4A logic step diffs the new list against the prior-quarter record pulled from Airtable.
  5. 5Airtable writes a delta record (new mentions, dropped mentions, count changes) and updates the baseline for next quarter.

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 AirtableBases, tables, views, 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.