LP fundraising

Rainmaker is a fundraise chief of staff for a GP without an IR team. After each LP you meet, you tell your agent about them in a voice note. It stores them, drafts the follow-up into your own Gmail in your own voice, arms the reminders, and every morning tells you who to chase and why, including the ones your CRM says are fine but your notes say are dead. The Board shows the whole raise, one card per firm, with a pre-call brief behind every card. Nothing is sent without you.

What it does

Three pieces work together:

• Rainmaker (cloud tool) keeps your LP memory: contacts, stages, check sizes, allocation timing, every interaction, your follow-up workflows and the daily digest. It never touches your inbox or your CRM.
• LP Pipeline (free skill) runs on your Mac. It parses your voice notes, writes Gmail drafts, watches for replies and bookings, and syncs your CRM with your own credentials.
• Rainmaker Board (free skill) turns the memory into one page: a card per firm, an account brief per firm, a pre-call brief per person, and a private link that opens the same board on your phone.

What it costs

Rainmaker has five cloud calls: logging contacts, importing a CRM batch, the daily digest, a portfolio-news scan, and building briefs. They are free today. If a price is ever set, your agent shows it before it calls. Everything else is free too: reading and correcting contacts, workflows, reporting outcomes, the Board and your phone link. Both skills are free. Any charge or refund shows in your wallet activity.

Start: hand this page to your agent

For the desktop app 0.6.10 or newer.

Copy this page's link and send it to your agent. It installs everything under Requires, after showing you the plan, then walks you through setup. New skills and cloud tools work at once. Only if the setup says a restart is required: click your name at the bottom left, choose Agent, open This device → Runtime and click Restart engine. You can also add them by hand from the Marketplace: Activate Rainmaker, Install the two skills. Installed skills refresh on their own; see how skills stay up to date.

Requires

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

Before you start

Have these ready and setup takes about ten minutes:

• Fund facts. Fund name and target, your Calendly, the data-room link, and the deck: the file in your Google Drive (your agent attaches it), a local path, or a link only if it is genuinely shared. For the Board, also the names of every fund and SPV you have raised (that is how it tells an existing investor from a prospect), your email domain, and your team with their emails.
• Gmail connected to your agent. Drafts go into your Gmail, and replies are found there. Your agent creates drafts only; it has no way 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.
• Your follow-up styles, in your own words. If you already say "this one's a dodger", that becomes a named workflow. If not, the defaults are fine.

A CRM is optional. LP Pipeline syncs day.ai, Affinity, HubSpot, Pipedrive and Attio, or a CSV. Without one, your voice notes are the book.

Set it up in one sitting

A workflow is a follow-up plan with days on it, named in your words: "dodger: day 0 the follow-up with the deck link, day 3 a one-line nudge, day 10 a short breakup note, skip the nudges if they replied." Steps that should stop after a reply do; a quarterly check-in for existing LPs does not.

Habit 1 · After every LP: dump it

Thirty seconds, right after the conversation.

Send your agent a voice note in your room, on Slack, Telegram or Discord, or just type it. Name, firm, where you met, and the one thing you would otherwise forget. Say the codename if you know how you want to play it.

Ten LPs after a dinner is ten notes, or one long one. The same person from two notes, or from a note and a CRM row, becomes one contact; your agent tells you about each merge so a wrong match is caught. If a note produced nothing, your agent says so.

Habit 2 · Every morning: "what should I do today?"

The briefing arrives on the morning cron, or whenever you ask. Once a day Rainmaker re-reads the whole book and opens with the state of the raise, the few priorities that matter, suggested stage corrections, and data-hygiene flags. This is where "your CRM says soft circle but the note says they passed" shows up. Stage corrections are never applied on their own; your agent puts each one to you as a yes or no.

Then the ranked actions: follow-ups due, next steps you promised and have not done, existing LPs due their quarterly touch, allocation windows opening soon, and portfolio news worth a personal note. Each line has its reason, written from your own notes.

Portfolio news is a reason to write. Give your agent your portfolio companies once. The weekly scan finds rounds, exits and milestones, and Rainmaker picks which few LPs should hear about each one personally, never a blast. Your own news works too: "we just closed the Series C at [company], share it".

Habit 3 · Replies and bookings

Twice a day your agent checks Gmail for replies from tracked LPs and watches for Calendly and calendar bookings with their email. A reply moves the person to in dialogue and cancels the rest of that workflow's nudges, so nobody gets "just bumping this" after answering. A booking moves them to meeting scheduled.

Habit 4 · Keep your CRM the source of truth

A sync reads the opportunities in your CRM pipeline and the people on them, not the whole contact database. For day.ai it reads one pipeline by name (default "Fund Raising"). It brings stage, expected commitment, close date and notes, and for each organization its email threads, meeting notes, upcoming meetings and open tasks, so the briefs have something to cite. Closed-lost is dropped. A row with an email and a firm but no name comes in as Contact at [firm]; names are never guessed from an email address. After each import the skill checks what landed against what it sent and lists any gaps.

After a sync, every contact's stage equals the CRM's stage, down as well as up. Rainmaker's stages, in order: identified, met, followed up, in dialogue, meeting scheduled, soft-circled, committed; passed and existing LP sit to the side. Warmth is separate from stage and comes from one thing only: a recent two-way interaction.

The Board

Say "show me the pipeline". Your agent checks the chain first (Rainmaker reachable, CRM connected and synced, fund facts, briefs built) and gives you the next step if a link is missing, instead of a half-empty page. Then it opens the board: the state of the raise in one row, a stage strip with totals, investor-type tabs, and the pipeline in your CRM's own stage names, one card per firm however many people you know there. Each card shows existing investor or prospect, the amount, the close date, days in stage, a temperature dot from the last time they reached out, and the owner.

Open a card for the account brief: the whole relationship across everyone at the firm, with stakeholders and their stance, open opportunities, what each side owes, ranked next steps with a drafted opener, and risks. A tab per person holds their pre-call brief: where you stand in three sentences, the decision drivers they raised in their own words, prior investments with your funds, and everyone on the deal. Every claim cites its source; anything without a citation is removed before you see it. A brief whose evidence changed is marked stale. With the Board installed, a nightly refresh pulls your day.ai activity and rebuilds only the stale briefs.

Buttons hand work to your agent: draft the email, prep me for a call, schedule, log a note, move a stage, refresh a brief. Nothing runs in the page and nothing sends.

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 returns tomorrow. A voice note that produced nothing is reported as a failure.
• Your channels stay yours. Your agent never contacts an LP on LinkedIn or a conference app for you.
• Stage corrections are suggestions. The triage proposes, you confirm, the change goes to your CRM, then syncs.
• Your credentials stay on your Mac. Gmail, calendar, CRM keys and voice samples live in the local skill. The cloud only gets what the skill has already parsed into a contact.
• Every claim in a brief cites its evidence. Uncited claims and quotes that are not word for word are removed in code.

If your agent ever seems lost, say: "Read the LP Pipeline and Rainmaker Board skills, run the LP pipeline doctor, and do its next steps until it says ready." The full operating manual ships inside the LP Pipeline skill.