Workflows · Investor relations
Investor updates that take 20 minutes, not a Sunday.
The monthly update is the cheapest fundraising work a founder does. It pays back at the next round. Here's the structure investors actually read, with Claude doing the heavy lifting.
Why this matters
Why the default doesn't work
Investor updates die because founders write them when they're tired. Sunday night, in front of the laptop, trying to remember what happened five weeks ago, the writing comes out vague. The investor skims it. The signal nobody got is what hurts you at the next round.
The standard advice ('keep them short, send them monthly') is correct but unactionable. The actual bottleneck is writing the thing while you remember what happened. Three weeks later, the energy is gone.
Claude with your data wired does the first 80%. Pipeline movement, key wins, key losses, ask. You write the part that needs your voice (the framing, the lesson, the ask) in 20 minutes instead of two hours.
What the workflow does
What changes when an agent runs the workflow
Generated draft from real data
The agent reads your pipeline, hires, releases, customer wins, churn events, and renewable metrics. The first draft is grounded in what actually happened, not in what you can remember.
Structure investors actually read
Subject line that signals progress. TL;DR in the first paragraph. Asks at the top, not buried. Metrics in a clean block. Lowlights named honestly. The structure that gets read at scrolling speed.
Personalization without redoing the work
Per-investor variants generated from the same source: the lead investor gets the data-room ask, the angel gets the customer-intro ask, the warm contact gets the friends-of-Nerve framing. One source of truth, multiple voices.
Send loop that closes
Drafts queue, you approve, the agent sends through your domain. Engagement (opens, replies, link clicks) feeds back into the investor pipeline. The 'who is paying attention' surface stays current automatically.
The workflow
Three steps to running it
Connect data sources
Pipeline (CRM or Nerve's), product metrics (Posthog, Stripe, whatever you use), and your team's win/loss notes. The agent ingests on cron and remembers month over month.
Run the monthly draft
One command, or it fires on the 1st of every month. The agent drafts the update from this month's data. You read, edit the framing, write the ask, tap approve.
Send and track engagement
The update goes out (Bird, Mailchimp, your own SMTP) with per-recipient personalization. Opens and replies flow back. The investors who never open get tagged for re-engagement; the ones who reply get routed for follow-through.
Signal from operators
What people running this say
First month with the agent draft, I wrote my update in 22 minutes. Before it was a Sunday afternoon. Same quality, sometimes better, because I was less tired.
Pre-seed founder (paraphrased)
Two investors replied to the first update I sent. The previous quarter I had three replies total across three updates.
Seed-stage founder, B2B SaaS
Investor updates compound. The founder who sent 24 monthlies before the Series A always raises faster than the one who sent four.
Patrick Hillstrom, Nerve
FAQ
Common questions
What metrics should I include?
ARR or revenue, growth rate, cash and runway, key customer wins, key losses (or 'no churn'), team adds, product shipped. Avoid vanity metrics. Pre-revenue, lead with usage and design partner traction.
Should I personalize per investor?
For the top 10 to 20 most-active investors, yes. The agent generates variants from a single source: tone, ask, and emphasis differ. For broader distribution lists, the same body is fine.
What about bad months?
Send the update anyway. Investors trust founders who report through hard months more than founders who go dark. The agent helps frame honestly without disaster-narrative drift.
How does this integrate with my CRM / Affinity?
Engagement events (open, reply, click) flow back into the investor record. The 'who is paying attention' signal stays current. If you use Affinity, Nerve mirrors there.
Can it handle the Friends of Nerve / lightweight update format?
Yes, this is one of Nerve's native flows. The Friends of Nerve template is a lighter touch (no metrics block, no asks) for warm-network monthly cadence. Same agent, different template.
Who this is for
Roles where this matters most
Nerve for first-time founders
First-time founders run lean on instinct. Nerve gives you the operating layer experienced founders built over years, on day one. AI agents for pipeline, customers, and follow-through.
Nerve for fundraising founders
Fundraising is a sales process. Nerve runs the investor pipeline the same way you'd want your sales team to run a B2B pipeline: nothing slips, nothing goes cold, every warm signal gets a follow-through.
Nerve for agency owners
Agencies run on context-switching. Nerve gives agency owners an AI agent team that holds state per client, drafts reporting, surfaces account risk, and runs the operations layer that used to require a senior hire.
Nerve for investors
Investors run two pipelines (deals and portfolio) on the same brain. Nerve is the AI agent team that handles sourcing followups, deal-flow triage, and portfolio relationship management so your time stays on the calls that move money.
Cheapest fundraising work you'll do. Stop skipping it.
Start free, no credit cardMore workflows
Other workflows
How to track investor follow-ups with Claude (and not drop a single one)
A working founder's guide to tracking every investor conversation in flight, with Claude doing the heavy lifting. The system, the prompts, the failure modes, and how Nerve closes the loop.
How to manage a B2B pipeline with Claude (without abandoning your CRM)
A working operator's guide to running a B2B pipeline with Claude in the loop. The setup, the daily rhythm, the failure modes, and how Nerve turns Claude's reasoning into closed deals.
How to forecast revenue with Claude (when the spreadsheet has stopped helping)
A founder-grade guide to revenue forecasting with AI in the loop. Pipeline math, conversion priors, and the agent layer that keeps the forecast honest week over week.
How to run daily standups with an AI chief of staff (and skip the meeting)
The standup most teams run is a status meeting that burns 20 minutes and surfaces nothing actionable. Here's the AI-driven version: generated brief, surfaced blockers, no required meeting.