Sales & CRM

How to enrich leads with linkedin data as Small Investor Relations Teams

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

Your IR contact list lives in three places: a shared Google Sheet your CFO updated last quarter, a HubSpot trial someone set up and never fully configured, and whatever your Outlook contacts pulled in from the last capital call distribution. When an LP asks who the GP met with at the Goldman conference, you spend 20 minutes cross-referencing LinkedIn manually. When you're building out the Q2 LP letter distribution list, you don't know which contacts have current titles, which have moved firms, or which LPs have added a co-investor who should be in the loop. LinkedIn is the freshest source of truth for institutional investor data, but opening 40 profiles to check titles before a send is a full afternoon you don't have.

Build this on Starch → See the apps used

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

Outcome

What you'll set up

A live investor CRM where every LP, prospective LP, and intermediary contact has a current LinkedIn profile, title, firm, and last-contact date — refreshed automatically, not when you remember to check

An outbound workflow that identifies investors matching a target profile (fund size, strategy, geography) and queues LinkedIn connection requests on your behalf at a pace that looks human

A triage layer on your inbox that surfaces LP replies, intro requests, and commitment-related threads so you're never three days late on an investor email

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 LinkedIn Automation Email Agent

Data sources & config

Starch connects directly to Outlook (scheduled sync) for email thread history and calendar data, and uses browser automation on LinkedIn to enrich contact profiles and run outreach — no LinkedIn API needed. The CRM surfaces are built on top of your Outlook data via scheduled sync; LinkedIn enrichment runs through browser automation and updates contact records on a schedule you set.

Prompts to copy

Build me an investor CRM with fields for LP name, firm, commitment amount, fund number, preferred communication channel, last meeting date, and LinkedIn profile URL. I want a pipeline view that shows active prospects by stage: introduced, first call, under diligence, soft-circled, committed. Pull in email thread history from Outlook so I can see the last message for each contact without leaving the CRM.

Set up LinkedIn Automation to review incoming connection requests and accept anyone who is a partner, principal, or investment director at a family office, endowment, foundation, or institutional LP. Also send outbound invites to people matching this profile: fund-of-funds or endowment professionals in the US or Europe with 5+ years of experience, and leave a thoughtful comment on posts from IR contacts I haven't spoken to in over 60 days.

Create an Email Agent that triages my Outlook inbox and flags anything from existing LPs or contacts in my CRM as high priority, summarizes any thread longer than 5 messages, and drafts a reply for capital call notices, distribution questions, and meeting requests. Set a follow-up reminder for any LP email I haven't replied to within 48 hours.

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

Walkthrough

Step-by-step

1 Connect Outlook to Starch via scheduled sync. Starch pulls your messages, contacts, and calendar events on a recurring schedule — this is the foundation that ties LP email history to CRM records.

2 Start from the CRM app in the Starch App Store. Describe your investor pipeline stages and the fields that matter to your fund (commitment amount, fund number, soft-circle date, LP type) in plain English — Starch adapts the schema to match, not the other way around.

3 Import your existing contact list — paste in the spreadsheet or connect your existing contact source. Starch maps fields and flags duplicates. Any contacts with a LinkedIn URL get queued for enrichment.

4 Activate LinkedIn Automation. Define your criteria for who Starch should accept, who to reach out to, and which existing IR contacts' posts to engage with. Starch runs this through browser automation on your account at human-paced intervals.

5 Let LinkedIn Automation run for 48–72 hours. Starch visits each contact profile in your CRM and updates title, firm, and current employer. Contacts who have moved funds or been promoted are flagged for your review.

6 Set up the Email Agent on your Outlook inbox. Tell it which senders are always high priority (existing LPs, your CFO, your fund admin) and what kinds of threads to summarize and draft replies for — capital call questions, distribution inquiries, meeting requests.

7 Review the Email Agent's draft replies queue each morning. For LP inquiries that touch fund data, the agent can pull context from the CRM (last meeting date, commitment amount, fund number) to make the draft accurate, not just polite.

8 Build a 'stale contacts' automation: ask Starch to identify every LP or prospect in the CRM you haven't emailed or met with in 90 days and surface them in a weekly digest with their current LinkedIn title and a suggested outreach note.

9 Configure an outbound LinkedIn sequence for your target LP profile — describe the investor type, geography, and firm size you're prospecting. Starch queues connection requests daily and logs each accepted connection back to the CRM automatically.

10 Before each quarterly LP letter distribution, run a CRM audit: ask Starch 'which contacts in my CRM have LinkedIn profiles that haven't been checked in 60 days or more?' and trigger a fresh enrichment pass to catch job changes before the send.

11 Set a standing weekly automation: every Monday, surface any LP replies or capital call threads from the past seven days that haven't received a response, and show me the three prospects who've accepted a LinkedIn connection but haven't been contacted by email yet.

12 Publish the investor CRM as a shared app your CFO can view (read-only) so they stop maintaining their own spreadsheet — one source of truth, no version conflicts.

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 IV Pre-Marketing Push, Q1 2026

Sample numbers from a real run

Existing LP contacts imported from shared sheet	147
Contacts with stale or missing LinkedIn data flagged on import	61
LinkedIn profiles enriched via browser automation in first 72 hours	58
Contacts with firm or title changes detected	14
Outbound connection requests sent to target LP profile over 3 weeks	89
New connections accepted and logged to CRM	34
LP email threads triaged and draft replies queued by Email Agent	23

Heading into Fund IV pre-marketing, your IR contact list had 147 names spread across a Google Sheet and an Outlook contact folder. You connected Outlook to Starch (scheduled sync) and built a CRM in about an hour by describing your pipeline stages and the fields your GP cares about — commitment amount, LP type, fund number, last meeting date. On import, Starch flagged 61 contacts with missing or unverified LinkedIn data. Over the next 72 hours, LinkedIn Automation visited each profile through browser automation and updated records — 14 contacts had moved firms or changed titles since your last capital call. You caught two limited partners who'd joined new family offices that weren't yet in your prospect list, and added them as fresh outbound targets. The outbound sequence ran for three weeks: 89 connection requests sent to endowment and family-office professionals matching your ICP, 34 accepted. Each acceptance was logged to the CRM automatically. Meanwhile the Email Agent triaged your inbox and drafted replies to 23 LP threads — subscription document questions, distribution timing asks, and two meeting requests from prospects who'd seen your deck. What would have been two weeks of manual LinkedIn work and inbox archaeology took your team about two hours of actual decision-making.

Measurement

How you'll know it's working

Percentage of investor CRM contacts with current LinkedIn title and firm (target: >90% verified within last 60 days)

LP email response rate and average reply latency (are you getting back to LPs within 48 hours?)

Outbound connection acceptance rate by target LP segment (endowment vs. family office vs. fund-of-funds)

Number of contacts flagged for title or firm changes per enrichment cycle — a leading indicator of relationship risk

Pipeline coverage ratio: soft-circled commitments as a percentage of Fund IV target close

Comparison

What this replaces

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

Juniper Square or Addepar

Built for fund admin and LP portal management; strong on waterfall calculations and document distribution, but costs $50k+/year, assumes a dedicated IR-ops analyst, and won't enrich your contact list or automate your LinkedIn outreach.

HubSpot + LinkedIn Sales Navigator

A real CRM plus a real prospecting tool, but you're paying for two seats, spending hours configuring HubSpot fields that don't match how an IR team tracks commitments, and still doing LinkedIn enrichment manually or via an expensive add-on.

Affinity CRM

Strong relationship-intelligence layer and widely used in VC; gets expensive fast for small teams, and the enrichment is relationship-graph-based rather than live LinkedIn profile data — titles and firms can lag real changes by weeks.

Google Sheets + manual LinkedIn

Free and flexible, but it's a maintenance job, not a system — no email thread history, no automated enrichment, and your CFO will always have a different version.

On Starch RECOMMENDED

One platform — crm, linkedin automation, 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 my account for using automation?

LinkedIn Automation in Starch runs through browser automation — Starch navigates LinkedIn the way a human would, at human-paced intervals, not via API calls. This is the same approach that keeps your account within LinkedIn's expected activity patterns. No guarantees, but it's materially safer than tools that hit LinkedIn's API directly or send hundreds of requests in a burst.

We use Outlook, not Gmail. Does this work?

Yes. Starch connects directly to Outlook with a scheduled sync that pulls messages, events, calendars, and contacts. Everything described here — email thread history in the CRM, Email Agent triage, follow-up reminders — works on Outlook the same way it works on Gmail.

Is Starch SOC 2 certified? We have LP data in here.

Starch is not SOC 2 Type II certified today. If your fund has strict data-handling requirements from LPs or your compliance team, that's worth knowing upfront. Starch doesn't replace your LP portal (DocSend, Intralinks, Juniper Square) for document custody — it's the operational layer on top of your existing systems.

Can Starch pull data from our existing LP portal or fund admin system?

Starch connects to QuickBooks and NetSuite via scheduled sync for financial data, and to Stripe and Plaid for cash movements. For LP portals like Juniper Square, Addepar, or Intralinks, Starch can automate them through browser automation — no API needed — to pull reports or log data into the CRM. Describe what you need and Starch builds the workflow.

What if a contact's LinkedIn profile is private or they're not on LinkedIn?

LinkedIn Automation only enriches profiles it can visit as your logged-in account. Private profiles and people who aren't on LinkedIn won't be enriched automatically — those records stay as-is in the CRM and can be updated manually. The enrichment pass flags which contacts couldn't be verified so nothing silently falls through.

Can I give my GP or CFO read-only access to the investor CRM?

Yes. Once you've built the CRM app in Starch, you can share it as a view for other users on your account. Your CFO sees the same live data you do without being able to change the pipeline stages or field configuration — which is usually exactly what you want.