How many Grok Bots does a small business need? One main Bot, specialists and group chats

What to hand to an agent first

• Start with one Bot that owns an outcome

  xAI's docs say to start small: give one Bot ownership of an end-to-end outcome, and add another only when the work has a stable specialist role (xAI's Bots docs). For most small businesses that first Bot is a main Bot, often called a chief of staff, that owns a daily digest of what changed and what needs you. xAI's own Chief of Staff example connects Slack, email, calendar, meeting notes and planning documents, returns only items that match your priorities, and is told not to send messages or change meetings (xAI's Use cases docs). Get that one Bot reliable before you add a second.

• When a job earns its own Bot

  Create a separate Bot when the work has its own goal or area of ownership, its own tools and sources, its own working style, its own approval boundary or its own recurring schedule (xAI's Bots docs). Good jobs are specific, such as Expense Manager or Talent Scout. A General Helper gives the Bot less guidance and makes its saved context harder to reuse (xAI's Bots docs). For a small business, a bookkeeping Bot that only reads your books and drafts reminders is a good second Bot, because its tools and approval rules differ from your main Bot's.

• Give each Bot its job in the first message

  Cursor's help says: "In your first message, tell the Bot what work it should do, which sources to use, and when to ask for your approval. Ask it to remember that for future work." (Grok Bot help: Onboarding). Describe the role in operational terms: what it owns, which sources it pulls from, what it produces and what it must never do without you. To create one, choose New chat (the + button) at the top of the sidebar, then Create new Bot (Grok Bot help: Onboarding). xAI's Bots docs still say to set a description from Edit Profile (xAI's Bots docs), but Cursor's current help says personal Bots no longer have a description, while Team Bots still do (Grok Bot help: Edit a Bot). We follow Cursor's help here. Our free business brief builder writes a one-page summary of your business that every Bot can work from.

• Group chats: two to six Bots, visible handoffs

  Use a group chat when several Bots need one shared outcome and you want to see the handoffs. Choose New in the sidebar, select two to six Bots in New chat, and open the group. On iPhone or Android, use + → New Group Chat (xAI's Message and collaborate docs). Write normally to let the Bots decide who answers, type @ and a Bot's name when one Bot owns the request, and use @everyone sparingly. Approval requests, secret and login requests, and email or Slack drafts don't appear in a group, so keep jobs that need your sign-off in that Bot's own chat (xAI's Message and collaborate docs). You can't voice chat in a group, and group chats don't have the per-Bot Notifications switch (Grok Bot help: Group chats).

• Handoffs between Bots

  A Bot can send another Bot a message. The receiving Bot wakes, handles the request and can reply later, and you can see the handoff in the conversation. Ask for a single owner at each stage, because too many parallel handoffs create duplicate work and noisy updates (xAI's Message and collaborate docs). One honest note: Cursor's help says there's no switch to stop Bots messaging each other, while xAI's docs describe a Messaging Between Bots setting that a team admin can turn off on the dashboard. We follow the docs. On a Cursor team, ask your admin. On your own, tell your Bots "Don't message other Bots. Ask me first." and ask each one to remember it (Grok Bot help: Group chats).

• What every Bot shares

  Every Bot on your account uses the same cloud computer, so browser sign-ins, files and command-line credentials are shared, and one Bot can pick up work another saved. Each Bot's screen is a separate work surface, not a security boundary, so don't put a credential or file on the computer if another of your Bots shouldn't use it (xAI's Computer and apps docs). Installed connectors are account-wide too (xAI's Computer and apps docs). Splitting work across Bots organises it; it doesn't wall off access.

• More Bots means more replies to pay for

  Every Bot reply counts toward your usage, including replies in a group and messages between Bots, so fewer Bots in a group means fewer replies (Grok Bot help: Group chats). Your Bots can also create focused Bots of their own (xAI's Bots docs). A helper Bot shows in your sidebar and notifies you like any other, so turn off its notifications or hide it if you don't need to hear from it (Grok Bot help: How-tos). Hiding a Bot doesn't pause it or its routines (xAI's Bots docs).

• Keep a small roster tidy

  On desktop, right-click a Bot and choose Move to new section to group Bots by project, client or business (Grok Bot help: How-tos). Duplicate a Bot when you want the same role for a different scope. The copy keeps its profile, skills and routines, but not its conversation history or learned memory (xAI's Bots docs). A three-Bot start for a small business, our example rather than xAI's: a main Bot for the morning digest and your approval list, a bookkeeping Bot that reads invoices and drafts reminders, and a reviews Bot that drafts replies for you to approve. If you'd rather start from routines already written with approval rules, the $29 One-Person AI Business Pack has them in Grok Bot format. Not sure which three jobs to start with? Our free What should my bot do? planner picks them in 5 quick questions. Adding a ready-made Bot instead? Run the 5 Marketplace checks in our best Grok Bot templates guide first.

• From running 30+ bots (20 Oct 2026): don't wake them all at once

  This is one team's experience (ours), not xAI guidance. With more than 30 Bots, our limit errors didn't line up with how many tokens we used. Our busiest 15 minutes used about 110 million tokens with no problem, while the failures came at a quieter time, right after we woke every Bot at once and sent one message to all of them. xAI doesn't document a link between simultaneous wakes and limits, so treat that as what we observed. What works for us is a shared capacity board, one file every Bot reads before heavy work: at most 7 heavy jobs at once, 2 of those slots kept for the work that earns money, the cap raised by 1 after each quiet hour and cut by 2 after a burst of failures, and no more than 1 wake every 2 minutes. xAI's docs point the same way for handoffs: "Too many parallel handoffs can create duplicate work and noisy updates." (xAI's Message and collaborate docs). We also run one health-checker Bot. It checks the others, asks the Bot that owns a change whether it's safe before touching anything, makes only small safe fixes itself, and reports to our chief of staff Bot, so the owner's inbox stays quiet.

Ready-made use cases

1. 01CEO morning brief in 5 minutes
   One message each morning: calendar, urgent emails, money in/out, and the 3 things that move the business today.
   ~3h/week · estimate
2. 02Weekly CEO review & plan
   Every Friday the agent compiles wins, numbers, stuck items and proposes next week's priorities.
   ~2h/week · estimate
3. 03One daily list of drafts to approve
   Your bots hold every email, message and post they write as a draft. Once a day (or once a week) you get one numbered list and answer approve, edit or reject for each. Nothing goes out unapproved.
   ~1h/week · estimate
4. 04Invoice chaser, with your OK on every reminder
   Every Monday the agent lists unpaid invoices and drafts polite, escalating reminders. You approve each one before it sends. Sending friendly first reminders without review is an optional upgrade.
   ~2h/week · estimate

Grok Bot routine: CEO morning brief in 5 minutes
Schedule: Daily 7:30

Every morning, read my calendar for today, my unread emails from the last 24h and yesterday's revenue. Send me a brief: (1) meetings with one prep note each, (2) emails that need my reply with a suggested one-line answer, (3) money in/out, (4) the 3 highest-leverage tasks for today. Keep it under 200 words.

Rules: draft first, never send or post anything external without my approval. Keep summaries short.

Grok Bot, ChatGPT, Claude and n8n versions: all templates

Email me this template + the Starter Kit

Keep these human

• Splitting work across Bots doesn't separate access. Every Bot shares the computer, its sign-ins and your connectors (xAI's Computer and apps docs).
• An approval from work that started without you, such as a message from another Bot, expires after about 10 minutes (xAI's Approvals docs). Turn on notifications for Bots that ask for approvals.
• Make the approval boundary one of each Bot's lasting rules, for example "Never send external messages without approval" (xAI's Bots docs). Ask the Bot to remember it, and on a Team Bot add it to the description (Grok Bot help: Edit a Bot).
• Deleting a Bot removes its profile, conversation and routines, but shared files and sign-ins may stay on the computer. Hide it instead if you may need the work later (xAI's Bots docs).
• Start in draft mode: the agent prepares, you approve, then you loosen the leash routine by routine.

FAQ

Related guides

• Grok Bot computer running out of memory with many Bots? What helps
• Grok Bot for personal and business accounts: what's shared and how to split them
• What happens to your data when you delete Grok Bot, a Bot or your plan
• Why doesn't Grok Bot remember my rules or preferences? Fixes to try before you cancel
• How to set up an AI team for your business
• Grok Bot Team Bots: set one up for your staff, and why it isn't showing up
• Grok Bot skills vs routines: how a job is done, and when it runs
• Grok Bot approvals: set it up so nothing goes out without your OK
• AI for solo founders: a one-person company with an AI team