Investor Intro Requests Belong in the Fund Inbox
An LP introduction offer should reach the GP as a reply-ready note, while the GP keeps the relationship call.
An LP offering to help a portfolio company should not have to guess whether clicking a link opened an email draft. In GPAgent's investor portal, a request through the fund sends a note to the fund's inbox. The GP can reply to the LP, check with the founder, and make the introduction when it is appropriate. The portal records the request, not an introduction outcome.
- An investor chooses I can help on an ask or Ask for an intro on an eligible person.
- The investor writes a short note and sends it through the portal.
- The fund receives a reply-ready email with the investor's note.
- The GP decides whether, when, and how to introduce anyone.
The useful handoff is a message, not a workflow stage
Northwind Capital posts a fictional ask for Driftwake: introductions to data-center operators. Dana, an investor, can help. Her note should land where the Northwind team already talks to people: its inbox. A reply can clarify the offer. A forward can check with the founder. The fund does not need a second queue of pending intro cards to maintain.
| Portal action | What GPAgent sends | What the GP still decides |
|---|---|---|
| Investor offers help on an ask | The investor's note to the fund | Whether the help fits and whom to contact |
| Investor requests a founder intro | A request to the fund | Whether the founder wants the conversation |
| Investor requests a member intro | A request to the fund | Whether the other member consents |
The email goes to the fund, not to the founder or directory member. A request is not evidence that two people met. It is not AI-led outreach. The relationship decision stays with the people involved.
Know what was sent
A plain mailto: link can open a draft, fail to open anything, or leave the investor with an unsent message. A portal-sent request has a clearer boundary: the investor deliberately presses Send, and GPAgent records that request. If delivery fails, the investor can use an email-draft fallback. A draft is still only a draft.
Fund teams can review intro activity without treating it as a task list. There is no automatic follow-up claim and no inferred outcome. That restraint matters when the best answer is to talk to the founder first.
See the Investor Portal for the investor experience and the GPAgent platform for the fund's broader workflow.
FAQ
Does GPAgent email the founder for me?
No. A request through the fund is sent to the fund's address. The GP chooses whether to contact the founder or another member.
Does a request mean the introduction happened?
No. It records an investor's request or offer. The later conversation happens outside that record.
What if the fund's email is unavailable?
The portal offers an email-draft path when relay delivery cannot complete. Opening that draft does not prove it was sent.
Build on the fund record, not a prompt.
See how GPAgent keeps agentic investing workflows tied to a durable CRM, API, and activity ledger.