Dock for investors is a workspace where deal memos, portfolio-monitoring agents, and LP-update threads carry attribution. A diligence agent drafts a memo from Affinity and Pitchbook. A monitoring agent reads Carta cap tables and flags dilution. An IR agent synthesizes the LP letter from portfolio updates. Each artifact lands in a Dock row with the partner who signed off and the timestamp. The CRM stays the CRM. The cap table stays the cap table. Dock holds the interpretation.
The architectural split
Affinity, Carta, Notion, Pitchbook, and AngelList stay the system of record for raw investor data: relationship signals, cap tables, portfolio docs, comps, syndicate rosters. Dock is the system of record for what the AGENT INTERPRETS from that data: the prioritized memo queue, the monitoring decision, the partner's sign-off, the audit log. Each Dock row carries a pointer back to the platform record (affinity_organization_id, carta_company_id), the agent identity, the decision, the reviewer, and the timestamp. The agent re-fetches platform data via fresh API reads when it needs current state. Dock holds the persistent interpretive layer that survives across partner meetings and quarter ends.
One surface: the deal-and-portfolio table
A single Dock table tracks active diligence and live portfolio. The agent writes proposed rows. A partner approves.
| company | stage | affinity_organization_id | carta_company_id | agent_recommendation | rationale | partner | status |
|---|---|---|---|---|---|---|---|
| Lattice Robotics | seed diligence | aff_88312 | (none yet) | advance to partner meeting | warm intro from 2 LPs, Pitchbook comps at higher ARR multiple | priya@ | approved |
| Stellate Health | portfolio Q2 check | aff_55190 | carta_co_4421 | flag dilution: option pool refresh cuts ownership 1.8 pts | board-approved refresh in cap-table pull | govind@ | reviewing |
| Forecourt AI | LP update line item | aff_71044 | carta_co_3107 | include in winners section | ARR doubled QoQ per founder update | priya@ | approved |
A partner viewing the Stellate row clicks through to the Carta snapshot and the Affinity thread. The decision (advance, flag, include) is the Dock-native field.
A worked workflow
IC meeting is Thursday. Tuesday morning the diligence agent reads Affinity for new inbound, pulls Lattice Robotics from Pitchbook, and drafts a one-page memo as a Dock doc row. It writes the recommendation (advance) and rationale. The partner opens Dock, comments requesting a reference call, and flips status to "approved for partner meeting." The audit log records: drafted by diligence-agent-v2, reviewed by priya@, decided 2026-05-28 09:14 UTC. Wednesday the monitoring agent runs its Carta sweep, sees the Stellate option-pool refresh, and writes a flag row. Thursday the IR agent assembles the LP update from approved Dock rows only. Unapproved drafts never reach LPs. The consent gate is the approval flip.
Why this matters
Investing runs on judgment that needs to be defensible later. When an LP asks why the fund passed on a company that became a unicorn, the partner needs the memo, the rationale, and the date. When the SEC examines a fund's process, the auditor needs to see who decided what and when. A drafting agent that leaves no trace forces partners to reconstruct reasoning from memory. A workspace that captures the draft, the reviewer, and the decision creates the record by default.
The NVCA's industry reporting shows fund operations as the constraint on deal velocity, not deal flow (NVCA Yearbook). ILPA's reporting templates exist because LPs need consistent, attributable narrative (ILPA Resources). Bain's research argues value creation now depends on faster, data-driven operations (Bain Global Private Equity Report). Agent attribution is how the record gets built without doubling the associate workload.
The pattern generalizes. The same Dock surface that holds investor decisions holds founder operating decisions, research synthesis, and sales pipeline reviews. The vertical changes. The attribution discipline does not.
Start a Dock workspace for your fund and point your diligence and monitoring agents at it.
FAQ
Does Dock replace Affinity or Carta? No. Affinity stays the CRM. Carta stays the cap table. Dock holds the memos, flags, and LP drafts agents produce, with partner sign-off attached. See agent audit and compliance for the pointer model.
Can multiple agents write to the same investor workspace? Yes. Diligence, monitoring, and IR agents share one workspace, each with its own identity. Rows record which agent wrote them.
How does Dock handle LP confidentiality? LP drafts sit in a Dock doc with row-level permissions. Agents draft, partners approve, only approved versions ship externally.
What about regulated funds with audit requirements? Every row carries agent identity, reviewer, decision, and timestamp. Audit logs export to standard formats, with attribution native rather than reconstructed.
