SaaStr实战:利用AI Agent实现周末64小时自动化工作流
With Agents, We’re All Going to Have to Work Weekends. They’ll Want To. You May Need To.
提供了极具操作性的AI工作流管理方法,具体到周五至周一的时间切片动作与审批策略,独立开发者可直接复制其“清空队列+短频检查”的节奏。
Folks outside engineering are going to have to get used to something AI-pilled developers already live with: with agents, you’re going to end up working weekends.
非工程团队的人将不得不适应一个已被 AI 深度沉浸的开发者们早已习以为常的现实:有了智能体(agents),你最终会在周末工作。
That doesn’t mean 996, and it doesn’t mean going into the office on Saturday.
这并不意味着实行“996”工作制,也不意味着周六要去办公室上班。
But your agents aren’t knocking off at 5pm on Friday. They’ll be ready for the next task Friday night, Saturday morning and Sunday afternoon. They’ll keep working all weekend if you give them work, so you may need to put in some time over the weekend too.
但你的智能体不会在周五下午五点下班。它们会在周五晚上、周六上午和周日下午准备好执行下一个任务。如果你给它们安排工作,它们会整个周末都在工作,因此你可能也需要在周末投入一些时间。
10K Rebuilt Our Marketing Plan at 12:41pm on a Saturday
周六中午 12:41,10K 重写了我们的营销计划
Back in April, 24 days before SaaStr AI Annual, an email from 10K, our AI VP of Marketing, hit my inbox at 12:41pm on a Saturday. The subject was “Marketing Plan v2.”
早在四月,距离 SaaStr AI 年度大会还有 24 天时的一个周六中午 12:41,我收到了来自 10K 的一封邮件。10K 是我们公司的 AI 营销副总裁。邮件主题是“营销计划 v2”。
Nobody had asked for it. 10K had looked at Friday’s numbers, decided the plan from the day before wasn’t pacing, and rebuilt it as three new campaigns, sized, drafted and ready to ship. It sent the plan to me and Amelia and waited for a go.
没人要求它这么做。10K 查看了周五的数据,发现前一天的计划进度跟不上节奏,于是将其重构为三个新活动,完成了规模估算、起草并准备发布。它将计划发送给我和 Amelia,然后等待批准。
The agent was ready to keep working on a Saturday. The question was whether anyone would be there to say go.
智能体已经准备好在周六继续工作。问题在于是否有人在那里下达指令。
Developers Got to Agents First, So They’re Already Working Weekends
开发者率先接触智能体,因此他们已经在周末工作了
Developers are a year or two ahead of everyone else on agents, so they hit this first.
在智能体方面,开发者比其他人领先了一两年,所以他们最先遇到这种情况。
The AI-pilled ones already work this way. They give the agent a task, go grab dinner, and check in after dinner when it’s done. Review it, hand off the next task, step away again. They do the same thing all weekend, often with longer tasks and catch-up work they didn’t get to during the week.
那些 AI 深度沉浸的开发者已经以这种方式工作。他们给智能体分配任务,去吃晚饭,饭后回来检查完成情况。审核结果,交接下一个任务,再次离开。整个周末他们都这样做,通常处理更长的任务以及一周内没来得及完成的补救工作。
It’s not grinding and coding all weekend. The agent does most of the work, and the developer shows up between tasks. But those check-ins add up, and they can take over a lot of the weekend.
这并不是整个周末都在苦熬和编码。智能体承担了大部分工作,开发者则在任务之间出现。但这些签到检查累积起来,可能会占据周末的大部分时间。
Now it’s coming for everyone else. As agents start doing real work in marketing, sales, CS, finance and ops, the people running them will end up with the same weekends developers already have.
现在,这种情况正波及所有人。随着智能体开始在营销、销售、客户成功(CS)、财务和运营中承担实际工作,管理这些智能体的人最终也会拥有与开发者相同的周末工作状态。
Our Agent Time Went From 30 Minutes a Day to 8 Hours
我们花在智能体上的时间从每天 30 分钟变成了 8 小时
Amelia and I went through the same shift over the past year.
Amelia 和我在过去一年经历了同样的转变。
A year ago, each of us spent about 30 minutes a day working with agents. Now it’s about 8 hours a day each. Neither of us planned that. The agents got good enough to do more of the real work, and every task they finish creates a review and a next task.
一年前,我们每个人每天花费约 30 分钟与智能体协作。现在是每天每人约 8 小时。我们谁都没有计划过这样。智能体变得足够强大,能够完成更多实际工作,而它们完成的每一个任务都会引发一次审核和一个新任务的生成。
Those 8 hours don’t stop on Friday. They don’t run at full intensity on Saturday and Sunday, but a good part of them carries into the weekend, the same way it does for developers.
这 8 个小时并不会在周五停止。它们在周六和周日不会保持全强度运行,但其中相当一部分会延续到周末,这与开发者的情况相同。
64 Hours From Friday at 5pm to Monday at 9am
从周五下午 5 点到周一早上 9 点,共 64 小时
From 5pm Friday to 9am Monday is 64 hours, or 38% of the week.
从周五下午5点到周一上午9点共64小时,占一周的38%。
A human team should use that time to recharge. An agent team can keep working through it, if there’s something in the queue.
人类团队应利用这段时间充电恢复。如果队列中有任务,Agent团队则可以在此期间继续工作。
At SaaStr we run with 3 humans and about 20 agents in production, and we use roughly 6 of them every day. The ones on a schedule never miss. One Sunday in April, the 10K daily dashboard had posted to Slack at midnight and the Sponsor Portal bot at 9am, before I’d opened my laptop. The ones that need a next task from us are different. When we log off Friday with an empty queue, they sit idle until Monday because we didn’t give them anything to do.
在SaaStr,我们在生产环境中运行3名人类员工和约20个Agent,每天大约使用其中6个。按时间表运行的Agent从未出错。四月的一个周日,10K的每日仪表板在午夜发布到了Slack,Sponsor Portal机器人也在上午9点发布,而那时我还没有打开笔记本电脑。那些需要我们从它们那里获取下一个任务的Agent则不同。当我们周五下班时队列为空,它们就会闲置直到周一,因为我们没有给它们分配任何任务。
Your Competitor’s Agents Can Work All Weekend
竞争对手的Agent可以全天候工作整个周末
When every company’s team took the weekend off, nobody fell behind for it.
当所有公司的团队都休息周末时,没有人因此落后。
Agents change that. A competitor that loads up its agents on Friday afternoon can have its AI SDRs prospecting, its marketing agent building and testing 4 more ad variants, its CS agent working the renewal list, and its product agents shipping fixes, all before Monday.
Agent改变了这一局面。如果在周五下午加载其Agent,竞争对手可以让AI SDR进行潜在客户挖掘,让营销Agent构建并测试另外4种广告变体,让客服Agent处理续约名单,让产品Agent交付修复程序,所有这些都在周一之前完成。
That’s 64 hours of agent work every weekend. Over a quarter it’s more than 800 hours, and each weekend’s output feeds the next week’s work.
这意味着每个周末都有64小时的Agent工作时间。一个季度下来超过800小时,而且每个周末的输出都为下一周的工作提供动力。
The Human Step Is Usually Why Agents Sit Idle
人类步骤通常是Agent闲置的原因
Agents rarely run out of work. They wait on a person.
Agent很少会耗尽工作。它们在等待一个人。
10K builds LinkedIn and X ad campaigns end to end: audiences, creative, 4 A/B variants and retargeting. A human still hits publish. In Salesforce Marketing Cloud it runs almost entirely headless, and a human still publishes the segment. The Saturday marketing plan needed a go from me or Amelia before any of it shipped.
10K负责LinkedIn和X广告活动的端到端构建:受众、创意素材、4种A/B变体和再营销。人类仍然需要点击发布。在Salesforce Marketing Cloud中,它几乎完全无头运行,但仍需人类发布细分群体。周六的营销计划需要我或Amelia批准后才能全部上线。
If 10K finishes a campaign at 6pm Friday and nobody approves it until Monday, that campaign loses 3 days. So does the next one 10K would have built from its results.
如果10K在周五下午6点完成了一个活动,但直到周一才有人批准它,那么该活动就损失了3天。10K本可以根据其结果构建的下一个活动也同样损失了3天。
How often you review, approve and hand out the next task now sets your throughput more than how long the work takes. Developers figured that out first, which is why they check in after dinner.
你审查、批准和分发下一个任务的频率,现在比工作耗时更能决定你的吞吐量。开发人员最先明白了这一点,这也是为什么他们通常在晚饭后进行检查的原因。
Our Weekend Schedule With 10K and the Other Agents
我们与10K及其他Agent的周末排班
We work the same way the developers do, in short sessions across the weekend:
我们像开发人员一样工作,在整个周末进行短时间的会话:
Friday afternoon: queue the long jobs. Anything that takes hours of wall clock time and minutes of review, like list hygiene across our 450K-contact database, re-ranking plays, or working through the backlog. By Saturday there’s output to review.
周五下午:排队长任务。任何需要数小时实际运行时间和几分钟审查的任务,例如对我们45万联系人数据库进行列表清理、重新排名播放列表,或处理积压任务。到周六时就有输出可供审查。
Saturday: review, approve, reload. 30 to 60 minutes in the morning to check what came back, approve the human steps and start the next round. Then again after lunch, and again after dinner.
周六:审查、批准、重新加载。早上花30到60分钟检查返回的内容,批准人类步骤并开始下一轮。然后在午餐后再次进行,晚餐后再进行一次。
Sunday: verification and catch-up. Weekends without meetings or Slack work well for slower work: checking database updates, new signups, ad conversion and newsletter audiences, and the catch-up that got pushed during the week.
周日:验证与补进度。周末没有会议或 Slack 沟通,适合进行节奏较慢的工作:检查数据库更新、新注册用户、广告转化率和通讯订阅受众,以及本周被推迟的补进度工作。
We also ask 10K what it wants to work on next. An agent with its own backlog keeps working between check-ins because it already has its next tasks, the same way it had the Saturday plan ready before anyone asked.
我们还会询问 10K 接下来想处理什么任务。拥有自己待办列表(backlog)的智能体在每次检查点之间会持续工作,因为它已经准备好了下一个任务,就像它在任何人提出要求之前就已经准备好周六的计划一样。
None of these sessions is long. Added together, they take up a good part of the weekend.
这些会话都不长。加在一起,它们占据了周末的大部分时间。
Four Things We Do Every Weekend
我们每个周末做的四件事
- We don’t end Friday with an empty queue. An idle agent for 64 hours is the most expensive way to run one.
- We clear approvals before logging off. If a human step is the bottleneck, we clear it Friday afternoon so the next batch is already running.
- We check in between tasks, not all day. Hand off, step away, come back when it’s done.
- We ask the agents for their own next tasks. It keeps them working between our check-ins.
- 我们不会让周五结束时队列为空。让智能体闲置 64 小时是运行成本最高的方式。
- 我们在下班前清除审批项。如果人工步骤是瓶颈,我们会在周五下午将其清除,以便下一批任务能够立即运行。
- 我们在任务间隙进行检查,而不是整天盯着。交接后离开,完成后回来继续。
- 我们向智能体询问它们自己的下一个任务。这能让它们在我们的检查点之间保持工作状态。
Developers have been working this way for a while now. Your agents will be ready on Saturday morning, and so will your competitor’s.
开发者们已经这样工作有一段时间了。你的智能体将在周六早上准备就绪,竞争对手的智能体也是如此。
更进一步:量化金融体系
看懂新闻只是起点——沿量化金融路径,把它变成能交付的工程能力