How to Get Ahead of 99% of Companies Using AI

Marc Chabot lays out a four-step playbook for extracting ten times more value from AI than competitors. Run 100 AI agents across your business, each surfacing one improvement monthly. Capture every idea in a centralized system, rank by value and effort, deploy the top eight changes every week instead of waiting for quarterly cycles.
Chapters
I've been working inside enterprise software for over 20 years, and there's a small group of organizations using a simple 4-step process to get 10 times more leverage out of AI than their competitors. So in this video, I'm going to reveal those exact 4 steps, and if you copy them, you'll be ahead of 99% of companies using AI in no time. Step 1, set your target at 8 changes a week. All right, so most organizations innovate by going project to project, but what does one big project at time actually get you over a few years? You pick the project, it takes somewhere between 6 and 18 months, and by the end of it, that part of the business works noticeably better than it did before. Then the team moves on to whatever is next, and that same part of the business doesn't really change again until somebody funds another big project for it. You replatform your ERP, a big long project, and when it's finally live 18 months later, it makes an impact, but now no one really wants to do anything else with it. And because it cost you millions, the next project to make enhancements will also take a long time and cost you millions more. So hard to keep up the momentum. This is just how software and SaaS are. Now, let's say each of these projects doubles how much that part of the business can get done. So it makes a real impact. That's a great result. And most leadership teams would be extremely happy with that. But you only get to start a project like that every couple of years. So over the course of 6 years, you've done, let's say, 3 of them. The first project, let's say it doubles how much you get done. The second one doubles it again. And by the third, you're getting 8 times as much done in your business than when you started. Huge impact over 6 years. But now let's compare that to getting just 1% better every day. That sounds like nothing. And on any given day, it is basically nothing. But 1% a day compounded across the full year comes out to 37.78 times as much as when you started. So 3 big projects over 6 years gets you 8 times better and getting 1% More done every day gets you 37 times better in a single year. And when I say 1%, I'm talking about one small specific change to how the business runs. This could be raising an approval limit that was set back when the company was much smaller. It could be dropping a form somebody has to fill out before a new customer can get set up. It could be writing a condition into a rule so an agent stops asking a person about that condition and escalating it every time. Or it could be automating a task somebody's been doing manually for years. So in practice, that works out to about 8 changes a week. Each of those changes is roughly 1% for that day. So you want a bit more than one a day, call it 8 a week, and that's your target. Do that for an entire year, and by the end of it, you're roughly getting 37 times as much done as when you started. So building with big projects versus small incremental and continuous changes has very different results on the business. Step 2, getting 100 agents running across the business. Now, 8 changes a week is way more than most teams can come up with in a month. So the important question is, where are all these ideas coming from? Well, they definitely don't come from getting your team in a room and trying to think up all these improvements in a meeting. They come from the agents you already have live because those agents are doing work 24/7. They're confronting problems, they're escalating work, they're confronting where they're good at automating, they're making decisions about what they can and cannot Do, and they're uncovering all of the opportunity for you. Every agent you're running comes across things nobody planned for— a situation it doesn't have a rule for, a step in a process that clearly isn't working, or a whole task no one realized could be automated. And each one of those is a change you could make. So if you have 100 agents running and each one finds just one useful thing a month, that's 100 a month, or about 23 potential improvements a week. And we just said you only need 8, but now you get 23 improvements. That's almost 3 times as many as you need. So that one useful thing a month is almost nothing to ask of an AI agent to deliver for you. It works all month. It only has to find a single thing that entire time. So really, all this comes down to how many agents you have running and if you're set up to listen to them. And the way to add them is to start with the workflows where your team does the most repetitive manual work and keep going from there. Those are usually the types of tasks where somebody's copying information between 2 systems checking whether something breaks a rule or answering the same question over and over. Basically, every agent you add increases the number of improvements you have to choose from each and every month. Every agent that you deploy is going to give you 10 new project ideas on a silver platter. Step 3, catch everything your agents find. Now, at almost every organization I've worked with, pretty much none of those 23 improvement ideas your agents find are going to turn into a change. And, and that's because there are only 3 things that happen to them, none of which lead to an actual change. The first is a human-in-the-loop approval request, which an agent sends when one of your rules won't let it do something. It ends up in an inbox, they approve it or deny it in about 2 minutes, and it's done. Nobody ever asks whether that rule that stopped the agent was still the right rule or could be improved. So the agent request got answered, but the chance to fix the rule or improve is gone. The second type is the agent's own history inside whatever platform it runs. That's where an improvement ends up anytime the agent handles something your rules never covered. So you've got an agent processing invoices and an invoice arrives from a vendor that bills in a format that maybe none of the rules cover. The agent uses probability analysis and chooses the closest rule it has and processes the invoice and nobody even knows it. So the same vendor sends the same kind of invoice again next month. And the agent guesses again and processes it again. So that's an opportunity for improvement that's buried in the work that the agent does routinely month after month. Can you improve it? Do you want it to lean in that matching the intent of your business? Being able to access this is key to understanding where improvements can be delivered within how the agents are actually automating the work itself. And the third type is an improvement that does get talked about usually once in a monthly review. Somebody mentions it every Everyone agrees it needs to be prioritized. The meeting ends, doesn't really get written down or anyone has time to do anything with it. So it gets left on the table. So your agents are producing improvements every week, ideas for improvements every week, but you're building none of them, ending up no better off than the companies running one big project at a time. And that's not a problem with your agents or your team. There's just, you're not set up. You don't have a system for where those improvements and ideas need to go so that they can be immediately impacting your business. You want is all of these opportunities showing up in one place, and then a way to decide which ones are actually worth building every single week. Because you're not going to build all 23 of these opportunities every week, and you shouldn't. Some of them would save your team a lot of time or money, some aren't worth the effort, and a few are probably already covered in a project that's already in flight with your team. So you need each one of these ideas to get ranked by how much it's worth to the business right now And the 8 most important opportunities are the ones that need to become projects that you plan out and build fast. And it's because if you do 8, that's the 1% change a day we're going for that we talked about earlier. Now, I built my platform Force Equals to be the place to do exactly all of what we just discussed. It connects to all the agents you're already running, so everything they find shows up in one area handling all of the conditions we just talked about. So it connects to all the agents you're already running. So everything they find shows up in one place instead of the 3 different disparate places that we just went through. From there, it automatically ranks each of these opportunities, which ones, what it's worth to your business, how much effort is it, do you have resources for it, are there constraints that are limiting it, so that you can actually see which 8 are the best ones to build this week. So this screen has everything my agents have run into this week across every platform They're running on all the different agents. These are getting presented because the system is proposing insight from how it works. Each agent is showing us which guardrails are potentially could be improved. These opportunities are the ones that are flagged by your team that are participating in the escalations where they are uncovering an opportunity for improvement. All of these are captured in one place. So it's figuring out how much each improvement is worth our attention right now based on what our goals are of the organization and what it would cost cost to build from a resources and constraints perspective. And because this improvement ranks high enough, it's going to get momentum, turn into a project, and can be considered right next to everything else the team's working on. So prioritization becomes the means for understanding what should move forward right now fast. And if you want to implement this process in your own company, I'll leave a link at the top of the description where you can get started with Force Equals for free. Step 4: Get every change live the same week. So now let's talk actually about getting these changes live the same week you decide they're worth it. At most big organizations, a change waits for the next planning cycle, quarterly, annually, gets scoped, goes through approvals, and is live in 6 to 18 months. Even with a few of them moving at the same time, you're limited at how many changes go live in a year. So let's take 2 companies with the exact same setup and change only how fast they can get deployments and changes live. Both of them have 100 agents running. Both of them are finding the same 23 improvements a week. The first one runs through the planning cycle, so it gets 4, 5 changes grouped together, a bunch of them, maybe 20 changes across the course of the year, all deployed. The second one gets 8 live every week, or a bit over 400 for the year. So somewhere between 4 and 20 changes a year versus 400 a year. Most of that year you wouldn't be able to tell the 2 companies apart. Nothing your competitor that's doing one a week looks very different because each change is bite-sized and small and incremental. It's raising an approval limit one week. It's cutting a step out of a process the next week. So there's no big project you'd notice all at once making a big impact. But by the end of the year, they're getting 37 times as much done as when they started. And by that time, you can see the difference. You're already so far behind if you're the company doing project by project. So sure, you can buy the same agents they have, but you can't buy the 400 changes they already made to how their business operates. Over the next 5 to 10 years, I bet fewer than 15% of companies will figure this out. So what you're going for is getting those 8 changes live every week and keeping that pace for an entire year and keep each change small enough that it can go live in a week or 2 from when somebody decides it's worth it. And don't let a change that's already been decided on wait around for a budget cycle, because every week it waits is a week you're not getting anything out of it. You've already identified the opportunity for improvement— deploy it. You need your system to react dynamically. Do that for a year and you've made 400 changes to how your business runs while you're competitor has only made 4, 5, 10, or 20. Now, the only way to get 8 changes a week is if every improvement your agents find gets to a place where they can be weighted against your strategy, prioritized, and approved so somebody can actually start building it. And that's the whole reason I built Force Equals. I'll leave a link to it at the top of the description where you can get started for free. It connects to the agents you're already running, puts everything they find in one place, and ranks by how much time or money each would save you. So the best ones turn into projects your team actually builds. So again, you can get started with 4Sequals for free by clicking the first link in the description. And if you want to know exactly what to do with an approval request when one of your agents gets stopped by a rule, then check out this next video.










