一人公司的 Bot 组织：约 140 个 Bot 只直接对接 8 个，Notion 作共享大脑、Top 10 规则页与五类必批动作
A one-person company on Grok Bot: ~140 bots, 8 direct reports, Notion as the shared brain, a Top-10 rulebook and five actions that always need a yes
X, @aymanalabdul, 2026-11-09
https://x.com/aymanalabdul/status/2119811377199981012
场景
作者把每个工作流当成一个岗位，用 Bot 搭出 CEO 办公室、领导层、季度 GM、内容、销售、教练等部门
The author treats each workflow as a hire and builds an office of the CEO, leadership, quarterly GMs, content, sales and coaching out of bots
他们怎么做
先锁定账号：银行等金融账户不上 Bot 电脑；个人与业务分不同用户；本机执行设为 Never；开 Auto-review，为发布、对外发送、花钱、删除、改权限五类加 Ask first 规则；接 1Password，禁止在聊天贴密码。先建 Chief of Staff 并设为 primary bot，负责名册、Start Here 规则页、入职 SOP、头像配色、Standing Corrections 纠错日志、晨报；每个 Bot 在 Notion 有私有主页，建 8 类上下文库（身份、优先级、汇报格式、决策权、语气、归属、地图、部门简报）。三层组织：Chief → 各 Head（一句话说清所负责的结果）→ Doer；直接对接限 5–8 个 Bot；CFO 与法务 Bot 私有。运行规则：Notion 是唯一事实源；规则页最多 10 条；每次纠正同轮更新 SOP 并记日志；每个 Bot 有六段式 SOP；统一汇报格式；同一请求问 3 次就做成 Routine，先每日而非每小时。安全：后台审批卡 30 分钟过期；卡片存 Vault 会在结账时自动填，想逐笔批准就别存；同账号 Bot 共享电脑与登录，不是安全边界，需要隔离就分用户；让 Chief 做只读的 7 级隐私审计
Lock the account down first: no banking or financial accounts on the bot computer; separate users for personal and business; local execution set to Never; Auto-review on with Ask first rules for publishing, sending outside the team, spending, deleting and changing permissions; 1Password connected and no passwords in chat. Hire the Chief of Staff first as primary bot, owning the roster, a Start Here rulebook, the onboarding SOP, avatar colours, a Standing Corrections log and the morning brief; every bot gets a private Notion home and reads an 8-part context database (identity, priorities, reporting format, decision rights, voice, ownership, map, department briefs). Three layers: Chief, heads that each own one outcome, doers; 5-8 direct reports; CFO and legal bots private. Run rules: Notion is the single source of truth; the rulebook is capped at 10; every correction updates the SOP and the log in the same turn; every bot has a six-part SOP; one report format; anything asked for three times becomes a routine, daily before hourly. Safety: background approval cards expire after 30 minutes; a card saved in Vault autofills at checkout, so don't save it if you want to approve each payment; bots on one account share a computer and logins and are not a security boundary, so isolate with separate users; have the Chief run a read-only seven-tier privacy audit
可以拿走的做法
五类必批动作 + Ask first 规则；纠错同轮更新 SOP；Top 10 规则页；「需要独立登录就分用户」；第三方补充的只读权限盘点提示词（列出每个 Bot 登录过的站点并按钱/客户数据分组）
Five always-approve actions as Ask first rules; every correction updates the SOP in the same turn; a Top-10 rulebook; separate users when a job needs its own logins; the third-party read-only access inventory prompt (list every site each bot is signed into, grouped by money and client data)结果与限度
营收与规模数字（AppSumo 3M→84M、约 140 个 Bot）为作者自述；文中带有其 CEO 社群与 Bot 模板链接，有一定推广性质；第三方评述提醒 140 个 Bot 共用同一电脑与登录的安全面。
Revenue and scale figures (AppSumo $3M to $84M, ~140 bots) are self-reported; the article links his CEO community and a bot template, so it is partly promotional; a third-party post flags the security surface of 140 bots sharing one computer and set of logins.
来源
- 平台
- X
- 作者
- @aymanalabdul
- 日期
- 2026-11-09 23:16 Asia/Taipei (UTC+8)
- 日期依据
- 案例库画布，采集截止 2026-11-11 09:26 Asia/Taipei
- 时间窗
- 近7天 案例字段「近7天」相对采集截止 2026-11-11 09:26 Asia/Taipei，不是相对打开页面的今天
- 原分类
- 一手实践/组织设计与安全
这条证据标签是什么意思
全文核对
来源已经读过（帖子、文章或字幕）。这只说明原文被读过，不代表本站复现了作者的结果。
标签不是评分。全文核对只表示来源被读过，不表示结果已被复现。