Internal Comms & Meetings

How to write a weekly team update as Small Investor Relations Teams

Internal Comms & MeetingsFor Small Investor Relations Teams4 apps12 steps~24 min to set up

Your two-person IR team produces a weekly update that should take 45 minutes and consistently takes half a Thursday. You're pulling NAV figures from QuickBooks or NetSuite, cross-referencing capital call schedules from a spreadsheet the CFO last touched in February, checking Plaid for cash movements, and then writing the actual narrative in a Google Doc before pasting it into Outlook. LPs reply asking why last week's numbers don't match the data room. The GP wants a different cut of the same data. Nobody owns a canonical source of truth. The update goes out late, or you send a correction email two hours after.

Build this on Starch → See the apps used

Internal Comms & MeetingsFor Small Investor Relations Teams4 apps12 steps~24 min to set up

Outcome

What you'll set up

A recurring weekly update that auto-pulls live QuickBooks and Plaid data — deployed net assets, cash position, capital called to date — and drafts the narrative so you're editing, not writing from scratch

An inbox workflow that triages LP reply threads by priority and queues follow-up drafts so correction emails get handled in minutes, not buried until Monday

A searchable archive of every weekly update, LP question, and action item so when someone asks 'didn't we change how we report management fees?' you can find the exact week it happened

The Starch recipe

Apps, data, and prompts

The combination of Starch apps, the data sources they pull from, and the prompts you use to drive them.

Apps used

Investor Reporting Knowledge Management Meeting Notes

Data sources & config

Starch syncs your QuickBooks data on a schedule (invoices, payments, journal entries, management fee line items) and your Plaid data on a schedule (cash balances, transaction categorization). Connect Outlook from Starch's integration catalog; the agent queries it live when the inbox triage runs. Your LP commitment tracker in Google Sheets is connected from Starch's integration catalog and queried live. Notion syncs on a schedule to power the Knowledge Management wiki.

Prompts to copy

Every Friday at 8 a.m., pull this week's cash balance from Plaid, net assets and management fee accruals from QuickBooks, and total capital called to date from our commitment tracker spreadsheet. Draft a weekly IR update in this format: [paste template]. Flag any line item that moved more than 5% week-over-week and explain the delta in plain English.

Triage my Outlook inbox and surface any LP emails that arrived since last Friday. For each one, summarize the question in one sentence, draft a reply pulling from our last three weekly updates, and set a follow-up reminder if I haven't responded within 24 hours.

Save this week's update, the draft narrative, and any LP replies into our Knowledge Management wiki under 'Weekly Updates > 2026 Q2'. Tag it with the reporting period and flag any items marked as follow-ups.

Run these in Starch → or paste them into your favorite agent

Walkthrough

Step-by-step

1 Connect QuickBooks and Plaid in Starch — both sync on a schedule, so by Friday morning the data is already in Starch's database waiting for the agent, not being pulled on demand.

2 Connect Outlook from Starch's integration catalog and grant the agent read and send permissions so it can triage LP emails and queue draft replies.

3 Install the Investor Reporting starter app from the Starch App Store and customize the template fields to match your fund's reporting line items: deployed capital, management fee accruals, unrealized NAV, cash available for drawdown.

4 Set up a scheduled automation that runs every Friday at 8 a.m.: the agent pulls QuickBooks entity data and Plaid balances, computes the week-over-week delta on each line, and drafts the narrative in your standard update format.

5 Add a delta-flagging rule in plain language — tell Starch: 'If any balance or accrual line moves more than 5% from last week, highlight it in the draft and write a one-sentence explanation of the likely cause.'

6 Wire the Email Triage app to your Outlook so LP replies that arrive between Friday afternoon and Monday morning are automatically sorted by urgency — capital call questions go to the top, routine access requests go to a queue.

7 For each flagged LP email, the agent drafts a reply that references the most recent weekly update data. You review, edit if needed, and send — one click for routine questions, two minutes for anything substantive.

8 After you approve and send the weekly update, tell Starch: 'Archive this week's update in Knowledge Management under Weekly Updates > 2026 Q2, tag it with the reporting date, and mark any open LP follow-ups as tasks.' Starch logs the update, creates tasks for anything unresolved, and the wiki entry is searchable immediately.

9 Wire Meeting Notes into your weekly LP call schedule so any investor call that week — commitment pacing question, J-curve discussion, ad hoc check-in — gets transcribed, summarized, and linked to the relevant weekly update entry automatically.

10 At the end of each quarter, tell Starch: 'Compile every weekly update from Q2 2026, extract the NAV trajectory, capital call timing, and any LP questions that repeated more than twice, and draft a one-page summary for the GP.' This becomes the first draft of your quarterly letter narrative.

11 If your GP or CFO wants a different cut mid-week, describe what they need in plain language — 'Show me capital called by vintage year, pulling from QuickBooks and the commitment tracker' — and Starch builds the view without you rebuilding the spreadsheet.

12 Review the full workflow once a quarter: check that QuickBooks and Plaid syncs are current, confirm the Outlook integration is still live, and update the narrative template if your reporting format changed.

See this running on Starch

Connect your tools, describe what you want, and the agent builds it. Closed beta is free.

Try it on Starch →

Worked example

Week of April 14, 2026 — mid-quarter update with capital call pending

Sample numbers from a real run

Cash (Plaid — operating account)	2,340,000
Management fee accruals (QuickBooks)	187,500
Capital called to date (Google Sheets tracker)	34,200,000
Total LP commitments	75,000,000
Uncalled capital remaining	40,800,000

Friday at 8:05 a.m., Starch's automation fires. It pulls the operating account balance from Plaid ($2.34M, down $410K from last Friday because a vendor invoice cleared), management fee accruals from QuickBooks ($187,500 for the quarter to date), and capital called to date from the Google Sheets commitment tracker ($34.2M of $75M total commitments, 45.6% drawn). The draft update writes itself: 'As of April 14, the fund has called $34.2M of $75M total commitments. Cash on hand is $2.34M. Management fee accruals through Q2 stand at $187.5K. Note: operating cash decreased $410K week-over-week due to the Apex vendor payment clearing on April 11.' The agent flagged the cash delta because it exceeded the 5% threshold and added the one-line explanation automatically. You open the draft, confirm the Apex payment note is accurate, and send. Total time: 11 minutes. Two LP emails arrived Friday afternoon — one asking about the April capital call timeline, one asking for data room access. The Email Triage app surfaces the capital call question first, drafts a reply citing the commitment pacing numbers from this morning's update, and flags the data room request as a separate task. You send both replies before lunch. The update, both replies, and the open data room task are archived in the Knowledge Management wiki by 1 p.m.

Measurement

How you'll know it's working

Time from data pull to update sent (target: under 20 minutes on a recurring basis)

LP email response time — specifically for capital call and pacing questions (target: same business day)

Percentage of weekly updates sent on schedule (Friday, before noon)

Number of correction emails or restatements per quarter (target: zero)

Uncalled capital as a percentage of total commitments — tracked weekly for GP visibility

Comparison

What this replaces

The other ways teams handle this today, and how the Starch version compares.

Juniper Square or Addepar

Purpose-built for fund administration and LP reporting at scale, but costs $50K+ per year, assumes a dedicated IR-ops analyst to configure, and doesn't let you build the specific surfaces you actually work in — you get their UI, not yours.

Google Sheets + Outlook + manual copy-paste

Free and fully in your control, but the update takes half a day because you're the integration layer — pulling from four systems, reconciling discrepancies, and writing the narrative by hand every week.

Notion + Zapier

Good for documentation and lightweight automations, but Zapier can't draft a narrative from live financial data, and you'll still be doing the QuickBooks-to-Notion data reconciliation yourself.

Q4 IR platform

Strong for public company IR and earnings communications, but oriented around investor relations at the market-cap level — not built for the LP-communication and commitment-tracking workflows that dominate a fund IR team's week.

On Starch RECOMMENDED

One platform — investor reporting, founder inbox, knowledge management all running on connected data. Setup in plain English; numbers stay current via scheduled syncs and live agent queries.

Try it on Starch →

FAQ

Frequently asked questions

Can Starch pull directly from our QuickBooks, or does someone have to export a CSV every week?

No CSV exports. Starch syncs your QuickBooks data on a schedule — invoices, bills, payments, journal entries, vendors. By the time your Friday automation runs, the data is already in Starch's database. One honest caveat: QuickBooks report views like the P&L summary are temporarily disabled pending a fix on our end. Entity-level data — which covers everything you'd need for the weekly update — syncs normally.

We use Outlook, not Gmail. Does that matter?

No. Connect Outlook from Starch's integration catalog. The Email Triage workflow reads your messages, surfaces LP emails by priority, and queues draft replies — same behavior as the Gmail version.

Our LP commitment tracker is in Google Sheets because the CFO refuses to move it. Can Starch still use it?

Yes. Connect Google Sheets from Starch's integration catalog; the agent queries it live when the weekly automation runs. You don't have to migrate the data anywhere. If the CFO updates the sheet mid-week, the next automation run picks up the current version.

Is Starch SOC 2 certified? Our compliance team will ask.

Not yet — Starch is not SOC 2 Type II certified today. If your LP agreements or your compliance team require SOC 2 certification for any tool that touches fund financial data, that's a genuine constraint to evaluate. We'd rather you know upfront than find out after setup.

What if our LP data room is in DocSend or Intralinks, which have no open API?

Starch automates both through your browser — no API needed. You'd describe the workflow: 'When a new LP requests access, log into DocSend, grant access to the current data room, and send them the confirmation link.' Starch handles the navigation. This is the same mechanism we use for any web-based tool that doesn't have a formal API connector.

Can Starch generate the actual LP letter narrative, or just the data table?

Both. Give Starch your standard narrative template — the structure you use every week, the tone, the specific phrases you use for capital call updates — and the agent fills in the live numbers and writes the explanatory sentences. You're editing a 90%-complete draft, not writing from a blank page. For the quarterly letter, you can tell Starch to compile all the weekly updates from the quarter and draft the narrative arc from the data it already has.

We also use NetSuite for some portfolio entities. Can Starch pull from both QuickBooks and NetSuite in the same update?

Yes. Starch syncs your NetSuite data on a schedule — invoices, expenses, journal entries, balance sheets, income statements. You can build a single weekly update that pulls QuickBooks data for some entities and NetSuite data for others and presents them in a unified view. Describe the layout you want and Starch builds it.