返回列表
🧠 阿头学 · 💬 讨论题

AI 原生不是装插件,而是重写公司操作系统

这篇文章最成立的判断是“AI 原生”本质上是组织重构而不是工具采用,但它把机会讲得很大、把落地难度和证据讲得太轻,明显带有咨询获客式放大。
打开原文 ↗

2026-05-12 原文链接 ↗
阅读简报
双语对照
完整翻译
原文
讨论归档

核心观点

  • AI 原生的门槛不在模型,在组织可读性 作者最有价值的判断是,真正的 AI 原生公司不是“有人在用 ChatGPT”,而是数据、流程、权限、政策、SOP 都被整理成智能体可理解、可执行、可审计的形式;这个区分是对的,因为绝大多数企业今天确实只有 AI 辅助,没有 AI 架构。
  • 核心流程重做,比边角提效更重要 文中把“AI 辅助型公司”与“AI 原生公司”区分为前者在边缘省时间、后者重做核心工作流,这个判断抓住了问题本质;客服、销售、招聘等流程如果还是人先找信息、再拼上下文、再手工推进,那 AI 顶多是文案外挂,不会改业务结构。
  • AI 带来的不是单点提效,而是管理模型变化 文章判断未来强公司会变成“智能体做结构化工作,人类处理判断、关系、例外”,这个方向站得住;如果成立,竞争优势会体现在人均收入、响应速度、毛利率、交付稳定性,而不是体现在 PPT 里的“我们接了大模型”。
  • 最现实的切入口是高重复知识劳动行业 作者认为最好的机会不一定是通用 AI SaaS,而是家政、保险、招聘、合规、BPO、会计等“客户按结果付费、成本主要是重复智力劳动”的行业,这个投资判断有现实感;这些行业更容易把流程标准化,也更容易把自动化直接转成利润。
  • 文章最大的争议在于把叙事说得比证据更满 “全球 ARR 超过 500 万美元且真正 AI 原生的公司可能只有 1000 家”这个数字基本是拍脑袋,作者自己也承认只是猜测;它能制造紧迫感,但不能当事实依据,更不能直接推出“赛道几乎空白、现在必然是大机会”。

跟我们的关联

  • 对 ATou 意味着什么、下一步怎么用 ATou 如果在看 AI 创业,不该再问“做什么 AI 功能”,而该问“哪个行业的核心流程能先按 agent 执行、人类审核来重构”;下一步可以直接拿一个垂直流程做尽调模板:触发条件、数据源、决策点、审批边界、错误成本、可量化结果。
  • 对 Neta 意味着什么、下一步怎么用 Neta 如果关注组织设计,这篇文章的价值不在“AI 热词”,而在“隐性知识显性化”这一管理命题;下一步可以把一个团队常见流程拆成规则、例外、升级路径和评估标准,验证哪些知识真的能系统化,哪些仍然必须靠人。
  • 对 Uota 意味着什么、下一步怎么用 Uota 如果关心产品与工作流结合,这篇文章提醒的是 agent 产品不能只卖一个聊天界面,必须嵌进具体流程;下一步要优先找“已有规则、错误可控、量大重复”的场景,把摘要、分类、建议、补全做成工作流节点,而不是做一个泛泛的 AI 助手。
  • 对投资判断意味着什么、下一步怎么用 对投资来说,真正该看的不是团队会不会讲 agent 故事,而是它是否把组织知识、权限系统、数据结构和反馈闭环做成了难复制的操作层;下一步尽调时要看单位人效、流程自动化深度、错误率、续约率和毛利,而不是只看 demo 漂不漂亮。

讨论引子

1. 什么指标最能判断一家公司是“AI 原生”而不是“AI 辅助”,人均收入够不够,还是必须看核心流程自动化率? 2. 老公司真的很难转成 AI 原生,还是作者为了创业叙事故意低估了 incumbents 的改造能力? 3. 哪些行业最适合先做“AI 原生服务公司”,哪些行业则会因为责任、监管或例外过多而很难跑通?

关于什么才叫 AI 原生,这里把真相说清楚。

https://1543b7c1.click.convertkit-mail4.com/27u6n9m9x6uoh8zozwpc3hg993d8ncghnog2w/6qheh8hlegekl2ho/aHR0cHM6Ly9sYXRlY2hlY2tvdXQuYWdlbmN5

现在到处都有人说自己是 AI 原生,通常意思不过是团队里有人开着一个 ChatGPT 标签页,市场负责人做了一个名叫 Brand Voice Assistant 的自定义 GPT。

挺可爱。

也确实有用。

但这不叫 AI 原生。

大家一直忽略的,正是这里的区别。AI 原生公司,不是使用 AI 的公司。它是那种已经被重新搭建过,能让 AI 真正在内部运转起来的公司。它的业务结构、文档、权限和观测方式,都已经整理成智能体能理解的样子。它让自己对机器而言是清晰可读的。

这话听起来有点无聊,直到你意识到,这可能会是未来十年里最大的商业优势之一。

因为绝大多数公司,对机器来说都不可读。很多公司,甚至对自己的员工都谈不上清晰可读。

CRM 里写的是一套。Slack 线程里说的是另一套。真正的客户历史躺在某个人的邮箱里。定价逻辑放在一个名叫 Final_v7_NEW 的表格里。退款政策在一篇谁也不太信任的 Notion 文档里。销售流程是 去找 Sarah 聊,她知道企业客户怎么做。入职流程要经过五个工具、三个人、两个审批步骤,外加一个创始人,直到今天还会被随机边缘情况拉进去,因为从来没人把判断沉淀成系统。

然后这些公司会问,为什么 AI 不能替我们做更多事?

因为 AI 不能靠感觉运转。

它没法经营一种真相分散在人员、工具、习惯、例外和组织记忆里的公司。智能体需要上下文。需要干净的输入。需要规则。需要访问权限。需要边界。需要知道什么才算好。需要知道什么时候该行动,什么时候该发问。

过去二十年里,大多数公司一直在买软件,却没有花二十年去设计一套操作系统。它们拥有的是一堆工具,不是一台机器。

这就是为什么,真正称得上 AI 原生的公司,数量可能少得惊人。我的猜测是,全球年经常性收入超过 500 万美元、并且在真正意义上做到了 AI 原生的公司,也许只有 1000 家。不是那种 我们用了 copilot。也不是 我们把一些邮件自动化了。我的意思是,那些核心工作流本来就是为智能体执行、人类监督而设计的公司。

也许这个数字是 500。也许是 2000。具体多少并没有结论本身重要。

因为现在,几乎没人真正做到这件事。

尽管噪音铺天盖地,尽管融资消息一波接一波,尽管每一家 SaaS 官网都把 agentic 这个词重写进去了,这片赛道实际上几乎还是空的。

第一个有用的区分是这个。AI 辅助型公司,把 AI 用在边缘。AI 原生公司,重做的是核心。

AI 辅助型公司会问,哪里能加上 AI 来省时间?

AI 原生公司会问,如果前 80% 的工作由智能体完成,那这个工作流本来该怎么存在?

第二个问题会改变一切。

拿客服来说。在普通公司里,一张工单进来后,由人工先阅读,再去搜索上下文、核对账户、回忆政策、写回复,可能还要问工程团队,可能要升级处理,也可能忘了正确标记原因。它本质上是一个由人驱动、四周零星撒着软件的流程。

在 AI 原生公司里,这张工单会进入一个智能体能够理解的系统。智能体会读取客户历史,检查套餐限制,查看过往工单,检索政策,起草回复,建议动作,要么直接解决问题,要么把它交给人工,并明确指出为什么这个点需要人来判断。人工不再是搜索引擎、路由器和文案写手。人工负责的是审查模糊性。

这是两种完全不同的公司。

把同样的逻辑套到销售上也是一样。旧方式是 SDR 自己去 Google 搜潜在客户,猜测怎样个性化,写一封平庸的邮件,因为经理催才去更新 Salesforce,然后把半套上下文交给 AE。AI 原生的做法则是,让智能体监控购买信号、补全账户信息、绘制利益相关方图谱、起草触达内容、学习哪些切入点转化更高、自动更新 CRM,并给销售人员一场已经准备好的对话,而不是一张空白纸。

法务也是这样。招聘也是这样。财务也是这样。理赔处理也是这样。客户管理也是这样。研究工作也是这样。

这个模式会在所有地方反复出现。智能体做结构化的工作,人类处理品味、信任、判断、关系和例外。

这不是一点点生产力提升。

这是一种新的管理模型。

过去一百年里,公司扩张的默认方式是多招人、设部门、加管理层、买软件,再发明流程去协调这团混乱。每多一层,解决一个问题,又制造出三个新问题。公司变大了,也变慢了。会议更多。交接更多。谁负责这个的追问更多。内部重力更强。

AI 原生公司会以不同方式扩张。

它们不会像传统公司外挂一个聊天机器人。它们会像一小支团队在运作一整支由专业智能体组成的大舰队。一个 12 人的公司,能做过去需要 80 人才能做的事。一个 40 人的公司,能和 400 人的老牌对手竞争。人均收入会变成最清楚的信号之一,说明这家公司是否真的为新时代而建。

https://1543b7c1.click.convertkit-mail4.com/27u6n9m9x6uoh8zozwpc3hg993d8ncghnog2w/6qheh8hlegekl2ho/aHR0cHM6Ly9sYXRlY2hlY2tvdXQuYWdlbmN5

很多人听到这里就会开始防御。他们一听到 智能体做工作,就以为这意味着人要消失了。

重点不在这里。

更准确的理解是,现代公司长期把人的智力浪费在机器形状的任务上。我们让人去在不同工具之间搬运信息。让人去记流程。让人去翻文件夹。让人去重写同样的邮件。让人去追审批。让人去总结电话、填写字段、复制数据、分类请求,再去问别的人某个东西放在哪里。

很多工作,其实根本不是真正的工作。

它只是组织摩擦贴着一撮假胡子。

AI 原生公司会把这些摩擦剥掉。

它们保留真正重要的人类部分,把那些只是因为过去的软件太笨、无法理解上下文才存在的部分自动化掉。这意味着人的角色不是更不重要,而是杠杆更大。一个优秀的运营,能监督十条工作流。一个优秀的销售,能去完成那些由智能体提前铺好的对话。一个优秀的客服负责人,会变成升级逻辑和客户体验质量的设计者。一个优秀的创始人,会成为公司思考方式的架构师。

创始人这一点尤其重要。

AI 原生的创始人,不只是做产品的人。他们是在设计一家能被智能体理解的公司。

这意味着,创始人必须把隐含的东西讲明白。我们的退款政策是什么?什么情况下可以破例?什么样的线索算合格?面对愤怒的客户要用什么语气?哪些事情绝不能自动化?哪些动作必须审批?什么叫一个好答案?什么叫一个危险答案?哪个数据源才是真正的事实来源?两个系统打架时怎么办?智能体该如何从纠正中学习?

这些不性感的工作,才会把真正的 AI 原生公司和 LinkedIn 上的表演区分开。

人人都想要魔法。

没人想打扫厨房。

可厨房就是公司本身。

最后赢的公司,会以异乎寻常的认真去做那些无聊但基础的事。它们会清洗数据。会整理工作流。会编写智能体可读的 SOP。会建立权限和审计轨迹。会把客户记录结构化,不让上下文被困在人脑里。会建立评估闭环,让智能体随着时间变得更好。会把每一次重复决策都变成一套决策系统。

然后,一旦底层运作层干净了,它们就会快得离谱。

所以,AI 原生其实不是一个技术标签。

它是一个组织标签。

一家公司可以用上世界上最好的模型,但在结构上依然无法从中获益。如果智能体还得猜真相藏在哪儿,如果它拿不到正确的系统权限,如果没人定义决策规则,如果每个工作流都依赖于某个人脑子里埋着的例外,那 AI 终究只会是个玩具。它会起草东西。会总结东西。会让人感觉自己更快了。但它不会改变这门生意。

真正的变化,会发生在智能体成为公司运作织体的一部分之后。

想象一家真正 AI 原生的家政服务公司。每一个进入系统的请求都会被自动分类。每一份报价都从结构化的定价规则中生成。每位技师在到达前都会收到工作摘要。每位客户都会得到主动更新。每一次评价请求都会被个性化处理。每一次爽约都会自动触发补救工作流。每一种运营模式都会反馈回派单、定价和人员配置里。

再想象一家保险经纪公司。智能体会收集文件、预审提交内容、比较保单、标出缺失细节、起草给客户的解释、准备续保选项,并监控账户变化。人类负责建立信任和处理复杂情况,但下面那套机器,整天都在做重复性的智力劳动。

再想象一家招聘公司。智能体会搜寻候选人、补全资料、对照岗位要求进行比较、起草触达内容、总结面试、核查推荐信、更新流程管道,并在候选人异常强时提醒人工。招聘顾问不再是数据清洁工,而成了关系成交者。

这些都不是科幻公司。

它们只是普通行业里,把内脏重新搭建过的公司。

这正是人们低估的机会。那些显眼的 AI 公司已经很拥挤了。通用 copilot、写作工具、会议机器人、代码助手、图像生成器、客服包装层。都可以是不错的生意,但也都很显眼。更不显眼的机会,是进入那些无聊、赚钱、分散的行业,围绕智能体把它们的操作模型重新搭起来。

AI 原生代理公司。AI 原生经纪公司。AI 原生类法律服务。AI 原生会计事务所。AI 原生合规服务。AI 原生医疗行政公司。AI 原生房地产运营。AI 原生教育服务。AI 原生物流协调方。AI 原生 BPO,而且看起来根本不像 BPO。

这个世界上有太多行业,客户为结果付费,而服务方的成本结构主要是重复性的知识劳动。

这正是 AI 原生公司最容易切进去的地方。

最好的机会,起初看起来未必像软件公司。有些会更像服务型企业,只是里面藏着软件级的利润率。这会让投资人和竞争对手都看不懂,而这正是好事。当所有人都在寻找下一个 SaaS 仪表盘时,真正的赢家可能正在悄悄打造 AI 原生服务公司,用远低得多的劳动强度,交付更好的结果。

这话很有 Greg 的风格,但我确实觉得,下一波互联网生意,看起来可能不像创业公司,反而更像一台台奇怪的小型印钞机。

小团队。窄市场。专有工作流。高自动化。高信任。明确的客户痛点。无聊的品类。漂亮的利润率。

从外面看,不性感。

从银行账户里看,性感得很。

而且因为这些公司从第一天起就是按另一种方式建的,老玩家会很难复制。老公司不可能靠宣布一个 AI 计划,就变成 AI 原生。这就像你想把一艘邮轮改成快艇,只靠换一个新方向盘。

难点不在于能不能接触到模型。

大家都能接触到。

真正难的是,老公司全身都是旧流程债务。它们的数据很乱。政策彼此冲突。团队各守地盘。工作流是围绕人头堆出来的。软件栈像胶带和季度规划仪式硬缝起来的一样。它们的操作系统默认把人类当成信息处理器。

新公司最大的优势,是根本没有家具要搬。

它可以从一开始就是干净的。它可以在设计每个流程时都先问,这件事能不能先让智能体跑第一遍?它可以从第一天开始就做文档。可以让每个数据对象都可用。可以在人为失误变成灾难之前,就先设计好人工审核点。可以在公司僵化之前,就先建好反馈闭环。

这就是为什么 只有 1000 家公司 这个想法重要。它带来了紧迫感,也带来了许可感。

这片赛道之所以空着,是因为大多数人仍然把 AI 采用误认为 AI 架构。

他们以为游戏的关键是提示词工程。

不是。

他们以为关键是选对模型。

也不是。

他们以为关键是给网站加一个聊天机器人。

那更不是。

真正的游戏,是把公司重新设计成一个能让智能流经其中的系统。

这里其实有一套很实际的打法。

第一步,挑一个足够窄、经济价值又足够明显的工作流。不要一上来就想着 让整个公司变成 AI 原生。那太抽象。可以从客服处理、外呼开发、客户入职、理赔录入、文档审查、续约管理或者报表开始。选择那些量大、规则存在、而且现在人花了太多精力在协调上的流程。

第二步,把这个工作流像一台机器一样拆开来看。是什么触发它?需要哪些数据?中间有哪些决策?哪些决策是可逆的?哪些必须审批?成功长什么样?错误通常出在哪儿?人知道、系统却不知道的是什么?

第三步,把知识结构化。如果智能体需要一条政策,那就把政策写出来。如果它需要定价规则,那就把规则讲明白。如果它需要客户历史,那就把客户对象清洗干净。如果它需要样例,那就创造样例。如果它需要语气,那就定义语气。大多数团队都会在这里放弃,因为这看起来像文档工作。其实不是。这是基础设施。

第四步,把智能体放进工作流里,但要带着边界。让它们去起草、分类、建议、补全、总结和准备。只有在风险可控的地方才给它们动作权限。在判断重要的地方要求审批。把一切都记下来。审查输出。跟踪质量。持续改进系统。

第五步,衡量业务影响。不要拿某张假模假式的表格去算 节省了多少小时。要量真正的指标,比如处理时长、转化率、毛利率、人均收入、错误率、客户满意度、销售推进速度、入职时间、续约率。AI 原生公司,应该在数字上看得出来。

这是我最感兴趣的部分。再过几年,AI 原生就不会再是一种感觉。

它会直接体现在指标里。

人均收入会不一样。

毛利率会不一样。

执行速度会不一样。

客户体验会不一样。

最好的公司会显得异常敏捷,像整家公司都是醒着的。客户会更快拿到答案。销售团队会以更好的时机跟进。运营问题会更早浮现。创始人会更清楚地看见业务。管理者会少花时间催进度,多花时间优化系统。

整家公司会少很多阻力。

这才是真正的优势。

不是把 AI 当派对把戏。

而是把 AI 变成组织的新陈代谢。

所以,是的,如今全球真正做到 AI 原生、而且已经有实质收入的公司,大概确实只有 1000 家左右。

而这件事,应该会让你立刻想去建一家。

因为当一个市场足够喧闹时,人们会误以为它已经成熟了。但噪音不等于成熟。通常,噪音恰恰出现在真正的建设者快要弄清楚什么最重要之前。

现在,所有人都在高声谈 AI。

真正从结构上准备好迎接它的公司,少得可怜。

这就是空档。

这就是机会。

下一批伟大的公司,会是那些从内到外围绕智能体重建了数据、工作流、政策和团队的公司。它们看起来会比应有规模更小。它们的速度会快得不合常理。它们会用更少的人做更有价值的工作。它们会把混乱的服务变成可扩展的系统。它们会让老牌公司看起来像是在运行 Windows 95,只不过登录界面更好看一点。

大多数人还在问,怎样把 AI 用到工作里?

更好的问题是,怎样建一家公司,让 AI 能在里面工作?

这个问题,就是那道门。

而此时此刻,几乎还没有人真正走进去。

不管你读到的是什么,这片赛道其实是空的。也许可以把这篇文章分享给一个朋友。

我真心希望你成功。

  • Greg Isenberg

注:我平时不太常提这件事,因为我们确实忙不过来,但我的公司 LCA 在帮助企业走向 AI 原生这件事上,水准是一流的。原因也很简单,他们做得真的很好。我们和《财富》500 强公司以及你熟悉的品牌合作,帮助它们打造 AI 原生产品和 AI 原生组织。

如果你的公司也想走向 AI 原生,可以考虑通过上面的链接联系他们。

如果你在找创业点子,也可以去 Ideabrowser.com 看看那些已经验证过、可以用 AI 来做的点子。

The truth about being AI native. I'll break it down.

https://1543b7c1.click.convertkit-mail4.com/27u6n9m9x6uoh8zozwpc3hg993d8ncghnog2w/6qheh8hlegekl2ho/aHR0cHM6Ly9sYXRlY2hlY2tvdXQuYWdlbmN5

Everyone is walking around saying they’re “AI-native” now, which mostly means someone on the team has a ChatGPT tab open and the head of marketing made a custom GPT called “Brand Voice Assistant.”

Cute.

Useful, even.

But not AI-native.

That’s the difference people keep missing. An AI-native company is not a company that uses AI. It is a company that has been rebuilt so AI can actually operate inside it. The business is structured, documented, permissioned, and instrumented in a way that agents can understand. The company has made itself legible to machines.

That sounds boring until you realize it might be the single biggest business advantage of the next decade.

Because most companies are not legible to machines. Most companies are barely legible to their own employees.

The CRM says one thing. The Slack thread says another. The real customer history lives in someone’s inbox. The pricing logic is in a spreadsheet called “Final_v7_NEW.” The refund policy is in a Notion doc nobody trusts. The sales process is “talk to Sarah, she knows how we do enterprise.” The onboarding flow is five tools, three humans, two approval steps, and one founder who still gets pulled into random edge cases because nobody ever turned judgment into a system.

Then these companies ask, “Why can’t AI do more for us?”

Because AI cannot run on vibes.

It can’t operate a business where the truth is scattered across people, tools, habits, exceptions, and institutional memory. Agents need context. They need clean inputs. They need rules. They need access. They need boundaries. They need to know what good looks like. They need to know when to act and when to ask.

Most companies have spent twenty years buying software, but they have not spent twenty years designing an operating system. They have a pile of tools, not a machine.

That is why the number of truly AI-native companies is probably shockingly small. My guess is there are maybe 1,000 companies on earth doing $5M+ ARR that are actually AI-native in the real sense. Not “we use copilots.” Not “we automated some emails.” I mean companies where the core workflows are designed for agents to execute and humans to supervise.

Maybe the number is 500. Maybe it’s 2,000. The exact number matters less than the conclusion.

Almost nobody is doing this yet.

Despite all the noise, despite all the funding announcements, despite every SaaS homepage being rewritten with the word “agentic,” the field is basically empty.

The first useful distinction is this: AI-assisted companies use AI at the edges. AI-native companies redesign the center.

An AI-assisted company asks, “Where can we add AI to save time?”

An AI-native company asks, “How should this workflow exist if agents are doing the first 80%?”

That second question changes everything.

Take customer support. In a normal company, a support ticket arrives, a human reads it, searches for context, checks the account, remembers policy, writes a response, maybe asks engineering, maybe escalates, maybe forgets to tag the reason properly. It’s a human-driven process with software sprinkled around it.

In an AI-native company, the ticket enters a system an agent can understand. The agent reads the customer history, checks plan limits, reviews prior tickets, consults policy, drafts a response, recommends an action, and either resolves the issue or sends it to a human with the exact reason it needs judgment. The human is not the search engine, router, and copywriter. The human is the reviewer of ambiguity.

That is a very different company.

Now apply the same logic to sales. The old way is an SDR Googling a prospect, guessing at personalization, writing a mediocre email, updating Salesforce because their manager nags them, then passing half-context to an AE. The AI-native way is an agent that monitors buying signals, enriches accounts, maps stakeholders, drafts outreach, learns which hooks convert, updates the CRM automatically, and gives the human seller a prepared conversation instead of a blank page.

Legal is the same. Recruiting is the same. Finance is the same. Claims processing is the same. Account management is the same. Research is the same.

The pattern repeats everywhere: agents do the structured work, humans handle taste, trust, judgment, relationships, and exceptions.

That is not a small productivity improvement. That is a new management model.

For the last hundred years, the default way to scale a company was to hire more people, create departments, add managers, buy software, and invent processes to coordinate the mess. Every new layer solved one problem and created three more. The company got bigger, but it also got slower. More meetings. More handoffs. More “who owns this?” More internal gravity.

AI-native companies will scale differently.

They will not look like traditional companies with a chatbot bolted on. They will look like small teams operating large fleets of specialized agents. A 12-person company will do what used to require 80 people. A 40-person company will compete with a 400-person incumbent. Revenue per employee will become one of the clearest signals that a company is actually built for the new era.

https://1543b7c1.click.convertkit-mail4.com/27u6n9m9x6uoh8zozwpc3hg993d8ncghnog2w/6qheh8hlegekl2ho/aHR0cHM6Ly9sYXRlY2hlY2tvdXQuYWdlbmN5

This is where a lot of people get defensive. They hear “agents do the work” and assume it means humans disappear.

That’s not the point.

The better way to think about it is that modern companies have been wasting human intelligence on machine-shaped tasks. We use humans to move information between tools. We use humans to remember process. We use humans to search folders. We use humans to rewrite the same email. We use humans to chase approvals. We use humans to summarize calls, fill in fields, copy data, classify requests, and ask other humans where something lives.

A lot of work is not really “work.” It is organizational friction wearing a fake mustache.

AI-native companies strip that out.

They preserve the human parts that matter and automate the parts that only existed because software was too dumb to understand context. That means the human role becomes more leveraged, not less important. A great operator becomes the supervisor of ten workflows. A great salesperson becomes the closer of conversations agents helped create. A great support lead becomes the designer of escalation logic and customer experience quality. A great founder becomes the architect of how the company thinks.

That founder point is important.

The AI-native founder is not just building a product. They are designing a company that can be understood by agents.

That means the founder has to make the implicit explicit. What is our refund policy? When do we break it? What makes a lead qualified? What tone do we use with angry customers? What should never be automated? Which actions require approval? What is a good answer? What is a dangerous answer? Which data source is the source of truth? What do we do when two systems disagree? How does the agent learn from corrections?

This is the unsexy work that will separate real AI-native companies from LinkedIn theater.

Everyone wants the magic. Nobody wants to clean the kitchen.

But the kitchen is the company.

The companies that win will do boring, foundational things with unusual seriousness. They will clean their data. They will document their workflows. They will create agent-readable SOPs. They will build permissions and audit trails. They will structure customer records so context is not trapped in human memory. They will create evaluation loops so agents get better over time. They will turn every repeated decision into a decision system.

Then, once the operating layer is clean, they will move absurdly fast.

This is why “AI-native” is not really a tech label. It is an organizational label.

A company can use the best models in the world and still be structurally incapable of benefiting from them. If the agent has to guess where the truth lives, if it cannot access the right systems, if nobody has defined the decision rules, if every workflow depends on exceptions buried in someone’s head, then the AI will remain a toy. It will draft things. It will summarize things. It will make people feel faster. But it will not transform the business.

The transformation happens when agents become part of the operating fabric.

Imagine a home services company that is truly AI-native. Every inbound request is classified automatically. Every quote is generated from structured pricing rules. Every technician gets a job summary before arrival. Every customer receives proactive updates. Every review request is personalized. Every missed appointment creates an automatic recovery workflow. Every operational pattern feeds back into routing, pricing, and staffing.

Now imagine an insurance brokerage. Agents gather documents, pre-check submissions, compare policies, flag missing details, draft client explanations, prepare renewal options, and monitor accounts for changes. Humans build trust and handle complexity, but the machinery underneath is doing the repetitive intelligence work all day.

Now imagine a recruiting firm. Agents source candidates, enrich profiles, compare against role requirements, draft outreach, summarize interviews, check references, update pipelines, and alert humans when a candidate is unusually strong. The recruiter stops being a data janitor and becomes a relationship closer.

These are not sci-fi companies. These are normal businesses with the guts rebuilt.

That’s the opportunity people are underestimating. The obvious AI companies are crowded. Horizontal copilots, writing tools, meeting bots, code assistants, image generators, customer support wrappers. Fine businesses, but obvious. The less obvious opportunity is taking boring, profitable, fragmented industries and rebuilding the operating model around agents.

AI-native agencies. AI-native brokerages. AI-native law-adjacent services. AI-native accounting firms. AI-native compliance shops. AI-native healthcare admin companies. AI-native real estate operations. AI-native education services. AI-native logistics coordinators. AI-native BPOs that don’t look like BPOs.

The world is full of industries where customers pay for outcomes, but the provider’s cost structure is mostly repetitive knowledge work. That is exactly where AI-native companies can wedge in.

The best opportunities will not always look like software companies at first. Some will look like services businesses with software margins hiding inside. That will confuse investors and competitors, which is useful. While everyone else is looking for the next SaaS dashboard, the real winners may be quietly building AI-native service companies that produce better outcomes with dramatically lower labor intensity.

This is a very Greg thing to say, but I think the next wave of internet businesses may look less like “startups” and more like weird little money machines.

Small teams. Narrow markets. Proprietary workflows. High automation. High trust. Clear customer pain. Boring category. Beautiful margins.

Not sexy from the outside.

Extremely sexy in the bank account.

And because these companies are built differently from day one, incumbents will struggle to copy them. An old company cannot become AI-native by announcing an AI initiative. That is like trying to turn a cruise ship into a speedboat by buying a new steering wheel.

The hard part is not access to models. Everyone has that.

The hard part is that incumbents are full of old process debt. Their data is messy. Their policies conflict. Their teams protect turf. Their workflows were built around headcount. Their software stack is stitched together with duct tape and quarterly planning rituals. Their operating system assumes humans are the default processors of information.

A new company has the advantage of having no furniture to move.

It can start clean. It can build every process with the question: “Could an agent do the first pass on this?” It can document from day one. It can make every data object usable. It can design human review points before errors become disasters. It can build feedback loops before the company calcifies.

This is why the “only 1,000 companies” idea matters. It creates urgency, but it also creates permission.

The field is empty because most people are still mistaking AI adoption for AI architecture.

They think the game is prompt engineering. It’s not.

They think the game is picking the right model. It’s not.

They think the game is adding a chatbot to the website. It’s definitely not.

The game is redesigning the company so intelligence can flow through it.

There is a practical playbook here.

First, pick a narrow workflow with obvious economic value. Don’t start with “make the company AI-native.” That’s too abstract. Start with support resolution, outbound prospecting, onboarding, claims intake, document review, renewal management, or reporting. Choose a workflow where volume is high, rules exist, and humans are currently doing too much coordination.

Second, map the workflow like a machine. What triggers it? What data is needed? What decisions happen? Which decisions are reversible? Which require approval? What does success look like? Where do errors happen? What does a human know that the system does not?

Third, structure the knowledge. If the agent needs a policy, write the policy. If it needs pricing rules, make them explicit. If it needs customer history, clean the customer object. If it needs examples, create examples. If it needs tone, define tone. This is where most teams quit, because it feels like documentation. It is not documentation. It is infrastructure.

Fourth, put agents in the workflow with boundaries. Let them draft, classify, recommend, enrich, summarize, and prepare. Give them actions only where the risk is understood. Require approval where judgment matters. Log everything. Review outputs. Track quality. Improve the system.

Fifth, measure the business impact. Not “hours saved” in some fake spreadsheet. Measure resolution time, conversion rate, gross margin, revenue per employee, error rate, customer satisfaction, sales velocity, onboarding time, renewal rate. AI-native companies should show up in the numbers.

That is the part I’m most interested in. In a few years, “AI-native” will not be a vibe. It will be visible in the metrics.

Revenue per employee will look different.

Gross margins will look different.

Speed of execution will look different.

Customer experience will look different.

The best companies will feel strangely responsive, like the whole business is awake. Customers will get answers faster. Sales teams will follow up with better timing. Ops problems will surface earlier. Founders will see the business more clearly. Managers will spend less time asking for updates and more time improving the system.

The company will have less drag.

That is the real advantage.

Not AI as a party trick. AI as organizational metabolism.

So yes, there are probably only around 1,000 truly AI-native companies on earth doing meaningful revenue today.

And that should make you want to build one immediately.

Because when a market is loud, people assume it is mature. But noise is not maturity. Noise is usually what happens right before the real builders figure out what matters.

Right now, everyone is loud about AI.

Very few companies are structurally ready for it.

That is the gap.

That is the opportunity.

The next great companies will be the ones whose data, workflows, policies, and teams are rebuilt around agents from the inside out. They will look smaller than they should. They will move faster than makes sense. They will have fewer employees doing more valuable work. They will turn messy services into scalable systems. They will make incumbents look like they are running Windows 95 with a nicer login screen.

Most people are still asking, “How do I use AI at work?”

The better question is, “How do I build a company AI can work inside?”

That question is the doorway.

And right now, almost nobody has walked through it.

Despite what you read, the field is empty. Maybe consider sharing this with a friend.

I’m rooting for you.

  • Greg Isenberg

Note: I don't know about it often because we're swamped, but my firm LCA is world class at helping companies go AI native. Because they do really good work. We work with Fortune 500s and your favorite brands on building AI native products and AI native orgs.

If your company wants to go AI native, consider contacting them up here.

And if you're looking for startup ideas, consider grabbing some validated ideas you can build with AI at Ideabrowser.com

关于什么才叫 AI 原生,这里把真相说清楚。

https://1543b7c1.click.convertkit-mail4.com/27u6n9m9x6uoh8zozwpc3hg993d8ncghnog2w/6qheh8hlegekl2ho/aHR0cHM6Ly9sYXRlY2hlY2tvdXQuYWdlbmN5

现在到处都有人说自己是 AI 原生,通常意思不过是团队里有人开着一个 ChatGPT 标签页,市场负责人做了一个名叫 Brand Voice Assistant 的自定义 GPT。

挺可爱。

也确实有用。

但这不叫 AI 原生。

大家一直忽略的,正是这里的区别。AI 原生公司,不是使用 AI 的公司。它是那种已经被重新搭建过,能让 AI 真正在内部运转起来的公司。它的业务结构、文档、权限和观测方式,都已经整理成智能体能理解的样子。它让自己对机器而言是清晰可读的。

这话听起来有点无聊,直到你意识到,这可能会是未来十年里最大的商业优势之一。

因为绝大多数公司,对机器来说都不可读。很多公司,甚至对自己的员工都谈不上清晰可读。

CRM 里写的是一套。Slack 线程里说的是另一套。真正的客户历史躺在某个人的邮箱里。定价逻辑放在一个名叫 Final_v7_NEW 的表格里。退款政策在一篇谁也不太信任的 Notion 文档里。销售流程是 去找 Sarah 聊,她知道企业客户怎么做。入职流程要经过五个工具、三个人、两个审批步骤,外加一个创始人,直到今天还会被随机边缘情况拉进去,因为从来没人把判断沉淀成系统。

然后这些公司会问,为什么 AI 不能替我们做更多事?

因为 AI 不能靠感觉运转。

它没法经营一种真相分散在人员、工具、习惯、例外和组织记忆里的公司。智能体需要上下文。需要干净的输入。需要规则。需要访问权限。需要边界。需要知道什么才算好。需要知道什么时候该行动,什么时候该发问。

过去二十年里,大多数公司一直在买软件,却没有花二十年去设计一套操作系统。它们拥有的是一堆工具,不是一台机器。

这就是为什么,真正称得上 AI 原生的公司,数量可能少得惊人。我的猜测是,全球年经常性收入超过 500 万美元、并且在真正意义上做到了 AI 原生的公司,也许只有 1000 家。不是那种 我们用了 copilot。也不是 我们把一些邮件自动化了。我的意思是,那些核心工作流本来就是为智能体执行、人类监督而设计的公司。

也许这个数字是 500。也许是 2000。具体多少并没有结论本身重要。

因为现在,几乎没人真正做到这件事。

尽管噪音铺天盖地,尽管融资消息一波接一波,尽管每一家 SaaS 官网都把 agentic 这个词重写进去了,这片赛道实际上几乎还是空的。

第一个有用的区分是这个。AI 辅助型公司,把 AI 用在边缘。AI 原生公司,重做的是核心。

AI 辅助型公司会问,哪里能加上 AI 来省时间?

AI 原生公司会问,如果前 80% 的工作由智能体完成,那这个工作流本来该怎么存在?

第二个问题会改变一切。

拿客服来说。在普通公司里,一张工单进来后,由人工先阅读,再去搜索上下文、核对账户、回忆政策、写回复,可能还要问工程团队,可能要升级处理,也可能忘了正确标记原因。它本质上是一个由人驱动、四周零星撒着软件的流程。

在 AI 原生公司里,这张工单会进入一个智能体能够理解的系统。智能体会读取客户历史,检查套餐限制,查看过往工单,检索政策,起草回复,建议动作,要么直接解决问题,要么把它交给人工,并明确指出为什么这个点需要人来判断。人工不再是搜索引擎、路由器和文案写手。人工负责的是审查模糊性。

这是两种完全不同的公司。

把同样的逻辑套到销售上也是一样。旧方式是 SDR 自己去 Google 搜潜在客户,猜测怎样个性化,写一封平庸的邮件,因为经理催才去更新 Salesforce,然后把半套上下文交给 AE。AI 原生的做法则是,让智能体监控购买信号、补全账户信息、绘制利益相关方图谱、起草触达内容、学习哪些切入点转化更高、自动更新 CRM,并给销售人员一场已经准备好的对话,而不是一张空白纸。

法务也是这样。招聘也是这样。财务也是这样。理赔处理也是这样。客户管理也是这样。研究工作也是这样。

这个模式会在所有地方反复出现。智能体做结构化的工作,人类处理品味、信任、判断、关系和例外。

这不是一点点生产力提升。

这是一种新的管理模型。

过去一百年里,公司扩张的默认方式是多招人、设部门、加管理层、买软件,再发明流程去协调这团混乱。每多一层,解决一个问题,又制造出三个新问题。公司变大了,也变慢了。会议更多。交接更多。谁负责这个的追问更多。内部重力更强。

AI 原生公司会以不同方式扩张。

它们不会像传统公司外挂一个聊天机器人。它们会像一小支团队在运作一整支由专业智能体组成的大舰队。一个 12 人的公司,能做过去需要 80 人才能做的事。一个 40 人的公司,能和 400 人的老牌对手竞争。人均收入会变成最清楚的信号之一,说明这家公司是否真的为新时代而建。

https://1543b7c1.click.convertkit-mail4.com/27u6n9m9x6uoh8zozwpc3hg993d8ncghnog2w/6qheh8hlegekl2ho/aHR0cHM6Ly9sYXRlY2hlY2tvdXQuYWdlbmN5

很多人听到这里就会开始防御。他们一听到 智能体做工作,就以为这意味着人要消失了。

重点不在这里。

更准确的理解是,现代公司长期把人的智力浪费在机器形状的任务上。我们让人去在不同工具之间搬运信息。让人去记流程。让人去翻文件夹。让人去重写同样的邮件。让人去追审批。让人去总结电话、填写字段、复制数据、分类请求,再去问别的人某个东西放在哪里。

很多工作,其实根本不是真正的工作。

它只是组织摩擦贴着一撮假胡子。

AI 原生公司会把这些摩擦剥掉。

它们保留真正重要的人类部分,把那些只是因为过去的软件太笨、无法理解上下文才存在的部分自动化掉。这意味着人的角色不是更不重要,而是杠杆更大。一个优秀的运营,能监督十条工作流。一个优秀的销售,能去完成那些由智能体提前铺好的对话。一个优秀的客服负责人,会变成升级逻辑和客户体验质量的设计者。一个优秀的创始人,会成为公司思考方式的架构师。

创始人这一点尤其重要。

AI 原生的创始人,不只是做产品的人。他们是在设计一家能被智能体理解的公司。

这意味着,创始人必须把隐含的东西讲明白。我们的退款政策是什么?什么情况下可以破例?什么样的线索算合格?面对愤怒的客户要用什么语气?哪些事情绝不能自动化?哪些动作必须审批?什么叫一个好答案?什么叫一个危险答案?哪个数据源才是真正的事实来源?两个系统打架时怎么办?智能体该如何从纠正中学习?

这些不性感的工作,才会把真正的 AI 原生公司和 LinkedIn 上的表演区分开。

人人都想要魔法。

没人想打扫厨房。

可厨房就是公司本身。

最后赢的公司,会以异乎寻常的认真去做那些无聊但基础的事。它们会清洗数据。会整理工作流。会编写智能体可读的 SOP。会建立权限和审计轨迹。会把客户记录结构化,不让上下文被困在人脑里。会建立评估闭环,让智能体随着时间变得更好。会把每一次重复决策都变成一套决策系统。

然后,一旦底层运作层干净了,它们就会快得离谱。

所以,AI 原生其实不是一个技术标签。

它是一个组织标签。

一家公司可以用上世界上最好的模型,但在结构上依然无法从中获益。如果智能体还得猜真相藏在哪儿,如果它拿不到正确的系统权限,如果没人定义决策规则,如果每个工作流都依赖于某个人脑子里埋着的例外,那 AI 终究只会是个玩具。它会起草东西。会总结东西。会让人感觉自己更快了。但它不会改变这门生意。

真正的变化,会发生在智能体成为公司运作织体的一部分之后。

想象一家真正 AI 原生的家政服务公司。每一个进入系统的请求都会被自动分类。每一份报价都从结构化的定价规则中生成。每位技师在到达前都会收到工作摘要。每位客户都会得到主动更新。每一次评价请求都会被个性化处理。每一次爽约都会自动触发补救工作流。每一种运营模式都会反馈回派单、定价和人员配置里。

再想象一家保险经纪公司。智能体会收集文件、预审提交内容、比较保单、标出缺失细节、起草给客户的解释、准备续保选项,并监控账户变化。人类负责建立信任和处理复杂情况,但下面那套机器,整天都在做重复性的智力劳动。

再想象一家招聘公司。智能体会搜寻候选人、补全资料、对照岗位要求进行比较、起草触达内容、总结面试、核查推荐信、更新流程管道,并在候选人异常强时提醒人工。招聘顾问不再是数据清洁工,而成了关系成交者。

这些都不是科幻公司。

它们只是普通行业里,把内脏重新搭建过的公司。

这正是人们低估的机会。那些显眼的 AI 公司已经很拥挤了。通用 copilot、写作工具、会议机器人、代码助手、图像生成器、客服包装层。都可以是不错的生意,但也都很显眼。更不显眼的机会,是进入那些无聊、赚钱、分散的行业,围绕智能体把它们的操作模型重新搭起来。

AI 原生代理公司。AI 原生经纪公司。AI 原生类法律服务。AI 原生会计事务所。AI 原生合规服务。AI 原生医疗行政公司。AI 原生房地产运营。AI 原生教育服务。AI 原生物流协调方。AI 原生 BPO,而且看起来根本不像 BPO。

这个世界上有太多行业,客户为结果付费,而服务方的成本结构主要是重复性的知识劳动。

这正是 AI 原生公司最容易切进去的地方。

最好的机会,起初看起来未必像软件公司。有些会更像服务型企业,只是里面藏着软件级的利润率。这会让投资人和竞争对手都看不懂,而这正是好事。当所有人都在寻找下一个 SaaS 仪表盘时,真正的赢家可能正在悄悄打造 AI 原生服务公司,用远低得多的劳动强度,交付更好的结果。

这话很有 Greg 的风格,但我确实觉得,下一波互联网生意,看起来可能不像创业公司,反而更像一台台奇怪的小型印钞机。

小团队。窄市场。专有工作流。高自动化。高信任。明确的客户痛点。无聊的品类。漂亮的利润率。

从外面看,不性感。

从银行账户里看,性感得很。

而且因为这些公司从第一天起就是按另一种方式建的,老玩家会很难复制。老公司不可能靠宣布一个 AI 计划,就变成 AI 原生。这就像你想把一艘邮轮改成快艇,只靠换一个新方向盘。

难点不在于能不能接触到模型。

大家都能接触到。

真正难的是,老公司全身都是旧流程债务。它们的数据很乱。政策彼此冲突。团队各守地盘。工作流是围绕人头堆出来的。软件栈像胶带和季度规划仪式硬缝起来的一样。它们的操作系统默认把人类当成信息处理器。

新公司最大的优势,是根本没有家具要搬。

它可以从一开始就是干净的。它可以在设计每个流程时都先问,这件事能不能先让智能体跑第一遍?它可以从第一天开始就做文档。可以让每个数据对象都可用。可以在人为失误变成灾难之前,就先设计好人工审核点。可以在公司僵化之前,就先建好反馈闭环。

这就是为什么 只有 1000 家公司 这个想法重要。它带来了紧迫感,也带来了许可感。

这片赛道之所以空着,是因为大多数人仍然把 AI 采用误认为 AI 架构。

他们以为游戏的关键是提示词工程。

不是。

他们以为关键是选对模型。

也不是。

他们以为关键是给网站加一个聊天机器人。

那更不是。

真正的游戏,是把公司重新设计成一个能让智能流经其中的系统。

这里其实有一套很实际的打法。

第一步,挑一个足够窄、经济价值又足够明显的工作流。不要一上来就想着 让整个公司变成 AI 原生。那太抽象。可以从客服处理、外呼开发、客户入职、理赔录入、文档审查、续约管理或者报表开始。选择那些量大、规则存在、而且现在人花了太多精力在协调上的流程。

第二步,把这个工作流像一台机器一样拆开来看。是什么触发它?需要哪些数据?中间有哪些决策?哪些决策是可逆的?哪些必须审批?成功长什么样?错误通常出在哪儿?人知道、系统却不知道的是什么?

第三步,把知识结构化。如果智能体需要一条政策,那就把政策写出来。如果它需要定价规则,那就把规则讲明白。如果它需要客户历史,那就把客户对象清洗干净。如果它需要样例,那就创造样例。如果它需要语气,那就定义语气。大多数团队都会在这里放弃,因为这看起来像文档工作。其实不是。这是基础设施。

第四步,把智能体放进工作流里,但要带着边界。让它们去起草、分类、建议、补全、总结和准备。只有在风险可控的地方才给它们动作权限。在判断重要的地方要求审批。把一切都记下来。审查输出。跟踪质量。持续改进系统。

第五步,衡量业务影响。不要拿某张假模假式的表格去算 节省了多少小时。要量真正的指标,比如处理时长、转化率、毛利率、人均收入、错误率、客户满意度、销售推进速度、入职时间、续约率。AI 原生公司,应该在数字上看得出来。

这是我最感兴趣的部分。再过几年,AI 原生就不会再是一种感觉。

它会直接体现在指标里。

人均收入会不一样。

毛利率会不一样。

执行速度会不一样。

客户体验会不一样。

最好的公司会显得异常敏捷,像整家公司都是醒着的。客户会更快拿到答案。销售团队会以更好的时机跟进。运营问题会更早浮现。创始人会更清楚地看见业务。管理者会少花时间催进度,多花时间优化系统。

整家公司会少很多阻力。

这才是真正的优势。

不是把 AI 当派对把戏。

而是把 AI 变成组织的新陈代谢。

所以,是的,如今全球真正做到 AI 原生、而且已经有实质收入的公司,大概确实只有 1000 家左右。

而这件事,应该会让你立刻想去建一家。

因为当一个市场足够喧闹时,人们会误以为它已经成熟了。但噪音不等于成熟。通常,噪音恰恰出现在真正的建设者快要弄清楚什么最重要之前。

现在,所有人都在高声谈 AI。

真正从结构上准备好迎接它的公司,少得可怜。

这就是空档。

这就是机会。

下一批伟大的公司,会是那些从内到外围绕智能体重建了数据、工作流、政策和团队的公司。它们看起来会比应有规模更小。它们的速度会快得不合常理。它们会用更少的人做更有价值的工作。它们会把混乱的服务变成可扩展的系统。它们会让老牌公司看起来像是在运行 Windows 95,只不过登录界面更好看一点。

大多数人还在问,怎样把 AI 用到工作里?

更好的问题是,怎样建一家公司,让 AI 能在里面工作?

这个问题,就是那道门。

而此时此刻,几乎还没有人真正走进去。

不管你读到的是什么,这片赛道其实是空的。也许可以把这篇文章分享给一个朋友。

我真心希望你成功。

  • Greg Isenberg

注:我平时不太常提这件事,因为我们确实忙不过来,但我的公司 LCA 在帮助企业走向 AI 原生这件事上,水准是一流的。原因也很简单,他们做得真的很好。我们和《财富》500 强公司以及你熟悉的品牌合作,帮助它们打造 AI 原生产品和 AI 原生组织。

如果你的公司也想走向 AI 原生,可以考虑通过上面的链接联系他们。

如果你在找创业点子,也可以去 Ideabrowser.com 看看那些已经验证过、可以用 AI 来做的点子。

The truth about being AI native. I'll break it down.

https://1543b7c1.click.convertkit-mail4.com/27u6n9m9x6uoh8zozwpc3hg993d8ncghnog2w/6qheh8hlegekl2ho/aHR0cHM6Ly9sYXRlY2hlY2tvdXQuYWdlbmN5

Everyone is walking around saying they’re “AI-native” now, which mostly means someone on the team has a ChatGPT tab open and the head of marketing made a custom GPT called “Brand Voice Assistant.”

Cute.

Useful, even.

But not AI-native.

That’s the difference people keep missing. An AI-native company is not a company that uses AI. It is a company that has been rebuilt so AI can actually operate inside it. The business is structured, documented, permissioned, and instrumented in a way that agents can understand. The company has made itself legible to machines.

That sounds boring until you realize it might be the single biggest business advantage of the next decade.

Because most companies are not legible to machines. Most companies are barely legible to their own employees.

The CRM says one thing. The Slack thread says another. The real customer history lives in someone’s inbox. The pricing logic is in a spreadsheet called “Final_v7_NEW.” The refund policy is in a Notion doc nobody trusts. The sales process is “talk to Sarah, she knows how we do enterprise.” The onboarding flow is five tools, three humans, two approval steps, and one founder who still gets pulled into random edge cases because nobody ever turned judgment into a system.

Then these companies ask, “Why can’t AI do more for us?”

Because AI cannot run on vibes.

It can’t operate a business where the truth is scattered across people, tools, habits, exceptions, and institutional memory. Agents need context. They need clean inputs. They need rules. They need access. They need boundaries. They need to know what good looks like. They need to know when to act and when to ask.

Most companies have spent twenty years buying software, but they have not spent twenty years designing an operating system. They have a pile of tools, not a machine.

That is why the number of truly AI-native companies is probably shockingly small. My guess is there are maybe 1,000 companies on earth doing $5M+ ARR that are actually AI-native in the real sense. Not “we use copilots.” Not “we automated some emails.” I mean companies where the core workflows are designed for agents to execute and humans to supervise.

Maybe the number is 500. Maybe it’s 2,000. The exact number matters less than the conclusion.

Almost nobody is doing this yet.

Despite all the noise, despite all the funding announcements, despite every SaaS homepage being rewritten with the word “agentic,” the field is basically empty.

The first useful distinction is this: AI-assisted companies use AI at the edges. AI-native companies redesign the center.

An AI-assisted company asks, “Where can we add AI to save time?”

An AI-native company asks, “How should this workflow exist if agents are doing the first 80%?”

That second question changes everything.

Take customer support. In a normal company, a support ticket arrives, a human reads it, searches for context, checks the account, remembers policy, writes a response, maybe asks engineering, maybe escalates, maybe forgets to tag the reason properly. It’s a human-driven process with software sprinkled around it.

In an AI-native company, the ticket enters a system an agent can understand. The agent reads the customer history, checks plan limits, reviews prior tickets, consults policy, drafts a response, recommends an action, and either resolves the issue or sends it to a human with the exact reason it needs judgment. The human is not the search engine, router, and copywriter. The human is the reviewer of ambiguity.

That is a very different company.

Now apply the same logic to sales. The old way is an SDR Googling a prospect, guessing at personalization, writing a mediocre email, updating Salesforce because their manager nags them, then passing half-context to an AE. The AI-native way is an agent that monitors buying signals, enriches accounts, maps stakeholders, drafts outreach, learns which hooks convert, updates the CRM automatically, and gives the human seller a prepared conversation instead of a blank page.

Legal is the same. Recruiting is the same. Finance is the same. Claims processing is the same. Account management is the same. Research is the same.

The pattern repeats everywhere: agents do the structured work, humans handle taste, trust, judgment, relationships, and exceptions.

That is not a small productivity improvement. That is a new management model.

For the last hundred years, the default way to scale a company was to hire more people, create departments, add managers, buy software, and invent processes to coordinate the mess. Every new layer solved one problem and created three more. The company got bigger, but it also got slower. More meetings. More handoffs. More “who owns this?” More internal gravity.

AI-native companies will scale differently.

They will not look like traditional companies with a chatbot bolted on. They will look like small teams operating large fleets of specialized agents. A 12-person company will do what used to require 80 people. A 40-person company will compete with a 400-person incumbent. Revenue per employee will become one of the clearest signals that a company is actually built for the new era.

https://1543b7c1.click.convertkit-mail4.com/27u6n9m9x6uoh8zozwpc3hg993d8ncghnog2w/6qheh8hlegekl2ho/aHR0cHM6Ly9sYXRlY2hlY2tvdXQuYWdlbmN5

This is where a lot of people get defensive. They hear “agents do the work” and assume it means humans disappear.

That’s not the point.

The better way to think about it is that modern companies have been wasting human intelligence on machine-shaped tasks. We use humans to move information between tools. We use humans to remember process. We use humans to search folders. We use humans to rewrite the same email. We use humans to chase approvals. We use humans to summarize calls, fill in fields, copy data, classify requests, and ask other humans where something lives.

A lot of work is not really “work.” It is organizational friction wearing a fake mustache.

AI-native companies strip that out.

They preserve the human parts that matter and automate the parts that only existed because software was too dumb to understand context. That means the human role becomes more leveraged, not less important. A great operator becomes the supervisor of ten workflows. A great salesperson becomes the closer of conversations agents helped create. A great support lead becomes the designer of escalation logic and customer experience quality. A great founder becomes the architect of how the company thinks.

That founder point is important.

The AI-native founder is not just building a product. They are designing a company that can be understood by agents.

That means the founder has to make the implicit explicit. What is our refund policy? When do we break it? What makes a lead qualified? What tone do we use with angry customers? What should never be automated? Which actions require approval? What is a good answer? What is a dangerous answer? Which data source is the source of truth? What do we do when two systems disagree? How does the agent learn from corrections?

This is the unsexy work that will separate real AI-native companies from LinkedIn theater.

Everyone wants the magic. Nobody wants to clean the kitchen.

But the kitchen is the company.

The companies that win will do boring, foundational things with unusual seriousness. They will clean their data. They will document their workflows. They will create agent-readable SOPs. They will build permissions and audit trails. They will structure customer records so context is not trapped in human memory. They will create evaluation loops so agents get better over time. They will turn every repeated decision into a decision system.

Then, once the operating layer is clean, they will move absurdly fast.

This is why “AI-native” is not really a tech label. It is an organizational label.

A company can use the best models in the world and still be structurally incapable of benefiting from them. If the agent has to guess where the truth lives, if it cannot access the right systems, if nobody has defined the decision rules, if every workflow depends on exceptions buried in someone’s head, then the AI will remain a toy. It will draft things. It will summarize things. It will make people feel faster. But it will not transform the business.

The transformation happens when agents become part of the operating fabric.

Imagine a home services company that is truly AI-native. Every inbound request is classified automatically. Every quote is generated from structured pricing rules. Every technician gets a job summary before arrival. Every customer receives proactive updates. Every review request is personalized. Every missed appointment creates an automatic recovery workflow. Every operational pattern feeds back into routing, pricing, and staffing.

Now imagine an insurance brokerage. Agents gather documents, pre-check submissions, compare policies, flag missing details, draft client explanations, prepare renewal options, and monitor accounts for changes. Humans build trust and handle complexity, but the machinery underneath is doing the repetitive intelligence work all day.

Now imagine a recruiting firm. Agents source candidates, enrich profiles, compare against role requirements, draft outreach, summarize interviews, check references, update pipelines, and alert humans when a candidate is unusually strong. The recruiter stops being a data janitor and becomes a relationship closer.

These are not sci-fi companies. These are normal businesses with the guts rebuilt.

That’s the opportunity people are underestimating. The obvious AI companies are crowded. Horizontal copilots, writing tools, meeting bots, code assistants, image generators, customer support wrappers. Fine businesses, but obvious. The less obvious opportunity is taking boring, profitable, fragmented industries and rebuilding the operating model around agents.

AI-native agencies. AI-native brokerages. AI-native law-adjacent services. AI-native accounting firms. AI-native compliance shops. AI-native healthcare admin companies. AI-native real estate operations. AI-native education services. AI-native logistics coordinators. AI-native BPOs that don’t look like BPOs.

The world is full of industries where customers pay for outcomes, but the provider’s cost structure is mostly repetitive knowledge work. That is exactly where AI-native companies can wedge in.

The best opportunities will not always look like software companies at first. Some will look like services businesses with software margins hiding inside. That will confuse investors and competitors, which is useful. While everyone else is looking for the next SaaS dashboard, the real winners may be quietly building AI-native service companies that produce better outcomes with dramatically lower labor intensity.

This is a very Greg thing to say, but I think the next wave of internet businesses may look less like “startups” and more like weird little money machines.

Small teams. Narrow markets. Proprietary workflows. High automation. High trust. Clear customer pain. Boring category. Beautiful margins.

Not sexy from the outside.

Extremely sexy in the bank account.

And because these companies are built differently from day one, incumbents will struggle to copy them. An old company cannot become AI-native by announcing an AI initiative. That is like trying to turn a cruise ship into a speedboat by buying a new steering wheel.

The hard part is not access to models. Everyone has that.

The hard part is that incumbents are full of old process debt. Their data is messy. Their policies conflict. Their teams protect turf. Their workflows were built around headcount. Their software stack is stitched together with duct tape and quarterly planning rituals. Their operating system assumes humans are the default processors of information.

A new company has the advantage of having no furniture to move.

It can start clean. It can build every process with the question: “Could an agent do the first pass on this?” It can document from day one. It can make every data object usable. It can design human review points before errors become disasters. It can build feedback loops before the company calcifies.

This is why the “only 1,000 companies” idea matters. It creates urgency, but it also creates permission.

The field is empty because most people are still mistaking AI adoption for AI architecture.

They think the game is prompt engineering. It’s not.

They think the game is picking the right model. It’s not.

They think the game is adding a chatbot to the website. It’s definitely not.

The game is redesigning the company so intelligence can flow through it.

There is a practical playbook here.

First, pick a narrow workflow with obvious economic value. Don’t start with “make the company AI-native.” That’s too abstract. Start with support resolution, outbound prospecting, onboarding, claims intake, document review, renewal management, or reporting. Choose a workflow where volume is high, rules exist, and humans are currently doing too much coordination.

Second, map the workflow like a machine. What triggers it? What data is needed? What decisions happen? Which decisions are reversible? Which require approval? What does success look like? Where do errors happen? What does a human know that the system does not?

Third, structure the knowledge. If the agent needs a policy, write the policy. If it needs pricing rules, make them explicit. If it needs customer history, clean the customer object. If it needs examples, create examples. If it needs tone, define tone. This is where most teams quit, because it feels like documentation. It is not documentation. It is infrastructure.

Fourth, put agents in the workflow with boundaries. Let them draft, classify, recommend, enrich, summarize, and prepare. Give them actions only where the risk is understood. Require approval where judgment matters. Log everything. Review outputs. Track quality. Improve the system.

Fifth, measure the business impact. Not “hours saved” in some fake spreadsheet. Measure resolution time, conversion rate, gross margin, revenue per employee, error rate, customer satisfaction, sales velocity, onboarding time, renewal rate. AI-native companies should show up in the numbers.

That is the part I’m most interested in. In a few years, “AI-native” will not be a vibe. It will be visible in the metrics.

Revenue per employee will look different.

Gross margins will look different.

Speed of execution will look different.

Customer experience will look different.

The best companies will feel strangely responsive, like the whole business is awake. Customers will get answers faster. Sales teams will follow up with better timing. Ops problems will surface earlier. Founders will see the business more clearly. Managers will spend less time asking for updates and more time improving the system.

The company will have less drag.

That is the real advantage.

Not AI as a party trick. AI as organizational metabolism.

So yes, there are probably only around 1,000 truly AI-native companies on earth doing meaningful revenue today.

And that should make you want to build one immediately.

Because when a market is loud, people assume it is mature. But noise is not maturity. Noise is usually what happens right before the real builders figure out what matters.

Right now, everyone is loud about AI.

Very few companies are structurally ready for it.

That is the gap.

That is the opportunity.

The next great companies will be the ones whose data, workflows, policies, and teams are rebuilt around agents from the inside out. They will look smaller than they should. They will move faster than makes sense. They will have fewer employees doing more valuable work. They will turn messy services into scalable systems. They will make incumbents look like they are running Windows 95 with a nicer login screen.

Most people are still asking, “How do I use AI at work?”

The better question is, “How do I build a company AI can work inside?”

That question is the doorway.

And right now, almost nobody has walked through it.

Despite what you read, the field is empty. Maybe consider sharing this with a friend.

I’m rooting for you.

  • Greg Isenberg

Note: I don't know about it often because we're swamped, but my firm LCA is world class at helping companies go AI native. Because they do really good work. We work with Fortune 500s and your favorite brands on building AI native products and AI native orgs.

If your company wants to go AI native, consider contacting them up here.

And if you're looking for startup ideas, consider grabbing some validated ideas you can build with AI at Ideabrowser.com

📋 讨论归档

讨论进行中…