Customer Support

How to track renewals and expansion as Asset Management Founders

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

You're managing 12-18 LP commitments, 3-5 service provider contracts (fund admin, legal, auditor), and renewal cycles across portfolio company service agreements — all tracked in a combination of Google Sheets, calendar reminders, and your own memory. You have no analyst to flag that your fund administrator agreement auto-renews in 45 days or that an LP's side letter includes a preferred terms clause that triggers at the next close. Juniper Square costs $50k/year and assumes you have an ops team to run it. You're the ops team. A missed renewal or a lapsed expansion conversation with a re-upping LP is a real dollar cost.

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 tracks every LP relationship, commitment status, side letter terms, and the last time you actually spoke — with renewal and expansion flags surfaced automatically before they matter

An email-linked renewal tracker that monitors your inbox for contract language, auto-drafts follow-up reminders for expiring agreements, and flags LP re-up windows based on your fund's close timeline

A unified view of which LPs are eligible for expansion (based on commitment tier, communication cadence, and your own notes), so every quarterly LP call has a pre-prepared agenda and a clear ask

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

Data sources & config

Starch syncs your Gmail data on a schedule so the Email Agent has full thread history to pull from when drafting renewal outreach. The CRM connects to Gmail and LinkedIn — Gmail for email thread sync, LinkedIn enrichment through browser automation to keep LP profiles and their firm context current. Any external contract portal or fund admin system that's web-accessible can be automated through your browser — no API needed.

Prompts to copy

Build me a CRM for LP relationship management. Fields I need: LP name, entity type (individual/family office/institution), commitment amount, fund vehicle, side letter flags (MFN clause yes/no, co-invest rights yes/no), last contact date, renewal date or re-up eligibility window, expansion conversation status (not started / in progress / committed), and notes from our last call. Pipeline stages: Active LP, Re-up Eligible, Expansion Conversation Open, Committed to Next Vehicle, Dormant.

Set up automated follow-up reminders: if I haven't replied to an LP email thread in 7 days, flag it. If a contact in my CRM has a renewal date within 60 days, draft me a warm outreach email based on our last conversation thread. Summarize any email thread mentioning 'next fund,' 'additional capital,' or 'co-invest' and surface it to me by 8am Monday.

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

Walkthrough

Step-by-step

1 Start from the CRM app in Starch's App Store. When prompted to describe your process, paste your LP tracking fields: commitment amount, vehicle, side letter terms, re-up eligibility date, and expansion status. Starch configures the schema around what you actually track, not a generic sales pipeline.

2 Import your existing LP list — whether that's a CSV from a spreadsheet or contacts from a prior CRM. Tell Starch which columns map to which fields. It handles the cleanup.

3 Connect Gmail as a scheduled-sync provider. Starch will pull your thread history so the CRM can show you the last time you emailed each LP and what was discussed, without you manually logging calls.

4 For each LP record, add their renewal or re-up eligibility date. If your fund has a defined re-up window (e.g., 18 months post-first close), tell Starch the rule and it will calculate the field automatically across all LP records.

5 Set a renewal alert automation: 'Sixty days before any LP's re-up eligibility date, draft me an outreach email that references our last thread and asks to schedule a call to discuss their interest in the next vehicle.'

6 Wire the Email Agent to monitor for expansion signals. Prompt it: 'Flag any inbound email from an LP or prospect that uses language around co-invest interest, additional commitments, or next fund — summarize the thread and add a task to the CRM.'

7 For service provider contracts (fund admin, auditor, legal), create a separate CRM view. Fields: vendor name, contract type, annual cost, auto-renewal date, notice period required, current satisfaction rating. Starch will surface any vendor whose notice window opens in the next 90 days.

8 Set a weekly Monday digest automation: 'Pull every LP and vendor whose renewal or re-up date falls within 90 days. For each, show last contact date, open tasks, and whether I've had an expansion conversation. Send this to me as a Slack message by 8am Monday.' Starch connects to Slack from the integration catalog and queries it live when the automation runs.

9 Before each quarterly LP call cycle, run a prompt against your CRM: 'Which LPs haven't I contacted in the last 45 days, have a commitment over $500k, and have no open expansion conversation?' Use that list to build your call schedule.

10 For LP re-up conversations that close, update the expansion status field in the CRM. Set a trigger: 'When an LP's status moves to Committed to Next Vehicle, draft a follow-up email thanking them and confirming next steps for the subscription docs.'

11 If your fund admin portal is web-accessible, Starch can automate checking it through your browser — pulling contract renewal dates or fee schedules without needing a direct API connection.

12 At the end of each quarter, ask the CRM: 'Show me a summary of expansion conversations opened, closed, and pending this quarter, with total committed capital from re-ups.' This is your fundraising pipeline report without building a separate tool.

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 Re-Up Cycle — $47M Emerging Buyout Fund

Sample numbers from a real run

LP re-up conversations opened (Q1)	8
LP re-up conversations closed (committed to Fund II)	5
Capital committed from re-ups ($M)	9,200,000
Service provider renewals flagged before auto-renew	3
Hours saved on manual LP tracking (est.)	11

Going into Q1 2026, you had 14 active LPs across Fund I and a 90-day re-up window before your Fund II first close target. The Starch CRM flagged 8 LPs whose eligibility windows opened in January — three of them hadn't been contacted in over 60 days. The Email Agent surfaced a thread from a family office LP mentioning 'co-invest appetite in Fund II' that had been buried under deal flow emails. You drafted a follow-up in one click. By the end of Q1, 5 of the 8 re-up conversations had converted, representing $9.2M in Fund II commitments. Separately, the vendor renewal tracker caught that your fund administrator agreement had a 60-day notice window opening February 1st — you used that window to renegotiate fees before the auto-renew triggered, saving roughly $18,000 annually. None of this required a spreadsheet audit or a calendar reminder you'd set 12 months ago and forgotten about.

Measurement

How you'll know it's working

LP re-up conversion rate (conversations opened → capital committed)

Days since last contact per LP — tracked across the full LP roster

Renewal notice windows open in the next 90 days (LP agreements + service provider contracts)

Expansion capital committed as a percentage of target Fund II raise

Email follow-up response rate on re-up outreach

Comparison

What this replaces

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

Juniper Square

Purpose-built for fund LP management but starts at $50k+/year and assumes a dedicated ops person to configure and maintain it — not practical for an emerging manager wearing multiple hats.

Salesforce + custom configuration

Can be configured for LP tracking but requires a CRM admin to build the schema, costs $150+/user/month, and won't auto-draft your LP outreach emails based on thread history.

Google Sheets + calendar reminders

Zero cost and maximum flexibility, but renewal dates live in your head and a spreadsheet doesn't draft your follow-up emails, flag buried LP threads, or give you a Monday morning digest without you building it yourself.

HubSpot CRM

Good general-purpose CRM with solid email integration, but its pipeline model is built for B2B sales, not LP relationship management — you'll spend time fighting the schema rather than adapting it to fund-specific fields like commitment vehicles, side letter terms, and re-up eligibility windows.

Affinity (relationship intelligence CRM)

Strong relationship-graph features used by VC funds, but expensive at scale, doesn't generate draft LP outreach, and doesn't wire into your service provider contract renewals or give you a unified operator view.

On Starch RECOMMENDED

One platform — 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

Can Starch actually track side letter terms and flag when they're relevant — like an MFN clause at a new close?

Yes. You tell the CRM what fields matter — including yes/no flags for MFN clauses, co-invest rights, or any other side letter term — and Starch stores them on each LP record. You can then query across your LP roster: 'Which LPs have MFN clauses and haven't been notified about the terms offered at the Fund II first close?' Starch gives you a real answer, not a canned filter.

Does Starch replace my fund administrator or cap table tool?

No, and it's not trying to. Starch is where you track the relationship and the conversation — who to call, when to call them, what was said last time, and whether they're a re-up candidate. Your fund admin handles the legal and financial record-keeping. The two coexist; Starch just removes the manual work of keeping your own relationship layer organized.

What happens if my fund admin portal doesn't have an API?

Starch can automate it through your browser — no API needed. If you can log in and navigate to a page with renewal dates or contract terms, Starch can pull that data and surface it alongside your CRM records. This is how Starch handles tools that don't expose a formal integration.

Is Starch SOC 2 certified? I have LPs who will ask.

Not yet — Starch is not currently SOC 2 Type II certified. That's worth knowing upfront. If your LPs have formal vendor security requirements, that's a real consideration. It's on the roadmap.

Will it store my historical LP email history, or just new emails going forward?

Starch syncs your Gmail data on a schedule, pulling up to 30 messages per page. For most LP thread histories, that covers what you need. One honest limit: Starch surfaces and queries live data; it's not a long-horizon email archive. If you need a searchable 10-year email warehouse, that's not what Starch is built for. For active relationship management and the last several months of thread context, it works well.

I track some LPs in a spreadsheet and some in my head. Can I start from that mess?

Yes. Import your CSV, tell Starch which columns map to which fields, and it handles the cleanup. For anything that lives only in your head, you can describe the LP record in plain language and Starch will populate the fields. You don't need clean data to start — you just need to start.