Eric Siu walks through Claude's Opus 4.8 and its dynamic workflows feature, showing how parallel specialist agents can handle revenue recovery, client expansion, and SEO pipelines. The update cuts hallucinations and lets agents run longer, with ready-to-use prompts for sales, marketing, and engineering teams.
Chapters
Opus 4.8 is a big deal when it comes to making more money for your business. Now, the implications are huge when you think about all the different workflows that you have. I'm gonna talk about one of the major things that are gonna make— it's gonna make a world of difference. So first, let's get into the announcement itself. Let's take a look at it. And then we could talk about the massive implications. I'm gonna give you a couple of examples of money-making workflows that you can use using Opus 4.8. And you can see that they just announced this. Yesterday. And okay, the capabilities here, they have all these kind of SWE benchmarks over here. And then so usually what happens is, yes, Opus 4.8, whatever the latest model is, they're kind of going to favor themselves, right? So they want to make sure that they're doing well there, which is good. But what I want to bring your attention to, so I'm in a lot of these CEO AI tech groups and a lot of people in there, they're going crazy. They're like, oh my God, my engineers are going crazy with 4.8 right now. I'm like, crazy in a good way or crazy in a bad way? And it's all crazy in a good way, right? And so 4.7, a lot of people are like, oh, you know, they're kind of cutting down on, you know, it seems like it was maybe more of like a nerfed version that didn't really, didn't seem like a big step change from 4.6. Now 4.8 is a different story. So when you look at one of the major things I wanna call out when it comes to business is this dynamic workflows feature over here. So you can see it says this new feature available in research preview Allows Claude to take on even bigger tasks in Claude Code. So Claude can plan the work and then run hundreds of parallel subagents in a single session. And with Opus 4.8, the agents can run for even longer, which is great, right? People like to like spam these /goal commands, which is what I was doing before. So it then verifies its outputs before reporting back to the user. For example, Claude Code with Opus 4.8 can now carry out codebase scale migrations across hundreds of thousands of lines of code from kickoff to merge with the existing test suite as its start. You can read more about dynamic workflows and available in Cloud Code or Cloud Code for Enterprise, Team, and Max. Okay, great. Well, here's the thing. You might be thinking, well, I don't know how to code, right? And more so like maybe you're watching this right now, maybe you're not gonna handle migration, right? And frankly, you probably shouldn't handle migration, but there are a lot of implications here as it relates to business. So let me show you a couple workflows that my Hermes actually came up with, and then this will hopefully spawn a couple ideas for you when it comes to growing your business. business faster. Okay, so let's take a look at, um, let's share this screen over here and hopefully you can see this. So this is how it, this is how it looks. I, I always like to ask my Hermes, you know, what is the highest leverage Claude code dynamic workflow, uh, stuff that we can use? Um, and I asked for some prompts here so you can literally even steal these prompts. Just, just take a screenshot of this stuff over here. Okay, so number 1 is a revenue command center. So use a workflow, uh, build a revenue command center for a company and inspect every available data source I provide. So CRM, call transcripts, email threads, analytics proposals, SEO data, whatever. Create a unified map of where revenue is being created, delayed, leaked, or ignored. Then run specialist sub-agents in parallel for pipeline retention, upsells, SEO, paid acquisition, outbound partnerships, and operational bottlenecks. Return a rank of top 25 revenue opportunities with estimated upside, confidence, owner, next action, required assets, and 7-day execution plan. Then implement any safe automations, dashboards, scripts, or draft assets needed to start capturing the top opportunities immediately. So that is a pretty beefy prompt and you can have this repeat over and over, have it run, it could be once a month or so. You probably don't, I don't think you wanna run it every day just depending on how big your business is. Maybe every week might make sense. I really like the, this one's really helpful too, stalled revenue recovery. So use a workflow, analyze all deals, proposals, old sales calls, CRM notes, and email history from the last 180 days. Find every stalled, forgotten, underfollowed, or mishandled revenue opportunity. For sure you have this as an issue, right? Score each by recoverable revenue, buying intent, relationship warmth, reason stalled, and recommend a next move. Draft personalized follow-up messages for every high-value opportunity grouped by angle, urgency, new insight, case study, strategic check-in, offer refresh, or executive nudge. Produce a ready-to-send table and a daily follow-up sequence. Guess what? You should be taking all of these prompts over here and just dumping them into your Claude code and just ripping it. Like, in fact, that's what I'm gonna be doing over the weekend. I'm gonna look, I'm gonna also ask this Hermes and say, hey, you know what? Based on all my goals as a company, what other high leverage dynamic workflow should we be running? But literally on my screen right now, you can steal any of these. There's a client expansion engine over here. There's even an SEO one as well. I shared another tweet over here, and this is from Kat Wu, who is one of the leaders at Claude Code. And so she just talked about how dynamic workflows, you can see it has all these, this is how this flowchart is. And it looks pretty complex over here, right? So what I did was I was just like, hey, what are the practical use cases as it relates to the work that we do? Is there any way that Hermes can control this inside of Claude Code? Because maybe I don't want to log into Claude Code. Maybe I'm on the go, maybe I'm traveling. How should we think about this and how high leverage is this even if it isn't used within Hermes and just inside of Claude Code? So here, check this out. So my Hermes will always tell me, you know, what, how high leverage something is. Because I like to ask that question. If I put in like $1, do I get $100 back? Okay. Right. So my take here is high leverage, especially for your world, not because the workflow is magic, But the leverage is that it reduces the classic agent failure mode, doing step 4 before step 1, skipping verification or coding itself into a ditch with a tiny shovel and big confidence. So my thing's a little sassy. So practical use cases for us. So revenue stack closed loops. Okay, these are really good as well. So I would encourage you to take a picture of this as well. So pull HubSpot, Gong, Sheets data, identify bottlenecks, draft follow-ups, verify numbers, produce Slack-ready output. Okay, that's pretty good. This needs ordering. So dynamic workflows help present, I analyzed vibes and forgot the data, right? So it's just keeping things in order. And if you're doing it in parallel on many things, it doesn't drift, which is pretty important, especially if you're doing like a migration, right? You want to make sure that things don't drift. SG, so single grain SEO, AEO, GEO recovery work. So crawl pages, pull Google Search Console, GA4, Ahrefs, compare winners and losers, generate recommendations, create content briefs, verify against business impact. So strong fits, lots of dependencies, right? And then you have content machine. So there's a lot of this stuff over here. Gather trend intel, check calendar constraints, score hooks, draft options, dry run sheet updates, only then write engineering refactoring work, agent skill upgrades. Like all these things over here that you have already as repeatable workflows. If you run it as dynamic workflows, guess what? You're gonna have more scalability and it's also gonna be predictable too. So you can, it's reliable. And it's scalable. So that's why I think dynamic workflows are so important. And you, again, you can run it for sales, you can run it for marketing, you can run it for anything that is a workflow in your company, which a company is mostly workflows, right? You are going to be, it's gonna be higher ROI. So that's what I wanted to talk about here. And then we can come back to, let's just look more at the blog post for a little more. But I just think the dynamic workflows piece is pretty big. And I do think that based on kind of what I've researched so far, that this Opus 4.8 is kind of like— I think the next launch is probably going to be Mythos. And the fact that it's already pretty good at making sure, at scanning for kind of security vulnerabilities and things like that, it's more reliable, it doesn't hallucinate as much, I think is pretty good. So what's next? Users will find Opus 4.8 to be a modest but tangible improvement on its predecessor. There's still more work to be done. And here's the thing. It doesn't necessarily cost more money. It's the same thing as Opus 4.7, which is good. And users can now choose this extra high mode in Claude Code or Max. And then by the way, if you want to use the workflows when you're using Claude Code, you just type in the word workflow and then it'll kind of work on it from there. So I think this is cool. Like, look, embrace long writing tasks with Opus 4.8 and Claude Code. I think this to me is maybe it seems like an upgraded version of using /tools, which I think is still very powerful. If you're using it in Codex and Hermes or OpenCLAW and even in Claude Code as well. And so anyway, all that to say is, yeah, look, it's honest, right? It's less hallucinations as well. And then you can just see what the teams at Shopify and Notion are saying. So our new super AI benchmark, Claude Opus 4, is the only model to complete every case end-to-end, beating prior Opus models at 5.5x parity on cost for agent products in translation, deep research, slide building, Analysis, it provides powerful reliability. So I'm excited to test it in that context as well when it comes to designing things, using maybe using Claude Design to build, just to see how high quality it can be. Because I went to a networking event yesterday with a friend and he showed me the decks, the designs that he made using Claude Design, and they looked really good. So good in fact that I had him share it with me and I just made my own design MD out of it. This one from Shopify, Claude Opus 4.8 has noticeably better judgment in Claude Code. It asks the right questions, catches its own mistakes, pushes back when a plan isn't sound. Okay, so this is all good, but the most important thing I think, because we're talking about this in the context of business, is how do you actually use these dynamic workflows to ultimately help you make more money? That's what I'm interested in, right? So hope you enjoyed this video and we will catch you in the next one.
