Four Bots on expansion. Checks value first, contacts nobody.
Expansion desk Team
Finds accounts that have outgrown their plan, and separates that from accounts simply being squeezed.
Bots
- Usage Grok Bot
- Value Grok Bot
- Timing Grok Bot
- Draft Grok Bot
Expansion desk group chat
- Usage Grok BotFinds accounts consistently at or over their plan limits.
- Value Grok BotChecks the account is getting value before anyone suggests paying more.
- Timing Grok BotNames the right moment, which is rarely right after a support problem.
- Draft Grok BotDrafts the conversation, framed on their usage.
HubSpot
Mixpanel
Stripe
Gmail
Usage Grok BotGrok Bot
Finds accounts consistently at or over their plan limits.
Mixpanel
Value Grok BotGrok Bot
Checks the account is getting value before anyone suggests paying more.
Stripe
Timing Grok BotGrok Bot
Names the right moment, which is rarely right after a support problem.
HubSpot
Draft Grok BotGrok Bot
Drafts the conversation, framed on their usage. Never sends.
Gmail
Limit check
Owner: Usage Grok BotEvery Monday at 09:00
List accounts at or over plan limits for three consecutive weeks.
Timing check
Owner: Timing Grok BotEvery Monday at 09:30
For expansion candidates, flag anyone with an open complaint. Never contact a customer.
find-skills by vercel-labsLooking up counts on Skillselion. · Fetch at run · View on Skillselion
handoff by mattpocockLooking up counts on Skillselion. · Fetch at run · View on Skillselion
Sidebar section
Revenue
Run Expansion desk yourself
Free to copy, adapt, and edit. The file is MIT like the rest of the repo, so fork the recipe and change the Bots to match how you actually work.
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 Expansion 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 → Plugins.
From https://botteams.io (revenue-expansion). Source: https://github.com/ellelion/botteams.
## 1. Create these Bots
Create each Bot below. Use the names exactly. After create, set Name, Title, and Description on the profile.
A Bot is persistent and named. Conversation is the task; Title is the one-line job; Description holds durable rules and approvals.
### Expansion desk Team - Usage Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Mixpanel
Job:
Finds accounts consistently at or over their plan limits.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Expansion desk Team - Usage Bot
- Title: Finds accounts consistently at or over their plan limits.
- Description: Finds accounts consistently at or over their plan limits. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
### Expansion desk Team - Value Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Stripe
Job:
Checks the account is getting value before anyone suggests paying more.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Expansion desk Team - Value Bot
- Title: Checks the account is getting value before anyone suggests paying more.
- Description: Checks the account is getting value before anyone suggests paying more. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
### Expansion desk Team - Timing Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): HubSpot
Job:
Names the right moment, which is rarely right after a support problem.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Expansion desk Team - Timing Bot
- Title: Names the right moment, which is rarely right after a support problem.
- Description: Names the right moment, which is rarely right after a support problem. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
### Expansion desk Team - Draft Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Gmail
Job:
Drafts the conversation, framed on their usage. Never sends.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Expansion desk Team - Draft Bot
- Title: Drafts the conversation, framed on their usage.
- Description: Drafts the conversation, framed on their usage. Never sends. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
## 2. Create this group chat
Open a group chat with two to six of the Bots above. Do not add more than six.
### Expansion desk group chat
Members (4, two to six Bots): Expansion desk Team - Usage Bot, Expansion desk Team - Value Bot, Expansion desk Team - Timing Bot, Expansion desk Team - Draft Bot
## 3. 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.
### Limit check
Owner Bot: Expansion desk Team - Usage Bot
Schedule: Every Monday at 09:00
Prompt to save (I will confirm the card):
List accounts at or over plan limits for three consecutive weeks.
### Timing check
Owner Bot: Expansion desk Team - Timing Bot
Schedule: Every Monday at 09:30
Prompt to save (I will confirm the card):
For expansion candidates, flag anyone with an open complaint. Never contact a customer.
## 4. 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 → 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.
- HubSpot: Ask before send. Use HubSpot only after a human says yes in the chat. Say the post, wait for a yes.
- Mixpanel: Draft. Use Mixpanel read-only.
- Stripe: Read. Use Stripe read-only. Never move funds.
- Gmail: Draft. Use Gmail for drafts only. Draft the message, do not send.
## 5. Skills
Skills live under Settings → Plugins → Yours, and they are per Bot. Reference a skill with /.
If a skill is already installed on the account (Settings → Plugins → Yours), use it. Enable it for this Bot if / does not show it.
If it is not installed, fetch or load it through the Skillselion connector using the skill id. Do not install a second copy.
Connect the Skillselion connector only when a fetch is needed. Do not start OAuth from this prompt.
Do not pin or hide a Bot unless I say so. Hide does not pause routines.
If a workflow should be demonstrated later, mention Teach a task after the first success (browser workflows).
### find-skills
https://skillselion.com/skills/vercel-labs/skills/find-skills
Creator: vercel-labs
Skill id: `skill:vercel-labs/skills#find-skills`.
Scope: every Bot on this team (team scope).
### handoff
https://skillselion.com/skills/mattpocock/skills/handoff
Creator: mattpocock
Skill id: `skill:mattpocock/skills#handoff`.
Scope: every Bot on this team (team scope).
## 6. Also
Standing instructions for every Bot on this team:
- Never move money or issue a credit.
- Never mail a customer about billing without a yes.
## Human steps
These are yours. The Bot cannot do them.
- Set each Bot avatar (Bot actions → Edit Profile). Attach an image if you want a custom one.
- Create a sidebar section named exactly: Expansion desk Team. Move the group chat and Bots into it.
- In Settings → Plugins, disable the write tools for Mixpanel, Stripe, Gmail. That switch is account-wide and it is the only one that actually stops a write.
- Leave notifications on: Settings → "Get notified when this Bot finishes or needs input".
## Done when
- Named Bots exist
- Named group chat exists ("Expansion desk group chat", two to six Bots)
- I have created section "Expansion desk Team"
- 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
- Churn analysis Team
Reads cancellations for the reason rather than the reason box, and separates the preventable from the rest.
Stripe
Zendesk
Mixpanel
Notion
- Revenue forecast Team
Builds a forecast from committed evidence and shows how wrong the last one was.
HubSpot
Salesforce
Stripe
Notion
- Pricing desk Team
Watches what customers actually pay against list, and where discounting has quietly become the default.
Stripe
Salesforce
Notion
Google Cloud BigQuery

