Notes on working with AI
Claude for VCs: The Three Skills a Fund Builds First
Not another chatbot that reads a pitch deck faster. The three skills a VC fund builds first with Claude, and why the order you build them in matters.
The three Claude skills a fund builds first
Claude for VCs isn't about a chatbot that reads a pitch deck faster. It's three specific skills, each built once and reused on every deal: deal triage, the diligence memo and the LP update. Build those three first, in that order, and everything else in the fund's workflow gets easier to automate later.
Skill one: deal triage
More deal flow arrives than anyone has time to read closely, and most of it gets a glance before it's passed or ignored. A deal-triage skill checks every inbound deal against the fund's own criteria, thesis, check size, stage, sector, and returns a clear recommendation before the first meeting. The partner still makes the call. The skill just makes sure nothing that fits the thesis gets missed because it landed on a Friday afternoon, and it treats every deal the same way whether it came through a warm intro or a cold inbound form.
Skill two: the diligence memo
Due diligence on contracts and data-room documents still happens page by page, by hand, in most funds. A diligence-memo skill turns a full data room into a first-draft investment memo in hours instead of days, with every red flag marked and a source behind each finding. The same skill checks a new term sheet against the fund's last several, flagging anything unusual before anyone signs. The analyst reviews and tightens the draft instead of opening two hundred files across a dozen tabs, and the memo that used to consume a weekend is ready for the partner meeting Monday morning.
Skill three: the LP update
Portfolio tracking and LP reporting run on a manual update every quarter in most funds, pulled from whatever each company happened to send that month. A portfolio-reporting skill keeps a dashboard current from every report the companies send in, and turns that into the quarterly LP update without someone rebuilding the same spreadsheet from scratch. The same setup runs ongoing market and competitor monitoring for each portfolio company, so a partner gets a weekly note instead of running the same searches by hand every time an LP asks how a company is doing.
Why skills, not a chat habit
A chat window that gets asked good questions is not the same as a fund with three working skills. A skill runs the same way every time someone on the team uses it, on the fund's own documents, not a generic prompt copied from a newsletter. That's the gap between a partner who personally got good at prompting Claude and a fund where deal triage keeps working the same way even when that partner is on a plane.
How the workshop actually runs
The session runs on-site or online, built around your fund's own term sheets, data rooms and portfolio reports, not a sample dataset. No engineering background is needed. Each skill is set up through plain-language instructions to Claude, refined on your real documents until the analyst or partner in the room trusts the output.
A common question: do we need engineering support to build these
No. Each skill is built and adjusted through plain-language instructions to Claude, on the fund's own documents, with no engineering time required to get a first working version running that day.
Next step
The Claude workshop for VC and investment teams builds these three skills on your own pipeline, not a demo dataset. Tell us where deal flow backs up today and we'll start there.