Decision · What each agent found
What each agent found, eleven agents in the order they ran, on illustrative data
What each agent found on Project Alder (illustrative). The eleven agents in order, each with its headline, whether it reasoned with Claude, and its status — ok, prepared or skipped.

A data room tells you what the seller chose to put in it. Company intelligence tells you what the world says: the subsidiaries a policy may need to name, who leads the business, what is happening in its industry, and whether there is adverse news the schedules don’t mention.

Five questions, each answered with a date

Playbook questionFrom InsightPulse
What does the company profile say?Sector, revenue, employees, parent
Which subsidiaries must the policy name?The corporate hierarchy
Who leads the target; any recent change?Leadership with since-dates
What are the industry’s trends?Industry notes and metrics
Is there adverse news?News with category and date
sequenceDiagram participant IA as Intelligence agent participant P as InsightPulse participant M as Claude participant F as Findings IA->>P: Company 360 for the target key P-->>IA: Profile, subsidiaries, leaders, industry, news, as of date IA->>M: Facts cited Pulse, as of M-->>IA: Answers per question IA->>F: Intelligence findings, adverse news as red flag

On Project Alder (illustrative), InsightPulse reports a security incident at the UK subsidiary in August. The intelligence agent turns it into a red-flag finding cited “Pulse: news, as of” its date — and the quote agent later uses it to explain why a data privacy exclusion matters on this deal.

Findings
Findings to review with severity, kind, citations and Approve, Change, Reject
Findings (illustrative). A missing schedule, a cyber diligence gap and disclosed known issues — each with severity, kind, the page it cites, the agent's reading and Approve, Change or Reject.
flowchart LR N["Pulse news:
UK subsidiary incident"] --> RF["Red flag finding"] RF --> QA["Quote agent: data privacy
exclusion matters here"] RF --> UW["UW call: expect
the question"] RF --> SUB["Submission: company
and industry section"]

Without InsightPulse

With no Pulse endpoint configured, an illustrative stand-in answers for the demo book, and every fact still carries “Pulse (illustrative)” and a date. In production the lookup is signed and the as-of date is Pulse’s own.

Keep reading