Skip to main content
§ Product

Fund Communications Engine

An LLM-and-templating layer covering the fund's recurring and one-off communications — investor updates, LP letters, fundraise materials (data room, pitch deck) — drafted from portfolio data with the fund's voice and finalized by the IR team.

Engagement
6–10 week build · ongoing operation
Built for
IR teams · Fundraise leads · GP principals
§ Problem

Quarterly investor updates, annual LP letters, fundraise data rooms and pitch decks for the next fund — all of it written from scratch, all of it pulling the same portfolio data via the same person-week assembly process every quarter.

What this is

The fund's communications surface, automated where the work is mechanical. Three planes:

  • Recurring communications. Quarterly investor updates, annual LP letters, capital-call notices. Drafted on cadence, finalized by IR.
  • One-off communications. Fundraise pitch decks, data-room assembly for prospective LPs, ad-hoc partner-letter generation. On-demand.
  • Personalization layer. Per-LP framing where the LP base is segmented (institutional vs. family-office LPs may receive different framings of the same underlying data).

How it's built

Same architecture as the FO Family Report Drafter — fine-tuned LLM for voice, structured templating for numbers, per-recipient parameterization. The differences are domain: VC track-record artifacts (IRR by vintage, deal-by-deal returns, attribution analysis) instead of FO multi-entity accounting.

What you get

  • The fine-tuned drafting model deployed to your fund.
  • Templates for the canonical communication types.
  • Per-LP parameterization configured to the LP base.
  • The IR review UI with markup-and-finalize workflow.
  • Fundraise data-room assembly and refresh.
§ How we engage

Engagement is shape, not list.

Length and price are functions of the data and the destination. The shape below is the typical engagement.

Length
6–10 week build · ongoing operation

Scoped during the discovery call against the actual data and the operation it integrates with.

Lead
Bogdan

Principal engineer. Architecture and most code ships through one keyboard.

Cadence
Async, weekly

Written updates between, calls when the decision needs the room.

Bar
Production

Async correctness, capacity under burst, observability at every boundary.

§ Questions

What buyers ask about this one.

  • How does this handle the fundraise data room specifically?

    Data-room assembly is the most labor-intensive piece — track record summaries per portco, deal-by-deal returns analysis, attribution decomposition, comparable-fund benchmarking. The engine pulls from the fund's accounting and portfolio data, generates the data-room artifacts to a documented template structure, and refreshes them through the fundraise process.

  • What's the voice-preservation approach?

    Fine-tuned on the fund's historical communications — typically two-to-three years of quarterly updates and annual letters. The drafts read in the fund's voice; the IR team finalizes the strategic framing.

  • Does it hallucinate portfolio numbers?

    Numbers come from the data layer (Portfolio Pulse Dashboard, fund accounting), inserted via structured templating. The LLM writes the prose; the LLM doesn't generate the financials.

  • How does it handle the 'good news' bias problem in investor updates?

    Configurable per fund. Some IR teams want neutral framing; others want the partner-tonality preserved. The engine generates a neutral-baseline draft and a partner-tonality draft side-by-side; the IR team chooses which to ship.

  • Pricing?

    Scoped to communication cadence and the breadth of document types covered. Discovery call covers both.

§ The next step

If the deliverable matches the gap, the next step is one call.

We'll scope length and price against your data and the operation it integrates with. No retainer, no fishing.

Bogdan and team · async-first · OP—2026