Customer Support

How to run customer qbrs as Asset Management Founders

Customer SupportFor Asset Management Founders3 apps12 steps~24 min to set up

You're running QBRs with LPs on a quarterly cadence, but you have no analyst to pull the data, no EA to prep the deck, and no CRM that actually reflects how you track your LP relationships. You're copying numbers out of QuickBooks or Plaid into a Google Sheet, building slides in PowerPoint the night before, and taking notes on a legal pad you'll lose by Friday. Meanwhile, the QBR itself is supposed to be a trust-building conversation with the people who wrote you a check — not a scramble to find last quarter's IRR figure. Emerging fund managers run this process entirely manually, and it shows.

Build this on Starch → See the apps used

Customer SupportFor Asset Management Founders3 apps12 steps~24 min to set up

Outcome

What you'll set up

A live LP relationship tracker that logs every touchpoint, surfaces who you haven't spoken to in 45+ days, and pulls meeting notes directly into contact records so your QBR prep takes minutes instead of hours

A meeting notes system that transcribes every LP call in real time, extracts action items, and archives everything in a searchable history so you can answer 'didn't we discuss this last quarter?' with an exact quote

A quarterly presentation workflow that pulls your live financial data and produces a polished LP update deck from a text description — no designer, no Sunday-night slide formatting

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, payments, journal entries) and your Stripe data on a schedule (charges, payouts) to power the financial sections of your QBR deck. Gmail is connected as a scheduled-sync provider so LP email thread history flows into CRM contact records automatically. Google Calendar syncs on a schedule to surface upcoming QBR meetings and flag overdue LP touchpoints. Calendly connects from Starch's integration catalog; the agent queries it live when scheduling follow-up calls. Meeting notes transcription runs natively inside Starch on each recorded LP call.

Prompts to copy

Build me an LP relationship CRM with fields for commitment size, vintage year, last contact date, preferred communication cadence, QBR attendance history, and any open follow-up items. Flag any LP I haven't emailed or called in more than 45 days.

Transcribe my LP QBR call with Meridian Capital Partners, generate a summary with key topics covered, extract any commitments I made and assign them to me, and save it to Meridian's contact record in the CRM.

Build me a 12-slide Q1 2026 LP update deck with our fund performance summary, portfolio company highlights, capital deployed this quarter, remaining dry powder, and a market outlook section. Use our fund branding and export to PowerPoint.

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

Walkthrough

Step-by-step

1 Connect QuickBooks and Stripe as scheduled-sync providers so Starch pulls your fund's financial data — capital deployed, management fees received, portfolio company invoices — on a recurring schedule without you touching a spreadsheet.

2 Connect Gmail as a scheduled-sync provider so every email thread with an LP automatically logs against that LP's contact record in your Starch CRM — no manual entry, no BCC to a separate inbox.

3 Open the CRM app and prompt Starch to build your LP tracker: commitment size, vintage year, preferred cadence, QBR attendance history, and a 'days since last contact' field that turns red at 45 days.

4 Two weeks before quarter end, ask Starch 'Which LPs haven't I spoken to this quarter?' and use that list to prioritize outreach before the formal QBR window opens.

5 Schedule QBR calls through Calendly (connected from Starch's integration catalog); Starch surfaces each LP's prior meeting summaries, open action items, and commitment history in a single pre-call brief.

6 During each QBR call, run the Meeting Notes app to transcribe in real time — after the call, review the auto-generated summary, confirm action items, and let Starch push them back into the LP's CRM record.

7 After each call, Starch flags any follow-up commitments you made (capital call notice date, a model you promised to send, an intro you owe) and surfaces them in your task queue.

8 At quarter close, prompt the Presentation Agent to build your LP update deck: pull Q1 deployed capital from QuickBooks, net revenue from Stripe, and your portfolio company highlights from the CRM notes. Describe the structure in plain language and get a complete 12-slide deck.

9 Review the deck inside Starch, swap any slide layouts, update the narrative sections, and export to PowerPoint or a shareable link for LPs who prefer async review.

10 After each QBR, log the attendance, key discussion themes, and any sentiment signals ('expressed concern about deployment pace') directly in the CRM — Starch can pre-populate this from the meeting transcript.

11 Set a recurring automation: every Monday morning, Starch checks your Google Calendar for upcoming LP meetings that week, pulls the relevant contact records, and Slacks you a digest of who you're meeting, what you discussed last time, and any open items.

12 At the end of the QBR cycle, ask Starch for a summary across all LP conversations this quarter — common themes, recurring questions, relationship health by LP — so you can adjust your fund narrative for next quarter.

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

Q1 2026 QBR cycle — 14-LP emerging fund, $42M AUM

Sample numbers from a real run

Capital deployed Q1 2026	3,200,000
Management fees received (Q1)	210,000
Remaining dry powder	8,750,000
Portfolio companies with active follow-on discussions	3
LP QBR calls completed	12
LPs flagged overdue for contact (>45 days)	2

With 14 LPs across three vintages and a $42M fund, the Q1 2026 QBR cycle ran across three weeks in April. Starch flagged two LPs — a family office in Dallas and a fund-of-funds out of Chicago — who hadn't been contacted since January. Both got calls before the formal QBR window, which surfaced a concern the Dallas office had about deployment pace that would have blindsided the QBR conversation. QuickBooks sync showed $3.2M deployed in Q1 against a $12M target pace, and Stripe captured $210K in management fees received — both numbers pulled automatically into the LP update deck without touching a spreadsheet. The Presentation Agent built the 12-slide Q1 deck from a prompt in about four minutes; the fund manager spent 20 minutes editing the narrative sections and exported to PowerPoint for the three LPs who prefer offline review. Meeting notes from all 12 QBR calls were transcribed, summarized, and pushed into each LP's CRM record, leaving a searchable archive of every commitment made — including a follow-on model promised to the Chicago fund-of-funds, which showed up in the task queue the next morning.

Measurement

How you'll know it's working

Days since last LP contact (per LP, target <45 days)

Capital deployed vs. vintage-year deployment pace

QBR completion rate (calls completed / LPs in fund)

Open follow-up items per LP after each QBR

Management fee collection rate (fees received / fees invoiced, from QuickBooks)

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 reporting but starts at $50K+/year and assumes a dedicated ops team — not built for a one- or two-person emerging fund doing everything themselves.

HubSpot + Zoom + Google Slides

Each tool does its job, but you're copying data between three systems manually every quarter and paying for HubSpot admin time you don't have.

Notion + Loom + manual QuickBooks exports

Free or low-cost, but there's no live financial data connection — every QBR deck starts with a spreadsheet export and manual copy-paste that takes half a day.

Grata or DealCloud

Strong for deal sourcing and pipeline, but LP relationship management and QBR workflows require significant customization and a price point that assumes a larger ops budget.

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

Can Starch actually pull my fund's financials for the QBR deck, or do I still have to export from QuickBooks manually?

Starch syncs your QuickBooks data on a schedule — invoices, bills, payments, journal entries, and vendor data. When you prompt the Presentation Agent to build your LP update deck, it can pull those numbers directly without a manual export. One honest caveat: QuickBooks report views like the P&L summary are temporarily unavailable due to an upstream issue, but entity-level data (invoices, payments, journal entries) syncs normally and is enough to build the financial summary your LPs actually want.

I track LP relationships differently than a traditional sales CRM — deal stages don't apply. Can Starch's CRM handle fund-specific fields?

Yes — that's the point of the CRM app. You describe your LP tracking model in plain language: commitment size, vintage year, preferred communication cadence, QBR attendance, capital call history, whatever matters to you. Starch builds the schema around how you actually work, not a generic B2B sales pipeline. You're not configuring HubSpot fields; you're telling Starch what an LP record should look like.

Is Starch SOC 2 certified? My LPs may ask about data security before I put their information in a new platform.

Starch is not currently SOC 2 Type II certified — that's worth knowing before you store sensitive LP data. There's no self-hosted option today either. For an emerging fund that's comfortable with SaaS tools (you're already using QuickBooks, Gmail, and Google Calendar), this is usually a manageable conversation with LPs; for a fund with strict institutional LP requirements around data residency, it's worth flagging.

How does the Meeting Notes app handle calls where I'm on Zoom with an LP? Does it integrate with Zoom directly?

Starch connects to Zoom from its integration catalog; the agent queries it live when your workflow needs it. The Meeting Notes app transcribes calls in real time and generates a summary with key decisions and action items after the call ends. If you want the transcript and action items to sync back into the LP's CRM record automatically, you can describe that workflow to Starch and it will build the automation.

The Presentation Agent sounds useful, but is it actually available now?

The Presentation Agent is currently in development. You can request beta access to get notified when it launches. In the meantime, the CRM and Meeting Notes apps are live today and handle the prep and follow-up sides of the QBR workflow — the deck building piece comes when Presentation Agent ships.

Can Starch remind me which LPs I haven't spoken to before the QBR window opens, without me having to run a report?

Yes. Set an automation that runs on a schedule — say, every Monday morning — that checks your CRM for LPs whose last contact date exceeds 45 days and Slacks or emails you a list. You describe the logic in plain language: 'Every Monday, check my LP CRM and flag anyone I haven't contacted in more than 45 days. Slack me the list.' Starch builds and schedules that automation. Google Calendar and Gmail both sync on a schedule, so Starch can factor in actual email threads and meeting attendance, not just manual log entries.