Michal Barus @webjuice_ie
11 seats - Multi-seat Grok @bot fleet I talk to coordinator, he runs...
11 seats - Multi-seat Grok @bot fleet I talk to coordinator, he runs the fleet This is the ops map we actually use. One coordinator seat plus specialist seats. Humans stay on send, spend, and merge. Who owns what: 1. Auditor seat → foundation audits, pushes Critical/High to SEO = @seoutils_app 2. SEO seat → fixes and PRs (I merge) - @dataforseo 3. Ads seat → recommend-only (no live spend without me) using Google Ads MCP 4. Copy seat → blogs and pages, asks Designer for images 5. Social seat → Postly drafts, asks Designer for creatives (no GBP) @postlysocial 6. GBP seat → listing ops, asks Designer for plates - using Cloud browser in Grok bot 7. Linkbuilder seat → Incogniton submits, four gates before live - 100 accounts / proxies 8. Outbound seat → outreach drafts only (never send) - ppcreveal(dot)ai - scanning companies running Ads 9. Research seat → last-30-days packs @slashlast30days 10. Designer seat → all visuals (Higgsfield) @higgsfield_ai 11. CEO coordinator seat → routes the fleet under my approve gate Standing clocks: 1. Daily X draft + hook research (early morning) 2. Multi-channel social Tue–Fri 3. GBP Mon/Wed/Fri 4. Weekly blog Tuesday 5. End-of-month audit 6. Obsidian Vault lint every morning with each agent SOPs - sharing with Hermes Truth layers: 1. Obsidian → durable SOPs per seat 2. Nifty → work log and VAs 3. Grok memory → working facts 4. Hermes → QUERY only for us 5. Git + Cursor + Astro → code and site work when the job needs it The diagram at the bottom is the real rule: every path ends at me approve. The bots draft and queue. I hit send, spend, or merge. Tools: 1. Grok Bot → seats, routines, memory 2. Obsidian + Nifty → SOPs and work log 3. Hermes → query vault 4. Postly / Higgsfield / Incogniton → channel and creative ops 5. Cursor + Astro + Git → build and ship 6. DataForSEO / SEO Utils / PPC Reveal Why it matters: 1. One person can run specialist loops without hiring a VA per channel 2. Handoffs are explicit (audit → SEO, copy/social/GBP → Designer) 3. Approvals sit where money and reputation live If your “AI agency” is still one chat window and a pile of prompts, you’re missing the seat map.
根據 @webjuice_ie 在 X 公開分享的例子。
查看 X 原帖 ↗他們做了什麼
11 seats - Multi-seat Grok @bot fleet I talk to coordinator, he runs the fleet This is the ops map we actually use.
怎麼運作
UseGrokBot ingested this public X post. We keep the original permalink and did not re-run this Bot.
爲什麼重要
The original X post is the source. This card is a short curator summary, not a reprint of the thread.
爲什麼有用
A public example of someone handing work to Grok Bot, kept here with attribution.
誰應該試
- Developers
- Engineering teams
Michal Barus on X
X 原帖
如果原帖被刪、賬戶之後改爲受保護或被停用,X embed 可能加載不了。這頁的摘要會留下。
更多發現
Nate Herk@nateherk
5 天前 · 2026年8月19日
308 萬
X 瀏覽
一周 Grok Bot 技巧
Nate Herk 在 X 發表〈A Week of Grok Bot Lessons in 10 Mins〉:九個把默認 Bot 變成一隊的做法。Elon 同一個早上引用,問大家在跑什麼 Bot。
結果
九個技巧 · 一隻幕僚長
Elon 讚過
Blake King@BlakeKing777
5 天前 · 2026年8月19日
35.4 萬
X 瀏覽
頭 48 小時,不用會 code
Blake 接了公開挑戰,跳過 OpenClaw,兩個晚上:接郵件、讓 Bot 做一份 12 頁家庭預算 PowerPoint、爲太太生意開一隊 Bot、再每天收 Tesla 新聞摘要。
結果
12 頁預算幻燈片 · 48 小時,不用 code
Elon 讚過
Rahul@sairahul1
5 天前 · 2026年8月19日
530 萬
X 瀏覽
一人公司
2026 年 8 月 19 日,Rahul(@sairahul1)在 X 發表文章〈How To Build a One-Person Company Using Grok Bot〉。開頭就是一人公司的負荷——找客、寫外展、做圖、回復、數一星期——再用 Bot 系統接手這些線。
結果
六隻起步 Bot · 一人公司