AI Native 公司的 30 个特征

AI Native 公司的 30 个特征 传统公司用 AI 是"给人配工具" AI Native 公司是"围绕 Agent 重建流程" AI Native 公司的本质，是把"智能"从员工个人的能力...

AI Native 公司的 30 个特征 传统公司用 AI 是"给人配工具" AI Native 公司是"围绕 Agent 重建流程" AI Native 公司的本质，是把"智能"从员工个人的能力，变成公司可复用、可度量、可迭代的基础设施。 # 30 条特征的内在结构（六层架构） 第 1 层：数据与上下文地基（ #3 , #5 , #12 , #25 , #30 ） · 集中式智能层作为单一事实源；"上下文即代码"；一切工作被记录；每个输出可追溯到提示词、模型、数据和审批人。 · 这是最关键的一层：没有被结构化的上下文，Agent 就是无源之水。 "Traceability as training signal"（ #30 ）尤其深刻——反馈必须附着在具体对象上，才能变成改进信号。 第 2 层：模型与算力调度（ #4 , #11 , #21 , #23 ） · 模型路由优化"单次成功任务成本"；重规划用强模型、执行用便宜模型；用 RL 环境+自有数据微调开源模型；Evals 是核心基础设施。 · 核心思想：把模型当作可替换的商品，把评测当作护城河。 模型会贬值，eval 体系和私有数据不会。 第 3 层：Agent 工程体系（ #7 , #9 , #10 , #12 ） · 技能分发系统、Agent 舰队自动完成编码全流程、"每个被接受 PR 的成本"成为核心指标。 · 这标志着软件工程从"人写代码"转向"人定义意图和验收标准"。 第 4 层：治理与安全（ #26 , #28 , #29 ） · 权限在数据层继承、先建护栏再建功能、"挣来的自主权"（观察→建议→审批后执行→自主执行的阶梯）。 · #29 是全文最成熟的一条： autonomy 不是一次性授予的，而是由 eval 门禁逐级解锁的。 第 5 层：职能流程重构（ #13 , #14 , #18 , #19 , #20 ） · 财务连续记账、营销用 Agent swarm 测素材、SEO/AEO 自动引擎、AI 对抗 AI 的安全。 · 模式一致：从"周期性人工流程"变成"持续性自动流程 + 人类把关首尾"（ #22 ）。 第 6 层：组织与文化（ #1 , #2 , #6 , #8 , #15 , #17 , #24 , #27 ） · 全员日常用 AI、高管亲手 build、非技术人员走 Citizen Developer SDLC、每三个月敢于推倒重来、主动自我颠覆。 · 这是最稀缺的一层——工具可以买，文化买不到。 # 四个底层原则 1. 成本即指标： #4 、 #9 、 #23 共同指向一个新财务语言——token 效率、单次成功任务成本、单 PR 成本。AI 开支从"IT 预算"变成"单位经济模型"。 2. 人机分工的公式：人类管意图、标准、第一公里和最后一公里（ #8 , #10 , #22 ）；机器管中间的大规模执行与迭代。 3. 闭环即竞争力： #16 、 #29 、 #30 构成"执行→记录→评测→反馈→升级"的飞轮。AI 原生公司的壁垒不是用了什么模型，而是反馈回路转得有多快。 4. 可抛弃性： #6 是最反直觉的一条——在模型能力每季度跃迁的时代，流程和代码是消耗品，上下文和 eval 才是资产。 Alex Lieberman @businessbarista 30 features of an AI native company: 1) Function-by-function process blueprint of your entire business. 2) Everyone in org using a daily driver harness like Grok Bot, Claude Cowork, ChatGPT at Work. 3) Centralized intelligence layer that aggregates structured and unstructured data, documents, and business logic into a single source of truth that is queryable & agentic work can be done on top of. 4) Model routing via OpenRouter, Ramp, etc that optimizes cost-per-successful-task across the business. 5) Treat context as code, ensuring architecture documents and conventions remain updated while allowing for diligent upfront planning. 6) Willing to throw away everything that you've built every three months and reimagine all your workflows. 7) A “skills distribution system” is used to manage agent behavior and optimize for token efficiency by ensuring developers trigger consistent skills throughout their workflow. 8) Separate technical implementation from high-level specifications, enabling non-technical staff to contribute in a format that agents can utilize to build technical implementation plans. 9) A key software metric is “cost per accepted PR”, with a focus on driving these costs down through better token efficiency. 10) An automated, agent-native development system where fleets of AI coding agents handle planning, writing, testing, reviewing, and shipping code while humans define the intent and acceptance criteria. 11) Heavy planning with higher-effort models and executing with cheaper, faster models. 12) Agent harness that uses CLI tools to parse metadata within markdown files to traverse dependency relationships, allowing agents to be granular in their input token usage. 13) Finance org that runs processes continuously in accounting (record-keeping) to re-define/reset forecasts on a much, much tighter cadence. 14) Financial models embedded in the underlying OS across the org to help drive reasoning. 15) Citizen Developer SDLC where non-technical employees can take a solution from idea to production with governance, access, versioning, and software conventions built in. 16) Closed loop, self-improving non-engineering workflows that learn from previous runs based on external performance metrics or internal evals. 17) AI ROI framework that includes experimental phase, scaling phase, and optimizing phase with bets sitting in 3 buckets: infrastructure, innovation, and efficiency. 18) Paid marketing motion that uses agent swarms to deploy thousands of pieces of creative for testing, before increasing spend on human-generated ads. 19) AEO/SEO engine that audits, rewrites, and (ideally) generates SEO/AEO-optimized blogs on a weekly basis, and then measures if any of it worked. 20) Agentic cyber security solution that fights AI with AI. 21) Combo of RL gym and first-party data to fine-tune open source models on high-volume processes that need SOTA performance at reasonable cost. 22) Human touch and judgement gets reserved for the first and final mile of most processes. 23) Evals are core infrastructure of your business. Anytime new models come out you have an apparatus for testing cost & performance against core processes. 24) Everyone is a builder. Especially C-level execs. 25) Everything gets recorded because what you don’t capture can’t be turned into ai-enabled work. 26) Legal, HR, and IT work in lockstep with owners of AI agenda so that business’ ass is sufficiently covered without slowing down transformation. 27) Bias to disrupting yourself before being disrupted by others. 28) Guardrails before features. Agents inherit the permissions of whoever is asking, enforced in the data layer. 29) Earned autonomy. Feedback feeds the evals that gate each new version, and agents move up a ladder as they clear it: observe, suggest, act with approval, act alone. The endpoint is agents running whole workflows inside a defined boundary, with humans setting the standard instead of checking every answer. 30) Traceability as the training signal. Trace every output to its prompt, model, data, and approver, so human feedback attaches to something specific rather than a vague sense that something is off. What's missing? 🔗 View Quoted Tweet 💬 0 🔄 0 ❤️ 0 👀 206 📊 1 ⚡