Sales & CRM

How to run a win/loss analysis as Asset Management Founders

Sales & CRMFor Asset Management Founders2 apps12 steps~24 min to set up

You ran 12 LP meetings last quarter and closed two. You have a vague sense of why the others passed — one said fees were too high, two went with a larger fund, a few just went quiet — but you haven't actually mapped it. That pattern-matching lives in your head and in scattered email threads. You're not running formal win/loss calls because you don't have a process, and you don't have a CRM that captures deal stage progression with exit reasons attached. So every new LP conversation starts from scratch, and you keep making the same pitch adjustments by gut feel instead of data. Large funds have IR teams for this. You have yourself and a messy inbox.

Build this on Starch → See the apps used

Sales & CRMFor Asset Management Founders2 apps12 steps~24 min to set up

Outcome

What you'll set up

A CRM that tracks every LP prospect from first touch to close or pass, with exit-reason fields and stage history built around how you actually run IR

A structured win/loss log that surfaces patterns across fund vintage, LP type, fund size objection, and deal timeline — answered by asking questions in plain English

A recurring digest that tells you which outreach is converting, which objections are clustering, and where to focus IR effort next cycle

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 Growth Analyst

Data sources & config

Starch syncs your Gmail data on a schedule so email thread history surfaces inside the CRM against each LP contact. HubSpot and Apollo.io connect directly to Starch for any existing contact or sequence data you want to import. For LP portals, cap tables, or data rooms hosted on platforms without APIs — like Allvue, Dynamo, or a fund administrator's web portal — Starch automates those through your browser, no API needed. PostHog connects from Starch's integration catalog and is queried live to power the Growth Analyst digest if you're tracking LP-facing product or reporting page engagement.

Prompts to copy

Build me an LP relationship CRM with pipeline stages: Prospect, First Meeting, Materials Sent, Reference Check, Committed, Passed. Add fields for LP type (family office, fund of funds, endowment, HNWI), fund size they typically write, how they found us, primary objection if they passed, and days-to-close. Pull in Gmail thread history so I can see the last email exchange for each contact without leaving the CRM.

Show me every LP that passed in the last 18 months, grouped by their stated objection. Count how many times each objection appears, and flag any LP type where a specific objection clusters — like fund-of-funds repeatedly citing fee load.

Every Monday, email me a summary of my IR pipeline: how many LPs moved to a new stage last week, how many went quiet (no contact in 21+ days), win rate by LP type over the trailing 90 days, and average days from first meeting to commit for closed LPs.

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. Tell Starch your IR pipeline stages and the fields that actually matter to you — LP type, check size range, source of intro, pass reason — and Starch rebuilds the schema around your process, not a generic sales template.

2 Connect Gmail through Starch's scheduled sync. Thread history for every LP contact now appears inline in the CRM so you can see the last three emails without opening your inbox.

3 Import any existing LP list — from a spreadsheet, Notion database, or Airtable — and describe what the columns mean. Starch maps them to your CRM fields and flags duplicates.

4 Go back through every LP conversation from the last 12–18 months and log pass reasons. Ask Starch: 'Which contacts in my Passed stage are missing an objection field?' — it surfaces the gaps and you fill them in batch.

5 Ask Starch to group all passed LPs by objection and cross-tab by LP type. Example prompt: 'Show me a breakdown of pass reasons by LP category for the last two fund vintages.' This is your first real win/loss read.

6 Ask a follow-on question: 'Which objections came up most in first meetings versus later stages?' This tells you whether you're losing people on positioning or on diligence — two very different problems.

7 Set up a pipeline health automation: 'Every Friday, Slack me the count of LPs by stage, flag anyone who hasn't been contacted in 21 days, and show me my commit rate by LP type for the trailing quarter.' Starch runs it on schedule.

8 For LPs that passed on fees, pull their email threads and ask Starch to summarize common language patterns: 'Read the last three email exchanges with LPs who listed fees as their pass reason. What specific concerns came up most?' Use this to sharpen your fee justification before the next close cycle.

9 Track win/loss by intro source. Ask: 'For every committed LP in the last 18 months, what was their source of intro? And for passed LPs, same question — is there a channel where we convert worse?' This tells you where to focus relationship-building.

10 Before each new LP meeting, ask Starch: 'Pull everything I know about [LP name] — past touchpoints, what fund of theirs we're in consideration for, their typical check size, and any notes from prior conversations.' You walk in prepped instead of re-reading emails for 20 minutes.

11 At the end of each close cycle, run a structured debrief: 'Summarize this close cycle — total LPs contacted, conversion rate by stage, top three objection themes, average days to close for committed LPs, and which stage had the highest drop-off.' This becomes your IR post-mortem.

12 Publish the win/loss summary to a Notion page via Starch's scheduled sync so your advisory board or co-GP can see the data without you prepping a separate deck.

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 III Close — Q1 2026 Win/Loss Debrief

Sample numbers from a real run

LPs contacted in close cycle	47
First meetings completed	31
Materials sent (advanced to diligence)	18
Committed	9
Passed — fees cited	6
Passed — fund size / min check mismatch	5
Passed — allocation already deployed	4
Gone quiet / unresponsive	7
Average days, first meeting to commit	54
Conversion rate, first meeting to close	29

At the end of Fund III's first close, you ask Starch to run the debrief. Out of 47 LPs contacted, 31 took a first meeting — a 66% response rate driven largely by warm intros from your existing LP base. Of the 18 who received materials, 9 committed and 15 passed. When you group the passes by objection, fees appear 6 times — but 4 of those 6 are fund-of-funds, not family offices. Family offices passed mostly on check-size minimums: your $500K floor is too high for several smaller FOFs you approached. That's a segmentation mistake, not a pitch mistake. The 7 LPs who went quiet were all cold outreach with no shared connection, and their average time-since-last-contact is 38 days — Starch flagged them at day 21 but you didn't have a follow-up scripted. Average days to commit for the 9 who closed was 54 days, with reference checks adding 12 days on average. Armed with this, you go into Fund III's second close knowing to filter out sub-$500K-capacity FOFs earlier, to build a fee narrative specifically for fund-of-funds diligence, and to have a day-21 follow-up template ready for any LP who goes quiet after materials. That analysis used to take a half-day of spreadsheet work after every close. Now you ask for it.

Measurement

How you'll know it's working

LP conversion rate by stage (first meeting → materials sent → commit)

Win/loss rate by LP type (family office, FOF, endowment, HNWI)

Most common pass reasons, ranked by frequency across the trailing two closes

Average days from first meeting to signed subscription agreement

Percentage of pipeline sourced from warm intro vs. cold outreach, with conversion rate by source

Comparison

What this replaces

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

Salesforce + manual IR tracking

Salesforce can model an LP pipeline but requires admin configuration, a custom object schema, and ongoing maintenance that a solo GP won't have time for — and it doesn't answer plain-English questions about your pass-reason patterns.

Juniper Square / Allvue

Built for fund administration and LP reporting, not IR pipeline management or win/loss analysis — and at $50K+/year, they assume you have an ops team to run them.

HubSpot CRM

HubSpot covers contact and pipeline basics and connects directly to Starch's integration catalog if you want to import existing data, but its schema is built for SaaS sales motions, not LP relationship tracking, and it won't surface cross-close objection patterns without custom reporting you'd need an analyst to build.

Notion or Airtable with manual logging

Flexible and cheap, but you're the query engine — asking 'which LP type converts worst from first meeting to close' means building a formula or filter yourself every time, and it breaks down the moment your data isn't perfectly entered.

Excel / Google Sheets post-mortem

Most emerging managers do this today — a spreadsheet after each close with color-coded pass reasons — but it's backward-looking, lives outside your day-to-day workflow, and doesn't help you catch a stalling LP at day 21 before they go cold.

On Starch RECOMMENDED

One platform — crm, growth analyst 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

I don't have a formal CRM yet — do I need to set one up before I can run a win/loss analysis?

No. Start by describing your LP pipeline to Starch and it builds the CRM schema from scratch. If you have an existing spreadsheet or Notion database with past LP contacts, Starch imports it and maps the columns to the fields you define. You can backfill pass reasons on historical deals and run your first analysis the same day.

My LP conversations are mostly in Gmail. Can Starch read those threads?

Yes. Starch syncs your Gmail data on a schedule and surfaces thread history against each LP contact in your CRM. One honest note: the Gmail OAuth consent screen currently shows the name of Starch's verified connector rather than 'Starch' — that's on the roadmap to fix. The connection is secure; it's a cosmetic issue in the authorization flow.

Some of my LP data sits in my fund administrator's portal. Can Starch reach that?

If your fund admin portal is web-based and you can log in through a browser, Starch can automate it through browser automation — no API needed. This covers most fund admin and data room platforms. If you're unsure, describe what you're trying to pull and Starch will tell you the best path.

What if my LPs don't give me a clear reason for passing — they just go quiet?

That's actually useful data. Starch can flag any LP who received materials and hasn't responded in a defined window — say, 21 days — and you can track those as a 'no stated reason / unresponsive' bucket in your analysis. Over time, the pattern of who goes quiet (LP type, intro source, stage they reached) often tells you something even without an explicit pass reason.

Is Starch SOC 2 certified? I need to know before connecting LP contact data.

Starch is not SOC 2 Type II certified today. If your compliance process requires that certification before connecting LP relationship data, that's worth knowing upfront. There is no on-premises or self-hosted option. If you're comfortable connecting Gmail and CRM data to a non-SOC-2 platform — many emerging funds are, at their stage — you can get started today.

Can Starch connect to my existing HubSpot or Apollo if I already use those for LP tracking?

Yes. HubSpot and Apollo.io both connect directly to Starch, with data synced on a schedule. You can use your existing contacts and deal history as the foundation and build the win/loss analysis layer on top, rather than starting from scratch.