Investor Relations

How to manage a fundraising pipeline as Chief of Staff and Founder's Office

Investor RelationsFor Chief of Staff and Founder's Office3 apps11 steps~22 min to set up

You're the one who actually knows where the Series B stands. Not because anyone keeps you informed — because you built the tracker yourself, in a Notion doc that's two weeks stale, cross-referenced with a HubSpot pipeline the CEO updates sporadically and a Gmail thread where the last warm intro is buried under 40 replies. Every investor update means you're manually pulling deal stages from HubSpot, hunting through Gmail for the last touchpoint, checking Google Calendar for which partners have taken a second meeting, and assembling it all into a board-ready view that will be out of date before the PDF is attached. You spend 4-6 hours a week on pipeline hygiene that should be automatic.

Build this on Starch → See the apps used

Investor RelationsFor Chief of Staff and Founder's Office3 apps11 steps~22 min to set up

Outcome

What you'll set up

A live fundraising pipeline that pulls HubSpot deal stages, Gmail thread history, and Google Calendar meetings into one view — updated automatically, no manual reconciliation

An automated investor-update workflow that drafts the weekly status email from your pipeline data, flags stale relationships, and routes it to the CEO for one-click review

A pre-meeting brief generator that surfaces the last email, last meeting notes, and current deal stage for every investor call on today's calendar

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 syncs your HubSpot contacts and deals data on a schedule, syncs your Gmail messages on a schedule (read and send), and syncs your Google Calendar events on a schedule — these three are the core data sources. For any investor firm research (fund size, portfolio, recent news), Starch automates the lookup through your browser — no API needed. Connect Notion from Starch's integration catalog; the agent queries it live when pulling in context from your existing deal memos.

Prompts to copy

Build me a fundraising pipeline CRM with stages: Warm Intro, First Meeting, Partner Meeting, Term Sheet, Due Diligence, Closed, Passed. Each deal should track the lead partner name, firm AUM, check size interest, last email date (pulled from Gmail), last meeting date (pulled from Google Calendar), and next action. Let me filter by stage and sort by days since last contact.

Every Friday at 4pm, draft an investor update email that summarizes which deals moved stages this week, which investors haven't heard from us in 14+ days, and what the next ask is for our top 5 active conversations. Pull deal data from my fundraising CRM and surface it as a draft I can edit before sending.

Before every investor meeting on my Google Calendar, generate a one-page brief: who the firm is, where we are in the process with them, a summary of the last email thread, key decisions from our last meeting, and three suggested talking points based on what we discussed before.

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

Walkthrough

Step-by-step

1 Connect HubSpot — Starch syncs your contacts, companies, and deals on a schedule. If your current pipeline lives in HubSpot, your deal stages and contact records come over automatically. If it's a spreadsheet or Notion doc, describe the schema you want and Starch builds a clean CRM from scratch.

2 Connect Gmail — Starch syncs your messages on a schedule so the pipeline always reflects the latest touchpoint date, thread summary, and who sent the last email. This is what kills manual trackers: you never have to update 'last contact date' again.

3 Connect Google Calendar — Starch syncs your events so the pipeline knows which investors have had first meetings, partner meetings, or follow-up calls. Meeting count per investor becomes a calculated field, not something you track by memory.

4 Start from the CRM app in the Starch App Store and customize it for fundraising: add the fields that matter to you (check size interest, lead partner, firm AUM, source of intro) and remove the fields that don't. Describe your stage names exactly as your team uses them.

5 Wire the Email Agent to your fundraising pipeline. Tell Starch: 'Flag any investor in my CRM who I haven't emailed in 10 days and draft a short check-in based on our last conversation.' The agent reads the Gmail thread history and writes contextual follow-ups, not generic nudges.

6 Set up the pre-meeting brief automation using Meeting Notes. Tell Starch to generate a brief for every calendar event tagged as an investor meeting: pull the deal stage, last email summary, and prior meeting notes into a single doc that appears in your inbox 30 minutes before the call.

7 Set up the Friday investor-update draft. Tell Starch to pull all deals that changed stage this week, all investors past the 14-day contact threshold, and the next action for your top five active conversations — then draft the update email for your review. You edit and send; Starch does the data assembly.

8 Use Starch's browser automation for investor research that has no API. Tell Starch: 'For each new contact I add to my fundraising CRM, find their firm's LinkedIn page and pull their recent portfolio announcements.' Starch automates that through your browser — no WeWork-style manual lookup needed.

9 Build a board-prep view that surfaces pipeline health metrics: total active conversations by stage, average days per stage, conversion rate from first meeting to term sheet, and deals added vs. passed in the last 30 days. Describe what you want to see and Starch builds the dashboard.

10 After each investor call, Meeting Notes captures the transcript, extracts decisions and action items, and writes the follow-up back into the CRM deal record. The pipeline stays current without you touching it between calls.

11 When the CEO asks for a pipeline read before a board call, you pull up the live dashboard instead of rebuilding a slide. The data is current because the sync runs continuously — not because you spent Sunday afternoon reconciling spreadsheets.

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

Series B Pipeline — Week of March 10, 2026

Sample numbers from a real run

Sequoia (Partner Meeting)	0
Benchmark (First Meeting — 18 days stale)	0
Andreessen (Term Sheet — diligence active)	0
Lightspeed (Warm Intro — no response)	0
General Catalyst (Passed)	0

It's Thursday morning before a 9am partner meeting at Sequoia. The brief Starch generated at 8:30am shows: last email was March 6 (you sent a one-pager on GTM metrics, no reply yet), last meeting was February 28 (first partner meeting, positive on the space, wanted to see 90-day retention cohort), and the suggested talking point is to lead with the retention data from the February cohort before they ask. Meanwhile, the Friday update draft Starch queued shows that Benchmark has gone 18 days without contact — their last email was a request for the cap table that you sent but never confirmed receipt of. The agent flagged it and drafted a two-line check-in for your review. Andreessen is in active diligence; Starch pulled three open action items from last week's meeting notes (audit committee question, customer reference list, AWS cost structure) and surfaced them in the deal record so nothing gets dropped. You sent the board the pipeline dashboard link instead of a slide — they can see the stage breakdown live. Total time to prepare for the week: 25 minutes to review and send what Starch drafted, versus the 5 hours it used to take.

Measurement

How you'll know it's working

Days since last investor contact by deal (target: no active deal >10 days without a touchpoint)

Stage conversion rate: First Meeting to Partner Meeting (benchmark against prior rounds)

Average days per stage (flags where deals are stalling before the CEO notices)

Number of new intros added vs. deals passed per week (pipeline velocity)

CEO time in fundraising activities per week (you're protecting this number)

Comparison

What this replaces

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

HubSpot alone

HubSpot stores the deal data but won't auto-draft investor updates, generate pre-meeting briefs from Gmail and Calendar context, or flag stale relationships — you're still the glue between the CRM and your inbox.

Notion fundraising tracker

Notion is great for docs and context but has no live sync with Gmail or HubSpot, so last-contact dates and deal stages are only as current as the last time someone manually updated them.

Affinity CRM

Affinity is purpose-built for relationship tracking and relationship intelligence, with stronger network-graph features — it's the right tool if relationship mapping across your investors' portfolios is the primary need; Starch wins if you want to compose the pipeline tracker alongside board prep, OKR tracking, and exec briefings in one place.

Spreadsheet + Gmail search

Works until the pipeline hits 30+ conversations and the CEO starts asking for weekly updates — at that point the maintenance cost of the spreadsheet exceeds any flexibility advantage.

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 actually read my Gmail, or does it just connect to it?

Starch syncs your Gmail messages on a schedule and stores them in its database so your apps can query against them. That's what lets it calculate 'days since last contact' and draft context-aware follow-ups. The Gmail OAuth consent screen currently shows the underlying connector's name rather than Starch — that's a known item on the roadmap. Your data doesn't leave Starch's infrastructure.

We use HubSpot as our system of record for deals. Will Starch overwrite it?

No. Starch syncs HubSpot data on a schedule — it reads your contacts, companies, and deals. It doesn't write back to HubSpot unless you explicitly build an automation that does so. You can use Starch as a read layer and reporting layer on top of HubSpot without touching your HubSpot data.

What if our pipeline is in a spreadsheet or Notion, not HubSpot?

Connect Notion from Starch's integration catalog — the agent queries it live. For Google Sheets, same approach. Or describe your pipeline schema to Starch and build a fresh CRM from scratch using the CRM app as a starting point. Importing from a spreadsheet and having Starch clean up the field mapping is a first-class use case.

Is Starch SOC 2 certified? Investors sometimes ask about our data handling.

Not yet — Starch is not SOC 2 Type II certified. If your investors or legal team require SOC 2 certification before you route sensitive deal data through a new tool, that's worth knowing upfront. It's on the roadmap.

Can Starch track whether an investor opened the email we sent?

Not directly — Starch reads your Gmail sent and received messages, but email open tracking requires a separate pixel/tracking layer (like a CRM with built-in open tracking). What Starch can tell you is whether you got a reply and how many days ago.

How does the pre-meeting brief work if the investor relationship spans two years of email history?

Gmail sync is capped at 30 messages per page to avoid errors on long HTML threads. For very long relationships, the brief will draw on recent threads rather than the full history. You can tell Starch to prioritize the last 60 days of email context for the brief, which is usually what matters before a partner meeting.