Four Bots through a raise. Tracks and drafts, sends nothing.
Fundraise desk team
Runs a raise like a pipeline: who was met, what they asked, what was promised, and what is outstanding.
Fundraise desk team
Runs a raise like a pipeline: who was met, what they asked, what was promised, and what is outstanding.
Bots
- Pipeline Grok Bot
- Asks Grok Bot
- Meetings Grok Bot
- Drafts Grok Bot
Raise room group chat
- Pipeline Grok Bot
- Asks Grok Bot
- Meetings Grok Bot
- Drafts Grok Bot
Gmail
Google Calendar
Notion
HubSpot
Job
Pipeline Grok BotGrok Bot
Tracks every investor conversation and its actual stage.
HubSpot
Asks Grok BotGrok Bot
Records what each investor asked for and whether it was sent.
Notion
Meetings Grok BotGrok Bot
Holds the meeting schedule and flags anyone waiting too long for a follow-up.
Google Calendar
Drafts Grok BotGrok Bot
Drafts follow-ups with the specific thing that investor asked for. Never sends.
Gmail
Routines2
Outstanding asks
List investor requests still unsent, oldest first, with who owns each.
Pipeline read
Report the raise pipeline by stage. Name conversations that have gone quiet.
Skills3
find-skills by vercel-labs… · Fetch at run · View on Skillselion
handoff by mattpocock… · Fetch at run · View on Skillselion
grill-me by mattpocock… · Fetch at run · View on Skillselion
Notes
Sidebar section
Founder OS
Prompt Installer for Grok Bot
Paste the prompt into Grok Bot. This is not one-click OAuth and nothing is installed on this site.
# Grok Bot Teams installer
Set up a team for me called Fundraise desk team. Create the named Bots, then the group chat, then save the routines.
Ask me only for things you cannot see. Do not start OAuth. If a connector is missing, tell me to connect it in Settings, then Plugins.
From https://botteams.ai (founder-fundraise). Source: https://github.com/ellelion/botteams.
## 1. Create these Bots
Create each Bot below. Use the names exactly, including any prefix. After create, set Name, Title, and Description on the profile, then tell me to set the avatar.
A Bot is a single persistent, named agent. Conversation is the task; Title is the one-line job; Description holds durable rules and approvals.
### Fundraise desk · Pipeline Grok Bot
(Named "Raise · Pipeline" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): HubSpot
Job:
Tracks every investor conversation and its actual stage.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Fundraise desk · Pipeline Grok Bot
- Title: Tracks every investor conversation and its actual stage.
- Description: Tracks every investor conversation and its actual stage. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
Then tell me to open Edit Profile and set the avatar. You cannot stamp a custom image yourself unless I attach one.
If you create this Bot from an existing Bot, ask the new Bot to set those profile fields after create.
### Fundraise desk · Asks Grok Bot
(Named "Raise · Asks" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Notion
Job:
Records what each investor asked for and whether it was sent.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Fundraise desk · Asks Grok Bot
- Title: Records what each investor asked for and whether it was sent.
- Description: Records what each investor asked for and whether it was sent. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
Then tell me to open Edit Profile and set the avatar. You cannot stamp a custom image yourself unless I attach one.
If you create this Bot from an existing Bot, ask the new Bot to set those profile fields after create.
### Fundraise desk · Meetings Grok Bot
(Named "Raise · Meetings" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Calendar
Job:
Holds the meeting schedule and flags anyone waiting too long for a follow-up.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Fundraise desk · Meetings Grok Bot
- Title: Holds the meeting schedule and flags anyone waiting too long for a follow-up.
- Description: Holds the meeting schedule and flags anyone waiting too long for a follow-up. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
Then tell me to open Edit Profile and set the avatar. You cannot stamp a custom image yourself unless I attach one.
If you create this Bot from an existing Bot, ask the new Bot to set those profile fields after create.
### Fundraise desk · Drafts Grok Bot
(Named "Raise · Drafts" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Gmail
Job:
Drafts follow-ups with the specific thing that investor asked for. Never sends.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Fundraise desk · Drafts Grok Bot
- Title: Drafts follow-ups with the specific thing that investor asked for.
- Description: Drafts follow-ups with the specific thing that investor asked for. Never sends. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
Then tell me to open Edit Profile and set the avatar. You cannot stamp a custom image yourself unless I attach one.
If you create this Bot from an existing Bot, ask the new Bot to set those profile fields after create.
## 2. Create this group chat
Open a group chat with two to six of the Bots above. Do not add more than six.
### Raise room group chat
Members (4, two to six Bots): Fundraise desk · Pipeline Grok Bot, Fundraise desk · Asks Grok Bot, Fundraise desk · Meetings Grok Bot, Fundraise desk · Drafts Grok Bot
## 3. Sidebar section
You cannot create sidebar sections. When the Bots and group chat exist, tell me to Move to, then New section.
I will name that section exactly: Founder OS.
Ask me to move the group chat and Bots into it.
## 4. Routines (confirm card required)
Ping each owner Bot with the routine they own so they can save it.
A routine is owned by one Bot, and one Bot can own up to 50 of them. A confirm card will appear. I will confirm each one.
Do not assume a routine is saved until I confirm.
### Outstanding asks
Owner Bot: Fundraise desk · Asks Grok Bot
Schedule: Every weekday at 09:00
Prompt to save (I will confirm the card):
List investor requests still unsent, oldest first, with who owns each.
### Pipeline read
Owner Bot: Fundraise desk · Pipeline Grok Bot
Schedule: Every Monday at 08:00
Prompt to save (I will confirm the card):
Report the raise pipeline by stage. Name conversations that have gone quiet.
## 5. Connectors and how far they go
Connectors are account-wide. They must already be connected.
If any are missing, tell me to connect them in Settings, then Plugins, first.
Do not walk an OAuth flow from this prompt.
Every Bot on this account can reach every connected tool. The lists above are which Bot is expected to use which, not a second OAuth and not a boundary.
- Gmail: Draft. Use Gmail for drafts only. Leave every draft unsent and every change unsaved so a human can review it.
- Calendar: Draft. Use Calendar for drafts only. Leave every draft unsent and every change unsaved so a human can review it.
- Notion: Draft. Use Notion for drafts only. Leave every draft unsent and every change unsaved so a human can review it.
- HubSpot: Ask before send. Use HubSpot only after a human says yes in the chat. State exactly what you are about to do, wait for the reply, then act.
Human: the lines above are instructions, not permissions. In Grok Bot open Settings, then Plugins, and disable the write tools for Gmail, Calendar, Notion. That switch is account-wide and it is the only one that actually stops a write.
## 6. Skills
Skills live under Settings → Plugins → Yours, and they are per Bot. Enable the ones listed here for the named Bots. Reference a skill with /.
You cannot flip the human Notifications toggle. Tell me to leave Settings → “Get notified when this Bot finishes or needs input” on.
Do not pin or hide a Bot unless I say so. Hide does not pause routines.
Sidebar sections are human-only: tell me to Move to → New section. A group chat holds two to six Bots. An account holds 50 Bots and group chats combined. One Bot can own 50 routines. Confirm cards stay on me.
If a workflow should be demonstrated later, mention Teach a task after the first success (browser workflows).
Connect the Skillselion connector first if any skill below is Fetch at run (Settings → Plugins). Do not start OAuth from this prompt.
### find-skills
https://skillselion.com/skills/vercel-labs/skills/find-skills
Creator: vercel-labs
Scope: every Bot on this team (team scope).
Do not install. When this job comes up, use the Skillselion connector to search/load `skill:vercel-labs/skills#find-skills`. Connect Skillselion in Settings → Plugins first.
### handoff
https://skillselion.com/skills/mattpocock/skills/handoff
Creator: mattpocock
Scope: every Bot on this team (team scope).
Do not install. When this job comes up, use the Skillselion connector to search/load `skill:mattpocock/skills#handoff`. Connect Skillselion in Settings → Plugins first.
### grill-me
https://skillselion.com/skills/mattpocock/skills/grill-me
Creator: mattpocock
Scope: every Bot on this team (team scope).
Do not install. When this job comes up, use the Skillselion connector to search/load `skill:mattpocock/skills#grill-me`. Connect Skillselion in Settings → Plugins first.
## 7. Also
Standing instructions for every Bot on this team:
- Never send mail. Draft only.
- Never move funds.
## Done when
- Named Bots exist
- Named group chat exists ("Raise room group chat", two to six Bots)
- I have created section "Founder OS"
- Each routine has a confirmed save (or I declined)
- Connectors listed above are already connected
Uninstall: delete the Bots and group chats in the Grok Bot sidebar.
There is no remote uninstall from this catalog.Teams that share these connectors
- Company team
Six Bots run the company week. Product holds the list. Coding ships. Findability is SEO, AEO, and GEO. Marketing drafts. Trust reads security and legal. Money reads Stripe.
GitHub
Gmail
Google Calendar
Notion
Stripe
RampGoogle Search Console
Ahrefs
Exa
Firecrawl
- Board desk
Prepares board meetings from the real numbers, and tracks what was decided afterwards.
Notion
Stripe
Google Calendar
Gmail
- Founder hiring
Handles hiring while it is still the founder's job, without letting candidates sit unanswered.
Gmail
Google Calendar
AshbyNotion



