Nathan Lara
← Projects PwC Capstone × Fordham — Jan – May 2026

M&A Deal Intelligence

A fully deployed M&A intelligence platform for PwC: an agentic pipeline that monitors 51 live sources every day, extracts structured deal records, enriches them with SEC financials, and serves analyst-ready briefs through a production dashboard.

Role
AI Agent Developer
Client
PwC Capstone × Fordham
Timeline
Jan – May 2026
Status
Deployed · Railway + Vercel
Dealflow — the PwC M&A analyst dashboard
Dealflow — the analyst dashboard (Next.js): daily-refreshed deal table, confidence scoring, a source-drift monitor, and pipeline run status.
01 — Overview

This is a production M&A intelligence platform built as a PwC capstone. An LLM orchestration agent decides which of 51 live sources to crawl on each run, extracts structured deal records from unstructured filings and press wires, enriches them with SEC XBRL financials, and surfaces the results through a dashboard analysts can filter, brief, and export.

The goal wasn't a demo. It was a system that runs on a daily schedule, persists real data — 176 deals in live storage — and replaces a manual research workflow with a self-service intelligence layer.

02 — The business problem

Tracking M&A activity is a grind of manual sourcing: analysts monitor SEC EDGAR, press releases, law-firm and PE-firm announcements, and advisory wires, then hand-copy deal attributes into spreadsheets with inconsistent formatting.

  • The user — deal analysts who need timely, structured M&A intelligence without spending hours sourcing it.
  • Why it matters — deal signals are time-sensitive, and manual extraction is slow, inconsistent, and doesn't scale across dozens of sources.
  • The gap — no persistent, queryable layer; every question meant a fresh, ad-hoc research request.
03 — The solution

An end-to-end agentic pipeline with three moving parts: source selection, structured extraction, and a self-service dashboard.

  • Agentic source selection — the LLM reads live source yield scores and chooses which of 51 sources to crawl each run, with targeted 8-K section parsing and MD5 deduplication.
  • Structured extraction & enrichment — a 15-field DealRecord extracted with source-specific GPT-4o prompts and Pydantic typing, enriched via the SEC XBRL API for target/acquirer financials and EV multiples.
  • Confidence-based persistence — a daily APScheduler cron with upsert logic where higher-confidence re-extractions overwrite lower-confidence records; same-confidence runs only fill null fields.
  • Analyst dashboard — filterable deal tables, per-deal LLM one-pager briefs, EV/EBITDA multiples, sector analysis, deal comparison, a 7-day morning brief, and Google Sheets export.
04 — Architecture
01 · Ingest 51 Live Sources
SEC EDGAR (8-K)press wires · RSSlaw / PE / IB sitesAI search APIs
raw feeds
02 · Orchestrate LLM Selection Agent
LangChainreads yield scorestargeted 8-K parseMD5 dedup
candidate deals
03 · Extract + enrich Structured Deal Extraction
GPT-4o promptsPydantic 15-field recordSEC XBRL financialsEV multiples
typed DealRecords
04 · Persist Storage + Scheduler · Railway
SQLite (confidence upsert)ChromaDBAPScheduler daily cron
6 REST endpoints
05 · Serve Analyst Dashboard · Vercel
Next.js 16deal tables · filtersLLM one-pager briefsEV/EBITDA · export
05 — Challenges
  • Inconsistent sources. 51 sources meant 51 formats. Source-specific prompt templates plus keyword pre-filtering and exponential backoff kept extraction reliable without hand-tuning per site.
  • Idempotent daily runs. Re-crawling the same deals daily risked overwriting good data with worse. Confidence-based upsert logic made re-runs safe — better data wins, weaker data only fills gaps.
  • Financial grounding. LLM-extracted deal terms needed hard numbers. SEC XBRL enrichment attached real financials and computed EV multiples alongside the model's output.
06 — Lessons & what's next
  • An "agent" earns its keep when it makes a real decision — here, which sources are worth crawling — not when it just wraps a prompt.
  • Confidence scoring isn't just a quality signal; it's the control logic that makes a daily pipeline safe to re-run.
  • Next: alerting on high-probability deal-stage transitions, and an analyst feedback loop that tunes extraction confidence over time.
PythonGPT-4oLangChainFastAPINext.jsChromaDBSEC XBRL
Next case study
AEGIS →
Live app ↗