Sales & CRM

How to log sales calls to your crm automatically as Small Investor Relations Teams

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

Your two-person IR team runs on a patchwork of call notes in Notion, a shared HubSpot instance your CFO keeps 'optimizing,' and a Gmail inbox where the after-call follow-up email is the only record that a conversation happened. After every LP check-in or capital call call, someone has to manually paste highlights into the CRM — usually you, usually that evening, usually missing three details because the Zoom recording is 47 minutes long. When an LP asks 'what did we discuss in our March call?' you're greedy-searching your sent folder. Investor relations lives and dies on relationship continuity, and you're burning an hour per call just keeping the log accurate.

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 CRM where every LP call is logged automatically — with summary, key topics, and action items — pulled from your meeting notes and email threads, no manual data entry required.

An automatic follow-up draft ready in your Gmail within minutes of the call ending, referencing the actual talking points from that conversation.

A searchable, structured call history for every investor contact — so when an LP asks about their commitment pacing or J-curve question from last quarter, you can pull the exact moment in 30 seconds.

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

Data sources & config

Starch syncs your Gmail data on a schedule, pulling email thread history into each LP contact record in the CRM. Meeting Notes captures and transcribes calls, then the Email Agent reads the summary and drafts outbound follow-ups via Gmail. For LP portals like Juniper Square or Intralinks that don't have a direct integration, Starch automates them through your browser — no API needed.

Prompts to copy

Build me an investor CRM where each contact has fields for LP name, fund commitment size, relationship owner, last contact date, next scheduled touchpoint, and call log notes. Pull email thread history from Gmail for each contact. I want to be able to ask 'which LPs haven't had a call logged in 60+ days?' and get a real answer.

After each meeting ends, generate a summary with key decisions, any capital call or distribution questions raised, action items with owners, and a one-paragraph narrative I can paste into the LP record. Archive every meeting in a searchable history tagged by investor name.

When a call summary is ready, draft a follow-up email to the LP that references the specific topics we discussed — commitment pacing, portfolio company updates, whatever came up — and queue it for my review before sending.

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

Walkthrough

Step-by-step

1 Start from the CRM app in the Starch App Store. Describe your IR-specific fields out loud: LP name, fund vintage, total commitment, pacing status, relationship owner, last call date, next touchpoint. Starch builds the schema to match how you actually track investors, not a generic B2B sales pipeline.

2 Connect Gmail to Starch — Starch syncs your Gmail data on a schedule and surfaces email thread history inside each LP contact record. No more switching between the CRM and your inbox to reconstruct the conversation arc before a call.

3 Set up Meeting Notes from the App Store. Before your next LP call, open Meeting Notes and start a session. It transcribes in real time so you can stay in the conversation instead of typing.

4 When the call ends, Meeting Notes auto-generates a summary: key topics covered (J-curve questions, capital call timing, portfolio company updates), decisions made, and action items with assigned owners.

5 Tell Starch: 'Tag this meeting summary to the LP contact record for [Investor Name] and log today's date as their last contact date.' The call log entry writes itself to the CRM without a copy-paste.

6 The Email Agent reads the call summary and drafts a follow-up email to the LP — referencing the actual topics from that call, not a generic 'great to connect' template. You review and send, or edit first. Either way, the draft is ready in minutes, not the next morning.

7 The sent follow-up automatically threads back into the LP's email history in the CRM, keeping the relationship timeline complete without any extra steps.

8 Set a recurring check: 'Every Friday, show me every LP who hasn't had a call logged in 45+ days and doesn't have a scheduled touchpoint on the calendar.' Starch pulls from the CRM and your Google Calendar — Starch connects directly to Google Calendar — and surfaces the gap list in your weekly IR review.

9 For LP portals where meeting join links or prep materials live — DocSend, Intralinks, or a fund-admin portal — Starch automates access through your browser so you can pull the relevant data room activity into your pre-call prep without logging into four systems.

10 Before each quarterly LP update call, ask Starch: 'Summarize all calls and emails with [Investor Name] in the last 90 days, flag any open action items, and draft a pre-call briefing.' You get a one-page prep sheet in under a minute.

11 After your GP closes an investor round or issues a capital call, run: 'Which LPs had a call in the last 30 days where capital call timing was discussed? Pull their contact details and draft individualized follow-up notes.' Starch filters the call logs and produces drafts personalized to each LP's specific context.

12 Over time, the CRM becomes a genuine institutional record — every call logged, every follow-up tracked, every LP relationship documented — so when your third team member joins or your CFO wants to see the investor engagement history, it's all there.

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 Check-In Series — 14 calls across 3 weeks

Sample numbers from a real run

Call summaries logged automatically	14
Follow-up emails drafted by Email Agent	14
Hours of manual CRM entry eliminated	6
Open action items surfaced across all LP calls	9
LPs flagged as 45+ days since last contact	3

In Q1 2026, your team ran 14 scheduled LP check-in calls across three weeks — a mix of quarterly portfolio reviews and capital call timing conversations. Previously, logging those calls meant blocking 30 minutes after each one to paste notes into HubSpot and draft a follow-up, often slipping to the next morning. With Meeting Notes running on each call, every session produced a structured summary within five minutes of the call ending: what the LP asked about (in most cases, pacing on the Fund III vintage and two specific portfolio company exits), any commitments your team made ('we'll send updated IRR figures by end of week'), and action items with owners. The Email Agent drafted a follow-up for each of the 14 LPs referencing those specific topics — not a template, but a note that reflected the actual conversation. All 14 call records wrote to the CRM automatically. At the end of the three-week series, Starch surfaced 9 open action items across all LP conversations and flagged 3 investors who'd had a call over 45 days ago with no follow-up scheduled — two of whom your CFO had assumed were 'handled.' Total manual CRM entry time: under 20 minutes for the entire series.

Measurement

How you'll know it's working

Days since last logged contact per LP (target: no active LP over 45 days without a scheduled touchpoint)

Call-to-follow-up lag time (target: follow-up sent within 24 hours of every LP call)

Open action items per LP relationship (tracked across all logged calls)

LP engagement coverage rate — percentage of committed LPs with a logged touchpoint in the last quarter

Pre-call prep time per investor meeting (target: under 5 minutes with Starch briefing)

Comparison

What this replaces

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

HubSpot CRM + Gong

Gong gives you excellent call recording and some CRM logging, but the HubSpot configuration to match your actual IR schema — vintage, pacing status, commitment tier — requires an admin and ongoing maintenance; and you're paying for a sales tool built for a 20-person SDR team, not a 2-person IR operation.

Juniper Square / Addepar

These are the institutional IR standard and handle LP portal, capital account, and reporting functions Starch doesn't try to replace — but at $50k+/year they assume a dedicated IR-ops analyst, and neither one gives you an AI that drafts your follow-up email or flags the LP you forgot to call.

Notion + manual call notes

Flexible and free, but there's no automated logging, no CRM intelligence, and 'which LPs haven't I spoken to in 45 days?' requires you to scroll through pages yourself — which is exactly what you're already doing.

Salesforce + Zoom IQ

Enterprise-grade call intelligence and CRM, but the configuration overhead and per-seat cost are sized for a company with a RevOps function — not two people who also write the LP letters.

On Starch RECOMMENDED

One platform — crm, meeting notes, 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 record or transcribe calls automatically, or do I have to start it manually?

You start a Meeting Notes session before the call — it's one click. It then transcribes in real time for the duration of the call and generates the summary when you close the session. There's no automatic bot that joins your Zoom uninvited.

Our LP contacts also live in HubSpot, which our CFO manages. Can Starch pull from HubSpot without replacing it?

Yes. Starch connects directly to HubSpot — it syncs contacts, companies, and deals on a schedule — so you can build an IR-specific view on top of whatever's in HubSpot today without asking your CFO to change anything. You get the CRM surface you want; the CFO's HubSpot stays intact.

Can Starch log calls to Juniper Square or Addepar directly?

Juniper Square and Addepar don't expose the kind of API that would let Starch write structured records into them. Starch won't pretend otherwise. What it can do: automate those portals through your browser to read LP data out, and maintain the call log in Starch's own CRM as your working record. Think of it as your IR team's internal layer on top of the fund admin stack, not a replacement for it.

Is Starch SOC 2 certified? We're cautious about LP data.

Starch is not SOC 2 Type II certified today. That's worth knowing if your LPs or compliance team asks. It's on the roadmap. In the meantime, the data that lives in Starch is the same call summaries and contact notes your team would otherwise keep in Notion or a shared Google Doc — not wire instructions or account statements.

What happens to the Gmail sync — does it store all my emails in Starch?

Starch syncs Gmail messages on a schedule (30 per page), storing enough to surface thread history inside your LP contact records. One thing to know: the Gmail OAuth consent screen currently shows the underlying connector's name rather than Starch — that's a known issue on the roadmap to fix. It's cosmetic, not a security issue, but it's worth flagging to your team before they see it and wonder.

Can I use this for capital call communications, not just relationship logging?

Yes. Once the call log and LP contact records are structured, you can ask Starch to draft individualized capital call communications that reference each LP's specific commitment, pacing, and any questions they raised in recent calls. The Email Agent handles the drafting; you review before anything goes out.