GP · Fund · Daily during a raise
Triage inbound LP interest
Every pending data room and Explorer request gets your decision in one batch, with a fit note per requester, and only the prospects you approve enter your CRM, enriched.
PlanTriage inbound LP interest
Read the pending requests
HeldReads every pending access request on your fundraising data room and on the fund’s Explorer listing.
API actionLook up each requester
HeldChecks each requester against your CRM, so you know who is already a contact.
API actionper requesterWrite a fit note for each
HeldOperator writes a one-line fit note for each requester against your LP criteria, with a recommendation to approve or decline.
OperatorApprove the good fits
HeldApproves the requests you agree with, each shown with its fit note, and lets each requester know. One you take out of the batch stays pending for another day.
API actionper requestGP approves all in one goDecline the rest
HeldDeclines the requests that don’t fit, and each requester gets a polite answer.
API actionper requestGP approves all in one goAdd new prospects to your CRM
HeldAdds each approved requester who isn’t a contact yet to your inbound prospects group, at the reviewing materials stage.
API actionper prospectGP approves all in one goEnrich each new contact
HeldOperator looks each new contact up with your enrichment provider and fills in their details once you approve the lookup. A lookup that times out is tried again.
Operatorper contact
The plan as it runs: each step waits for the one before it, and stops at its gate until the owner approves.
At a glance
Who runs it, and when
- Who runs it
- GP
- What starts it
- Access requests come in while your fund is raising, and you ask Operator to go through them each day.
- How often
- Daily during a raise
- Vehicle
- Fund
Ask Operator
Start it in a sentence
Ask Operator in chat. It drafts the plan for your fund, and nothing runs until you release it.
- You
Go through today’s data room requests for Fund II.
- You
Who asked for access this week? Approve the good ones.
- You
Triage the Explorer requests.
The outcome
Every pending request is approved or declined as you decided, every requester has heard back, and only the people you approved are in your CRM, enriched.
What it proves
- Checks every requester against your CRM before it writes a word.
- Writes a fit note for each requester against your own LP criteria.
- Approves or declines a whole batch in one go; a request you take out stays pending.
- Adds only the people you approved to your CRM, already enriched.
- Tries a timed-out lookup again and keeps the run inside its spend budget.
- Answers every requester, by email or in the app.