Customer Support

How to run customer qbrs as Small Investor Relations Teams

Customer SupportFor Small Investor Relations Teams3 apps12 steps~24 min to set up

Your two-person IR team is running QBRs for LPs and the GP with data living in QuickBooks, NetSuite, Stripe, and a Plaid-connected operating account — none of which talk to each other without someone manually pulling exports and pasting into a slide deck at 11pm. The quarterly LP letter takes two days to produce because you're reconciling capital account balances, commitment pacing, and cash distributions by hand. QBR prep for a single LP relationship means pulling their J-curve, their IRR, their co-invest history, and whatever questions they emailed last week — across four systems, a spreadsheet graveyard, and a DocSend data room nobody updated since Q2.

Build this on Starch → See the apps used

Customer SupportFor Small Investor Relations Teams3 apps12 steps~24 min to set up

Outcome

What you'll set up

A live QBR dashboard that pulls portfolio KPIs, capital calls, distributions, and cash balances from QuickBooks, NetSuite, Stripe, and Plaid — refreshed on a schedule so the numbers are current the morning of every meeting

An LP CRM that tracks contact history, commitment size, open questions, co-invest interest, and last-meeting notes — all in one place your CFO can also see without stepping on your work

An automated QBR deck-generation workflow that takes your live data and produces a meeting-ready presentation for each LP relationship, with action items captured and filed after every call

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

CRM Meeting Notes Presentation Agent

Data sources & config

Starch syncs your QuickBooks data on a schedule (invoices, bills, payments, journal entries) and your NetSuite data on a schedule (balance sheets, income statements, journal entries). Starch syncs your Stripe data on a schedule for distribution and cash movement history, and your Plaid data on a schedule for operating account balances and categorized transactions. Gmail is synced on a schedule for LP email thread history, which flows into the CRM. LP portal sites like Juniper Square, Addepar, or DocSend are automated through your browser — no API needed. Google Calendar is synced on a schedule to auto-populate QBR scheduling and link meeting notes to the right LP records.

Prompts to copy

Build me an LP CRM with fields for commitment size, capital called to date, distributions received, co-invest interest level, J-curve stage, last contact date, and any open questions from their last communication. Pull contact history from Gmail. Flag any LP I haven't contacted in 45 days.

Create a QBR preparation dashboard for each LP that shows their capital account summary, commitment pacing vs. fund schedule, cash distributions from Stripe and Plaid, and net IRR pulled from our QuickBooks and NetSuite data. Refresh every Monday morning.

After each QBR call, summarize the meeting, extract action items with owners and due dates, and log everything to the relevant LP record in my CRM.

Build me a quarterly QBR presentation for Landmark Capital using their capital account data, the last two quarters of distributions, and our fund-level KPIs. Format it as a 12-slide deck with an executive summary, portfolio performance section, capital pacing table, and next steps slide.

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

Walkthrough

Step-by-step

1 Connect QuickBooks and NetSuite so Starch syncs your fund's financial data on a schedule — capital accounts, expense entries, journal entries, and balance sheet line items are available every time you open a QBR view.

2 Connect Plaid and Stripe so operating account balances and distribution history refresh automatically — no more pulling bank exports the night before a meeting.

3 Install the CRM starter app from the Starch App Store and describe your LP tracking schema: commitment size, called capital, distributions, co-invest flag, J-curve stage, last contact date, open questions. Starch builds the schema to match how you actually work, not a generic pipeline.

4 Connect Gmail so Starch syncs LP email threads and surfaces them inside each LP record — when an investor asks 'didn't we discuss this last quarter?' you can search for it in under ten seconds.

5 Connect Google Calendar so QBR meetings are automatically linked to the right LP record, and so the Meeting Notes app knows which relationship the call belongs to.

6 Before each quarterly cycle, open your QBR prep dashboard and ask: 'Show me capital pacing vs. schedule, last two quarters of distributions, and any open LP questions for the next five meetings.' Starch pulls from your synced financial data and CRM in one view.

7 Run each QBR call with Meeting Notes active — it transcribes in real time, generates a summary with key decisions, and extracts action items with owners when the call ends.

8 After the call, action items are logged automatically to the LP's CRM record. No manual note-taking, no 'I'll send a recap later' that never happens.

9 Use the Presentation Agent to generate the QBR slide deck for each LP — describe the structure ('12-slide quarterly update for Landmark Capital with capital pacing table, IRR since inception, distribution waterfall, and Q3 portfolio highlights') and get a draft you can review and export.

10 For LP portal updates — uploading documents to DocSend, Intralinks, or a fund admin portal — Starch automates the browser workflow so your IR associate isn't manually logging into four portals every quarter.

11 Set a weekly scheduled automation: every Monday morning, Starch pulls refreshed capital account balances, flags any LP with an unanswered question older than two weeks, and sends you a Slack summary of who needs outreach before the next QBR cycle.

12 At quarter-end, run the LP letter generation prompt: 'Draft our Q3 LP letter using fund-level performance data from QuickBooks and NetSuite, distribution history from Stripe, and the top three portfolio developments from my notes. Match our Q2 letter tone.' Review, edit, send.

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

Q3 2025 QBR Cycle — 14 LP Relationships, 2-Person Team

Sample numbers from a real run

Total commitments under management	187,000,000
Capital called to date (fund-level)	124,000,000
Distributions paid YTD (Stripe + Plaid)	18,400,000
LPs with open unanswered questions (pre-cycle)	6
QBR decks generated via Presentation Agent	14
Hours saved vs. prior manual cycle (estimated)	31

Going into the Q3 2025 QBR cycle, your team had 14 active LP relationships to cover across three weeks. The prior quarter took 18 hours of prep per IR associate — pulling QuickBooks journal entries by hand, reconciling Plaid distributions against the fund admin report, and building each deck from a PowerPoint template that was three versions out of date. This time, with QuickBooks and NetSuite synced on a schedule into Starch, the capital pacing and income statement data was current Monday morning of week one. Plaid and Stripe covered the $18.4M in distributions paid YTD without a single manual export. The CRM flagged six LPs with unanswered email threads from Q2 — all surfaced from synced Gmail history — so those got a call before the formal QBR rather than a surprise during it. The Presentation Agent generated a first-draft 12-slide deck for each relationship from a single prompt per LP. Meeting Notes captured every call, filed action items to the right CRM record, and produced a two-paragraph recap that went out the same day. Total prep and follow-up time across all 14 QBRs: under 40 hours combined, down from roughly 71 hours the quarter before. The team spent that recovered time on a co-invest process memo that had been on the backlog since January.

Measurement

How you'll know it's working

Capital called as % of total LP commitments, by fund and by LP relationship

Time from quarter-end close to QBR deck delivery (target: under 5 business days)

LP response rate to quarterly letters and action-item follow-ups

Distribution coverage ratio: distributions paid vs. prior commitment schedule

Number of open LP questions older than 14 days (team's internal accountability metric)

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 IR ops but costs $50k+ per year, assumes a dedicated IR-ops analyst to configure and maintain, and doesn't let you build the custom surfaces — LP CRM schema, QBR prep dashboard, letter generator — that match your actual workflow rather than their template.

Google Sheets + Slides + manual exports

Free and familiar, but capital account reconciliation across QuickBooks, NetSuite, Plaid, and Stripe is entirely manual every quarter — the process that Starch replaces with scheduled syncs and a natural-language dashboard prompt.

HubSpot CRM + Notion

Solid general-purpose stack but HubSpot's schema is built for sales pipelines, not LP commitment tracking, and connecting it to your fund's financial data requires custom API work or a third-party integration that you'll be maintaining indefinitely.

Salesforce + Conga for deck generation

Enterprise-grade and deeply customizable, but the configuration overhead and licensing cost are built for a 10-person ops team — not a 2-person IR function that needs something running by next QBR cycle, not next fiscal year.

On Starch RECOMMENDED

One platform — crm, meeting notes, presentation agent 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

Does Starch connect to our fund admin platform — Juniper Square, Addepar, or iLevel?

If your fund admin has a web portal you log into, Starch can automate it through your browser — no API needed. That covers document uploads, capital account lookups, and portal-based reporting workflows. Starch doesn't replace your fund admin or sync its database directly, but it can read and interact with the portal the same way you do, and pipe the output into your dashboards or LP CRM.

How current is the financial data in our QBR dashboard?

QuickBooks, NetSuite, Plaid, and Stripe all sync on a schedule — typically daily or near-daily depending on your configuration. AWS is on-demand only. For most QBR prep workflows, having data that refreshed overnight is more than sufficient. If you need a real-time snapshot at the moment of a call, you can trigger a manual refresh before the meeting.

Can Starch generate the LP letter itself, or just pull the data?

Both. You can ask Starch to draft your quarterly LP letter using fund-level performance data from QuickBooks and NetSuite, distribution history from Stripe, and notes from your CRM. It produces a first draft that you review and edit — not a finished product you send without reading, but a starting point that takes two hours instead of two days. Note: Presentation Agent, which handles QBR deck generation, is currently in development — request beta access to be notified when it launches.

We're not SOC 2 Type II certified at Starch — is that a problem for LP-facing data?

Starch is not SOC 2 Type II certified today, which is worth knowing if your LPs or compliance process requires it of vendors handling fund data. This is an honest limit. The financial data that Starch reads comes from your existing synced providers (QuickBooks, NetSuite, Plaid, Stripe) — Starch surfaces it for your team's operational use, not for LP-direct access. Whether that's acceptable depends on your fund's data governance policy.

Our CFO thinks they own the LP CRM. Can both of us work in the same system without stepping on each other?

Yes. The Starch CRM is a shared surface — you can define who can edit LP records, who can view commitment data, and how pipeline stages are structured. You can also ask Starch to build a read-only CFO view that shows aggregate commitment pacing and distributions without exposing the contact-level notes your IR team maintains. Describe the access model you want and Starch builds it.

What happens to QuickBooks P&L report views — I've heard there are some limitations?

QuickBooks report views — P&L, Transaction List, and Vendor Expenses — are temporarily disabled pending an upstream fix. Entity-level data syncs normally: invoices, bills, payments, vendors, and journal entries are all available. For most QBR financial summaries, the entity data is what you need; if you rely on the formatted P&L report view specifically, that's a current gap worth knowing about.