How to Draft LP Updates from Quarterly Portfolio Check-In Calls with Fellow and Claude
•
9
MIN READ
AI Summary by Fellow
For most portfolio operations and investor relations teams, the days before an LP letter goes out follow a familiar pattern. Someone starts re-listening to or re-reading notes from 15 to 30 portfolio company check-in calls, trying to reconstruct what actually changed since last quarter. A KPI shifted, but whose notes mention it? Management changed at one company, but was that call this quarter or last? The information exists somewhere. It's just scattered across email threads, a deal team member's memory, and notes that were never written down consistently in the first place.
This isn't a one-time diligence problem. It's a calendar-driven cycle that repeats every quarter, across every active portfolio company, for every fund a firm runs. A mid-size fund with 20 or more portfolio companies runs this reconstruction exercise four times a year, and the cost compounds: hours of re-listening per company, inconsistent detail depending on who took the call, and a reporting bottleneck that lands right when IR teams can least afford one.
This is exactly the kind of recurring, portfolio-wide problem Fellow and Claude are built to take off your plate. Here's how to actually set it up.
What does a quarterly LP update need to cover?
A quarterly LP update typically needs to communicate five things clearly and consistently across every portfolio company in the fund: performance against plan, movement in key operating metrics, management or leadership changes, notable risks and opportunities, and any capital activity for the period. LPs expect this information in a comparable format company to company, quarter to quarter.
The problem isn't that this information doesn't exist. It's that the source material, the quarterly check-in call with portfolio company management, gets captured differently every time. One deal team member takes detailed written notes. Another relies on a recording they never revisit. A third remembers the highlights but not the specifics an LP letter needs, like the exact KPI figure or the precise wording of a management comment on a risk. The fix is to standardize how that source material gets captured in the first place, which is where Fellow comes in.
Capture every check-in call in Fellow with a shared template
Set up a "portfolio check-in" AI meeting notes template in Fellow, structured around what your LP letter actually needs: performance commentary, KPI mentions, management updates, and risk flags. Point every deal team member and ops associate at the same template for every portfolio company check-in call, then tag each call to the company and the reporting quarter as it happens.
Because Fellow captures calls the same way whether they're on Zoom, Google Meet, Microsoft Teams, or in person, it doesn't matter that your portfolio companies aren't all on the same video platform. Every call, regardless of where it happens, lands in Fellow's recordings library in the same structure. That consistency is what makes the next step possible: instead of one company's update reading as a paragraph of loose recollection and another's reading as a detailed spreadsheet reference, every company's quarterly data arrives in the same shape.
Have Claude draft a first-pass section per company
At quarter close, this is where Claude does the heavy lifting. Through Fellow's Claude integration or MCP Server, you can point Claude at that quarter's full set of tagged portfolio check-in calls and ask it to draft a first-pass section per company: a performance summary, notable developments, and an outlook, pulled directly from what was actually said on each call. You can also do this conversationally inside Fellow with Ask Fellow, asking something like "summarize this quarter's check-in calls for each portfolio company" and getting a per-company draft back.
This is the same underlying mechanism you'd use for a single-deal diligence memo, just pointed at a whole portfolio's worth of calls instead of one transaction. The output isn't a finished LP letter. It's a consistent first draft per company that your IR or ops team reviews, adjusts for tone, and assembles into the full letter. Claude's job is to eliminate the reconstruction step. The review and framing decisions for an external, LP-facing document still stay with your team.
The quarterly workflow in Fellow
Tag every portfolio check-in call in Fellow to the company and the reporting quarter as it happens.
Run each call through your shared portfolio check-in template, so every company's data lands in the same structure regardless of who took the call.
At quarter close, prompt Claude (via Ask Fellow, the Claude integration, or MCP Server) to draft the per-company section of the LP letter from that quarter's tagged calls.
Have IR or ops review and assemble the full letter in Fellow, adjusting tone and framing for an LP audience.
Route the draft through Fellow's compliance portal before it goes out, with the source calls and supporting figures retained per your firm's policy.
The same setup works for single-deal diligence memos too. This just runs it on a recurring quarterly cadence across your whole portfolio instead of once per transaction.
Why Fellow is built for regulated, LP-facing reporting
Fellow is built for firms that need both intelligence and governance in the same workflow, which is exactly the tension a quarterly LP reporting cycle creates. Fellow never trains on customer data, supports SOC 2 Type II, HIPAA, and GDPR compliance, and gives compliance teams privacy and access controls including transcript redaction, consent capture for auto-recorded meetings, and password-protected recap links for sharing drafts with LPs or outside reviewers.
That's the same infrastructure teams in private equity, hedge funds, and investment banking already rely on Fellow for elsewhere in their workflow, applied here to the specific, recurring problem of LP reporting.
Frequently asked questions
How do I automate LP quarterly update drafting with Fellow?
Capture every portfolio company check-in call in Fellow using a shared "portfolio check-in" template, tagged by company and quarter. At quarter close, use Claude through Fellow's Claude integration, MCP Server, or Ask Fellow to draft a first-pass performance summary per company, then have IR or ops review and assemble the final letter.
What should a quarterly LP update include?
A quarterly LP update should cover performance against plan, movement in key operating metrics, management or leadership changes, notable risks and opportunities, and any capital activity for the period, presented consistently across every portfolio company in the fund.
Is AI-drafted LP reporting compliant with SEC recordkeeping rules?
It can be, as long as your firm retains the records supporting any performance claims and routes the letter through a compliance review before sending, since LP letters are external, performance-related communications under Rule 204-2. Fellow's compliance portal and configurable retention support this, but this is general information, not legal advice, so confirm specifics with counsel.
Can Claude synthesize check-in calls across an entire portfolio at once?
Yes. Once portfolio check-in calls are tagged by company and reporting quarter in Fellow, Claude can read across the full set of calls for that period through the Claude integration, MCP Server, or Ask Fellow, and draft a per-company summary section instead of requiring someone to reconstruct each company's update by hand.
Does this work if portfolio companies are on different meeting platforms?
Yes. Fellow captures calls consistently across Zoom, Google Meet, Microsoft Teams, and in-person meetings, so it doesn't matter that your portfolio companies aren't standardized on one video platform. The quarterly data stays comparable regardless of which platform each check-in call runs on.
Record, transcribe and summarize every meeting with the only AI meeting assistant built with privacy and security in mind.
