Problem
Finance teams at pharmaceutical advertising agencies get surprised by margin-impacting developments — client procurement consolidations, regulatory shifts, competitive pipeline changes, pricing pressure — that were already signaled in publicly available data weeks or months earlier. Internal reporting catches these after they hit the P&L. Nobody was systematically mining public sources to generate predictive, finance-actionable intelligence.
Architecture
Federated swarm orchestration within Microsoft Copilot, powered by GPT-5.5 (1M-token context). Indication-specific swarms perform specialized due diligence. A central Chairman / Orchestrator synthesizes, challenges, prioritizes, tracks predictions, and feeds closed-loop learning back into the swarms.
Public Data Sources (SEC, FDA, Earnings, ClinicalTrials.gov, Press, M&A) ↓Source Monitoring Agent → Ingest, classify, log freshness, track cadence ↓Margin Lever Mapping → Map signals to shared taxonomy ↓Signal Router (IF) → Revenue at Risk / Pricing Pressure / Out of Scope ↓Analysis & Prediction ├── Finance Briefing Agent (standardize for Chairman) ├── Prediction & Confidence (hypothesis, evidence, time horizon) └── Evidence DB + Contradictory Evidence Search ↓Chairman / Orchestrator Synthesize · Challenge · Prioritize · Cross-indication detection Route to finance · Manage prediction status · Closed-loop tracking ↓Finance Outputs ├── Forecast Review Briefing (monthly, 3 days pre-meeting) ├── Revenue Risk Watchlist (account-level) ├── Pricing Pressure Watchlist └── Prediction Log (status · checkpoint · validation)
Key Design Decisions
- —Human-in-the-loop gate: Every prediction requires human validation before reaching finance workflows. The system advises; it does not act.
- —Closed-loop learning: Predictions tracked through a lifecycle — Open → Confirmed / Partially Confirmed / Disconfirmed / Expired / Superseded — with outcomes fed back into swarm weighting.
- —Anti-obsolescence doctrine: 60-day vendor/platform reassessment cycle. 12-month hard ceiling with conditional 90-day extension requiring 4 named criteria by Month 10.
- —Quantitative decision gates: 5 gates with hard pass/fail thresholds across source sufficiency, automation reduction, cross-indication comparison, governance readiness, and value-to-cost (must exceed 3x project cost).
- —Investment thesis before build: Plan requires identifying 3-5 historical margin events, quantifying dollar impact, estimating detection lead time, and calculating value of earlier detection at conservative mitigation rates.
Outcome
In MD review (Version 2.0, amended per MD feedback). Pilot scoped to defensive margin protection with reduced 4-agent set. Quantitative thresholds added to every decision gate. Investment thesis and retrospective backtest required before any build activity.
What It Proved
The plan's structure is the argument. Anyone can pitch "let's use AI for finance intelligence." The difference is showing up with source sufficiency analysis, a margin lever taxonomy, quantitative kill criteria, a budget framework with per-agent cost tracking, and a 12-month ceiling that forces a build-or-sunset decision. Project doctrine matters as much as architecture.