Closes finished projects properly: final assets filed, client access reviewed, last invoice checked, and a retro written while people still remember.
Notion
Google Drive
Stripe
Gmail


Grok Bot teamsGrok Bot teams
botteams.io is a directory of teams and Bots you paste into Grok Bot. Each team is named Bots, a group chat, and routines.
Use them at work, in a business, or for everyday life. Copy one installer prompt. Nothing is installed on this site.
What is Grok Bot? · Guides · Or start with one Bot.
Not affiliated with xAI.
Pick a team. Copy the installer prompt. Paste it into Grok Bot. The prompt creates named Bots and a group chat (two to six Bots), tells you to make a sidebar section, and pings each Bot so you can confirm routines. Connectors must already be on the account.
Every team here is one file. Front matter names the Bots, the group chat, the routines, and the connectors the account needs first. The installer prompt is generated from it, so the file is the product.
No GitHub needed: reply under a public X post that describes a Bot setup and tag @botteams_bot. The worker drafts an example pull request, and a maintainer reviews it before it appears here.
---
slug: founder-os
name: Founder OS
tagline: Money and inbox in one founder room.
bots: 2
section: Founder OS
kind: team
status: installable
connectors: [Stripe, Gmail]
bot_roster:
- name: Founder · Money
persona: Reads Stripe. Drafts the brief. Never moves funds.
connectors: [Stripe]
- name: Founder · Inbox
persona: Drafts mail. Never sends.
connectors: [Gmail]
rooms:
- name: Founder HQ
members: [Founder · Money, Founder · Inbox]
routines:
- name: Monday money brief
owner: Founder · Money
schedule: Every Monday at 08:00
prompt: Read Stripe. Draft the weekly money brief. Never move funds.
---Open a pull requestContribution guideRead the specAPI
12 of 140 results
Closes finished projects properly: final assets filed, client access reviewed, last invoice checked, and a retro written while people still remember.
Keeps filing deadlines and the numbers behind them in one place, so a return is never assembled the night before it is due.
Reads drafts before a human editor does, catching claims without sources, house-style breaks, and the things that get fixed at the last minute.
Keeps the data room current between raises, so diligence does not become a fire drill.
Drafts the monthly letter with the bad news first, and tracks what was promised in the last one.
Keeps the documents a new joiner actually reads in their first week correct, because those are the ones that mislead.
Measures whether people can find what exists, and fixes the naming that stops them.
Keeps one list of what the company signed, what it committed to, and when each obligation lands.
Tracks what personal data the company holds, where it goes, and which requests are running out of time.
Turns finished research into something people can actually use, and says when the answer is not known.
Runs a knowledge base across four stores: stale pages found, duplicates named, records checked, and gaps in documentation reported.
Assembles the monthly investor update: numbers pulled from source, the letter drafted, questions tracked, and nothing invented.
Pick a team. Copy the installer prompt. Paste it into Grok Bot. The prompt creates named Bots and a group chat (two to six Bots), tells you to make a sidebar section, and pings each Bot so you can confirm routines. Connectors must already be on the account.
Every team here is one file. Front matter names the Bots, the group chat, the routines, and the connectors the account needs first. The installer prompt is generated from it, so the file is the product.
No GitHub needed: reply under a public X post that describes a Bot setup and tag @botteams_bot. The worker drafts an example pull request, and a maintainer reviews it before it appears here.