FeaturedAgent Teams#Multi-Agent#Orchestrator#Due Diligence#Finance#Legal#AI

Due Diligence Agent Team

An orchestrator runs a financial analyst, a legal and risk analyst, and a synthesizer to produce a structured due diligence brief.

Workflow at a glance

The full canvas, before you import it

Click any node to see its config.

#Multi-Agent#Orchestrator#Due Diligence#Finance#Legal#AI

Click a node to select it — same as the Heym editor; the panel shows its settings.

6 nodes · Free & source-available

Due Diligence Agent Team

Structure the first pass of any deal review. An Orchestrator runs a Financial Analyst, a Legal and Risk Analyst, and a Diligence Synthesizer who combines their findings into a single brief with strengths, red flags, and open questions for the deal team.

What this workflow does

  1. dealInput holds the target company, deal context, and known facts
  2. Orchestrator delegates to the sub-agents and returns the diligence brief
  3. FinancialAnalyst reviews the financial picture, unit economics, and questions
  4. LegalRiskAnalyst flags legal, compliance, and operational risks to investigate
  5. DiligenceSynthesizer combines both into strengths, red flags, and open questions
  6. diligenceBrief surfaces the result

Use cases

  • A fast first-pass diligence brief before a deeper review
  • Combining financial and legal risk angles in one pass
  • Generating a focused open-questions list for the data room

Setup

Add an LLM credential to all four Agent nodes. Enter the deal context and known facts, then run. This is analysis support for a human deal team, not investment, legal, or accounting advice — verify every finding against primary documents.

How to import this template

  1. 1Click Import → Copy JSON on this page.
  2. 2Open your Heym and navigate to a workflow canvas.
  3. 3PressCmd+V/Ctrl+V— nodes appear instantly.
  4. 4Add your API keys in the node config panels and click Run.
More workflow templates
View all templates
Heym
incident analysis · production AI
Observed across 100s of AI rollouts

AI workflows don't fail because of prompts.
They fail because of orchestration.

symptom · glue code01
5 tools
Scripts, vector DB, approval bot, tracing, browser runner — none of them talk.
symptom · visibility02
~0%
Observable behavior across the stack. Debugging is guesswork.
with heym · one runtime
1 canvas
Agents, RAG, HITL, MCP, traces & evals. Self-hosted. Observable.
AI-Native RuntimeProduction-Grade
github.com/heymrun/heym