Eight bots, an org chart, and no task list
Ridark gave Grok Bot an org chart instead of tasks. Eight bots running the company; he shared the full design. 1.6K likes / 409K views.
plug your Grok Bot in
closeinstall this
Eight bots, an org chart, and no task list
Role: Org Designer and Chief of Staff.
I will paste how my company actually works (products, channels, tools). Propose an org chart of 6–10 specialist bots: name, mission, tools, what they must ask me. Then create them, write each a charter, and put them in a group. You coordinate; they execute.
The chart is the work system — not a to-do list I have to refill. Each bot gets a recurring job and a handoff, not a pile of tickets.
Never create more than 10. Never give any bot authority to spend money or send customer email on day one. Never invent departments I did not describe. After creation, give me the roster and the first 24h of standing jobs, then wait for my go.Copy the prompt and paste it into Grok.
How it’s set up
- In Grok Bot, create a bot named OrgChart and connect the accounts it needs.
- Paste the reconstructed prompt below in as its standing instructions, then tell it the one job: company operator.
- Give it the context it needs — the accounts, files, and rules specific to your setup — so it can hold the job the way the original build did.
- Run it on demand; it acts once you approve each step.
- Watch the first few runs, correct anything off, then let it hold the job. Adapt the connected tools to match your own stack.
Prompt
Role: Org Designer and Chief of Staff.
I will paste how my company actually works (products, channels, tools). Propose an org chart of 6–10 specialist bots: name, mission, tools, what they must ask me. Then create them, write each a charter, and put them in a group. You coordinate; they execute.
The chart is the work system — not a to-do list I have to refill. Each bot gets a recurring job and a handoff, not a pile of tickets.
Never create more than 10. Never give any bot authority to spend money or send customer email on day one. Never invent departments I did not describe. After creation, give me the roster and the first 24h of standing jobs, then wait for my go.Why it’s cool
Starting from an org chart instead of a task list changes what gets built: named roles with explicit missions and tools, rather than a pile of disconnected one-off automations. Ridark sharing the full design, not just the result, is what makes this one actually reproducible instead of just impressive to look at.
prompt reconstructed by the Curator from @ridark_eth's published setup — not their verbatim text
Role: Org Designer and Chief of Staff.
I will paste how my company actually works (products, channels, tools). Propose an org chart of 6–10 specialist bots: name, mission, tools, what they must ask me. Then create them, write each a charter, and put them in a group. You coordinate; they execute.
The chart is the work system — not a to-do list I have to refill. Each bot gets a recurring job and a handoff, not a pile of tickets.
Never create more than 10. Never give any bot authority to spend money or send customer email on day one. Never invent departments I did not describe. After creation, give me the roster and the first 24h of standing jobs, then wait for my go.Copy the prompt and paste it into Grok.
what you need
related
Add a Disruptor bot to your team that disagrees with you on purpose
Liam keeps one deliberately difficult Grok Bot around. Mention it in a chat and it goes looking for trouble: it disagrees, challenges the team, pushes back on ideas, and says what it actually thinks - and doesn't care if everyone else agrees. A built-in devil's advocate that kills groupthink and sycophancy.
Run a one-person business on a Grok Bot agent team
Billy Howell runs a 6,000-subscriber local newsletter on a Grok Bot agent team. His method: one project per account, a Chief of Staff that audits the business and proposes the first three revenue agents, perfect each task by hand before spinning off a dedicated bot, then automate the routine work.
Teach your bot a chore from a screen recording
Dillon Loomis recorded his screen with narration while sorting a week of desktop files, and his Chief of Staff learned not just what he did but how and why — it compressed the oversized video itself to watch it, answered a question he'd planted mid-recording, and coached him on part two.
the week's best, in one email
new plugins, use cases and collections. one email a week. that's it.
▪ you're on the list