LP fundraising

Rainmaker is a fundraise chief of staff for a GP without an IR team. You meet a dozen qualified LPs at a conference and tell your agent about each one in a voice note. It stores them, drafts the follow-ups into your own Gmail in your own voice, arms the reminders, and every morning tells you who to chase next and why — including the ones your CRM says are fine but your notes say are dead. When you want to see the raise, the Board shows the whole book one card per firm, and behind every card an account brief for the whole relationship plus a pre-call brief per person, where every line cites the meeting, email or note it came from. Nothing is ever sent without you.

The loop at a glance

Hand this page to your agent

AG2 Space 0.6.10 and newer. Send this page to your agent; no clicking through the Marketplace one tool at a time.

Copy this page's link from your browser and send it to your Sutando. It reads the page, installs every skill and activates every cloud tool listed under Requires below in one go, then follows the rest of the page with you, step by step. Before installing it shows you the plan: what it will add and what you already have. Anything that costs credits waits for your OK. Skills and cloud tools work the moment they land: your agent uses a newly activated cloud tool straight away, with no restart and no dashboard step. Only if the setup script itself reports that a restart is required does your agent ask you, once, to open Agent settings (the bot icon, bottom left), scroll to Runtime and click Restart engine.

Requires

• Cloud tools: rainmaker
• Skills: lp-pipeline, rainmaker-board

Or set it up by hand

Two pieces, two verbs, and they only work together:

• Rainmaker — Activate. The hosted cloud tool. It keeps your LP memory (contacts, stages, check sizes, allocation timing, every interaction), runs your named follow-up workflows, and produces the daily digest. It never touches your inbox or your CRM.

• LP Pipeline — Install. The free local skill. It runs inside your agent on your own machine: it transcribes and parses your voice notes, writes Gmail drafts, watches for replies and bookings, and connects to your CRM with your own credentials.

• Rainmaker Board — Install. The free local skill that turns the memory into a page: the pipeline one card per firm, an account brief per firm and a pre-call brief per person, and buttons that hand work to your agent or write straight into your CRM. It also mints the private link that opens the same board on your phone.

Before you start

Four things your agent will ask for. Have them ready and setup takes ten minutes:

• Fund facts. Fund name and target, your Calendly, the data-room link, and the deck — as the file in your Google Drive (your agent attaches the file itself), a local path, or a link only if that link is genuinely shared; a link nobody outside your firm can open is worse than no deck. For the Board it also wants the names of every fund and SPV you have raised (that is how it tells an existing investor from a prospect), your email domain (inbound versus outbound mail) and the team with their emails (owner names on cards). These ride along on every follow-up so you never paste them again.
• Your Gmail, connected to your agent. Drafts are written into your Gmail; your agent needs the Gmail connection to do that (and to notice replies later). It creates drafts only — it has no path to send.
• Three to five emails you actually sent to warm contacts. That is how it learns your voice. Without them the drafts sound like a bot, and an LP can tell.
• Your follow-up styles, in your own words. If you already say things like "this one's a dodger" or "give him the padre treatment", those become named workflows (see Workflows you name). If you don't, the defaults are fine to start.

A CRM is optional. If you have one (day.ai, Affinity, HubSpot, Pipedrive, Attio), the opportunities in it become the starting book; if you don't, the voice notes are the book.

Step 1 · Set it up in one sitting

One conversation. Your agent does the setup; you answer questions and click one consent.

Step 2 · After every LP: dump it

The one habit that makes this work. Thirty seconds, right after the conversation.

Send your agent a voice note in your AG2 Space room, or a memo on Slack, Telegram or Discord, or just type it. Name, firm, where you met, the one thing you'll otherwise forget. If you already know how you want to play it, say the codename.

Ten LPs after a conference dinner is ten voice notes, or one long one. Duplicates are handled: the same person from two dumps, or from a dump and a CRM row, collapses into one contact (email first, then LinkedIn, then a fuzzy match on name and firm that copes with accents).

Step 3 · Your CRM is the source of truth

Opportunities in, never the 50,000-lead firehose. After a sync, Rainmaker shows exactly what day.ai shows.

The CRM is the source of truth. Rainmaker is the intelligence around your database, not a replacement for it: it never disagrees with the stage you see in day.ai after a sync, the daily triage tells you when your notes disagree with that stage, and the writes back into the CRM are the ones you make yourself — a stage move, a note, a reminder, a role tag, on the Board or by telling your agent — which it writes from your own machine with your own credentials, confirms by reading them back, and only then mirrors into Rainmaker. A refused write is shown to you, never hidden.

Rainmaker's own stages, in order: identified (inventory — a CRM row or a list entry nobody has met), met, followed up, in dialogue, meeting scheduled, soft-circled, committed; passed and existing LP sit to the side. Warmth is a separate thing from stage, and it is measured one way only: evidence of a recent two-way interaction. Fifty dormant rows under one firm name are fifty cold rows, not "strong institutional interest" — the triage is told so in as many words.

Step 4 · Every morning: "what should I do today"

Ranked, reasoned from your own notes, and honest about the state of the raise.

The briefing arrives on the morning cron, or whenever you ask. It has two halves, and the first one is the reason the product exists.

The triage. Once a day, before answering, Rainmaker re-reads the entire book — every contact, due or not — and comes back with a state-of-the-raise summary, the handful of priorities that matter most, suggested stage corrections, and hygiene flags. This is where "your CRM says Soft Circle but the note says they passed by email" surfaces. Stage corrections are never applied on their own: your agent puts each one to you as a one-line yes or no.

The actions. Then the ranked list: follow-ups due, next steps you promised in a note and haven't done, existing LPs due their quarterly touch, allocation windows opening in the next sixty days, portfolio news worth a personal note, and a few insights no rule could find — a whole batch from one conference gone quiet, a timing play, a relationship move. Every line carries its reason, written from your notes, not from a template: "send Fund III references — that was his one ask in São Paulo, and the $5M soft circle is waiting on it."

Step 5 · Replies and bookings

Checked twice a day. A reply that waits until tomorrow's briefing is a missed one.

Your agent sweeps Gmail for replies from tracked LPs and watches for Calendly and calendar bookings that include one of their emails. A reply moves the person to in dialogue and cancels the remaining nudges of that workflow, so nobody gets a "just bumping this" after they already answered. A booking moves them to meeting scheduled — its own state, because a meeting on the calendar is more than a reply.

Step 6 · Portfolio news as a reason to write

"We just had a good Series C" is the most natural email you will ever send an LP.

Give your agent your portfolio companies once (they go into the fund facts). The weekly scan looks for material news — rounds, exits, milestones — and Rainmaker decides two things: whether the story is genuinely worth sharing, and which specific LPs get a personal note about it, by geography, entity type and what their notes say they care about. Never a blast; usually zero to four people per event.

Step 7 · The Board: the whole raise on one page

Your CRM shows deals. The Board shows relationships — and what to do about each one.

Say "show me the pipeline" and your agent renders it from Rainmaker's memory. What you get, top to bottom:

• The state of the raise in one row — open relationships, dollars soft-circled and committed, who is warm right now, who has gone cold, and how many briefs are fresh. Under it, the triage's summary from this morning.
• A stage strip with the whole-book totals — Identified 37 · Initial Meeting 24 · Due Diligence 10 … with dollars per stage. Each pill filters the board to that stage across every investor type.
• Investor-type tabs — All types is one board; tap Family Office 27 · $47.1M and the board becomes just those.
• The kanban itself, in your CRM's own stage names, with a colored bar and the firm count and dollars on every column. Columns open at ten cards and grow as you load more; search, owner, stage and temperature filters narrow it; the Table toggle lists every firm sortable by stage, amount, people, last touch and brief state.

Each card is one firm, however many people you know there: the firm, the lead person and their title, Existing investor or Prospect (any prior commitment to one of your entities, found automatically across every pipeline), the amount summed across the firm, the earliest close date, days in the current stage, the people at the firm, a temperature dot (from the last time they reached out: an email from them, a meeting, a reply; outbound mail never warms a relationship), and the owner. Five people at one firm were five cards before; they are one relationship now.

Click a card: the account brief

The whole relationship on one page, then a tab per person.

A firm where you know two or more people gets an account brief, written across all of them from the union of their evidence: a three-sentence account summary, the stakeholders with a role tag (economic buyer, champion, supporter, hurdle), how much they influence the decision and where they stand, the open opportunities with stage and amount, the decision drivers, we owe and they owe consolidated across people, the next steps ranked with the person to address and a drafted opener, the risks that could stall the account, and one merged interaction history with the person tagged on each line. A firm where you know one person opens on that person's brief. Until an account brief is built the page composes one from the people's briefs and says so.

The person tabs: the pre-call brief

Everything you need in the two minutes before the call — and every line tells you where it came from.

Each person tab is that person's own pre-call brief, the one to read before you write to them. It slides over the board so you never lose your place; Esc closes it, Back returns to the account, the arrows step through the firms in the column you were looking at.

The brief is written by Rainmaker from the person's record — the CRM fields, every note, every meeting summary, every email thread with its text, the upcoming meetings and open tasks your sync brought in — and it is held to one rule: every claim cites its source, or it is not shown. The model is handed a numbered list of evidence and must point at it; anything it says without a citation is dropped in code before you see it, and a "quote" that is not verbatim in the cited evidence loses its quote marks. What survives:

• Header. Existing investor or Prospective investor first — the one thing anyone needs to know about a card in a glance — then investor type, stage, temperature and owner.
• The stat strip. Prior commitment (the largest thing they ever did with one of your entities), the target for this fund, expected close and days out, days in the current stage, and the two mutual obligations: we owe them, they owe us.
• Where we stand. Three sentences: who they are to you, what the last touch actually revealed in their words, and what is open in each direction.
• What they flagged. The decision drivers, ranked by how much they gate the next stage, with their exact words when the record has them: "We come in bigger if we can ride along on two or three deals a year."
• Deal notes surfaced from the CRM, suggested next steps ranked with a drafted opener for the top email, prior investments with your entities, the interaction history, everyone on this deal with a role tag (economic buyer, champion, hurdle, not active), and the relationship data points — where you met, their lens, the events they invited you to.
• The footer says when the brief was generated and from how many meetings, emails and notes, and whether it is still fresh. A brief goes stale the moment its evidence changes — a new note, a reply, a stage move — and the page says so instead of pretending.

Buttons that do things

Every button hands the work to your own agent — and every CRM edit goes to your CRM first.

On your phone, from your AG2 Space room

You are at a conference, not at your desk. The board comes to you as a link.

An AG2 Space room can carry a link, so that is how the board travels: your agent mints a private link to the board — one per Sutando account, revocable, never indexed — and posts it in your own room once. Open it on any phone and you get the live board rendered from Rainmaker's memory at that moment. Buttons on the hosted board queue work for your agent (the cloud never holds your Gmail or your CRM credentials): tap Draft the email on the train, and within a few minutes your agent has written the draft into your Gmail from your laptop and the page shows "Draft in Gmail: Fund IV deck and co-invest terms". CRM edits work the same way — queued, executed from your machine, confirmed.

Why the board comes last

The board is the last step of a chain, and your agent checks the chain before it renders anything: Rainmaker reachable → your CRM connected → the opportunities synced (and how long ago) → the fund facts that the brief needs (your fund and entity names, your email domain, the team) → the briefs built. If a link is missing you get the exact next step, in order, instead of a half-empty board. The same check guards the phone link.

Every night the chain runs again on its own: the CRM's activity is pulled, the book re-synced, the coverage checked, and one build job rebuilds only the briefs whose evidence changed, people first, then the account briefs (a byte-identical sync rebuilds nothing). A 1,400-brief book takes about eighty minutes; your agent waits for the job and reports the counts. If a brief fails to build, the previous one stays and the card says brief failed; nothing stale is ever served silently.

Workflows you name yourself

A workflow is a follow-up playbook with days on it: a day-0 draft, a day-3 nudge, a day-10 breakup, a quarterly check-in. Rainmaker ships sensible defaults, but the ones that stick are the ones in your own vocabulary, because you will actually say them in a voice note at 11pm after a dinner.

What it remembers, and where

Rainmaker's memory is keyed to your Sutando account, so it survives laptops, phones and forgetting: every contact with stage, check band, timing, cadence and source; the CRM's structured record of each opportunity (people and their roles, prior commitments, stage history); every interaction and outcome; every pre-call brief with its evidence; your fund facts; your workflows; the history of daily triages; and your board link. Ask for any of it in plain words — "where are we with the Monterrey family offices?", "who did I meet at LAVCA and never follow up with?", "what did the triage say last Monday?".

Your Gmail, your calendar, your CRM credentials and your voice samples stay on your own machine, inside the local skill. The cloud only ever receives what the skill has already parsed into a contact.

Guardrails

• Nothing sends without you. Every follow-up is a Gmail draft. There is no send path.
• Nothing dies silently. Every suggested action comes back with an outcome or resurfaces tomorrow; a voice note that produced nothing is reported as a failure, never dropped.
• Your relationships, your channels. Your agent never contacts an LP on LinkedIn or a conference platform on your behalf. Existing LPs are touched on cadence, not on impulse.
• Stage corrections are suggestions. The triage proposes; you confirm; the change is made in your CRM, then synced.
• The CRM is the source of truth. After every sync Rainmaker's stages equal the CRM's, in both directions. The only writes into the CRM are the edits you make, done from your own machine with your own credentials, read back to confirm, and shown to you if refused.
• Warmth is evidence, not arithmetic. A relationship is warm only on a recent two-way interaction; how many rows share a firm name means nothing.
• Every claim in a brief cites its evidence. Uncited claims and non-verbatim quotes are removed in code before you see them; a brief whose evidence changed is marked stale, never served as fresh.

Credits & billing

Rainmaker's five cloud calls — logging contacts, importing a CRM batch, the daily digest, a portfolio-news scan, and building briefs (one call builds every stale person and account brief in the book as a job you poll for free) — each cost a flat, published credit price per call, whatever the size of the book; a call that fails its own checks is refunded automatically. Everything else is free: reading and correcting contacts, defining workflows, reporting outcomes, the source registry, the board page and your phone link. The LP Pipeline and Rainmaker Board skills are free and run on your own machine. Watch every debit and refund in your dashboard's wallet activity.

For your agent: the runbook

Hand this section to the agent that will run your raise. It is the whole job in order.

Everything below is what the LP Pipeline skill already tells the agent; it is here so you can see it, and paste it if an agent ever seems lost.