Sales & CRM

How to forecast quarterly revenue as Asset Management Founders

Sales & CRMFor Asset Management Founders3 apps12 steps~24 min to set up

Every quarter you're manually pulling together a revenue forecast for your LP updates and your own investment decisions — and you're doing it by hand. You've got capital calls tracked in a spreadsheet, management fee schedules in another tab, carry calculations you haven't touched since you set them up, and committed capital from LPs across a handful of closing dates. QuickBooks might have some of the picture, but it doesn't know how to read a fund structure. Juniper Square and Addepar would solve this but they want $50k+ and assume you have an ops team. So every quarter ends with you spending two days reconciling tabs before you can say with confidence what revenue looks like through year-end.

Build this on Starch → See the apps used

Sales & CRMFor Asset Management Founders3 apps12 steps~24 min to set up

Outcome

What you'll set up

A live quarterly revenue forecast that pulls your actual management fees, interest income, and carry projections from connected financial data — no spreadsheet reconciliation required

Scenario models for the decisions that actually matter to you: what revenue looks like if your next close slips a quarter, if AUM grows 20% slower than projected, or if you accelerate a capital call

LP-ready output — a quarterly update narrative with the revenue forecast baked in, drafted by Starch and sent on whatever cadence you set

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

Scenario Analysis Investor Reporting CRM

Data sources & config

Starch syncs your QuickBooks data on a schedule — invoices, bills, payments, and journal entries form the financial baseline. Starch also syncs your Stripe data on a schedule if you invoice management fees through Stripe. Your LP contact history pulls from Gmail, which Starch syncs on a schedule. For any fund administrator portal or LP reporting platform that doesn't have an API, Starch automates it through your browser — no API needed.

Prompts to copy

Build me a quarterly revenue forecast for my asset management fund. Revenue has three components: management fees (2% on $18M committed capital, called quarterly), interest income from deployed capital, and realized carry on exits. Connect my QuickBooks data as the baseline. I want to model three scenarios: base case, a scenario where my Q3 close slips to Q4 adding $5M AUM, and a downside where AUM stays flat through year-end. Show me projected revenue, cumulative called capital, and estimated carry for each scenario through Q4 2026.

Generate my Q2 2026 LP quarterly update. Pull my actual revenue and expense data from QuickBooks. The narrative should cover: management fee revenue recognized this quarter, deployed capital as a percentage of committed, any realized exits, and our revenue outlook for the back half of the year. Keep the tone factual — my LPs are institutional and don't want spin.

Set up my LP relationship CRM. I track relationships by LP name, committed capital amount, capital called to date, last contact date, next scheduled touchpoint, and whether they're a potential re-up candidate for Fund II. I want to be able to ask 'which LPs haven't had a touchpoint in 60 days' and get an answer immediately.

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

Walkthrough

Step-by-step

1 Connect QuickBooks as a scheduled-sync provider. Starch pulls your invoices, payments, journal entries, and vendor data automatically. This becomes the baseline your revenue forecast and scenario models run on — actual numbers, not estimates.

2 If you invoice management fees through Stripe, connect Stripe as a scheduled-sync provider so fee recognition and payment timing are visible in the same model.

3 Open the Scenario Analysis app. Tell Starch the three numbers that define your fund's revenue structure: AUM, management fee rate, and your current called capital schedule. The app uses your QuickBooks actuals as the floor and lets you adjust forward assumptions.

4 Build your base case scenario first: management fees on current committed capital, projected capital calls by quarter, and estimated carry based on your current portfolio valuations and expected exit timeline.

5 Fork the base case into a 'Q3 close slips' scenario. Change only the assumptions that differ — close date, incremental AUM, resulting fee step-up — and Starch recalculates quarterly revenue through year-end without rebuilding the model from scratch.

6 Add a downside scenario: AUM flat, no new close, same expense base. This is the version you run before committing to any hiring or office spend decisions.

7 Set up the CRM app for LP relationship tracking. Describe your actual fields — committed capital, called capital, last touchpoint, re-up interest level — and Starch builds the schema around your workflow, not a generic sales pipeline.

8 Sync Gmail so email threads with LPs attach automatically to the right contact record. When you need to know who you haven't spoken to in 60 days before a quarterly mailing, the CRM can answer that without a manual audit.

9 Open the Investor Reporting app. Connect it to your QuickBooks data and point it at your scenario model output. Tell Starch the tone, the metrics your LPs care about, and the cadence — quarterly, after each close, or both.

10 Before each quarterly send, answer Starch's questions about what happened this period: any exits, new investments, notable portfolio developments, or changes to your outlook. Starch drafts the full update — revenue recognized, deployed capital, runway narrative, and forward forecast — and you edit rather than write.

11 Review the draft against your scenario model output. If the base case shifted materially, update the assumptions in Scenario Analysis first, then let Investor Reporting pull the refreshed numbers into the narrative.

12 Send the LP update from inside Starch or export it. Your CRM touchpoint dates update automatically so you know exactly where each LP relationship stands going into the 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

Q2 2026 Quarterly Revenue Close — $18M Committed Capital

Sample numbers from a real run

Management fees — called capital (2% on $12.6M called)	63,000
Interest income — deployed capital	14,200
Realized carry — one portfolio exit at 2.4x	38,000
Total Q2 revenue	115,200
Q3 projected (base case, $5M additional close)	131,500
Q3 projected (downside, no close)	94,000

You closed Q2 with $115,200 in recognized revenue. Management fees on $12.6M of called capital came in at $63,000 for the quarter — exactly in line with your fee schedule. One portfolio company was partially exited at 2.4x, generating $38,000 in realized carry that you hadn't modeled as a Q2 event, which pulled the quarter above your base case. Heading into Q3, the scenario model shows two materially different outcomes: if your anticipated $5M close happens in July as planned, quarterly management fee revenue steps up to roughly $88,000 and total Q3 revenue reaches $131,500 under base case assumptions. If that close slips to Q4, Q3 revenue drops to approximately $94,000 — still cash-flow positive, but the gap matters for your hiring timeline. You show both numbers in your LP update, which Starch drafted in about 20 minutes after you noted the carry event and confirmed the close status. Three LPs flagged in the CRM as not contacted in over 60 days got a personal note before the quarterly mailing went out.

Measurement

How you'll know it's working

Management fee revenue recognized per quarter vs. fee schedule

Called capital as a percentage of total committed capital

Quarterly revenue variance: base case vs. actuals

Realized carry by portfolio company and exit quarter

LP touchpoint cadence — days since last contact per LP

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 priced for established managers with dedicated ops teams — typically $50k+ per year with implementation time measured in months, not days.

Excel + QuickBooks manual export

No recurring cost, but you're spending two days per quarter reconciling tabs, the model breaks every time something changes, and it can't draft your LP narrative.

HubSpot for LP CRM

General-purpose sales CRM that forces your LP relationship workflow into a deal-pipeline metaphor it wasn't designed for; schema customization requires paid tiers and admin time you don't have.

Visible.vc or Synaptic for investor reporting

Solid for pushing metrics to LPs but doesn't connect to your actual financial data or model forward scenarios — you're still building the numbers separately and pasting them in.

On Starch RECOMMENDED

One platform — scenario planning, investor reporting, crm 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 actually understand fund accounting — management fees, capital calls, carry waterfalls?

Starch doesn't ship a fund-accounting template out of the box, but you describe your fee structure in plain language and Starch builds the model around it. If you say '2% on called capital, called quarterly, with a 20% carry above an 8% hurdle,' the Scenario Analysis app and your custom revenue forecast will reflect that structure. Your QuickBooks data provides the actuals baseline; Starch doesn't try to replace your fund administrator.

Can Starch pull data from my fund administrator's portal if they don't have an API?

Yes. If your fund admin (or any LP reporting platform) has a web portal you can log into, Starch can automate it through your browser — no API needed. This is a standard Starch pattern, not a workaround.

Is QuickBooks data actually synced in real time, or do I have to trigger a refresh?

Starch syncs your QuickBooks data on a schedule — invoices, bills, payments, vendors, and journal entries. It's not instant on every transaction, but you're not triggering manual exports either. For a quarterly revenue forecast workflow, scheduled sync is the right model.

Note: QuickBooks P&L report views are temporarily unavailable — does that affect me?

The QuickBooks P&L and Transaction List report views are temporarily disabled pending a fix. Entity-level data — your invoices, bills, payments, and journal entries — syncs normally. Your quarterly revenue forecast is built on entity-level data, so this shouldn't block you. The report view limitation is worth knowing if you expected a one-click P&L pull.

I have LPs in HubSpot already. Can I import those contacts into Starch's CRM?

Yes. Connect HubSpot from Starch's integration catalog — the agent queries it live. You can pull your existing LP contacts into Starch's CRM and describe any additional fields or structure you want. You're not starting from a blank slate.

Is Starch SOC 2 certified? My LPs will ask.

Not yet — Starch is not SOC 2 Type II certified as of today. If that's a hard requirement from your institutional LPs for data you plan to store in Starch, that's worth knowing upfront. It's on the roadmap.

Can the LP quarterly update actually go out from Starch, or do I have to paste it somewhere else?

Starch can send email directly through Gmail. You draft the update in Starch, review it, and it sends from your Gmail account to your LP list. No copy-pasting into another platform.