Investor Relations

How to issue a capital call notice as Asset Management Founders

Investor RelationsFor Asset Management Founders3 apps10 steps~20 min to set up

Issuing a capital call notice as an emerging fund manager means stitching together a process with no good tooling. You're pulling committed capital figures from a spreadsheet you built yourself, calculating pro-rata call amounts per LP manually, drafting a notice in Word or Google Docs, chasing DocuSign signatures one by one, and then emailing each LP individually because you don't have a portal. A single call notice takes two to four hours of work that should take twenty minutes. Miss a LP's wire deadline because your follow-up email got buried and you're on the phone explaining yourself. Large funds use Juniper Square or Allvue for this — tools that cost $50k+ per year and assume you have an ops person who does nothing but investor relations.

Build this on Starch → See the apps used
Investor RelationsFor Asset Management Founders3 apps10 steps~20 min to set up
Outcome

What you'll set up

An automated capital call workflow that calculates each LP's call amount from your commitment schedule, drafts a notice letter per LP in your fund's standard format, and routes it for signature — without you doing the math by hand or writing the same letter twelve times.
A tracked record of every call issued, signed, funded, and outstanding, so you can see at a glance which LPs have wired and which need a nudge — pulled from your email and calendar data rather than a separate tracker you'll forget to update.
Follow-up email drafts that go out automatically on your timeline so no LP misses a wire deadline without at least two touches from 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 Email Agent Contract Lifecycle Management
Data sources & config

Wire your LP commitment schedule as an uploaded CSV or Google Sheet (connect Google Sheets from Starch's integration catalog; the agent queries it live). Starch syncs your Gmail data on a schedule so the email agent can track replies and flag non-responses. Contract Lifecycle Management — coming soon — will handle e-signature collection and the signed-notice audit trail; until it launches, Starch drafts each notice and you route it through DocuSign manually, with Starch tracking status via your Gmail sync.

Prompts to copy
Build me a capital call tracker that pulls LP names, committed capital, and prior call amounts from my uploaded commitment schedule CSV. For each LP, calculate their pro-rata share of the current call amount I specify, and generate a capital call notice letter using my fund's standard template. The letter should include fund name, LP name, call amount, wire instructions, and due date.
After I approve each capital call notice, draft a personalized email to each LP attaching their notice and include wire instructions. Set a follow-up reminder for any LP who hasn't confirmed receipt within 48 hours, and a second follow-up three days before the wire due date.
Track the status of each capital call notice — drafted, sent, signed, funded, or overdue — and show me a summary dashboard with total called, total funded so far, and which LPs are outstanding. Update the status when I mark a wire received.
Run these in Starch → or paste them into your favorite agent
Walkthrough

Step-by-step

1 Upload your LP commitment schedule to Starch — a CSV or Google Sheet with LP name, committed capital, and amounts called in prior notices. Connect Google Sheets from Starch's integration catalog so Starch can query it live each time you run a call.
2 Tell Starch the current call details: the total amount being called, the call date, wire due date, and your wire instructions. Starch calculates each LP's pro-rata share based on their commitment percentage.
3 Starch drafts a capital call notice letter for each LP using your fund's standard format — fund name, LP name, their specific call amount, wire instructions, due date, and any required legal language you've specified. Review the batch, not each one individually.
4 Approve the notices. Starch queues a personalized email to each LP with their notice attached. Review the email drafts and send, or set them to go automatically on a date you specify.
5 Starch tracks which LPs have replied to confirm receipt. Any LP without a reply within 48 hours gets a follow-up draft queued — you approve or it goes automatically depending on how you've configured it.
6 Three days before the wire due date, Starch sends a reminder to LPs who haven't confirmed their wire. The reminder references the original call amount and restates wire instructions so there's no 'I didn't have the details' excuse.
7 As wires arrive, mark each LP funded in your capital call tracker. Starch updates the running total — amount called vs. amount funded — and flags any LP who is overdue after the wire date.
8 For overdue LPs, Starch drafts an escalation email referencing the original notice date, call amount, and wire deadline. You review and send; Starch logs the outreach in the LP's thread history so you have a clean record.
9 Once the call is fully funded, Starch generates a close summary — total capital called, total received, date of last wire, and any shortfall — formatted for your own records and optionally included in your next LP update.
10 The entire call record — notices, emails, wire confirmations, follow-ups — lives in Starch tied to the call date, so when an LP asks 'what was my Q3 2025 call amount?' you find it in seconds instead of hunting through Gmail.

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 Capital Call — $2.1M across 14 LPs

Sample numbers from a real run
LP 1 — Family Office, 8.5% commitment178,500
LP 2 — HNW Individual, 6.0% commitment126,000
LP 3 — Institutional LP, 15.0% commitment315,000
LP 4 — Corporate LP, 4.5% commitment94,500
Remaining 10 LPs — combined 66% commitment1,386,000

You're calling $2.1M for a new portfolio investment — 70% of which needs to fund in 18 days. You have 14 LPs with commitments ranging from $500k to $3.5M. Doing this manually, you'd spend an afternoon calculating pro-rata amounts, another hour drafting 14 slightly different letters, and another hour setting up DocuSign envelopes. Instead: you tell Starch the call amount and due date, it pulls each LP's committed capital from your Google Sheet, calculates the 14 individual amounts (LP 3 owes $315,000; LP 1 owes $178,500), and drafts 14 notice letters in your fund's format. You review them in a batch — five minutes instead of an hour. Starch queues the 14 emails with notices attached. By day two, eleven LPs have replied to confirm. Three haven't. Starch flags them; you approve the follow-up drafts and they go out same day. Two wire on day four. One family office is slow — Starch drafts the escalation on day 14, you send it, they wire on day 16. All 14 LPs funded before deadline. Your close summary shows $2,100,000 called and received, with the last wire landing on day 16 of 18. That record — every notice, every reply, every wire date — is searchable in Starch when your auditor asks next year.

Measurement

How you'll know it's working

Days from notice issued to fully funded (target: under 21 days for standard calls)
Percentage of LPs who wire by due date without an escalation touch
Number of follow-up emails required per capital call cycle
Outstanding capital as a percentage of total called at the due date
Time spent by GP per capital call cycle (target: under 30 minutes of hands-on work)
Comparison

What this replaces

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

Juniper Square
Purpose-built for fund administration with a proper LP portal, but pricing starts well above what most emerging managers can justify before Fund II, and setup assumes you have an ops hire to run it.
DocuSign + Excel + Gmail (manual stack)
No software cost but two to four hours per call cycle, no status tracking, and a high probability of a wire deadline getting missed as your LP count grows past ten.
Allvue / iLevel
Institutional-grade portfolio monitoring and LP reporting, but these platforms are built for $500M+ funds with dedicated finance teams — the onboarding alone takes months.
AngelList Stack / Carta Fund Admin
Good for SPVs and early-stage funds with vanilla structures, but customization for non-standard LP agreements or call schedules hits a wall quickly.
On Starch RECOMMENDED

One platform — investor reporting, email agent, 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 do the math on pro-rata call amounts, or do I still calculate those manually?
Starch calculates them. You give it the total call amount and it reads each LP's committed capital from your spreadsheet, divides their commitment by the total fund size, and multiplies by the call amount. You review the figures before anything goes out — but you're not doing the arithmetic.
Can Starch collect LP signatures on the capital call notices?
Contract Lifecycle Management — coming soon — will handle e-signature collection and the signed-document audit trail natively inside Starch. Until it launches, Starch drafts and sends the notices; you route them for signature through DocuSign separately. Starch tracks status by monitoring your Gmail for replies and confirmations.
What if my LP commitment schedule is in a spreadsheet I've maintained myself, not a fund admin system?
That's the typical setup Starch is built for. Connect your Google Sheet from Starch's integration catalog and the agent queries it live. If it's an Excel file, upload it directly. You don't need a fund admin platform feeding structured data for this to work.
Does Starch store copies of the capital call notices for audit purposes?
Starch keeps a record of every notice it generates and every email it drafts or sends. Because Starch syncs your Gmail data on a schedule, the sent-email thread is also accessible. For a formal, signed-document repository with a full audit trail, you'll want Contract Lifecycle Management (coming soon) or to maintain your current DocuSign archive. Worth being honest: Starch is a live data and workflow platform, not a long-horizon document warehouse.
Can I use my fund's own capital call notice template, or does Starch impose its own format?
You give Starch your template — either paste the text with placeholder fields or upload a sample notice — and it fills in the LP-specific fields for each notice. It doesn't impose a format. If your LPA requires specific language or your notices have gone through legal review, paste that version in and Starch works from it.
What happens if an LP wires the wrong amount or needs a correction notice?
You tell Starch: 'LP 3 wired $300,000 instead of $315,000 — draft a correction notice for the $15,000 shortfall with a new due date of [date].' It drafts the correction using the same format as the original. You review and send. The status tracker updates to show LP 3 as partially funded until the balance clears.
Is Starch SOC 2 Type II certified? I may need to tell LPs about the tools I use.
Not yet. Starch is not currently SOC 2 Type II certified. If an LP or your compliance counsel requires SOC 2 Type II for any tool handling fund data, that's worth factoring into your decision. It's on the roadmap.

Ready to run issue a capital call notice on Starch?

Request closed-beta access. Everything is free during beta.

You're on the list! We'll be in touch soon.