Automation · Playbook 02

Generate investment committee brief.

Produce a partner-ready IC brief from a single CRM record without re-keying any data.

Diligence

Prompts used

The exact LLM prompts this automation calls — system instructions and user messages, in execution order, with the model each step uses.

  • Investment Committee Brief
    8 prompts

    Two-pager for early-diligence IC review. Pulls a corpus of internal memos and call notes from the firm's document store and fans out to section drafters plus a structured properties extractor for the cover.

Reference build

A working reference build that runs in production. Once a company is in early diligence and the firm has a working corpus on it — past memos, call notes, fact sheets — a partner adds the record to a "Generate IC Brief" list and, minutes later, a structured two-pager lands on the company folder and in the IC's inbox. Same orchestration spine as the Pre-Meeting Brief; the difference is that this one is grounded in internal material, not public search.

We document the flow in tooling-neutral terms. The vendors below are our choices; the same pattern runs cleanly on any combination listed in the swap matrix.

Flow
01 · Trigger
New entry in 'Generate IC Brief' list
CRM list entry — partner-initiated
02 · Gather corpus
Pull pipeline metadata + company record + semantic-search hits
One read against the notes DB, one against the CRM, one against the company document folder
03 · Fan-out
Parallel section drafters + properties extractor
One LLM call per section, run concurrently against the assembled corpus; one structured-output call extracts the cover fields
prompt
Properties (HQ, employees, capital raised, opportunity)
prompt
Overview & key points
prompt
History & funding
prompt
Products & value proposition
prompt
Market overview & competitive landscape
prompt
Go-to-market & unit economics
prompt
Preliminary investment thesis
prompt
Preliminary risks / key questions
04 · Assemble document
Render two-pager from template
Drafted sections + extracted properties pipe into a docx/PDF template — consistent IC formatting every time
05 · Write-back
Upload PDF to company folder
The brief lands in the same folder the corpus came from, so the next pass can find it too
06 · Route & notify
Branch on deal owner → email partner
Owner-aware routing so the brief lands in the right inbox, not a shared firehose
Partner APartner BPartner CPartner DPartner EPartner F

Prompts that power this build

The build (flow, swap matrix, vendors) lives here. The actual production prompts live in the Prompt Library, grouped under one entry per workflow and broken out by section inside. Section drafters share a common structure (senior-investor persona, plain language, no subsections, fixed paragraph budget) and one structured-extraction prompt populates the cover-page properties.

Swap matrix

The flow above is described in roles, not vendors. Every layer is replaceable without touching the others, because the orchestrator owns the wiring. The same ICB pattern runs whether your corpus lives in SharePoint, Drive, or Notion, and whether your retrieval is Glean, Hebbia, or in-house.