正在加载视频...

视频加载失败

We launched Agentic Batch Changes this week: the very first coding agent with outcome-based pricing. You only pay when you merge a PR, not per token. Despite the innovation in other verticals—Sierra, Fin, Decagon, and more all charge per resolution—dev tools have remained firmly tied to seat- and usage-based...

23,917 次观看 • 11 天前 •via X (Twitter)

13 条评论

Dan Adler 的头像
Dan Adler11 天前

And read more about the Agentic Batch Changes product here

Dan Adler 的头像
Dan Adler11 天前

As much as I like to believe that this is the future of the industry, there is a reason we can do this while others cannot. Most coding agents were designed to be general-purpose problem solvers, just as likely to be used for vacation planning or open-ended exploration as executing a code change. That makes ROI an impossible question. Agentic Batch Changes is a special-purpose agent, scoped deliberately in its harness, its system prompt, its permissions, and its tools, to solve one concrete problem. We built it to minimize cost at scale, rather than paying for an agent to do the same job a hundred or a thousand times over.

Chen 的头像
Chen11 天前

one agent that works beat five clever ones here

Brian Miller 的头像
Brian Miller11 天前

bold, this is real courage

Dan Adler 的头像
Dan Adler11 天前

Thanks!

Ian Andrews 的头像
Ian Andrews11 天前

How do your customers forecast their spend under this model? This is the most frequent question I get on outcome based pricing topic

Dan Adler 的头像
Dan Adler11 天前

It's not so hard for us. The product is used for migrations (library updates, security incidents, refactoring, etc). X repos covered, Y large-scale changes planned this Q, easy to estimate. The downside is more "yet another pricing model" than hard to predict.

pwguler 的头像
pwguler11 天前

per-merged-pr rewards tiny prs: the cheapest fee is a one line change nobody argues with. if the goal is incentives in lockstep, the contract needs the revert and re-open rate too, otherwise the metric is merge count

Dan Adler 的头像
Dan Adler11 天前

Definitely will be watching revert rates (it's just hard to track this). Happy to refund reverts for any customer who runs into them. We stand behind the results.

pwguler 的头像
pwguler11 天前

the hard part is attribution, not willingness. a revert three weeks later rarely points back at the pr. tag every agent pr and both revert and rot become priceable, including the dead code that never gets reverted and never gets billed

Dan Adler 的头像
Dan Adler11 天前

tracking is a challenge for sure. But we're taking a bet. And they would have paid for those tokens anyway. Won't keep our customers long if they question the quality.

Supportman 的头像
Supportman11 天前

Per-resolution pricing only works if "resolved" is shared. In support that definition is contested: no-reply closes, soft handoffs, and reopen within 48h all look green until you sample them. Who owns the definition when the invoice depends on it?

Winston 的头像
Winston10 天前

What happens if clients tell your agent not to merge, then go dig up the old branch and merge it?

相关视频