Measure conviction, not activity. Track signals of real intent, such as data room engagement, follow-up questions, introduction of investment committees and commitment timing, rather than meeting counts. This gives partners a realistic forecast and focuses IR effort on LPs most likely to commit.
Something I hear on a lot of calls: the person who keeps the LP pipeline usually isn't a partner. It's the head of platform, the chief of staff, the ops lead or a first IR hire. You own the spreadsheet or the CRM. You prepare the Monday update. And you're often the first person to notice that a lot of meetings are producing very little capital.
That's a hard thing to tell partners. "We've taken 120 meetings" sounds like progress, and without a better measure you have no clean way to say which of those meetings matter. So here's a practical setup for that measure. It also covers the part people skip, because the healthiest pipelines I see were built well before the raise started.
Activity metrics versus conviction signals
Activity metrics count what your team did. Conviction signals record what the LP did. Only the second group predicts a commitment.
| Activity metric | Conviction signal |
|---|---|
| First meetings taken | LP asked for a second meeting with a different partner |
| Decks sent | LP opened the data room and spent time on track record and references |
| Follow-up emails sent | LP sent written questions about strategy, team or terms |
| Events attended | LP introduced you to their investment committee or consultant |
| LPs "interested" | LP named a check size and a decision date |
An LP who says "we love the strategy, keep us posted" and then goes quiet has shown politeness, not intent. An LP who sends a due diligence questionnaire has shown intent, even if the meeting felt cooler.
Define stages by what the LP did
Most pipeline stages are named after your own actions: "Pitched," "Followed up," "Sent materials." Rename them so an LP has to do something to enter each stage:
- Identified: fits the fund on paper. No contact yet.
- Engaged: took a first meeting and asked for materials.
- Diligence: opened the data room, sent questions or asked for reference calls.
- Committee: introduced you to their IC, consultant or a decision-maker you hadn't met.
- Soft circle: named an amount and a timeline, verbally or in writing.
- Committed: signed subscription documents.
The rule is simple. Your team can't move an LP forward by doing more. Only the LP's behavior moves them. This one change takes most of the wishful thinking out of a pipeline.
A simple conviction score
Stages are coarse. Inside each stage, a short score helps you rank where to spend time. Here's a rubric to start with. Adjust the points to your own experience.
| Signal | Points |
|---|---|
| Spent real time in the data room (track record, case studies, references) | +2 |
| Sent written follow-up questions | +2 |
| Asked to speak with portfolio founders or existing LPs | +3 |
| Replied to a pre-raise portfolio update with a question | +2 |
| Introduced IC members or a consultant | +3 |
| Named a check size | +3 |
| Gave a decision date tied to their IC calendar | +3 |
| No LP-initiated contact in 30 days | -3 |
| Said the fund is "a bit early for us" | -2 |
Recalculate the score weekly. If it drops two weeks in a row, ask the LP directly where things stand, or move them back a stage.
Build conviction before the raise starts
This is the part I get most excited about. A pipeline that starts cold on the day the fund opens is already behind. The firms doing this well send prospective LPs portfolio momentum months before they ask for anything: a big customer win, a strong executive hire, a follow-on round led by a respected firm.
The trick is matching it to each LP. An LP with a climate focus hears about the climate companies. An endowment that likes technical founders hears about the research spinout. One generic newsletter to every LP gets skimmed (if it gets opened at all). A short, personal note with news they care about gets a reply.
"Always be raising" sounds right, and it falls apart without a content engine behind it. I used to ghostwrite investor updates as a chief of staff, so I know how long one good update takes. Nobody on a small team is hand-writing 80 personal notes a quarter. The engine is your portfolio data. If the news on each company is already in one place, the chain gets short: portfolio news → a draft for each LP → a partner edits it so it sounds like them and hits send. Don't let these go out automatically.
This feeds the pipeline directly. An LP who replies with a question has shown a conviction signal before the first pitch meeting. When the raise opens, those LPs are your first calls, and they show up already warm.
Weight the pipeline, then calibrate
A raw pipeline total adds every LP's target check together. That number always looks bigger than the fund you'll close. Weight each LP by stage instead.
Say your fund targets $50M and you have $15M committed. Your pipeline looks like this, with starting weights you picked:
| Stage | LPs | Average expected check | Starting weight | Weighted value |
|---|---|---|---|---|
| Engaged | 30 | $1M | 5% | $1.5M |
| Diligence | 12 | $1.5M | 20% | $3.6M |
| Committee | 6 | $2M | 50% | $6M |
| Soft circle | 4 | $2.5M | 80% | $8M |
Raw pipeline: $70M. Weighted pipeline: $19.1M. Add the $15M committed and the honest forecast is about $34M, not "we're well covered."
These weights are made up for the example. Use them through the first close, then look back. What share of LPs in each stage actually committed? Swap the starting weights for your own history. After one fund, your forecast gets much harder to argue with.
Keep the data clean
A forecast is only as good as the CRM behind it, and CRMs go stale fast. Whether you use Affinity, Attio, HubSpot or a well-kept Airtable base, a few rules help:
- Capture from email and calendar, not memory. Most LP activity happens in partners' inboxes. A pipeline that depends on partners logging their own calls goes stale within weeks. Sync email and calendar into the CRM, and have the owner confirm each stage change.
- One owner per LP. Every LP record has one named person responsible for the next step.
- Record the LP's actions, not yours. "LP sent DDQ" is a stage change. "Sent follow-up email" is a note.
- Apply a stale rule. No LP-initiated contact in 45 days means the LP moves back one stage automatically, and the owner gets a task to check in.
- Record the reason for every "no." Fund size, strategy, timing, team. After a full raise, these reasons tell you more about your positioning than any survey.
Existing LPs belong in this system too. Their re-up is the cheapest capital in your next fund. Regular, readable updates keep them warm, ideally in the format each LP already expects rather than one template for everyone; see how to write an LP update that LPs actually read. Cura can draft those LP updates from your portfolio data and create follow-up tasks tied to each company, so the update cadence doesn't slip in the middle of a raise. For first-time funds, family offices as anchor LPs covers where the early pipeline often comes from.
What CRM metrics matter for LP fundraising?
Track stage by LP action, expected check size, days since the last LP-initiated contact and a weighted pipeline value. Add a target close date tied to the LP's own approval calendar. Meeting counts and email volume tell you how busy the team is, not whether capital is coming.
A minimal field set for each LP record:
- Stage (from the six stages above)
- Conviction score
- Expected check size
- LP decision process: who decides, and when their IC meets
- Last LP-initiated contact (date)
- Next step and owner
- Reason for pass, if any
At the fund level, watch four numbers: committed capital, weighted pipeline, stage conversion rates and median days in each stage. If LPs pile up in one stage and stay there, that's where your pitch or your materials need work.
How do IR teams report fundraising progress to partners?
Send a one-page weekly report: committed capital against target, weighted pipeline, LPs that moved stage, LPs that went quiet and the three asks for partners this week. Keep the format the same every week so partners can spot changes in seconds.
Here's a template you can paste into Slack or email every Monday:
Fundraise update, week of [date]
Committed: $X of $Y target. Weighted pipeline: $Z.
Moved forward: LP A (Diligence to Committee), LP B (Committee to Soft circle)
Went quiet: LP C (35 days, owner to check in by Thursday)
New passes: LP D, reason: fund size
Asks for partners: call LP B's CIO before Friday, intro to LP E through a portfolio founder, review DDQ answers for LP A
The "asks for partners" line is the most useful part. It turns the report from a status note into a short to-do list, and partners actually read it because it tells them where their time matters this week. For more on fund-stage fundraising, see raising fund one.