Four Bots keeping diligence boring. Reads and reports, files nothing.
Data room team
Keeps the data room current between raises, so diligence does not become a fire drill.
Data room team
Keeps the data room current between raises, so diligence does not become a fire drill.
Bots
- Index Grok Bot
- Stale Grok Bot
- Financials Grok Bot
- Contracts Grok Bot
Data room desk group chat
- Index Grok Bot
- Stale Grok Bot
- Financials Grok Bot
- Contracts Grok Bot
Google Drive
Notion
Xero
Docusign
Job
Index Grok BotGrok Bot
Keeps the index of what the data room should contain.
Notion
Stale Grok BotGrok Bot
Names documents older than the period they claim to cover.
Google Drive
Financials Grok BotGrok Bot
Checks the financial statements filed match the ledger.
Xero
Contracts Grok BotGrok Bot
Lists signed agreements missing from the room.
Docusign
Routines2
Staleness pass
Name data room documents out of date for the period they cover.
Contract check
List agreements signed since last check that are not in the data room.
Skills2
find-skills by vercel-labs… · Fetch at run · View on Skillselion
handoff by mattpocock… · Fetch at run · View on Skillselion
Notes
Sidebar section
Investor updates
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 Data room 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 (investor-datroom). 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.
### Data room · Index Grok Bot
(Named "Room · Index" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Notion
Job:
Keeps the index of what the data room should contain.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Data room · Index Grok Bot
- Title: Keeps the index of what the data room should contain.
- Description: Keeps the index of what the data room should contain. 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.
### Data room · Stale Grok Bot
(Named "Room · Stale" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Google Drive
Job:
Names documents older than the period they claim to cover.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Data room · Stale Grok Bot
- Title: Names documents older than the period they claim to cover.
- Description: Names documents older than the period they claim to cover. 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.
### Data room · Financials Grok Bot
(Named "Room · Financials" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Xero
Job:
Checks the financial statements filed match the ledger.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Data room · Financials Grok Bot
- Title: Checks the financial statements filed match the ledger.
- Description: Checks the financial statements filed match the ledger. 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.
### Data room · Contracts Grok Bot
(Named "Room · Contracts" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Docusign
Job:
Lists signed agreements missing from the room.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Data room · Contracts Grok Bot
- Title: Lists signed agreements missing from the room.
- Description: Lists signed agreements missing from the room. 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.
### Data room desk group chat
Members (4, two to six Bots): Data room · Index Grok Bot, Data room · Stale Grok Bot, Data room · Financials Grok Bot, Data room · Contracts 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: Investor updates.
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.
### Staleness pass
Owner Bot: Data room · Stale Grok Bot
Schedule: Every month on the 1st at 10:00
Prompt to save (I will confirm the card):
Name data room documents out of date for the period they cover.
### Contract check
Owner Bot: Data room · Contracts Grok Bot
Schedule: Every Monday at 10:00
Prompt to save (I will confirm the card):
List agreements signed since last check that are not in the data room.
## 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.
- Google Drive: Draft. Use Google Drive 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.
- Xero: Read. Use Xero read-only. Read and summarise it. Do not create, edit, send, move, or delete anything in Xero.
- Docusign: Draft. Use Docusign for drafts only. Leave every draft unsent and every change unsaved so a human can review it.
Human: the lines above are instructions, not permissions. In Grok Bot open Settings, then Plugins, and disable the write tools for Google Drive, Notion, Xero, Docusign. 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.
## 7. Also
Standing instructions for every Bot on this team:
- Never send to investors without a human yes.
- Never state a number you cannot source.
## Done when
- Named Bots exist
- Named group chat exists ("Data room desk group chat", two to six Bots)
- I have created section "Investor updates"
- 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
- Investor asks
Turns vague investor offers of help into specific requests, and tracks whether anything came of them.
Notion
Gmail
HubSpot
Google Calendar
- Update letter
Drafts the monthly letter with the bad news first, and tracks what was promised in the last one.
Notion
Gmail
Stripe
Google Drive
- Investor metrics
Assembles the same metrics the same way every month, so the trend means something across a year of updates.
Stripe
Google Cloud BigQuery
Notion
Xero



