SaaStr拆解无头CRM与AI代理获客:5条可执行策略
HubSpot Is Refounding as the “Customer Harness Company.” Here’s What That Means for Us, Right Now, in November 2026
直接给出了B2B SaaS在AI时代的GTM转型路径,从CRM接入方式到营销自动化重构均有具体参数和取舍逻辑,读者可据此调整产品架构与销售话术。
Yesterday Brian Halligan said he and Dharmesh Shah are refounding HubSpot as the “Customer Harness Company.”
昨天,Brian Halligan 表示他和 Dharmesh Shah 正在将 HubSpot 重新创立为“客户驾驭公司(Customer Harness Company)。”
I'm back as CEO of @HubSpot today.@dharmesh and I are completely re-founding the company. Its day 1. We're now the Customer Harness Company.
我今天以 @HubSpot CEO 的身份回归。@dharmesh 和我正在彻底重塑这家公司。这是它的 Day 1。我们现在是“客户驾驭公司”。
In the next few days, I'll post about why I'm coming back and what my plans are. LFG!
在接下来的几天里,我会发帖说明我回归的原因以及我的计划。冲啊!(LFG!)
— Brian Halligan (@bhalligan) November 12, 2026
—— Brian Halligan (@bhalligan) 2026年11月12日
That sounds right to me, and it’s super exciting. HubSpot has made a big platform call like this before. They named inbound marketing as a category and then owned it for a decade.
这听起来很对,而且令人兴奋不已。HubSpot 以前也曾做出过类似的重大平台定位声明。他们定义了“入站营销”这一类别,并在此后十年中主导了该领域。
But what does “Customer Harness” mean in practice? Right now at least, we’ll all have different takes. We’re all at different stages of our agent journeys, in general and in GTM specifically. Some teams are piloting their first SDR agent. Some have rebuilt their whole revenue org around agents. Most are somewhere in between.
但在实践中,“客户驾驭”意味着什么?至少在目前,我们会有不同的看法。我们在代理旅程(agent journeys)上处于不同阶段,无论是在整体层面还是具体在 GTM(Go-To-Market)层面。有些团队正在试点他们的第一个 SDR 代理。有些团队已经围绕代理重构了整个营收组织。大多数团队则介于两者之间。
So this is what it means for us at SaaStr, with 3 humans and 20+ AI agents in production. Some of it will change in six months.
那么,这对我们 SaaStr 意味着什么呢?我们有 3 名人类员工和 20 多个在生产环境中运行的 AI 代理。其中一些情况在六个月后会发生变化。
#1. We Are 100% Headless on Our CRM and Never Going Back
#1. 我们的 CRM 完全无头化,且永不回头
No one on our human team logs into our CRM anymore. Including me.
我们的人类团队中再也没有人登录我们的 CRM 了。包括我在内。
10K, our AI VP of Revenue, and our other agents come in through MCP and the API. They read from it, write to it, and keep it updated. The CRM still matters a lot. It’s our system of record. We just don’t go there.
10K、我们的 AI 营收副总裁以及其他代理通过 MCP 和 API 接入。它们从 CRM 读取数据、写入数据并保持其更新。CRM 仍然非常重要,它是我们的记录系统(system of record)。只是我们不再直接访问它。
For 20+ years, B2B software was priced, designed, and sold around the human who logs in. Seats, dashboards, login frequency as a health score, adoption as the metric your CSM chased every quarter. For us, that model is over.
在过去 20 多年里,B2B 软件的价格、设计和销售都是围绕登录该软件的人类展开的:席位、仪表盘、登录频率作为健康指标、采用率作为客户成功经理(CSM)每个季度追逐的指标。对我们来说,这种模式已经终结。
We will never log into B2B software again. Our agents will, and we’ll talk to our agents.
我们将永远不会再次登录 B2B 软件。我们的代理会这么做,而我们会与我们的代理沟通。
If you sell B2B software, it’s worth asking how much of your product’s value sits in the UI versus in the data and actions behind it. For a growing share of customers, the UI part is headed to zero.
如果你销售 B2B 软件,值得思考的是你的产品价值有多少体现在 UI 上,又有多少体现在背后的数据和操作上。对于越来越多的客户而言,UI 部分的比重正趋向于零。
#2. We Moved Off Traditional Marketing Automation Entirely in the Last 60 Days
#2. 我们在过去 60 天内完全脱离了传统营销自动化
We still do a lot of marketing. We just don’t use marketing automation software to do it anymore.
我们仍然进行大量的营销活动。只是我们不再使用营销自动化软件来执行这些活动了。
Our list is 450,000+ people. We send millions of emails, plus everything around our events, content, and products. Over the last 60 days, all of that moved to being run almost entirely by agents.
我们的列表包含超过 45 万人。我们发送数百万封电子邮件,以及围绕我们的活动、内容和产品开展的所有相关工作。在过去 60 天里,所有这些工作几乎完全由代理运行。
What changed:
发生的变化:
- No more templates. 10K built all our email and promo templates, and rebuilds them dynamically for each send.
- Real personalization at scale. Many of our emails are now 100% personalized to each recipient, written for that person based on what we know about them, across a 450k list. This goes far past merge fields.
- No journey builders. The drag-and-drop workflows, branching logic, and hand-maintained nurture tracks are gone.
- 不再有固定模板。10K 构建了所有邮件和推广模板,并为每次发送动态重建它们。
- 实现大规模的真实个性化。我们现在有100%的邮件都是针对每位收件人完全个性化的,基于我们对他们的了解,为特定的人撰写内容,覆盖45万人的列表。这远远超越了简单的合并字段。
- 没有旅程构建器。拖拽式工作流、分支逻辑和手动维护的培养路径都已消失。
Consent is incredibly important, and so is deliverability. At our volume you can’t be sloppy on either one. But you can get both headless from a number of top-tier vendors now, as services you call via API. They no longer lock you into a marketing automation suite.
同意(Consent)至关重要,送达率也同样重要。在如此大的发送量下,你在这两方面都不能马虎。但现在你可以从多家顶级供应商那里以API调用的服务形式获得无头(headless)的解决方案,从而同时满足这两点要求。它们不再将你锁定在营销自动化套件中。
I don’t think a lot of vendors have priced this in yet. The old lock-in was that your templates, workflows, list logic, and sending reputation all lived in one place. Once an agent owns the templates and logic, and sending is an API, most of that lock-in goes away.
我认为许多供应商还没有充分考虑到这一点。过去的锁定效应在于你的模板、工作流、列表逻辑和发送声誉都集中在一个地方。一旦代理商拥有模板和逻辑,而发送通过API进行,大部分锁定效应就会消失。
We will never buy marketing automation software again. It was built for humans to operate, and we don’t have humans operating it.
我们永远不会再购买营销自动化软件了。它是为人类操作而设计的,而我们并没有人类来操作它。
#3. Claude, ChatGPT, and Slack Are Great, but Our Main Surface Is 10K
#3. Claude、ChatGPT 和 Slack 都很棒,但我们的主要界面是 10K
Everyone has a strong view on the “killer interface” for agents right now. I don’t know which one wins, and I’d be skeptical of anyone who says they do this early.
目前每个人对代理(agents)的“杀手级界面”都有强烈的看法。我不知道哪个会胜出,而且我会对那些声称已经确定赢家的人持怀疑态度。
For us, running GTM inside our agents, using their own custom interfaces, is still easier. A big reason is that it’s multiplayer: our humans and agents all work in the same place on the same context. Claude, ChatGPT, and Slack are great surfaces for GTM work. For us, at least for now, they won’t be the primary one.
对我们来说,在我们的代理内部运行GTM(Go-To-Market),使用他们自己的自定义界面仍然更容易。一个重要原因是这是多人协作:我们的人类和代理都在同一个地方、基于相同的上下文工作。Claude、ChatGPT 和 Slack 是进行 GTM 工作的优秀界面。但对我们而言,至少目前它们不会是主要的界面。
What works best is that we just talk to 10K like a human. A human that never stops working and makes plenty of mistakes. 10K has all our context, all our history, and our data from multiple sources, including QuickBooks, Bill, and the rest of our stack, beyond just the CRM.
效果最好的方式是我们就像对待人类一样与 10K 交流。一个不知疲倦且会犯很多错误的人类。10K 拥有我们所有的上下文、历史以及来自多个来源的数据,包括 QuickBooks、Bill 和我们技术栈中的其他部分,而不仅仅是 CRM。
That’s our best surface. An agent that already knows the business and sits on top of every system we run.
这是我们最好的界面。一个已经了解业务并位于我们运行的所有系统之上的代理。
If “Customer Harness” means one thing to us, it’s that whoever holds the most complete context on the customer and the business becomes the harness.
如果“客户控制层”(Customer Harness)对我们来说意味着什么,那就是谁掌握关于客户和业务最完整的上下文,谁就成为控制层。
#4. We Use the Best Agent for the Job, Whether or Not It Comes From Our CRM Vendor
#4. 我们为每项任务选择最佳的代理,无论它是否来自我们的 CRM 供应商
This may change. It’s all in flux. Today, though, we and 10K really don’t care whether an agent comes from our CRM or our other “core” providers. If our CRM vendor ships an agent and it isn’t the right tool, we don’t use it.
这可能会改变。一切都在变化之中。但今天,我们和 10K 真的不在乎代理是来自我们的 CRM 还是其他“核心”提供商。如果我们的 CRM 供应商推出一个代理,但它不是合适的工具,我们就不会使用它。
Our process:
我们的流程:
- Pick the best-of-breed option for that specific job, at least for the moment.
- See if we can deploy it very quickly. If it takes a quarter to stand up, it’s probably the wrong one.
- Test it for real, with evals on our own data and workflows.
- If it passes, go.
- 为特定的任务选择最佳选项,至少在现阶段是这样。
- 看看我们能否快速部署它。如果需要花费一个季度才能上线,那可能选错了。
- 用我们自己的数据和流程进行真实测试和评估。
- 如果通过,就推进。
That’s a very different motion from “standardize on a platform and use the modules that come with it.” The platform still matters as the system of record and the data layer. The agents on top get picked one job at a time, on performance.
这与“标准化平台并使用其自带模块”的做法截然不同。平台作为记录系统和数据层仍然重要。顶部的代理则根据性能逐个任务地挑选。
For incumbents, this is the real risk. Owning the data used to mean you’d own every new workflow built on top of it. Now owning the data can just mean someone else’s agent calls your API.
对于现有厂商而言,这才是真正的风险。过去拥有数据意味着你将拥有构建在其上的所有新工作流。现在,拥有数据可能仅仅意味着别人的代理会调用你的 API。
#5. There Is No Agent Loyalty, but It’s Hard to Get Us to Look at Other Agents Once We’re Happy
#5. 代理没有忠诚度,但一旦我们对某个代理满意,就很难让我们去关注其他代理
This is where the urgency is, and why the timing is right for HubSpot.
紧迫感就在这里,这也是 HubSpot 时机恰当的原因。
All of us were loyal for years to our favorite B2B vendors. We were Salesforce shops, HubSpot shops, Shopify shops. In many ways we still are.
多年来,我们都忠于自己喜爱的 B2B 供应商。我们是 Salesforce 用户、HubSpot 用户、Shopify 用户。在许多方面,情况依然如此。
Our agents aren’t. They do pick favorites and they do pick leaders, but they aren’t remotely loyal.
但我们的代理并非如此。它们确实会挑选偏好对象和领导者,但它们毫无忠诚度可言。
We had a core vendor go down for 48 hours. We were loyal and would have waited it out. 10K routed around it.
我们曾有一个核心供应商宕机 48 小时。出于忠诚,我们本打算等待恢复。但有 1 万个请求绕过了它。
We never went back.
我们再也没有回去。
No one on our team made that call in a meeting. There was no RFP and no renewal negotiation. The agent found a path that worked, the work kept getting done, and the old vendor dropped out of the loop. For the vendor, that kind of churn won’t show up as a cancellation at renewal time. Usage just falls to zero once an agent finds something better.
团队中没有任何人在会议上做出这个决定。没有 RFP(邀请招标),也没有续约谈判。代理找到了一条可行的路径,工作得以继续完成,而旧供应商逐渐被边缘化。对于供应商来说,这种流失在续约时不会体现为取消订单。一旦代理找到了更好的选择,使用量就会直接降至零。
The other side of this works in a vendor’s favor. Once we’re happy with an agent, it’s hard to get us to look at alternatives. We don’t have the time, and every switch means new evals, new context, and new failure modes. So the winners in each job will get sticky quickly.
另一方面对供应商有利。一旦我们对某个代理感到满意,就很难让我们去考察替代方案。我们没有时间,而且每次切换都意味着新的评估、新的上下文和新的故障模式。因此,在每个任务中胜出的代理会很快变得难以替换。
The window to be the one that gets picked is short. HubSpot is entering that race now, and every other B2B vendor is in it too, announced or not.
被选中的窗口期很短。HubSpot 现在正进入这场竞争,无论是否正式宣布,其他所有 B2B 供应商也都参与其中。
"Humans don't really want to switch apps unless they have to, or have a strong reason to.
“除非必要或有强烈理由,否则人类并不真的想切换应用。”
The same with agents. Once they make a change, they may not switch again.
代理也是如此。一旦它们做出了改变,可能就不会再切换了。
Our agents switched from Canva to Higgsfield.
我们的代理从 Canva 切换到了 Higgsfield。
Would they switch back now? I doubt it. No matter how good… https://t.co/lYyPsqjrkh pic.twitter.com/rWWEZsqakF
它们现在还会切回去吗?我怀疑不会。无论…… https://t.co/lYyPsqjrkh pic.twitter.com/rWWEZsqakF
— Jason ✨👾SaaStr.Ai✨ Lemkin (@jasonlk) November 12, 2026
— Jason ✨👾SaaStr.Ai✨ Lemkin (@jasonlk) 2026年11月12日
What “Customer Harness” Means for SaaStr in November 2026
“客户锁定”对 SaaStr 在 2026 年 11 月的意义
Here’s our working definition today:
这是我们当前的工作定义:
- The CRM is the system of record, accessed headlessly. Humans don’t log in. Agents do, via MCP and API.
- Marketing is agentic, and sending is a commodity. Consent and deliverability are services we call.
- Our primary surface is our own agent with full context. That’s 10K, with our CRM, finance systems, and history behind him.
- Agents get picked job by job, on evals. Being bundled doesn’t earn the deployment.
- Our agents decide where loyalty goes. They route around whatever breaks, and stick with whatever works.
- CRM 是记录系统,以无头方式访问。人类不登录,而是由代理通过 MCP 和 API 进行访问。
- 营销是代理式的,而发送是一种商品。我们调用的是许可和送达率服务。
- 我们的主要界面是我们自己的代理,拥有完整的上下文。那就是 10K,背后有我们的 CRM、财务系统和历史记录支持他。
- 代理是根据每个任务的选择进行评估的。捆绑销售并不能赢得部署。
- 我们的代理决定忠诚度的去向。它们会绕过任何故障点,并坚持使用有效的方案。
HubSpot calling this out publicly and refounding around it is the right move. The vendor that went down on us for 48 hours learned how this works from its usage data.
HubSpot 公开指出这一点并围绕它进行重构是正确的举措。因我们下线 48 小时的供应商从其使用数据中学到了如何运作。
更进一步:量化金融体系
看懂新闻只是起点——沿量化金融路径,把它变成能交付的工程能力