Customer Support

How to watch for churn risk accounts as Asset Management Founders

Customer SupportFor Asset Management Founders2 apps12 steps~24 min to set up

As an emerging fund manager, your 'customer support' is LP communication — and the early warning signs of a dissatisfied LP look a lot like churn: unreturned capital calls, delayed questionnaire responses, terse replies to your quarterly updates, or silence after a rough quarter. You're tracking this across Gmail threads, a Calendly log, and maybe a spreadsheet you update when you remember. You don't have an IR associate. When an LP goes quiet for 60 days before a new raise, you find out too late. The large fund tools like Juniper Square have LP portal tracking built in at $50k/year. You're trying to do the same job with your inbox.

Build this on Starch → See the apps used

Customer SupportFor Asset Management Founders2 apps12 steps~24 min to set up

Outcome

What you'll set up

A CRM that flags LPs who haven't had meaningful contact in 30+ days, so you know who to reach out to before they go cold ahead of your next close

An automated weekly digest surfacing engagement signals — unreplied emails, missed calls, skipped meetings — ranked by LP relationship importance and deployment size

A churn-risk dashboard that correlates LP communication gaps with fund timeline milestones (capital calls, quarterly reports, re-up windows) so you can act before the silence becomes a problem

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

Data sources & config

Starch syncs your Gmail data on a schedule so the CRM and Email Triage app can read LP thread history and flag unanswered messages. Starch also syncs your Google Calendar data on a schedule to track meeting cadence with each LP. Starch syncs your Slack data on a schedule so the Monday digest automation can deliver to your preferred channel. If you use Outlook instead of Gmail, Starch connects directly to Outlook the same way.

Prompts to copy

Build me a CRM for tracking LP relationships. Each LP record should have: commitment size, deployment percentage drawn, last contact date, preferred communication channel, relationship health score (1-5 I set manually), notes from our last conversation, and a flag for 're-up likely.' Show me a view called 'At Risk' that surfaces anyone I haven't contacted in more than 30 days, sorted by commitment size.

Set up a churn-risk automation: every Monday morning, look at my LP CRM records and my Gmail history, identify any LPs I haven't emailed or had a meeting with in the past 30 days, and send me a Slack message listing them by name, commitment size, and days since last contact. If anyone has a capital call due in the next 45 days and is in the 'At Risk' view, flag them separately.

Triage my inbox and surface any emails from LPs that I haven't replied to in more than 5 business days. Draft a short follow-up reply for each one and show it to me before sending.

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

Walkthrough

Step-by-step

1 Connect Gmail (or Outlook) and Google Calendar in Starch — both sync on a schedule, so LP thread history and meeting records are available the moment you open a Starch app.

2 Install the CRM starter app from the App Store and describe your LP relationship model: tell Starch what fields matter (commitment size, deployment drawn, re-up likelihood, relationship health, last contact date) and it builds the schema around how you actually work.

3 Import your existing LP list — from a spreadsheet, a previous CRM, or by having Starch scan your Gmail for recognized LP domains and bootstrap contact records automatically.

4 Define your 'At Risk' threshold: tell Starch that any LP with no email reply, no meeting, and no outbound message from you in 30 days should appear in the At Risk view, sorted by commitment size descending.

5 Install the Email Triage app (Founder Inbox) and configure it to prioritize LP emails above all other inbox categories — so a quiet LP surfacing with a question doesn't get buried under vendor emails.

6 Set up the Monday morning churn-risk automation: Starch queries your CRM for At Risk LPs, cross-references Gmail for any missed replies, and posts a ranked digest to Slack with names, days-since-contact, and upcoming capital call flags.

7 For each flagged LP, the Email Triage app drafts a brief re-engagement note — pulling from your last conversation thread so the outreach references something specific, not a generic check-in.

8 Add a relationship health score field you update manually after each meaningful LP interaction — a 1-5 scale you set — so the At Risk view can weight recent-but-terse contact differently from a genuine warm relationship.

9 Set a second automation trigger: if any LP's relationship health score drops to 2 or below, Starch sends you a Slack alert immediately (not just on Monday), with the LP name, commitment size, and their last message.

10 As you approach a new close or capital call window, pull a report from the CRM: 'Show me all LPs with re-up likelihood marked Yes or Maybe, sorted by At Risk status, and tell me the last date I contacted each one.' Use that list to prioritize outreach in the 60 days before the close.

11 After each LP call or meeting, log a quick note in the CRM — Starch updates the last contact date automatically from your calendar, but your written note is what keeps the relationship score accurate.

12 Review the At Risk digest weekly and close the loop: when you've reached out, mark the contact logged, and Starch resets the 30-day clock.

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 II pre-close LP engagement sweep, February 2026

Sample numbers from a real run

LP: Meridian Family Office — commitment $2M, 0% deployed, 47 days since last contact	2,000,000
LP: Chen & Partners — commitment $500K, 100% deployed, re-up likely, 34 days since last contact	500,000
LP: Okafor Capital — commitment $1M, 60% deployed, skipped last quarterly call, 61 days since last contact	1,000,000
LP: Sunrise Endowment — commitment $3M, 40% deployed, capital call due March 15, 22 days since last contact	3,000,000

It's February 3rd and you have a Fund II first close targeted for April 15th. You open Starch on Monday morning and the automated digest hits your Slack: three LPs are in the At Risk view. Meridian Family Office — $2M commitment, not yet deployed, hasn't heard from you in 47 days — is at the top. Okafor Capital, a $1M LP who skipped your December quarterly call and hasn't responded to your January update email, is flagged with a relationship health score of 2 (you marked it down after the skipped call). Starch has already drafted a re-engagement email to both, pulling from your last conversation threads. The Meridian draft references a specific portfolio company you discussed in October; the Okafor draft acknowledges the December call was rescheduled and offers a 20-minute catch-up. You review both, edit one line in the Okafor draft, and send. Separately, Sunrise Endowment has a $3M capital call due March 15th — they're not in the At Risk view (you spoke 22 days ago) but Starch surfaces them in the capital-call alert because the 45-day window just opened. You schedule the follow-up now instead of remembering in three weeks. Chen & Partners, your most likely re-up, is 34 days out — just inside the threshold. You log a note after a quick call on Tuesday and the clock resets. By the time your April close arrives, you haven't lost a room because you forgot to follow up.

Measurement

How you'll know it's working

Days since last meaningful LP contact, broken down by commitment size tier

Percentage of LPs in the At Risk view 60 days before a capital call or close window

Email reply rate from LPs on quarterly reports and capital call notices

LP re-up conversion rate (LPs marked 'likely' who actually commit to Fund II)

Average time to reply to inbound LP questions (from Gmail thread history)

Comparison

What this replaces

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

Juniper Square

Purpose-built for LP relationship management and portal access, but starts around $50k/year and assumes you have a dedicated IR or ops person to configure and maintain it — not practical for a sub-$100M fund with no back office.

HubSpot CRM + manual Gmail tracking

HubSpot can track email threads and deal stages but doesn't understand fund-specific constructs like commitment size, deployment percentage, or re-up likelihood out of the box — you'd spend more time configuring it than using it, and the churn-risk automation still doesn't exist.

Affinity CRM

Affinity is designed for VC relationship tracking and has good network mapping, but it's priced for established funds, requires integration work for the automations Starch handles natively, and won't connect your LP contact history to a capital call calendar trigger without custom engineering.

Spreadsheet + Gmail search

Free and already in use, but the 30-day at-risk check is manual, the Monday digest doesn't exist, and the re-engagement drafts are written from scratch — the whole workflow runs on you remembering to do it, which is the thing that fails during a close.

On Starch RECOMMENDED

One platform — crm, founder inbox 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 threads, or does it just see subject lines?

Starch syncs your Gmail messages on a schedule — full message content, labels, and send/receive metadata. The CRM can surface the last substantive email you sent to an LP, not just that a thread exists. One honest note: Gmail message sync is capped at 30 messages per page to avoid errors on long HTML threads, so very old deep-thread history may require manual review.

I track LPs in a spreadsheet right now. Can Starch import that?

Yes — describe the structure to Starch and it imports your LP list, maps the fields to the CRM schema it builds for you, and flags duplicates or missing data. If your spreadsheet has custom columns (commitment size, deployment drawn, re-up notes), tell Starch what they mean and it builds those fields into the CRM schema from the start.

What if an LP uses a different channel — WhatsApp, text, or LinkedIn DMs?

For LinkedIn messages, Starch syncs your LinkedIn connection and message data on a schedule, so DM history can feed into the last-contact tracking. For WhatsApp or SMS, those aren't currently synced automatically — you'd log those interactions manually as notes in the CRM, which updates the last-contact date. Browser automation can reach web-based WhatsApp if you want to pull in those threads, but that would be a custom workflow.

Is this the same as the Customer Support Agent I saw in the App Store?

No — the Customer Support Agent (coming soon, request beta access) is built for resolving inbound customer tickets at volume using a knowledge base. What you're building here is an LP relationship monitoring system using the CRM and Email Triage apps. They're different surfaces for different jobs. LP 'churn risk' is really about relationship engagement gaps, not ticket resolution.

Is Starch SOC 2 certified? My LPs may ask.

Not yet — Starch is not currently SOC 2 Type II certified. If your LPs or your own compliance posture require SOC 2 certification before you connect fund data, that's an honest reason to wait. It's on the roadmap.

Can I share the At Risk view with a part-time IR contractor without giving them access to my whole Starch account?

Starch doesn't currently have granular role-based access that would let you share a single view with an external contractor while locking down everything else. For now, the digest automation outputs to Slack, which you can share with a contractor in a channel without full Starch access.