Agentic investing team

Your fund runs while you take the meeting.

GPAgent puts a specialist team to work on sourcing, diligence prep, relationships, and portfolio reads. The agents do the legwork and show their receipts. You take every founder and LP conversation yourself.

SourcingFinds alpha before it is obviousInvestmentTurns sourced companies into investment attentionRelationshipBuilds accessPortfolioCompounds alpha after investmentGPAgentthe records, the guardrails, the receiptsGPLPs

Build Your Agentic Investing Team On GPAgent

GPAgent is the platform for GPs who want agents to operate like real investing team members.

GPAgent runs a hosted agentic investing team for fund managers. The platform owns integrations, orchestration, permissions, UI, guardrails, and the activity ledger. OpenClaw, Claude Code, Hermes, MCP clients, and custom agent fleets can connect through GPAgent's API and MCP surfaces, but GPAgent is the operating platform for the team. The goal is not automation theater. The goal is a sharper fund: better sourcing, better selection, better access, better portfolio support, and better LP outcomes.

This guide is generated from src/lib/agent-fleet.ts. Do not edit this file by hand. Run pnpm docs:agent-team after changing agent roles, and pnpm docs:agent-team:check before shipping.

The Investing Team

Sourcing Analyst

Finds alpha before it is obvious.

The Sourcing Analyst discovers companies from configured sources, enriches them with market and founder context, scores them against the GP’s investing lens, and introduces the most relevant companies into the pipeline with a clear rationale.

Investment Analyst

Turns sourced companies into investment attention.

The Investment Analyst reviews the best opportunities, writes reasoning a GP can trust, and moves the strongest companies into the human queue for founder conversations. It keeps the GP’s attention scarce and intentional.

Relationship Manager

Builds access.

The Relationship Manager acts like an EA for the investing workflow: calendar-to-CRM updates, founder connection queues, meeting context, follow-up actions, and card hygiene. It keeps source links, websites, deal notes, call recordings, and founder links attached to the right Deal Card when confidence is high.

Portfolio Analyst

Compounds alpha after investment.

The Portfolio Analyst reads portfolio updates, extracts metrics and risks, identifies where the GP can help, and turns company progress into structured intelligence for the GP and LPs.

GP Brand Strategist

Narrates alpha.

The future GP Brand Strategist will turn actual fund activity into public narrative: founder lessons, market themes, and public posts. It should be grounded in real GPAgent activity, not generic marketing prompts.

What GPAgent Owns

GPAgent is the durable center of the team:

  • The fund's canonical company, deal, founder, relationship, portfolio, and LP data.
  • API rails and scripts that agents use to write structured work.
  • UI surfaces where a GP can inspect, approve, and act.
  • Guardrails for tenant scoping, permissions, duplicate checks, ownership, and stage hygiene.
  • Hosted orchestration for production agent runs.
  • A RunActivity ledger that records what each team member did and whether the work actually succeeded.

GPAgent is the system of record and execution surface. External agent harnesses can connect through API and MCP without replacing the GPAgent-run team.

How The Team Works

The active team today is Sourcing Analyst, Investment Analyst, Relationship Manager, Portfolio Analyst. The Sourcing Analyst finds and qualifies companies. The Investment Analyst studies the best ones and prepares them for founder conversations. The Relationship Manager builds access and keeps relationship state current. The Portfolio Analyst supports companies after investment. The future GP Brand Strategist turns verified fund work into public narrative.

That sequence matters because each agent is doing a job a GP already understands. The product is not a bag of prompts. It is an investing team with clear ownership.

Why The Ledger Matters

Agentic work has to be auditable. A scheduler saying "ok" is not enough.

GPAgent's RunActivity ledger records who acted, what ran, what changed, what was checked, whether delivery succeeded, what failed, and what is safe to do next. That makes an investing team inspectable by a GP, recoverable by an operator, and safe enough to run across multiple funds.

A Simple Example

A GP connects fund data sources and enables a hosted sourcing run. GPAgent syncs configured company sources, ingests private source digests when available, enriches companies, writes only qualified deals, filters the rest with evidence, and records what happened. OpenClaw or another agent fleet can also call the same GPAgent APIs and MCP tools for custom workflows. The Investment Analyst reviews the strongest companies and moves a few into the GP's founder-conversation queue. The Relationship Manager turns qualified companies into passive founder-access prep, syncs real calendar activity back to the CRM, and attaches relevant meeting context. When the fund invests, the Portfolio Analyst tracks updates and turns progress into LP-ready intelligence.

The agents do real work. GPAgent keeps the work durable.

Current Roadmap

The current build order has completed canonical docs, single-writer cleanup, RunActivity implementation, Source Digest intake, and the first Relationship Manager operating loop. Next comes deeper integrations, richer person-level artifacts, more automated evidence gathering across the configured workspace, natural-run reliability, and Portfolio Analyst alignment.

Outreach prep is downstream of qualification. Deal Cards should carry the supporting context a GP would expect from a strong EA: source pages, websites, deal notes, call recordings, and founder links. Relationship actions should remain passive and internal until an operator explicitly enables external connectors. Public examples stay generic; customer-specific fund data stays inside authenticated workspaces.

Non-Divergence Rule

This public guide is generated from the canonical agent fleet config, not maintained as a separate source of truth. Public language translates the internal model into customer-safe product copy, but it must not create a different role model, roadmap, ownership boundary, or customer-specific example.

Every claim comes with a receipt

When an agent says it qualified six companies this week, you should not have to take its word for it. Every line below opens into the run behind it: what changed, what it checked, which records it touched, and whether the report reached you. The same drill-down works on every run your team makes.

Fictional example. Acme Robotics and every number below are invented; real fund data stays inside the fund's own workspace.

The glance
Sourcing Analyst
Finds alpha before it is obvious
DidReviewed 38 new companies this week and qualified 6 into the pipeline, each with its source attached.
NextSunday morning sourcing run · 24 companies waiting.
Investment Analyst
Turns sourced companies into investment attention
DidRead 11 qualified companies, wrote reasoning on each, and moved 2 into the founder-conversation queue.
NextDaily analysis pass · 9 companies held with written reasons.
Relationship Manager
Builds access
DidMatched this week’s founder calls to their deal records and attached 2 meeting recordings.
NextNightly calendar sync · 3 follow-ups queued.
Portfolio Analyst
Compounds alpha after investment
DidRead 3 portfolio updates, filed the metrics, and flagged 1 company where the GP can help.
NextWeekly update read · 1 open data gap to chase.
The runs behind it
Portfolio Analyst · Weekly update readSucceeded
Sun 9:04am · 2m

Read 3 founder updates, filed the metrics, and opened 1 data gap for a missing revenue figure.

3 updates read1 data gap opened
Relationship Manager · Nightly calendar syncSucceeded
Tue 10:01pm · 1m

Matched Wednesday’s Acme Robotics call to its deal record and attached the meeting recording.

2 meetings matched1 recording attached
Investment Analyst · Daily analysis passSucceeded
Mon 11:03am · 3m

Promoted Acme Robotics and Harbor Grid to the founder-conversation queue. Held 9 with written reasons.

11 analyzed2 promoted9 held
Sourcing Analyst · Weekly sourcing runSucceeded
Sun 10:02am · 4m

Qualified 6 of 38 new companies into the pipeline. Acme Robotics scored highest against the thesis.

38 reviewed6 qualified0 errors
Inside one run
Investment Analyst · Daily analysis pass
Succeeded · Live run · Hosted · Mon 11:03am · 3m · Safe to continue
What changed

Analyzed 11 companies. Promoted 2 to the founder-conversation queue, held 9 with written reasons, hit no errors.

11 analyzed2 promoted9 held0 skipped0 errors
What it checked
passQueue capacity respectedPromotions stayed under the founder-meeting cap.
passNo duplicate dealsEvery company matched exactly one deal record.
passReasoning written11 of 11 companies have a written assessment.
What it touched
Acme Robotics → Deal recordHarbor Grid → Deal record
Delivery

Run report emailed to the GP. Nothing sent to anyone else.

The one thing you will not find in this ledger is an agent talking to a founder or an LP. Agents prepare the work and show their receipts. The GP takes every conversation.