Investor Relations

How to track lp commitments and distributions as Real Estate Founders

Investor RelationsFor Real Estate Founders3 apps12 steps~24 min to set up

You closed three deals last quarter and you're still tracking LP commitments in a Google Sheet that someone last updated six weeks ago. Distributions get calculated in Excel, cross-referenced against a Juniper Square export, and emailed out manually — one LP at a time. When an investor calls asking about their Q1 distribution or their percentage of the Meridian Street deal, you're either digging through your inbox or stalling while you pull up the right tab. Capital call notices live in DocuSign. Commitment amounts live in the sheet. Actual wire confirmations live in your email. Nothing talks to anything else, and reconciling it all before an investor call takes two hours you don't have.

Build this on Starch → See the apps used

Investor RelationsFor Real Estate Founders3 apps12 steps~24 min to set up

Outcome

What you'll set up

A live LP commitment ledger that shows every investor, their committed capital, drawn capital, remaining unfunded commitment, and distribution history — all in one place, updated from your bank feed automatically

An investor reporting workflow that drafts distribution notices and capital call summaries on a set cadence, pulling transaction data from your connected Plaid accounts so you're not manually reconciling wire logs

Alerts that flag when a distribution wires out, a capital call deadline is approaching, or an LP's committed amount doesn't match what's been drawn — before an investor surfaces it to you

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 CRM Transaction Insights

Data sources & config

Starch syncs your Plaid bank accounts on a schedule — every transaction, balance, and wire confirmation flows into the LP ledger automatically. Gmail is connected as a scheduled-sync provider so distribution notice threads are logged against each LP contact in the CRM. QuickBooks is connected as a scheduled-sync provider for entity-level invoice and payment data. For any LP portal or fund administrator site that doesn't have a direct integration, Starch automates it through your browser — no API needed.

Prompts to copy

Build me an LP commitment tracker for my real estate fund. Each LP should have: name, entity name, committed capital, total capital called to date, remaining unfunded commitment, distribution history by quarter, and which properties they're invested in. I want to see the full table and be able to filter by property or vintage year.

Set up a monthly distribution notice workflow. After I enter the distribution amount and the property name, draft individual notices for each LP showing their pro-rata share, wire it to me for review, then send to each LP from my Gmail account.

Connect my Plaid bank accounts and flag any incoming or outgoing wire over $25,000. Label it as a capital call receipt, distribution payment, or unclassified, and add it to the LP ledger automatically.

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

Walkthrough

Step-by-step

1 Connect your Plaid business bank accounts — Starch syncs every transaction on a schedule, so capital call receipts and distribution wires show up automatically without manual entry.

2 Connect QuickBooks as a scheduled-sync provider. Starch pulls invoices, bills, payments, and journal entries so your fund-level accounting data matches what's in your LP ledger.

3 Install the Investor Reporting starter app from the Starch App Store. Fork it to add real estate-specific fields: property name, deal vintage, LP entity type (individual, family office, institutional), and waterfall tier.

4 Describe your LP commitment table in plain language — tell Starch every field that matters to you, including promote structure and preferred return thresholds, and it builds the schema around your fund docs, not a generic template.

5 Import your existing LP list from your spreadsheet or from the CRM app. Starch maps the columns, cleans duplicates, and flags any LP where committed capital doesn't have a corresponding subscription agreement on file.

6 Set up the distribution calculation workflow: enter the distributable amount and the property, and Starch calculates each LP's pro-rata share based on their ownership percentage, applies the waterfall, and generates a draft notice for each investor.

7 Connect Gmail as a scheduled-sync provider so every LP email thread — capital call replies, distribution confirmations, K-1 questions — is logged against the right contact in your CRM automatically.

8 Build a capital call aging view: which LPs have received a capital call notice, which have wired, and which are past the funding deadline. Starch cross-references the Plaid transaction log against the LP ledger to flag gaps.

9 Set up a weekly alert that checks your Plaid feed for any inbound wire over $10,000, matches it against open capital calls, marks the LP as funded, and sends you a Slack message with the updated funded-to-committed ratio.

10 Configure the monthly investor update cadence. Starch pulls the quarter's distribution total, the fund's cash balance from Plaid, any new acquisitions or dispositions, and drafts a one-page update to send to all LPs — you review, edit, and approve before anything goes out.

11 For fund administrator portals or LP reporting platforms that don't have a direct integration, Starch automates the login and data pull through your browser — no API required — and brings the data back into your LP ledger.

12 Set a quarterly reconciliation automation: Starch compares your LP ledger's distribution totals against QuickBooks payment records and Plaid outbound wires, surfaces any discrepancy over $500, and flags it for your review before K-1 season.

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 Distribution — Meridian Street Industrial Portfolio

Sample numbers from a real run

Total distributable cash (Plaid, operating account)	187,500
Preferred return accrual paid out (8% pref)	62,000
Return of capital portion	85,500
Promote (20% above pref)	40,000
LP distributions — 14 investors	147,500

After Q1 close on the Meridian Street portfolio, you had $187,500 in distributable cash sitting in the operating account. Starch pulled the Plaid transaction log, matched the incoming rent wires against the property ledger, and calculated each LP's distribution based on their ownership percentage and the fund's 8% preferred return waterfall. The 14 LPs in the deal range from a $50,000 individual commitment to a $400,000 family office position. Starch drafted 14 individual distribution notices — each showing the LP's ownership percentage, their share of the $147,500 LP distribution, the pref vs. return-of-capital split, and the cumulative distributions to date. You reviewed the batch, approved it, and Starch sent each notice from your Gmail account. The capital call aging view confirmed all 14 LPs had fully funded their Q4 2025 capital call; the one LP who was 12 days late on that call showed up as a flag in the ledger with the wire confirmation date logged automatically from Plaid.

Measurement

How you'll know it's working

Funded-to-committed ratio by LP and by property (% of total committed capital actually drawn)

Distribution yield by vintage year (annualized distributions ÷ invested capital, per deal)

Capital call collection time (days between notice sent and wire received, per LP)

Unfunded commitment aging (total remaining LP commitments available to call, by deal)

LP communication lag (days since last substantive email exchange, flagged in CRM)

Comparison

What this replaces

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

Juniper Square

Purpose-built for fund administration and investor portals, but costs $10K+/year, requires a setup engagement, and doesn't connect to your CRM, calendar, or Gmail — so you still manage LP relationships in a separate tool.

Google Sheets + DocuSign + Gmail

Zero cost and infinitely flexible, but the moment you have 15+ LPs across 3 deals, reconciling distributions manually takes a full day per quarter and the error rate climbs.

HubSpot + Excel

HubSpot manages LP contacts well but knows nothing about your cap table, committed amounts, or distribution history — you're still doing the financial layer in a spreadsheet that's disconnected from everything else.

Carta (real estate)

Strong equity management and waterfall modeling, but positioned for VC-backed funds and requires LP adoption of the portal — not ideal if your LPs are family offices who prefer email.

On Starch RECOMMENDED

One platform — investor reporting, crm, transaction insights 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 store my LP financial data, or does it just query it live each time?

For Plaid and QuickBooks, Starch syncs your data on a schedule and stores it in Starch's database — so your LP ledger and distribution history are always there without waiting for a live query. For apps you connect from Starch's integration catalog, data is queried live when your app runs rather than stored persistently. Worth knowing if you're expecting a long-horizon data warehouse — Starch is built for live operational surfaces, not archived analytics.

Can Starch handle a waterfall calculation with a preferred return and promote?

Yes — you describe your fund's waterfall structure in plain language (preferred return percentage, promote tier, return-of-capital ordering) and Starch builds the calculation logic into your LP commitment app. If your structure changes between deals, you describe the new terms and Starch updates the logic. You're not locked into a template someone else designed.

What if my fund administrator uses a portal that doesn't have an API?

Starch automates it through your browser — no API needed. If you can log in and click through it, Starch can pull the data and bring it back into your LP ledger. This works for fund admin portals, state filing systems, and any other web-based tool that doesn't offer a direct integration.

Is Starch SOC 2 certified? My institutional LPs will ask.

Not yet — Starch is not SOC 2 Type II certified. If you have LPs with hard compliance requirements around SOC 2 or on-prem data storage, that's worth knowing upfront. Most founder-led funds with individual and family office LPs find it's not a blocker at their current stage.

Can I track LPs across multiple deals or funds in one place?

Yes. When you describe your LP commitment tracker to Starch, you tell it which fields matter — including which properties or fund vehicles each LP is invested in. You can filter the ledger by deal, by vintage year, or by LP entity, and the distribution history is tracked per deal so you're not conflating returns across separate projects.

What happens if a QuickBooks report doesn't match what I see in my LP ledger?

Starch syncs QuickBooks entity-level data — invoices, bills, payments, vendors, journal entries. Note that QuickBooks report views like the standard P&L and Transaction List are temporarily unavailable due to an upstream connector issue; entity-level data syncs normally. For full report-view reconciliation, you can export from QuickBooks and import it into Starch manually, or use Plaid transaction data as the primary source and QuickBooks as the confirmation layer.