How to run a linkedin outreach campaign as Small Investor Relations Teams

Marketing & GrowthFor Small Investor Relations Teams3 apps11 steps~22 min to set up

Your two-person IR team is supposed to be building LP relationships, not copy-pasting LinkedIn URLs into a spreadsheet. But when a GP asks you to warm up three family offices before the Q3 close, you spend a Tuesday afternoon manually searching, clicking through profiles, checking connection status, drafting individual notes, and logging everything in a shared Google Sheet that's already six weeks out of date. You have no automated way to run a targeted outreach list, no system that tracks who's in sequence, and no visibility into whether that message you sent 12 days ago ever got a reply. LinkedIn's native tools assume you're a recruiter, not an IR professional managing 40-80 LP relationships at once.

Marketing & GrowthFor Small Investor Relations Teams3 apps11 steps~22 min to set up
Outcome

What you'll set up

A LinkedIn Automation app that reviews inbound connection requests against your LP ICP (family office principals, UHNW allocators, pension fund associates), sends targeted outbound invites to prospects matching criteria you define in plain English, and runs on a human-paced schedule so your account stays safe
A CRM that tracks every LP prospect by relationship stage, last contact date, commitment interest level, and fund focus — and surfaces 'who haven't I followed up with in 30 days?' as a real answer, not a manual filter
An automated loop that pipes new LinkedIn connections into the CRM, drafts a follow-up email via the Email Agent, and logs the thread so the CFO who also thinks they own this data can actually see it
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.

Data sources & config

LinkedIn Automation runs through browser automation on your LinkedIn account — no API needed, activity looks human-paced. The CRM connects to Gmail via Starch's scheduled sync so email thread history stays current against LP contact records. The Email Agent also connects to Gmail via scheduled sync. LinkedIn connection and enrichment data flows from browser automation into the CRM as new connections are accepted.

Prompts to copy
Build me a LinkedIn outreach campaign targeting family office principals and UHNW allocators at funds between $200M and $2B AUM. Send connection requests to 15-20 people per day with a note that mentions our Q3 fund close and references a shared interest in private credit. Flag anyone who accepts within 48 hours so I can prioritize follow-up.
Build me an IR prospect CRM. Fields I need: full name, institution, AUM range, fund focus (private equity / credit / real assets / multi-strategy), relationship stage (cold / connected / in conversation / soft commit / passed), last contact date, notes on LP interest, and whether they came in through LinkedIn or a warm intro. I want a view that shows everyone in 'connected' stage where last contact was more than 21 days ago.
Triage my inbox for messages from LP prospects and existing LPs. Summarize threads longer than 3 messages, draft a reply for any message that's been sitting unanswered for more than 48 hours, and set a follow-up reminder for any thread where I'm waiting on a response about a capital commitment or data room access.
Run these in Starch → or paste them into your favorite agent
Walkthrough

Step-by-step

1 Install the LinkedIn Automation app from the Starch App Store. Define your LP ICP in plain English: fund type, title seniority, AUM range, geography. Starch uses this description to filter both inbound connection requests and build your outbound target list.
2 Set your daily outbound volume (15-20 invites is a safe ceiling) and write a connection note template that references your current fund, a relevant market theme, or an upcoming close. Starch personalizes each note with the prospect's name and institution.
3 Install the CRM app and describe your IR pipeline stages — for example: Cold, LinkedIn Connected, Intro Call Scheduled, Data Room Shared, Soft Commit, Closed, Passed. Starch builds the schema around your actual process, not a generic sales funnel.
4 Add the LP-specific fields your team actually uses: AUM range, fund focus, commitment capacity, referral source, and whether the LP has invested in your previous funds. These become first-class CRM columns, not buried notes.
5 Connect Gmail via Starch's scheduled sync. The CRM will automatically attach relevant email threads to each LP contact record, so you can see the full conversation history without switching tabs or searching your inbox.
6 Set up a daily automation: every morning, Starch checks who accepted a LinkedIn connection request in the last 24 hours, creates or updates their CRM record, and flags them in a 'new connections — follow up' queue.
7 For each flagged new connection, the Email Agent drafts a follow-up message — typically a short note offering a fund overview deck or a 20-minute call. You review, edit if needed, and send with one click. The sent message is logged back to the CRM record.
8 Set a second automation to surface your 'at-risk relationships' view every Monday: anyone in the 'In Conversation' or 'Data Room Shared' stage where last contact is older than 21 days gets surfaced with a draft follow-up queued for your review.
9 Use the CRM's natural-language query interface to answer ad-hoc GP questions: 'Which LPs have we connected with on LinkedIn in the last 60 days but haven't had a call with?' or 'Show me everyone in the soft commit stage for Fund III sorted by commitment capacity.'
10 At quarter-end, export the LP pipeline view to include in your GP reporting — who's in the funnel, what stage, and what the projected commitment volume looks like across the active cohort.
11 Publish your customized IR CRM schema to the Starch marketplace (optional) so other funds running a similar structure can use it as a starting point — or keep it private.

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

Q3 2026 Fund IV LP Outreach — 6-Week Pre-Close Sprint

Sample numbers from a real run
LinkedIn outbound invites sent (browser automation)480
Connection requests accepted127
Follow-up emails drafted by Email Agent, sent after review119
LP prospects moved to 'In Conversation' stage in CRM34
Prospects who requested data room access11
Soft commits tracked in CRM by close date4

Six weeks out from the Fund IV first close, the GP asked for a push on family office allocators who hadn't been in a prior fund. The IR team used LinkedIn Automation to target principals at single-family offices and small MFOs with between $300M and $1.5B AUM, running 15-20 outbound invites per day with a note referencing the fund's private credit focus and the Q3 close timeline. Over six weeks, 127 of 480 invites were accepted — a 26% acceptance rate. Each new connection triggered the CRM automation: Starch created a prospect record, pre-filled institution and title from the LinkedIn profile, and queued a follow-up email via the Email Agent. The IR associate spent about 20 minutes each morning reviewing and sending the drafted emails rather than writing them from scratch. By week four, 34 prospects had moved to 'In Conversation,' and the team used the CRM's 'last contact over 21 days' view to make sure no warm lead went cold during the final push. The GP's Monday morning question — 'where are we on family offices?' — became a 30-second CRM query instead of a 90-minute manual reconciliation across LinkedIn, Gmail, and a spreadsheet.

Measurement

How you'll know it's working

LinkedIn connection acceptance rate (target: 20-30% for cold ICP outreach)
Days from connection to first substantive conversation (email reply or call booked)
LP prospects in 'In Conversation' stage as % of total connections accepted
Follow-up response rate on Email Agent-drafted outreach
Pipeline coverage ratio: soft commit capacity vs. fund close target, updated weekly in CRM
Comparison

What this replaces

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

LinkedIn Sales Navigator + manual spreadsheet CRM
Sales Navigator gives you search filters but you're still copy-pasting names, manually logging every touchpoint, and building no connection between your LinkedIn activity and your email follow-up — it's three disconnected tools stitched together by human memory.
Juniper Square or Addepar (institutional IR stack)
Purpose-built for LP reporting and capital account management, but neither runs outbound LinkedIn campaigns or drafts follow-up emails — and at $50k+/year they assume you have an IR-ops analyst to configure and maintain them.
Expandi or Dripify (LinkedIn automation tools)
Purpose-built for LinkedIn sequences but they output into their own dashboard, not into your CRM or inbox — you still do the reconciliation manually, and they have no awareness of your email threads or LP relationship history.
HubSpot CRM + LinkedIn integration
HubSpot's CRM is configurable but the LinkedIn integration is shallow (no browser-level automation), and building an IR-specific schema in HubSpot means hiring someone to set it up and maintain it — which is the headcount problem you're trying to avoid.
On Starch RECOMMENDED

One platform — linkedin automation, 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

Will LinkedIn flag or restrict my account if I'm running automated outreach?
This is the right question to ask any LinkedIn automation tool. Starch runs LinkedIn Automation through browser automation — meaning it navigates LinkedIn the way a human would, at human-paced intervals. It doesn't use LinkedIn's API or send high-volume API calls that trigger rate limiting. You set the daily volume ceiling (we'd suggest staying under 20 outbound invites per day for a new campaign) and Starch spreads activity across the day. That said, no automation tool can guarantee LinkedIn won't adjust its detection over time — this is a known risk with any LinkedIn outreach tool, and you should be aware of it.
Our LP contact data is sensitive. Where does it live?
Starch is not SOC 2 Type II certified today — that's worth knowing upfront. LP contact data you enter into the CRM lives in Starch's database. Gmail messages sync into Starch on a schedule. If your fund has a strict data residency or compliance requirement that mandates SOC 2 certification, Starch isn't the right fit yet. For IR teams at mid-size funds where the primary concern is operational efficiency rather than enterprise compliance, most find the tradeoff acceptable — but you should make that call with your CCO.
Can Starch connect to our existing LP CRM — like Juniper Square or Affinity?
Juniper Square and Affinity aren't in Starch's scheduled-sync provider list. Affinity and similar tools are likely reachable from Starch's integration catalog of 3,000+ apps — connect them and the agent queries them live when your CRM or automation needs the data. If they're not available via the catalog, Starch can automate them through browser automation — no API required. The more common pattern for IR teams is using Starch's CRM as the operational layer for active outreach and early-stage relationships, while Juniper Square stays as the system of record for committed LPs and capital accounts.
The GP wants to see the outreach pipeline in a dashboard. Can Starch build that?
Yes. Once your CRM is running, you can describe a dashboard to Starch in plain English: 'Show me a weekly view of LP pipeline by stage — total prospects, movement between stages week-over-week, and projected commitment capacity for soft commits.' Starch builds it on top of your live CRM data. You can share a link with the GP so they have a live view without needing to log into the CRM themselves.
We use Outlook, not Gmail. Does this still work?
Yes. Starch connects directly to Outlook — messages, events, calendars, and contacts sync on a schedule the same way Gmail does. The Email Agent and CRM thread sync work against Outlook instead of Gmail. Swap the connection during setup and everything else in the workflow is identical.
How does Starch handle the LinkedIn enrichment for LP contacts who aren't in the CRM yet?
When LinkedIn Automation logs a new accepted connection, Starch pulls the publicly visible profile data — name, title, institution, headline — via browser automation and pre-populates the CRM record. This isn't a deep data enrichment API; it's what's visible on the LinkedIn profile page. For more detailed firmographic data (AUM, fund strategy, prior investments), you'd add that manually or query a data provider you already have access to.

Ready to run run a linkedin outreach campaign on Starch?

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

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