AI AGENTS

Weekly Vendor-Landscape Refresh with Change Detection

On a weekly schedule, an agent re-researches a tracked vendor category, diffs it against last week's matrix, and emails a summary of new entrants, pricing changes, and shifts…

CategoryAI Agents
Enginesim
Difficultyadvanced
Triggerschedule
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule fires for each tracked category
  • ActionFan out fresh research across Exa and BraveExa
  • ActionRebuild the sourced matrixOpenAI
  • LogicDiff against last week's matrix for changes
  • OutputEmail the change summary with sourcesGmailGmail

What it does

Each week the agent re-runs research on a category you track, rebuilds the sourced matrix, and compares it to the prior version. It surfaces what changed — new vendors, pricing moves, feature launches, acquisitions — and emails a concise change report so you stay current without re-reading the whole landscape.

When to use it

When you own a buying decision that stays open for weeks or monitor a competitive category. Best for keeping a living vendor matrix fresh and catching market moves before they affect a deal.

How it works

  1. 1A weekly schedule triggers the run for each tracked category.
  2. 2The agent fans out queries to Exa and Brave Search for the current state.
  3. 3An OpenAI step rebuilds the sourced matrix from fresh results.
  4. 4A diff step compares the new matrix against the stored previous version and isolates changes.
  5. 5If changes exist, the agent emails a summary of new entrants, pricing shifts, and ranking moves with source links.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect ExaNeural search across the web.
  2. 2
    Connect Brave SearchWeb, news, image, video search.
  3. 3
    Connect OpenAIModels, embeddings, files.
  4. 4
    Connect GmailRead, draft, send, label.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    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.