A fundraising round, done seriously, is two weeks of compressed pattern-matching across forty conversations. You're meeting investors, learning what each partner cares about, iterating the deck after every call, tracking who's followed up and who's gone quiet, remembering whether the partner from the conversation on Tuesday morning was Sarah or Sara and which of them works at the firm with the new EU fund. By the end of the second week, your head is full and the round is at the part where the offers start coming in and you actually need to think clearly.
The fix isn't a CRM. It's a vault that holds the working record of the round — investor research, per-meeting recaps, the evolving deck, the FAQ that's growing in the background — in one place where the agent can read across all of it. The same shape underwrites pitch deck preparation and AI for fundraising — both built on the premise that the round is a writing project as much as it's a conversation project.
A vault shaped around the round
The shape that holds up across round size is roughly: one top-level page for the round, with sub-pages for investor research, per-firm pages, the running deck archive, the FAQ, the metrics commentary, the references list, and the daily roundup. The per-firm pages each have sub-pages per partner you're talking to.
Capy supports unlimited page nesting, so a heavy round can fan out by stage, geography, or strategic-vs-financial without forcing structure on a tighter round. The whole vault is plain markdown. That matters because at any moment in the two weeks, you can ask the agent to read across the round vault and tell you the state — who's met, who hasn't responded, what's the dominant question this week, what needs the deck adjusted to better address.
Investor research that compounds across firms
Most founders research investors firm by firm and forget most of what they read by the next firm. By meeting fifteen, you can't remember whether it was Firm A or Firm B that has the new EU fund and whether it was Partner X or Partner Y who wrote the thesis on your category.
A working setup: each firm gets a sub-page with the partner list, the recent fund vintage, the relevant portfolio companies, the partner's writing on your category, and any warm intro path you've found. Drop the research as you do it. Two minutes per entry. Drop the relevant PDFs — recent fund announcement, the partner's blog post compiled to PDF, the firm's portfolio summary — on the page. They auto-convert to markdown via docstrange, which means the agent can read them as searchable text.
Before a meeting with the firm, ask the agent to read the firm's page and draft a brief: what they invest in at your stage, who the partner is and what they've written about your category, who you should mention from their portfolio, and what the warm intro path was. You walk into the meeting having actually remembered the firm. (The same context-prep pattern is the spine of how account managers keep client context from slipping.)
Per-meeting recaps with the questions investors actually asked
Every investor meeting produces information that's useful for the next investor meeting. The question you didn't have a crisp answer to. The objection that landed sharper than you expected. The framing the partner used that worked better than your own. By meeting twenty, you can't remember which meeting produced which insight.
Record meetings in Capy where the setting allows. The transcript comes back with speaker diarization — labels like "Speaker 1: …" so you can tell who said what, not just a wall of text. Park the recording on the partner's sub-page. Ask the agent to pull the questions you didn't have crisp answers to, the questions you handled well, and the framing the partner used that you should consider adopting. Drop entries into the round's FAQ page.
By meeting ten, the FAQ page is a primary-source archive of what investors are actually asking, in their actual words. The deck and your speaker notes get sharper because the questions feeding into them are real, not imagined. (The recording-with-speaker-labels habit shows up in our writeup of board-of-directors meeting notes too — different room, same loss pattern.)
A pipeline database that's not just a spreadsheet
Most founders track their fundraising pipeline in a spreadsheet that's already drifting by week one. The state of each conversation is partly in the spreadsheet, partly in your inbox, partly in your head, and the round-end synthesis of "where are we" is hard to reconstruct.
A working alternative: an inline pipeline database in the round's top-level page via the :::database::: directive — rows for firm, partner, stage, last contact, next action, status. The database lives directly inside the page, not in a separate tab. Each row links to the firm's sub-page where the deeper context lives.
When you want to know the round state, ask the agent: read the pipeline and surface anything that's overdue for follow-up, anything where the partner's last response suggests they're warm but I haven't pushed, and anything where the silence has gone past the point of normal pacing. The synthesis takes one prompt instead of an hour of clicking through email.
A deck that iterates without losing its memory
Most founders iterate the deck across the round and end up with twenty Drive versions, each named slightly worse than the last, with no record of what changed and why. By round-end, you've forgotten which version you sent to which firm and which version is current.
A working setup: a deck-iteration sub-page that holds each version as plain markdown with a short rationale paragraph: what changed from the prior version, what feedback drove the change, which firms have seen which version. The actual visual deck still gets built in Figma or Pitch; the vault holds the narrative version and the change log.
Ask the agent periodically to read the iteration sub-page and the FAQ page, and to surface places where the deck still doesn't address a question that's come up multiple times across meetings. The deck gets sharper across the round instead of staler. (The deck-iteration discipline is the spine of pitch deck preparation — same artifact, deeper writeup.)
References and daily roundups that keep the round moving
The references conversation is where most rounds stall not because the round goes badly but because the founder gets tired and follow-up slips. The investor needs a reference call with three customers and two earlier-stage co-investors. You meant to send the intros on Wednesday and now it's Saturday and you've sent two of them.
A working setup: an inline followups database in the round's top-level page via the :::database::: directive — rows for what's owed to whom, by when, status. Ask the agent every morning to surface anything overdue. The follow-up becomes a normal morning routine instead of a Sunday-night panic.
This is the compounding habit that separates rounds that close cleanly from rounds that quietly drift. The same followups discipline is the spine of contract negotiation with AI notes — different deal, identical mechanic.
The daily-roundup pattern works on top of it. Every evening, ask the agent to read the day's per-meeting recaps, the new pipeline movements, and the FAQ entries you added, and draft a one-paragraph roundup: what progressed, what stalled, what changed in your read of the round. By Friday, the week is legible, and you can ask the agent to synthesize the week into a one-page summary for your co-founder, advisor, or future-you-in-the-next-round.
What this isn't
Capy isn't an investor CRM. The structured side of running a round — the official cap table, the data room, the eventual closing logistics — still lives in the tools that handle structured data. Capy is for the unstructured side: the investor research, the per-meeting recaps, the FAQ, the deck iteration, the daily roundup. That's the part that's currently sprawled across email, Drive, your inbox, and your memory.
It's also single-user by design. One founder, one vault. If your fundraising involves a co-founder editing the same workspace with role-based permissions, that isn't this product today. The shape that fits is the founder running their personal connective layer; a co-founder runs the same in their own vault and you compare outputs at the start of each working session. Pricing tiers are on the pricing page.
A note on confidentiality: investor conversations and fundraising materials are sensitive. The vault is on our cloud servers and is single-user, but treat it the same way you'd treat any other workspace where you hold sensitive material — with care about what you upload. If your situation requires keeping fundraising data on your own hardware, this isn't the right fit.
A small first test
Pick the firm you have a meeting with this week. Drop the partner's recent writing, your existing pitch deck, and the questions investors have asked you in prior meetings into a Capy page. Ask the agent to draft a one-page brief: who the partner is, what they care about, what they're likely to ask, and what part of the deck you should be ready to defend. If the brief catches a question you'd otherwise have walked into the meeting unprepared for, that's the agent doing what fundraising work asks for and rarely gets.
Try Docapybara free. Load one firm's research and see how the next meeting opens.