Investor Relations

How to issue a capital call notice as Small Investor Relations Teams

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

You're a two-person IR team managing capital call notices the same way a five-person team would — manually. Someone pulls the commitment schedule out of your fund admin system or QuickBooks, cross-references it against the LP contact list in a spreadsheet your CFO last touched in Q3, drafts the notice in Word, formats the PDF, attaches the wire instructions, and sends it from Outlook one LP at a time. If a wire instruction changes or an LP has a sub-advised account with a different notice address, you find out when the money doesn't show up. The whole process takes half a day and you do it three or four times a year minimum.

Build this on Starch → See the apps used

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

Outcome

What you'll set up

A capital call notice workflow that pulls committed capital amounts and LP contact details from your existing systems, drafts individualized notices with the correct wire instructions and call amounts for each LP, and queues them for your review before sending — all without manually reformatting a spreadsheet.

An audit trail of every notice sent, opened, and acknowledged, so when an LP asks 'did you send our Q2 call?' you have a timestamped answer in under 30 seconds.

A reusable template with your fund's legal boilerplate, wire instructions, and signature block that Starch populates each cycle — so the next capital call takes 20 minutes, not half a day.

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 Contract Lifecycle Management

Data sources & config

Starch syncs your QuickBooks data on a schedule (committed capital, LP entities, accounts receivable) and syncs your Gmail on a schedule for sent-notice tracking and reply monitoring. LP contact records live in Starch's built-in CRM app, connected directly. Wire instructions and notice templates are stored in Starch as structured text. Contract Lifecycle Management — coming soon — will handle the formal notice document workflow; in the meantime, notices are drafted as formatted email bodies with PDF attachments generated by Starch. For LP portals like Juniper Square or Intralinks that don't have a direct API, Starch automates them through your browser — no API needed.

Prompts to copy

Pull our LP commitment schedule from QuickBooks and our investor contact list from our CRM. For each LP with an outstanding unfunded commitment, calculate their pro-rata share of a $4.2M capital call at 18% of total commitments. Draft a capital call notice for each LP using our standard template, inserting their name, entity, call amount, due date of May 15 2026, and our wire instructions. Flag any LP where the notice address in the CRM differs from what's in QuickBooks.

Send the drafted capital call notices to each LP via email once I approve them. Log the send timestamp and LP name in a tracker. Set a follow-up reminder for May 12 for any LP who hasn't confirmed receipt.

After the call closes, update each LP's funded commitment total in our investor tracker and generate a one-page capital call summary showing total called, total received, and any outstanding wires — formatted for our GP.

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

Walkthrough

Step-by-step

1 Connect QuickBooks to Starch — Starch syncs your commitment schedule, LP entity names, and accounts receivable on a schedule so the data is current before every call.

2 Import or build your LP contact list in Starch's CRM app — include legal entity name, notice address, signatory, and any sub-advised account details that affect where the notice goes.

3 Store your standard capital call notice template in Starch — the legal boilerplate, your fund name, wire instructions, and signature block — as a reusable document that gets populated each cycle.

4 When a capital call is approved by the GP, tell Starch the total call amount and the call date. Starch pulls each LP's pro-rata share from their unfunded commitment in QuickBooks and calculates individual call amounts.

5 Starch drafts an individualized notice for each LP — correct entity name, correct dollar amount, correct due date — and surfaces any discrepancies between the CRM contact record and the QuickBooks entity name for your review before anything sends.

6 Review the batch in Starch's queue. Edit any individual notice where the facts need adjustment. Approve the batch or send notices one at a time if you prefer.

7 Starch sends each notice from your connected Gmail account and logs the send timestamp, LP name, and call amount in your capital call tracker.

8 Starch monitors your Gmail for LP replies confirming receipt or flagging questions — surfacing those threads in a prioritized view so you're not searching your inbox for 'capital call' across twelve LP email chains.

9 Three days before the wire due date, Starch sends a follow-up reminder to any LP who hasn't confirmed receipt or whose wire hasn't posted.

10 When wires clear, update the funded commitment totals in Starch's LP tracker. Starch reconciles what was called versus what was received and flags any shortfall.

11 Generate a post-close summary — total called, total funded, outstanding wires, and a log of all notices sent and acknowledged — formatted as a one-pager for your GP or CFO.

12 Archive the notice batch with timestamps, amounts, and LP acknowledgments so your audit trail is complete when your fund admin or auditor asks for documentation at year-end.

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

May 2026 Capital Call — Fund III, $4.2M Draw

Sample numbers from a real run

Oakwood Family Office (LP)	840,000
Meridian Endowment Partners (LP)	630,000
Carlisle HNW Fund-of-Funds (LP)	1,050,000
GP Commitment (General Partner)	84,000
Three additional LPs	1,596,000

Fund III is calling 18% of total commitments — $4.2M — to fund two portfolio investments closing in late May. The IR team connects QuickBooks (where the $23.3M total commitment schedule lives) and tells Starch: 'Calculate each LP's share of a $4.2M capital call at 18% of total commitments, due May 15.' Starch pulls seven LP records, calculates individual amounts — Oakwood at $840K on a $4.67M commitment, Carlisle at $1.05M on a $5.83M commitment — and flags one issue: Carlisle's QuickBooks entity name is 'Carlisle HNW FF LLC' but the CRM has 'Carlisle HNW Fund-of-Funds.' The IR associate corrects the notice name before approving the batch. Seven notices send from Gmail within four minutes, each with the fund's wire instructions and the LP's specific dollar amount in the subject line. By May 12, six of seven wires have confirmed; Starch has already sent a follow-up to Meridian Endowment, whose wire ops team needed a re-sent PDF. Total GP time to run the call: 35 minutes, down from the usual four hours.

Measurement

How you'll know it's working

Days from GP approval to last LP notice sent (target: same day)

Percentage of LP wires received by the stated due date

Notice error rate — wrong amount, wrong entity name, or wrong wire instructions per call cycle

Time from call close to funded-commitment reconciliation in the LP tracker

Number of LP follow-up inquiries per capital call (a proxy for notice clarity)

Comparison

What this replaces

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

Juniper Square

Full LP portal with capital call workflows built in, but costs $50K+ per year, assumes a dedicated IR-ops analyst to administer, and doesn't let you build custom surfaces or automations on top of the data without vendor support.

Word + Excel + Outlook (manual stack)

Zero software cost and full control, but every call cycle costs half a day of IR staff time, there's no audit trail unless you build it yourself, and one copy-paste error on a wire amount is a serious problem.

DocuSign + Salesforce

Handles e-signature and CRM well, but you're stitching two expensive platforms together and still doing the math on call amounts and the notice drafting manually — it's a better filing cabinet, not a workflow.

Anduin or Carta Fund Admin

Purpose-built for fund capital call workflows with LP portal access, but priced for institutional managers and the onboarding timeline is measured in months, not days.

On Starch RECOMMENDED

One platform — investor reporting, crm, contract lifecycle 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

Does Starch actually send the notices, or does it just draft them?

Both. Starch drafts the notices and puts them in a review queue. Once you approve, it sends them directly from your connected Gmail account. You stay in control of what goes out — Starch just eliminates the formatting and addressing work. If you'd rather send from Outlook, that's connected the same way.

We use Juniper Square for our LP portal. Can Starch pull data from it?

Juniper Square doesn't offer a public API, so Starch automates it through your browser — no API needed. That means it can pull commitment data, update funded amounts, or upload notices to the portal the same way you would manually, just faster. For the financial source of truth, QuickBooks or NetSuite synced directly to Starch is more reliable than scraping the portal.

Our notices have to match our LPA's exact language and reference specific section numbers. Can Starch handle that?

Yes. You store your standard notice template — legal boilerplate, LPA references, wire instructions, signature block — in Starch once. Every notice Starch drafts uses that template as the base and fills in the LP-specific fields (name, amount, due date). You review before anything sends, so you're the final check on legal language.

What happens if QuickBooks has a different LP entity name than our CRM?

Starch flags the discrepancy before drafting the notice rather than guessing which name is correct. You see the mismatch, correct it in whichever system is wrong, and approve the notice. This is one of the most common sources of capital call errors in manual workflows — Starch makes it visible instead of letting it sail through.

Is Starch SOC 2 certified? We have LPs who ask about data security before we connect anything.

Not yet — Starch is not SOC 2 Type II certified today. That's worth knowing before you run a live LP process through it. Starch doesn't store LP wire instructions in a way that's externally accessible, and data in transit is encrypted, but if your LPs or compliance team require SOC 2 Type II, that's an honest limitation right now.

What about the contract and notice templates — is Contract Lifecycle Management available?

Contract Lifecycle Management is currently in development and not available yet. For capital call notices today, you store your notice template as structured text in Starch and the app populates and sends it. The full CLM workflow — clause library, e-signature routing, renewal tracking — is coming. You can request beta access to get notified when it launches.

We call capital in tranches sometimes — 50% on signing, 50% at close. Can Starch handle that?

Yes. You describe the tranche structure to Starch when you set up the call — 'first notice for 50% of each LP's share, second notice to follow at close' — and it tracks funded amounts against each tranche separately. The commitment tracker in Starch shows where each LP stands against their total commitment across all tranches, not just the current call.