Investor Relations

How to manage a fundraising pipeline as Small Investor Relations Teams

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

You're two people running an IR operation that was designed for a six-person team. Every quarter you're manually pulling data from QuickBooks, Stripe, and Plaid into a spreadsheet to build the LP letter, then reformatting that same data into a separate deck for the GP. Your investor CRM lives in a shared HubSpot that your CFO also edits, so half the contact records are wrong. Commitment pacing and capital call schedules live in a Google Sheet nobody trusts. LPs email you asking about their J-curve position and you spend 45 minutes hunting down the answer across three systems. Juniper Square or Addepar would solve some of this, but at $50k+ per year and a six-month onboarding, that's not the quarter you're in.

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 fundraising pipeline CRM with investor stages, commitment amounts, and communication history — built around how your fund actually tracks a raise, not Salesforce's idea of a sales cycle

An LP reporting dashboard that pulls live from QuickBooks, Stripe, and Plaid so your quarterly letter starts from real numbers instead of a copy-paste chain

Automated follow-up workflows that flag cold investor contacts, draft re-engagement emails, and surface every LP thread before your next check-in call

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 Email Agent Meeting Notes

Data sources & config

Starch connects directly to QuickBooks (scheduled sync — invoices, payments, journal entries), Stripe (scheduled sync — charges, subscriptions, payouts), and Plaid (scheduled sync — transactions and balances) to feed your LP reporting dashboard with live financial data. Gmail is connected via scheduled sync for email thread history and the Email Agent's triage workflow. LinkedIn enrichment runs through browser automation — no API needed — to keep investor contact profiles current. DocSend and Intralinks are web-reachable and can be automated through your browser for data room access tracking. For LP portals or fund admin systems that don't have a direct API, Starch automates them through your browser.

Prompts to copy

Build me a fundraising pipeline CRM with stages: Prospecting, First Meeting, Diligence, Term Sheet, Committed, Wired, Passed. Each contact should have fields for: fund they're from, commitment amount, soft circle amount, last contact date, preferred communication channel, and any open asks. Flag any contact I haven't touched in 30 days.

Set up an email triage workflow that monitors my inbox for LP emails — anything from a tracked investor domain — prioritizes them above everything else, drafts a first-pass reply pulling in their commitment amount and last meeting summary, and sets a follow-up reminder if I haven't replied in 48 hours.

After every LP call, generate a summary with key decisions, open asks the LP made, any updated commitment signals they gave, and the next action with an owner and due date. Archive it under the contact record in my fundraising CRM.

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

Walkthrough

Step-by-step

1 Connect QuickBooks, Stripe, and Plaid to Starch (scheduled sync). This is your financial ground truth — fund cash position, capital calls wired, management fee revenue. It takes about 10 minutes and updates on a schedule automatically.

2 Start from the Starch CRM app and describe your fundraising pipeline in plain language: the stages you run, the fields that matter (commitment size, soft circle, LP tier, GP relationship owner), and any status flags like 'in legal review' or 'waiting on LPAC approval.' Starch builds the schema around your process.

3 Import your existing investor contact list — from HubSpot, a spreadsheet, or wherever it lives right now. Tell Starch to deduplicate, standardize fund names, and flag any records missing a last-contact date.

4 Connect Gmail via scheduled sync and wire it into the CRM so every inbound and outbound thread with a tracked investor domain attaches to the right contact record automatically. No more hunting for the email chain before a call.

5 Set up the Email Agent to triage LP emails: prioritize by sender (tracked investors first), summarize any thread longer than 10 messages, and draft a reply that pulls the LP's commitment amount and last meeting notes into context. You review and send; it does the prep.

6 Before your next LP close, build a commitment tracker dashboard: describe it as 'a table showing every investor, their soft circle, their hard commitment, amount wired, and the delta — sorted by close date and flagged red if wired is more than 10% below committed.' Starch pulls from your CRM and Plaid data together.

7 Set up Meeting Notes to auto-join LP calls and investor diligence meetings. After each call it generates a summary, extracts any updated commitment signals or open asks, and appends them to the investor's CRM record — so your GP always has context before the next conversation.

8 Build a quarterly LP reporting draft automation: tell Starch 'every quarter, pull net cash position from Plaid, revenue and payout data from Stripe, and expense data from QuickBooks, then draft the financial section of our LP letter with actuals vs. prior quarter and a one-paragraph narrative.' You edit the commentary; the numbers come pre-loaded.

9 Wire a follow-up automation that runs weekly: 'check my CRM for any investor in Prospecting, First Meeting, or Diligence stages who hasn't had an outbound touch in 21 days — draft a short re-engagement email for each, and send me a Slack summary of who needs attention this week.'

10 For LP portal updates (DocSend access requests, Intralinks file uploads, or fund admin portals without a direct API), Starch automates them through your browser — no API needed. Describe the action once and it runs on a schedule or trigger.

11 At the end of each close, run your commitment reconciliation: 'compare committed amounts in my CRM against wired amounts in Plaid for this close period, flag any gaps over $50k, and generate a reconciliation table for the CFO.' This replaces the manual spreadsheet that always has a version-control problem.

12 Publish your LP KPI dashboard (fund cash runway, capital called vs. committed, LP net IRR by vintage if you track it) as a Starch dashboard that refreshes automatically — so when the GP asks 'where are we,' you send a link instead of rebuilding a slide.

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 LP Close — $18M target, 22 active investor contacts

Sample numbers from a real run

Hard commitments in CRM	16,500,000
Soft circles not yet committed	3,200,000
Wired to date (from Plaid)	11,750,000
Gap: committed but not wired	4,750,000
LP emails triaged this quarter (Email Agent)	94
Follow-up drafts sent without manual writing	61

Going into the Q1 2026 close, the two-person IR team had $16.5M in hard commitments against an $18M target, with $3.2M in soft circles still floating. The commitment tracker dashboard — pulling CRM data against Plaid wire confirmations — showed a $4.75M gap between committed and wired, and flagged four LPs whose wire was more than 10% below their commitment amount. The team ran the reconciliation prompt ('compare committed amounts in my CRM against Plaid inflows for the Q1 2026 close, flag gaps over $200k') and had a clean list in under two minutes instead of the usual 90-minute spreadsheet exercise. The Email Agent had triaged 94 LP emails across the quarter, drafting 61 replies with the LP's commitment amount and last call summary pre-loaded — the team edited most but wrote none from scratch. Meeting Notes captured every LP diligence call and appended updated commitment signals to each CRM record, so when the GP asked 'where does Greenfield Capital stand,' the answer was one click away instead of a Slack thread asking 'who took notes on that call?'

Measurement

How you'll know it's working

Capital committed vs. target close amount (by LP and in aggregate)

Committed vs. wired gap — dollars not yet received from hard commitments

LP contact recency — days since last outbound touch, by pipeline stage

LP email response time — hours from inbound to first reply

Quarterly LP letter cycle time — days from quarter-end data pull to letter sent

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 IR and LP reporting, but starts at $50k+/year, assumes a dedicated IR-ops analyst to configure, and doesn't let you build custom surfaces on top of your own data without professional services.

HubSpot (Sales Hub)

Capable CRM but designed for B2B sales cycles, not fundraising pipelines — you'll spend weeks configuring it for LP stages, commitment tracking, and fund-specific fields, and the CFO will keep breaking your setup.

Salesforce + a BI tool

Powerful but requires a Salesforce admin and a separate analytics layer; total cost of ownership for a two-person IR team easily exceeds $30k/year in licenses plus implementation time.

Google Sheets + Notion

Free and flexible, but there's no connection to your live financial data — every quarterly update is a manual copy-paste cycle and you're always one bad paste away from a version-control disaster.

Q4 Inc. (for public company IR)

Strong for public company shareholder communications and transfer agent data, but it's a one-way reporting tool — it doesn't connect to your internal financial systems or let you build the pipeline CRM your team actually manages.

On Starch RECOMMENDED

One platform — crm, email agent, meeting notes 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 connect to Juniper Square, Addepar, or iLevel directly?

Not via a direct scheduled sync today. If your LP portal or fund admin system is web-accessible, Starch can automate it through your browser — reading data, navigating reports, or filling forms — without needing an API. For QuickBooks and NetSuite, Starch syncs directly on a schedule, which covers the financial data most LP reports are built from.

Can Starch pull data from our DocSend or Intralinks data room?

DocSend and Intralinks are web-reachable, so Starch can automate actions in them through your browser — checking access logs, uploading documents, or reading engagement data — without a formal API connection. Describe what you need and Starch builds the automation.

Is QuickBooks data in Starch always current?

Starch syncs QuickBooks on a schedule — invoices, bills, payments, vendors, journal entries, and more. One honest caveat: QuickBooks report views (P&L, Transaction List, Vendor Expenses) are temporarily unavailable due to an upstream connector issue, but entity-level data syncs normally. For most LP reporting use cases — pulling actuals for a letter, checking cash position, reconciling capital calls — the entity data is what you need anyway.

We're not SOC 2 certified — is Starch appropriate for LP data?

Starch is not SOC 2 Type II certified today, and there's no on-premises deployment option. If your LPs require SOC 2 Type II or your compliance team requires self-hosted infrastructure, that's a real constraint worth naming. For most emerging managers and mid-size funds, the question is whether the data surfaces you're building (pipeline CRM, KPI dashboard) contain fund-confidential information — and whether Starch's current security posture meets your threshold. That's a conversation worth having with your CFO before you go live.

Can two team members use the same CRM and dashboards in Starch?

Yes. The CRM and dashboards you build in Starch are shared surfaces — both IR team members see the same data, and the GP can be given view access to the dashboard you build for them. The Email Agent and Meeting Notes are tied to individual inboxes and calendar connections, so each team member connects their own Gmail or Outlook.

What does Starch actually replace versus complement?

Starch doesn't replace your fund admin, your ERP, or your transfer agent. It connects to them — QuickBooks and NetSuite via scheduled sync, Stripe and Plaid for cash movements, LP portals via browser automation — and lets you build the surfaces you actually work in on top of that data. Think of it as the layer between your systems of record and your day-to-day workflow: the LP letter draft, the commitment tracker, the investor CRM, the follow-up queue.