diff --git a/ROADMAP.md b/ROADMAP.md
index 1ae5c4f..4955cd0 100644
--- a/ROADMAP.md
+++ b/ROADMAP.md
@@ -84,6 +84,26 @@
 3. Email/communication integrations (optional)
 4. Granular permissions (if team grows)
 
+## Backlog (post-Phase-1 agentic)
+
+### Daily activity digest (email to the team)
+*Requested 2026-06-15. Not yet built.*
+
+Have the CRM send a **daily digest email** summarizing each registered user's activity — primarily **who emailed which investors and the substance of those emails** — to the fund principal (and eventually other admins). Scales with the synced-user count: 2 users synced today, ~5 eventually.
+
+- **Source data:** the captured email-activity already flowing through the Gmail DWD propose→approve pipeline (`backend/email_integration/`), keyed per registered user → per investor/contact. Optionally fold in other CRM activity (audit feed, automation runs, new opportunities) later.
+- **Send path is NEW capability.** Today nothing leaves the box — the system only *captures* Gmail and *creates drafts*. This needs outbound SMTP. Start9 exposes a system-wide SMTP config that services can consume; wire the digest sender to those credentials rather than hardcoding any account.
+- **Analysis runs on Spark, never Claude.** The digest is deliberately **un-anonymized** (real LP names + email substance), so any summarization/analysis must go through **Spark Control to local models** — this is the one path that intentionally bypasses the scrub→Claude→re-hydrate boundary, because keeping the substance local is the whole point. Never route digest content to Claude.
+- **Exempt from "agents draft, humans send."** That rule governs outward LP/prospect contact. This is an internal ops digest to the team's own inboxes — a different category — so an automated daily send here does not violate the draft-only guardrail. State this explicitly at build time.
+- **Scheduling:** a daily cron, naturally co-located with the existing `backend/email_integration/scheduler.py` sync cadence.
+- **Soft-delete:** every aggregate/read in the digest must filter `deleted_at IS NULL` (see the standing soft-delete rule).
+
+Open design questions to resolve before building:
+1. Recipients — just the principal, or all admins / each user gets their own?
+2. Summarization — rule-based rollup vs. Spark-LLM narrative summary of email substance?
+3. Digest granularity — per-user → per-investor threads, or a fund-wide activity roll-up?
+4. Cadence/controls — fixed daily time, opt-out, "nothing happened today" suppression.
+
 ## Definition of done for "Airtable substitute" v1
 - Team can manage all investors in one master table
 - Saved views replicate current Airtable workflows