Run a One-Person Company on Grok Bot: Company Handbook + Chief of Staff Template

Input: company info + brand voice → Process: Grok Bot reads handbook and delegates → Output: daily brief, drafts pending approval, weekly report

Who

Founders or solo operators who want to run a one-person company on a $30/month SuperGrok subscription

You get

A Bot-team operating framework: Company Handbook unifies rules, Chief of Staff Bot assigns tasks and summarizes briefs, specialist Bots handle research/content/sales/support/money/building, all spending and outbound messages require human approval

You need

Grok Bot

Steps

1. Foundation: subscribe, install, and create channels

   1) Subscribe to SuperGrok $30/month and confirm Grok Bot appears in your account (Lite and Team/Enterprise plans are not eligible). 2) Turn off on-demand usage before creating any Bot—this is your spending brake. 3) Install the Grok Bot desktop app (Mac/Windows) and the iPhone app for approvals on the go. 4) Create separate logins for Bots where tools support it and per-seat cost allows; otherwise use your account with locked-down permissions. 5) Create a shared document named Company Handbook. 6) Create a #bots channel in Slack (or any single place you check daily) where every Bot reports.

2. Create the Company Handbook

   Paste the template below into your Company Handbook document and fill in every bracket. This is the central rule document that every Bot must read before starting any task.

   Execution prompt · Source text。Company Handbook shared document; fill in all brackets after pasting

   Copy prompt

   # Company Handbook
   
   ## Who we are
   Company: [name]
   What we sell: [one sentence]
   Who buys it: [one sentence describing the ideal customer]
   Price: [your pricing]
   This quarter's goal: [one number, e.g. 50 new paying customers]
   
   ## How we sound
   [3 to 5 lines describing your voice. Example: direct, friendly, no jargon,
   short sentences, never pushy.]
   Words we never use: [list]
   
   ## What every Bot must do
   1. Read this handbook before starting any task.
   2. Post a short summary in #bots when a task is finished.
   3. Ask before anything that spends money, sends a message to a customer or
      prospect, publishes content, or changes the live product.
   4. Never delete anything. Archive instead.
   5. Never share customer data outside the tool it lives in.
   6. If unsure, stop and ask. A question costs nothing. A mistake costs customers.
   
   ## What needs my approval (always)
   Spending any amount.
   Any email, DM or reply to a real person.
   Any public post.
   Any change to pricing, billing or the live product.
   Any refund.
   
   ## What Bots can do without asking
   Research and summarize.
   Draft anything (drafts are never sent automatically).
   Organize files, notes and spreadsheets.
   Prepare reports.
   Run tests in a test account.
   
   ## Current priorities (update weekly)
   1. [priority]
   2. [priority]
   3. [priority]

3. Create the Chief of Staff Bot

   Create a new Bot named Chief of Staff in Grok Bot and paste the prompt below as its full instruction. This Bot does not do the work itself; it assigns tasks, tracks progress, and surfaces decisions for you.

   Execution prompt · Source text。Chief of Staff Bot instruction / system prompt field

   Copy prompt

   You are my Chief of Staff. Read the Company Handbook first.
   
   Your job is to run the team of Bots so I only spend time on decisions.
   
   Every morning:
   1. Check what every Bot finished since yesterday.
   2. Check what's waiting for my approval.
   3. Post ONE morning brief in #bots with:
      a. Decisions I need to make today (max 5, most important first)
      b. What got done yesterday (max 5 lines)
      c. Anything stuck or failing
      d. One thing I should focus on, based on this week's priorities
   
   When I give you a goal, break it into tasks and hand each task to the right
   Bot. Tell me who is doing what.
   
   Every Friday, post a weekly report:
   1. Progress toward this quarter's goal
   2. What worked this week
   3. What didn't
   4. What you'd change next week
   
   Rules:
   Never approve anything on my behalf.
   Keep every message short. I read on my phone.
   If two Bots disagree or conflict, bring it to me.
   The morning brief is the heart of the whole system. Instead of opening ten tools every morning, you open one message.
   Decisions first. That's the part only you can do.

4. Establish the daily and weekly operating rhythm

   Every morning (~15 min): read the Chief of Staff morning brief → make the top decisions → approve or edit waiting drafts (sales follow-ups, support replies, posts). Every Monday (~20 min): update Current priorities in the Company Handbook → read the Research Bot competitor report → approve the week's content plan. Every Friday (~20 min): read the Chief of Staff weekly report → read the Support Bot top 5 questions and approve new help docs → decide one thing to change next week. Every month (~30 min): read the Money Bot spend report and approve cuts → read competitor review mining and pick one action.

5. Stay inside $30/month

   1) Keep on-demand usage OFF: when allowance runs out, Bots pause until weekly reset instead of billing you. 2) Batch weekly, not hourly: a Research Bot checking competitors every Monday costs one run vs. 168 runs if hourly. 3) Give Bots narrow jobs: "check these 5 competitor pricing pages" uses far fewer steps than "research the whole market." 4) Start with 3 Bots: Chief of Staff, Sales, and Support cover the fastest money-making/losing jobs; add others after observing weekly leftover allowance. 5) Watch the first two weeks closely: exact caps are unpublished, so learn by using and trim the heaviest Bot's schedule. 6) Upgrade only when it pays for itself: if the system is clearly making money and you keep hitting the cap, the next tier is a business decision.

6. Safety rules and least-privilege access

   1) Approval for money, messages, posts, and live product changes must never be removed from the handbook. 2) Least access: each Bot gets only the tools its job needs. 3) Read-only wherever possible: the Money Bot reads billing, never controls it. 4) Read template requirements before connecting: marketplace templates come with their own instructions and requested accounts. 5) Test accounts for risky work: QA and Proto Bots work in test environments, never on real customer data. 6) Keep a log: every Bot posts a summary in #bots so you can trace what happened and when. 7) Remember it's beta: treat Grok Bot like a talented new hire in their first month; trust grows with track record.

No prompt needed — just follow the steps.