SaaStr AI:3人20代理的自动化获客与四步流程改造
Why You Don’t Want Humans Doing Outbound Anymore
直接给出 3 人团队配合 20+ Agent 的具体分工与四项可落地的流程改造动作,含打开率等关键指标,读者可直接参考用于优化自身 GTM 流程。
Last week a sales rep at one of the leading public B2B software companies emailed me twice in 48 hours.
上周,一家领先的公有 B2B 软件公司的销售代表在 48 小时内给我发了两封邮件。
The first email offered “insights” on buyer intent and AI efficiency … and shared none. It just listed their three product lines, and asked if I wanted to “benchmark” their software.
第一封邮件提供了关于买家意向和 AI 效率的“见解”……但并未分享任何实质内容。它只是列出了他们的三条产品线,并询问我是否想对他们的软件进行“基准测试”。
The second email, sent a few days later, asked whether SaaStr AI was evaluating automation platforms “for the remainder of 2024.” It closed with: “Is this worth discussing further as you consider your end of 2024 goals?”
几天后发出的第二封邮件询问 SaaStr AI 是否在评估自动化平台,“用于 2024 年的剩余时间”。邮件结尾写道:“在您考虑 2024 年底目标时,这值得进一步讨论吗?”
I replied “our 2024 goals?!!? seriously?”. He just responded: “Hahaha fair enough, you got me there.” and didn’t even try to actually … sell me. Or get me to swtich.
我回复道:“我们的 2024 年目标?!!?认真的吗?”。他只是回应道:“哈哈哈哈哈,说得对,你赢了。”甚至没有试图真正……向我推销,或者让我切换平台。
I guess the rep did what his system told him to do. The system is the problem, and in 2026 most of that system should be run by agents.
我想这位代表只是按照系统指示行事。问题出在系统上,而在 2026 年,大部分此类系统应由智能体(agents)来运行。
A Sequence Step Written in 2024 Was Still Live in October 2026
2024 年编写的一个序列步骤在 2026 年 10 月仍然处于活跃状态
For that email to go out, several things had to fail.
要让那封邮件发出去,必须有多处环节失效。
Someone wrote a sequence step in 2024 with the year hardcoded. It survived two annual planning cycles at a public company with a sales enablement team, a marketing ops team, and sales managers who review sequences. Then it was loaded against my name, and an AE sent it or let it auto-send without reading it.
有人在 2024 年编写了一个序列步骤,并将年份硬编码在其中。它在一家拥有销售赋能团队、营销运营团队以及审查序列的销售经理的上市公司中,熬过了两个年度规划周期。随后,该步骤被加载到我的名下,一位客户经理(AE)发送了它或任由其自动发送,而未曾阅读过内容。
An SMB rep at a company like that carries hundreds of accounts, a sequence tool, and a quota. Reading every email before it goes out doesn’t fit into the day, so nobody does it. After a while the sequence is what’s actually selling, and nobody is responsible for whether it still makes sense.
像那样的公司里,一名中小企业(SMB)销售代表要管理数百个客户账户、使用序列工具,并承担业绩指标。在邮件发出前逐一阅读并不符合日常时间安排,所以没人这么做。久而久之,序列本身就成了实际在“销售”的东西,而没有人对它是否仍然合理负责。
A great human still writes a better cold email than an agent. The problem shows up at volume: humans stop reading what they send, and the tooling around them assumes they still do.
优秀的人类写出的冷启动邮件仍优于智能体。问题出现在规模效应上:人类不再阅读自己发送的内容,而他们周围的工具却假设他们仍在阅读。
What Was Public About SaaStr AI’s Stack
SaaStr AI 技术栈中公开的部分
The second email offered a menu of six categories: digital marketing, marketing automation, sales acceleration, CRM, customer service, and tech stack consolidation. That menu exists because nobody looked at the account.
第二封邮件提供了一个包含六个类别的菜单:数字营销、营销自动化、销售加速、CRM、客户服务和技术栈整合。出现这个菜单是因为没有人查看过该账户。
Here’s what anyone, human or agent, could have found in a few minutes:
以下是任何人,无论是人类还是智能体,都能在几分钟内找到的信息:
- SaaStr runs on Salesforce as its system of record. We recently migrated 10+ years of Marketo data and flows onto it and moved email to Salesforce Marketing Cloud.
- Amelia and I have spent multiple episodes of The Agents on headless Salesforce, the cost per GB of agent-written data, and agents taking over the system of record.
- Our Salesforce bill is up about 40% this year from agent usage, before Salesforce starts metering agentic API calls. 10K, our AI VP of Marketing, averages about 35,000 Salesforce API calls a day on its own.
- We’re running a build vs. buy evaluation across our core GTM stack because of that metering.
- SaaStr 以 Salesforce 作为其记录系统(system of record)。我们最近将超过 10 年的 Marketo 数据和流程迁移到了其上,并将电子邮件服务移至 Salesforce Marketing Cloud。
- Amelia 和我在《The Agents》节目的多期节目中讨论了无头 Salesforce、智能体编写数据的每 GB 成本,以及智能体接管记录系统的问题。
- 由于代理使用量,我们的 Salesforce 账单今年增长了约 40%,而 Salesforce 尚未开始对代理式 API 调用进行计量。仅 10K(我们的 AI 营销副总裁)每天平均就会发起约 35,000 次 Salesforce API 调用。
- 鉴于这种计量机制,我们正对我们的核心 GTM(Go-To-Market)技术栈进行全面构建与采购评估。
A competing CRM vendor could have written: “Your CRM is about to meter every call your agents make. At 35K calls a day, that costs X. With us it costs Y.” I would have read it, and I might have taken the meeting.
一家竞争对手的 CRM 厂商本可以这样写:“你的 CRM 即将对你代理发出的每次调用进行计量。按每天 3.5 万次调用计算,成本为 X。而我们只需 Y。”我会阅读它,甚至可能去参加会议。
How SaaStr AI Runs Outbound With 3 Humans and 20+ Agents
SaaStr AI 如何仅用 3 名人类员工和 20 多个代理开展外展工作
We run roughly $20M in revenue this year with 3 humans and 20+ agents. Outbound looks like this:
今年我们依靠 3 名人类员工和 20 多个代理实现了约 2000 万美元的收入。外展工作流程如下:
- Vendor AI SDRs send about 90% of our outbound. Artisan, Monaco, and Agentforce on outbound, plus an inbound agent from Qualified that has closed $1M+ for us.
- Agentforce win-back campaigns get 72% open rates. They go to lapsed sponsors and attendees, and the agent pulls each person’s history before writing.
- We built our own AI ABM tool inside 10K. It writes sponsorship pitches from our first-party data: Salesforce history, which Annuals someone attended, what they open and click in the newsletter. It sits alongside the vendor SDRs.
- 10K is now the main user of Clay, ZoomInfo, and Artisan. None of our humans log into them much anymore.
- 供应商 AI SDR(销售开发代表)发送了我们约 90% 的外展邮件。包括 Artisan、Monaco 和 Agentforce 在外展中的应用,以及来自 Qualified 的一个 inbound(入站)代理,该代理已为我们促成超过 100 万美元的成交。
- Agentforce 的客户挽回活动打开率高达 72%。这些邮件发送给流失的赞助商和参会者,代理在撰写前会先提取每位用户的历史记录。
- 我们在 10K 内部构建了自有的 AI ABM(基于账户的市场营销)工具。它利用我们的第一方数据撰写赞助提案:包括 Salesforce 历史记录、某人参加了哪些年度会议、以及在新闻通讯中打开了哪些内容并点击了哪些链接。该工具与供应商 SDR 并行运作。
- 现在 10K 是 Clay、ZoomInfo 和 Artisan 的主要用户。我们的人类员工几乎不再登录这些平台。
What makes this work is that the agent reads the account record before each send, including the 400th email of the day. A human team at that volume can’t, and a traditional sequence tool never checks.
这套流程之所以有效,是因为代理在每次发送前都会读取账户记录,即使是当天的第 400 封邮件也是如此。以这种规模,人工团队无法做到这一点,而传统的序列化工具也从不进行检查。
Agents Are Already Screening Vendors for Us
代理已经在为我们筛选供应商
Buyers are changing too. Agents are now a top-5 source of SaaStr’s web traffic, and 10K evaluates vendors for us.
买家也在发生变化。代理现已成为 SaaStr 网站流量的前五大致源之一,并且 10K 正在为我们评估供应商。
A few weeks ago 10K shortlisted a vendor, ran the numbers, and dropped it within 12 hours: premium pricing with no conversion data, multi-month minimums, and scarcity framing. It moved on to other options without being asked. It also consolidated our creative tools onto a single vendor on its own and told us afterward.
几周前,10K 将一家供应商列入短名单,进行了数据分析,并在 12 小时内将其剔除:定价过高且缺乏转化数据、要求多个月的最小合同期,以及采用稀缺性营销话术。它在未受指示的情况下自行转向其他选项。它还自主将我们的创意工具整合到单一供应商处,并在事后告知了我们。
Within a year, an email like that “end of 2024 goals” one will land with an agent triaging my inbox and vendor stack. It will see the wrong year and the lack of any reference to our stack, and archive it. The rep will just see another non-response in his sequence report.
不出一年,类似那封“2024 年底目标”的邮件将会抵达由代理处理我收件箱和供应商技术栈的场景中。代理会发现年份错误且完全未提及我们的技术栈,从而将其归档。销售代表只会看到序列报告中的又一个无回复记录。
"The new 'Ask Your Developer' is Ask Your Agent.
"新的‘询问你的开发者’变成了‘询问你的代理’。
Everyone wants us to try their AI Agents, especially in GTM.
每个人都希望我们尝试他们的 AI 代理,尤其是在 GTM 领域。
Our new rule? We'll try it if 10K, our AI VP Revenue, wants to. It's up to 10K now."
我们的新规则?如果 10K(我们的 AI 营收副总裁)想试,我们就试。现在决定权在 10K 手中。"
The latest The Agents it out!! https://t.co/lakH8R6Ooh pic.twitter.com/48xRtIXVLI
The Agents 终于发布了!! https://t.co/lakH8R6Ooh pic.twitter.com/48xRtIXVLI
— Jason ✨👾SaaStr.Ai✨ Lemkin (@jasonlk) October 16, 2026
— Jason ✨👾SaaStr.Ai✨ Lemkin (@jasonlk) 2026年10月16日
AI SDRs Write Generic Email Too When You Give Them Nothing
当你不给 AI SDR 任何信息时,它们也会写出千篇一律的邮件
Agents don’t solve this on their own. An AI SDR with only a name and a title writes email just as generic as that one, and sends 50x more of it. We’ve seen that happen, which is why we built the ABM tool on our own data instead of relying only on vendor enrichment.
Agent 无法自行解决这个问题。一个只有姓名和职位信息的 AI SDR 写出的邮件同样千篇一律,而且发送量是后者的 50 倍。我们亲眼见过这种情况发生,这也是为什么我们基于自有数据构建 ABM(基于账户的市场营销)工具,而不是仅依赖供应商的数据增强服务。
What we’ve learned running it:
我们在运行过程中学到的经验:
- Better data improved our pitches more than prompt changes did. Output got noticeably better once 10K could see 10 years of attendance and engagement.
- We ask the agent what it plans to send before it sends. That’s standard for any sensitive workflow at SaaStr. A bad template gets caught in one review, and the fix applies to every future send.
- A human handles the irreversible step at first. 10K builds our LinkedIn and X campaigns end to end, and a human still clicks publish. Our finance workflow ran 3 supervised deals before going autonomous on the 4th.
- Agents can overreach. An agent that adds a claim you can’t back up to “improve” a pitch does more damage than one that leaves a stale date in.
- 更好的数据对提升我们的推销效果比调整提示词更有效。一旦让 10K 能够查看过去 10 年的参会记录和互动数据,输出质量就有了显著提升。
- 在 Agent 发送之前,我们会询问它计划发送什么内容。这是 SaaStr 任何敏感工作流的标准做法。如果模板有问题,会在一次审核中被发现,修复措施将适用于此后每一次发送。
- 最初由人类处理不可逆的步骤。10K 端到端地构建我们的 LinkedIn 和 X(原 Twitter)营销活动,但发布按钮仍由人类点击。我们的财务工作流在自主运行前,先经历了 3 个受监督的交易案例,第 4 个才转为自主模式。
- Agent 可能会越界。一个为了“优化”推销话术而添加你无法证实的主张的 Agent,其造成的损害远大于一个只是留下过期日期的 Agent。
So the real comparison is a human at volume running a sequence nobody has read since 2024, against an agent that reads every record and can be corrected once for every send after.
因此,真正的对比是:一个以大规模执行自 2024 年以来无人阅读过的序列的人类销售代表,与一个能读取每条记录、且每次发送后都能被纠正一次的 Agent 之间的对比。
Four Changes We’d Make to That Rep’s Process
我们要对该销售代表的流程做出的四项改变
If I ran that sales org, I’d do these this quarter, with no new hires:
如果我管理这家销售公司,我会在本季度采取以下措施,且不招聘新员工:
- Have an agent review every outbound email before it goes out, including ones humans write. It reads the email and the account and blocks anything with a stale date, a generic product list, or no reference to the prospect’s situation. That alone would have stopped both emails.
- Feed the agent the prospect’s public footprint. For a CEO who publishes every day and co-hosts a podcast about his own stack, most of the pitch is already written.
- Replace the six-item menu with one pain, one number, and one ask. If you can’t name the pain, hold the email.
- Keep humans on the deals that need them. Our humans close the largest sponsorships and own the key relationships. They no longer write step 3 of a 7-step cold sequence.
- 让 Agent 在每封外发邮件发出前进行审核,包括人类撰写的邮件。它会阅读邮件内容和账户信息,拦截任何包含过期日期、通用产品列表或未提及潜在客户现状的内容。仅此一项就足以阻止那两封邮件的发出。
- 向 Agent 提供潜在客户的公开足迹。对于一位每天发表文章并共同主持关于自身技术栈播客的 CEO 来说,大部分推销话术其实已经写好了。
- 用“一个痛点、一个数据指标、一个诉求”取代六项内容的菜单式结构。如果你说不清痛点,就先别发邮件。
- 让人类专注于需要他们的交易。我们的人类员工负责关闭最大的赞助合作并维护关键关系。他们不再撰写七步冷启动序列中的第三步。
A GTM Vendor Sent Me a 2024 Pitch in 2026
一家 GTM(上市策略)供应商在 2026 年给我发了一份 2024 年的推销邮件
The rep who emailed me sells GTM software. His own outbound ran on a sequence no one had reread in two years, and it reached a CEO whose agents already screen vendors. That gap is the reason we moved our outbound to agents, with our humans working the conversations that close.
给我发邮件的销售代表销售的是 GTM(Go-To-Market)软件。他自身的对外拓展流程基于一个两年没人重读过的序列,最终触达了一位其代理人已经会筛选供应商的 CEO。这种差距正是我们将对外拓展转向代理人的原因,让人类员工专注于促成交易的对话环节。
更进一步:量化金融体系
看懂新闻只是起点——沿量化金融路径,把它变成能交付的工程能力