Run a One-Person Company on Grok Bot: 6 Bots, 1 Handbook, 3 Rules

Subscribe to Premium → set security rules → write the handbook → hire 6 Bots day by day → run on a weekly rhythm

Who

Solo founders and one-person company operators who want to offload inbox, CRM, support, content, invoices, and research

You get

Six Bots run scheduled routines: morning brief, lead research, content drafts, support drafts, monthly books, and review gatekeeping. The founder approves the queue, does irreplaceable work, and reviews the Friday summary.

You need

Grok Bot

Steps

1. Safety tip

   Safety tip: before the bot deletes or removes anything, confirm the target and approve manually.

2. Subscribe and lock down security

   Subscribe to X Premium tier ($30/month). Create a dedicated email for your Bots. Set up limited seats in your CRM and help desk, default to read access, and grant write access only where the job requires it. Never attach banking logins, card details, or payment admin. In Grok Bot, set approval rules: all irreversible actions (send, publish, refund, delete, sign, pay) must Require Approval; reading and drafting can flow freely.

3. Write the handbook

   Create a handbook folder in Drive/Notion/GitHub with six short files. Be concrete and use real examples instead of adjectives. If you correct a Bot twice for the same issue, write the fix into the handbook.

   Setup guidance · Source text。Reference for handbook folder structure; create corresponding files outside Grok Bot in Drive/Notion/GitHub

   Copy prompt

   handbook/
     company.md     what we sell, to whom, for how much
     voice.md       how we write, with 5 real examples
     never.md       claims, phrases and topics we avoid
     faq.md         every customer question + approved answer
     policies.md    refunds, response times, escalation
     customers.md   ideal customer, in detail

4. Set up Brief (Chief of Staff)

   Create a Bot named Brief with the role Chief of Staff. Run the morning brief manually first: have it read the other Bots’ output and your calendar, then produce one brief under 200 words prioritizing decisions needed, meeting prep, key numbers, and anomalies. After confirming the output, schedule it for 07:00 on weekdays. Brief reports only and takes no actions.

5. Set up Helm (Support) and Kit (Reviewer)

   Create a Bot named Helm with the role Support. Connect faq.md and policies.md, and have it triage tickets and draft replies. Hard rule: if a ticket mentions a refund, a legal issue, an angry customer, or the FAQ has no answer, write an escalation note instead—never invent a policy. Test manually with a few tickets and measure time saved. Then create a Bot named Kit with the role Reviewer. Point Helm’s drafts to Kit and have it check against never.md, voice.md, and policies.md, attaching a one-line verdict: "clean" or "broke rule X". Tune until it catches the mistakes you would have caught yourself.

6. Set up Quill (Content) and Scout (Research)

   Create a Bot named Quill with the role Content. Every Friday, have it turn one long-form piece into a newsletter section, a thread, three standalone posts, and a short script, all saved as drafts. It writes in your voice from voice.md, but the ideas remain yours. Create a Bot named Scout with the role Research. Every Monday, have it check competitor pricing pages and changelogs, scan public discussions, and write a weekly file with links. Every claim needs a source; anything unverified is marked. Daily, enrich new leads with a two-line summary and fit score. Add one routine each—resist adding more.

7. Set up Penny (Ops) and review

   Create a Bot named Penny with the role Ops and cash. On the 1st of each month, have it read read-only exports, categorize expenses, reconcile payouts against invoices, and list renewals in the next 30 days. Every total must be computed with code and checked against source files—no estimates. For the first run, walk through the month’s books manually with Penny and check every number. Then open your Usage page to see which routines cost the most.

8. Enable group chats and keep tuning

   Multi-Bot group chats burn usage fast, so enable them last and only for work that truly crosses roles—such as a competitor price change triggering a Scout report, a Quill draft, and a Helm FAQ update in one pass. Keep daily routines separate. Ongoing caveats: Grok Bot is beta and details change; the shared computer is not a security boundary; browser automation can be blocked by CAPTCHAs, so prefer official connectors/plugins; skills drafted from screen recordings are first drafts and need human review before trusting.

handbook/
  company.md     what we sell, to whom, for how much
  voice.md       how we write, with 5 real examples
  never.md       claims, phrases and topics we avoid
  faq.md         every customer question + approved answer
  policies.md    refunds, response times, escalation
  customers.md   ideal customer, in detail