Sales & CRM

How to build an outbound email sequence as Small Investor Relations Teams

Sales & CRMFor Small Investor Relations Teams2 apps12 steps~24 min to set up

Your IR team is two people running a reporting operation built for six. Every quarter, you're manually pulling LP contact lists out of a spreadsheet, drafting outbound sequence emails one at a time in Gmail, and chasing CFO sign-off on language that changes anyway. Capital call notices go out in a flurry. Annual meeting invitations get personalized by hand. LPs who haven't committed in two years get the same update as your top-quartile re-investors. You have no sequenced follow-up — just a sticky note that says 'ping Meridian Capital again.' HubSpot is overkill and costs $800/month before you've configured anything. A real outbound sequence for a $50M re-up conversation deserves better than Gmail drafts and a shared Google Sheet.

Build this on Starch → See the apps used

Sales & CRMFor Small Investor Relations Teams2 apps12 steps~24 min to set up

Outcome

What you'll set up

An LP contact CRM that pulls email thread history from Gmail, tracks commitment stage, and surfaces contacts you haven't touched in 30+ days — built specifically for how your fund categorizes investor relationships, not a generic pipeline.

An outbound sequence engine that drafts personalized first-touch emails for LP re-up campaigns, capital call notices, and annual meeting invites, drawing from each LP's historical commitment data and current portfolio performance.

An automated follow-up reminder system that monitors reply status per LP, escalates unanswered messages at the right intervals, and logs every interaction so your CFO sees the same history you do.

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

Data sources & config

Starch syncs your Gmail data on a schedule — message history and labels flow into the CRM automatically so LP thread context is always current. Your LP contact list and commitment data come from a CSV import or manual entry into the Starch CRM. For LP portals like Juniper Square or iLevel that have no direct API, Starch automates them through your browser — no API needed — to pull commitment status or data room activity. Outlook users can substitute Outlook; Starch connects directly to Outlook on the same scheduled sync.

Prompts to copy

Build me an LP CRM where each contact has fields for: fund commitment amount, vintage year, commitment status (prospect / soft-circled / committed / re-upped), last contacted date, preferred communication cadence, and a notes field for GP relationship context. Pull in Gmail thread history for each LP so I can see the last email exchange without leaving the CRM. Flag anyone I haven't contacted in 30 days.

Draft a 3-touch outbound sequence for LPs who invested in Fund II but haven't yet indicated intent on Fund III. Email 1: personalized fund performance summary referencing their Fund II commitment size. Email 2 (if no reply in 7 days): one-paragraph J-curve update and a request for a 20-minute call. Email 3 (if no reply in another 7 days): short re-up deadline reminder from the GP. Pull each LP's commitment amount and vintage from my CRM to personalize each message.

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

Walkthrough

Step-by-step

1 Install the Starch CRM starter app and describe your LP pipeline in plain English: 'I need stages for Prospect, Soft-Circle, Committed, Re-Up Declined, and Passed. Each contact needs fund vintage, commitment size, and GP relationship owner.' Starch builds the schema to match how your fund actually tracks relationships.

2 Connect Gmail (or Outlook) as a scheduled-sync provider. Starch pulls in your message history and maps existing email threads to the LP contacts in your CRM — so every prior correspondence shows up on the contact record without manual logging.

3 Import your existing LP contact list from a spreadsheet or from your fund admin's export. Use Starch's field-mapping tool to align columns like 'Committed Capital' and 'Vintage Year' to the CRM fields you defined in step 1.

4 For LP data sitting inside Juniper Square, iLevel, or a similar portal, tell Starch: 'Log into my Juniper Square account, pull the commitment summary for Fund III, and update each LP's commitment status in my CRM.' Starch automates this through your browser — no API needed.

5 Tell the Email Agent: 'Review my LP CRM and flag every contact with commitment status Prospect or Soft-Circle who I haven't emailed in more than 21 days. That's my outbound target list for this week.' Starch surfaces the list with last-contact dates and commitment context.

6 Give the Email Agent the sequence parameters: 'Draft a 3-touch sequence for Fund III re-up outreach. Use each LP's Fund II commitment amount and the Q1 2026 net IRR of 18.4% in the first email. Keep each message under 150 words. Sign from [GP name].' Review and approve drafts before sending.

7 Set an automation: 'Every Monday at 8 AM, check my Email Agent for any LP in my active sequence who hasn't replied. If they're on touch 1 and it's been 7 days, queue touch 2 for my review. If they're on touch 2 and it's been 7 more days, queue touch 3.' Starch runs this automatically and surfaces a review queue, not a sent pile.

8 For capital call notices, run a separate sequence: 'Draft capital call emails for all LPs with commitment status Committed in my Fund III CRM. Each email should state their pro-rata call amount, wire instructions, and the funding deadline of [date]. Pull call amounts from my CRM commitment field.' Send after legal review.

9 After each LP reply, ask the CRM: 'Log that Meridian Capital replied positively to the Fund III re-up email on April 18, move them to Soft-Circle, and set a reminder for me to follow up with a draft term sheet summary in 5 business days.'

10 Build a sequence performance dashboard: 'Show me open rate by LP segment (re-up vs. new prospect), reply rate by sequence touch, and total capital soft-circled this month, pulling from my CRM commitment stage data.' Starch builds the dashboard; it updates as CRM data changes.

11 Before your quarterly LP update call, ask: 'Pull a brief on each LP I'm meeting this week — their Fund II commitment, last email exchange summary, any open action items in the CRM, and their current Fund III status.' Starch generates a one-page prep doc per LP from your CRM and Gmail history.

12 Publish the sequence template to your Starch workspace so your CFO or a future IR hire can run the same flow without rebuilding it — every prompt, stage, and automation stays documented inside the app.

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

Fund III Soft-Circle Campaign — Q1 2026

Sample numbers from a real run

LPs in Prospect stage (Fund II re-up candidates)	34
Target re-up capital per LP (average)	2,500,000
Emails drafted by Starch Email Agent (3-touch sequence)	102
Hours saved vs. manual drafting (est. 45 min/LP)	25
LPs moved to Soft-Circle within 3-week sequence	11
Capital soft-circled at sequence close	27,500,000

In February 2026, your IR team of two needed to re-engage 34 LPs who invested in Fund II but hadn't yet indicated intent on Fund III. Manually drafting personalized outreach for 34 relationships — with correct Fund II commitment sizes, current net IRR figures, and GP-signed language — would have taken the better part of a week. Instead, you imported your LP list into the Starch CRM with fund vintage and commitment data, connected Gmail as a scheduled-sync provider so thread history was already attached to each contact, and told the Email Agent to draft a 3-touch sequence referencing each LP's $2.5M average Fund II commitment and the fund's 18.4% net IRR as of Q4 2025. Starch produced 34 personalized first-touch emails in one session; you reviewed and approved in about 90 minutes. Touch 2 queued automatically for non-responders at day 7; touch 3 at day 14. By the end of the three-week window, 11 LPs had replied positively and moved to Soft-Circle — representing $27.5M in prospective Fund III commitments — without either IR team member spending a full day on email.

Measurement

How you'll know it's working

Percentage of LP re-up targets who advance from Prospect to Soft-Circle within a 30-day sequence

Capital soft-circled per outbound sequence campaign ($ and number of LPs)

Average days from first-touch email to LP reply or call booked

LP contacts with no outreach in 30+ days (lagging engagement indicator the CRM surfaces automatically)

Hours per quarter spent on LP communication vs. time spent on fund analysis (ratio the team tracks to justify IR tooling spend)

Comparison

What this replaces

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

HubSpot Sales Hub

Capable sequencing tool, but starts at $800+/month for the features a two-person IR team actually needs, requires a dedicated admin to configure custom LP fields, and doesn't connect to your fund admin portals or automate anything in Juniper Square or iLevel.

Salesloft / Outreach

Enterprise-grade sales sequencing built for large SDR teams; overkill for a two-person IR function, priced accordingly, and has no concept of LP vintage, commitment stage, or fund-specific CRM fields without heavy customization.

Gmail + Google Sheets

Free and familiar, but you're manually tracking reply status in a sheet no one updates consistently, there's no sequencing logic, and personalization at 30+ LPs means 30+ individual drafts.

Juniper Square (built-in communications)

Good for formal LP portal communications and document delivery, but not designed for warm outbound sequences or re-up campaigns — and the $50k+ annual cost assumes you're using the full fund admin stack, not just the email module.

On Starch RECOMMENDED

One platform — crm, email agent 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 store my LP contact data and email history, or is it queried live?

Your Gmail or Outlook data syncs to Starch on a schedule — message history and labels are stored in Starch's database so the CRM can surface thread context without a live API call every time you open a contact. Your LP commitment data (imported from a spreadsheet or fund admin export) lives in your Starch CRM. Starch is not a long-horizon data warehouse — it's a live data surface, so it's not the right place to archive 10 years of LP correspondence. For that, keep your existing records system.

Can Starch pull commitment data directly from Juniper Square or iLevel?

Yes, through browser automation. There's no formal Juniper Square or iLevel API connector, but Starch can log into your LP portal through your browser — no API needed — and pull commitment summaries or data room activity to update your CRM. You describe what you want it to retrieve, and it navigates the portal the same way you would.

We use Outlook, not Gmail. Does the email sequencing still work?

Yes. Starch connects directly to Outlook on the same scheduled sync as Gmail — messages, events, calendars, and contacts all flow in. The Email Agent drafts and queues outbound messages through Outlook the same way it does through Gmail.

Is Starch SOC 2 certified? Our LPs will ask about data security before we put their contact info in a new tool.

Starch is not SOC 2 Type II certified today — that's worth knowing before you make a decision. It also has no on-premises or self-hosted option. If your fund's security policy requires SOC 2 Type II for any tool that handles investor contact data, that's a real constraint right now.

What stops us from accidentally sending a draft sequence before it's been reviewed?

Starch queues emails for your review before sending — the automation surfaces a review list, not a sent pile. You approve each batch. You can also tell Starch explicitly: 'Never send outbound LP emails without my approval' and it will hold every draft in queue until you confirm. The Email Agent is designed to prepare and stage, not to fire autonomously on communications this consequential.

Can the CRM track multiple funds (Fund II and Fund III) on the same LP contact record?

Yes. When you describe the CRM schema to Starch, you define the fields and structure. Tell it: 'Each LP contact should have a Fund II commitment amount, Fund II vintage, Fund III status, and Fund III soft-circle amount as separate fields.' Starch builds that schema. You can also add fields later in plain English — 'add a field for co-investment interest' — and the CRM updates.