Active · MemoPop WG
Part of: Data-Driven Venture · Hack & Ship
Why this exists
The investment memo has barely changed in 30 years: 8–15 pages, written after diligence, read once at IC, then filed. We think it should be:
Drafted during diligence, not after — so the act of writing surfaces gaps in the work.
Structured for both humans and machines — same content, queryable later (e.g., "show me every memo where we flagged regulatory risk").
Traceable — every claim links back to a source artifact (call notes, model output, founder reference).
What we're building
A memo template that's structured enough to be parsed, loose enough to be readable.
An agentic loop that ingests diligence artifacts (call transcripts, data room files, model outputs) and produces draft memo sections.
A queryable memo archive — not RAG over PDFs, but structured queries over a memo collection.
Working group expectations
Bring a memo in flight, real or sanitized. Generic templates aren't enough to find the rough edges.
Be willing to share what you'd actually write to your IC. The point is partner-meeting-grade output.
Open questions
How much structure is too much? At some point a structured memo becomes a form-fill exercise.
What's the right relationship between a memo and a thesis document — same artifact or sibling artifacts?