System design: a financial research assistant with Stakeholder Communication

Quick answer

Treat stakeholder communication as a first-class product surface of the financial research assistant, not a side chat. Map audiences (PMs, analysts, risk/compliance, eng, execs) to what each needs: decision brief, evidence pack, risk flags, or status. Design APIs for audience-aware summaries, citation-backed claims, decision logs, and approval workflows. Store source docs, retrieval traces, and who-said-what for audit. Scale with async brief generation and cached packs for recurring meetings. Secure with role-based views, redaction of material non-public info, and no silent tool side effects. Observe delivery, open rates, dispute rate, and citation click-through. Roll out canary by desk or fund, with human review gates before auto-send.