MARKET RESEARCH

Agent-driven earnings deep-dive on demand

A chat-triggered research agent that, given a competitor and quarter, autonomously finds the transcript, reads it against the prior call, investigates any guidance change it spots.

CategoryMarket Research
Enginepaperclip
Difficultyadvanced
Triggerchat
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerChat request for competitor + quarter
  • ActionAgent searches for current + prior transcriptsExa
  • ActionAgent scrapes pages as neededFirecrawl
  • LogicAgent reasons over calls, decides follow-up research
  • OutputReturn cited deep-dive in chatOpenAI

What it does

Hands the analysis to an agent rather than a fixed pipeline. You ask in chat about a competitor's latest quarter; the agent decides what to gather, retrieves the current and prior transcripts, reads them, and when it notices a guidance change it digs further, pulling supporting context to explain why management moved the number. It returns a written deep-dive with citations and its chain of reasoning.

When to use it

Use it for the open-ended questions a rigid flow can't answer, like "did they really walk back the margin target, and what's their stated reason?" The agent adapts its research path to what it finds.

How it works

  1. 1An operator asks about a competitor + quarter in chat.
  2. 2The agent searches with Exa to locate current and prior transcripts.
  3. 3It scrapes the relevant pages via Firecrawl as it needs them.
  4. 4The agent reasons over both calls, identifies guidance shifts, and runs follow-up searches to explain each one.
  5. 5It composes a cited deep-dive and returns it in the chat thread.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect ExaNeural search across the web.
  2. 2
    Connect FirecrawlCrawl, scrape, structured extract.
  3. 3
    Connect OpenAIModels, embeddings, files.
  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.