Five months ago I introduced The Race to Autonomy as a blog series and told leaders the first step was believing the race was happening. I didn’t follow through on the series, but the work never stopped. I continued building my framework, defining the new software category, developing the platform, and transitioning our services for AI transformation. The problem was that all of these efforts looked like separate things from the outside, when they were always part of the same mission. Today I am relaunching The Race to Autonomy as the unifying identity for everything I do, with a dedicated home at RaceToAutonomy.com and a diagnostic to help leaders find their starting line.

---

In September 2025, I published the first blog in what I called “The Race to Autonomy” series on this site. The thesis was simple: every organization is in a race toward self-management, whether leadership recognizes it or not. The companies that acknowledge this and begin preparing will define the competitive standard for the next decade, and the ones that don’t will be left running a race they never trained for.

A few weeks later, I posted on LinkedIn with a line I still stand behind: “The first step is believing the race is happening.” At the time, it felt bold. Most of the executives I spoke to were still sorting through AI tool fatigue, unsure what mattered and what was noise. Some were skeptical. Some were overwhelmed. And a fair number simply didn’t believe that anything as structural as “autonomy” was relevant to their business yet.

That was five months ago, and the world has moved. The conversations I have now are different. Leaders are no longer asking whether AI changes things. They are asking how to get ahead of the change. The uncertainty hasn’t vanished, but the denial largely has. What I told people in September is what I am telling them today: you are in this race whether you acknowledge it or not, and you can get on top of it. The destination is the same. The urgency is just more visible, and if you don’t compete you almost certainly will cede all of your market to others who are competing.

The Problem I Couldn’t See Clearly

During those five months, I didn’t follow through on the series. I got pulled into the work itself, which is what happens when you’re building across multiple fronts simultaneously.

I continued developing my Ragsdale Framework for Autonomization, the research program that defines how organizations evolve from human-driven operations to machine-mediated, self-managing systems. I kept refining the concept of the Autonomous Operating Environment (AOE), a new category of software I believe every organization will eventually require, that is designed to give you sovereign control over your data and operations so AI can actually function with full context. I continued building Kaamfu, the first practical AOE, where my own distributed team runs its entire operation. I transitioned Prospus, my services company, into a Practical AI Transformation practice, offering hands-on help to founders who need their businesses restructured before any intelligent system can deliver real value. And I wrote extensively about the next generation of workers I call Evolution Architects, and the software companies that will help organizations navigate this transition as Evolution Partners.

All of it was real work with a deep, forward-looking message, and all of it was advancing the same cause. But from the outside, it looked like a lot of different messages coming from a lot of different, seemingly unrelated places. The Ragsdale Framework lived on its own domain. Kaamfu had its own positioning. Prospus was telling a services story. My personal site was running thought leadership in a different register. The concepts of Evolution Architects and Evolution Partners were floating in articles and LinkedIn posts without a clear home.

I knew the pieces were connected, and I had even mapped them into what I call the Autonomy Stack: theory, category, platform, transition. But the connective tissue between them wasn’t visible to anyone who hadn’t spent years inside my head. That’s a problem when you’re trying to help leaders both see what is ahead, and take the first steps.

What Clicked This Morning

This morning I was working through the content and messaging across all of these entities, trying to align them yet again, when something obvious finally hit me. I need one voice. Every entity I’ve built, every framework I’ve published, every concept I’ve introduced, they all serve the same fundamental purpose: to help organizations recognize they are in a race, and to equip them to run it. The Ragsdale Framework tells you what the race looks like. The AOE category tells you what kind of infrastructure the race demands. Kaamfu gives you the platform to actually run on. Prospus helps you get your footing if you’re not ready yet. Evolution Architects are the people who will lead the transformation inside your company. Evolution Partners are the firms that will guide the journey from the outside.

All of it is the Race to Autonomy. It orients you toward the goal and conveys the urgency in a single idea. It doesn’t require you to understand the Autonomy Stack or parse four different domains or distinguish between a framework and a category. It tells you exactly what’s happening: you’re in a race, and the finish line is autonomy. Plain and simple.

The moment I saw that clearly, I made the decision. The Race to Autonomy isn’t just a blog series I started in September. It is the unifying identity for everything I build, write, teach, and offer in this moment.

Why This Matters for Leaders

Here’s the practical challenge I’ve been wrestling with. When I explain Kaamfu to a new audience, it’s hard to convey why it matters if the person doesn’t understand the context of the race to autonomy. We are not just a work platform. We are an Autonomous Operating Environment, and that distinction is critical. If you continue running your business on platforms that don’t give you sovereign ownership of your operational data, and that aren’t architecturally committed to preparing you for autonomy, you will be in the same position a year from now that you’re in today. You won’t have the right shoes for the race.

But try explaining all of that in a cold introduction. It requires too much context. People need the frame before they can appreciate the specifics. The Race to Autonomy is that frame.

When someone understands that every organization is moving toward self-management, and that the competitive window for preparing is narrowing, the rest of the conversation becomes natural. Why does your data need to live in one place you control? Because autonomous systems need context to function. Why does your organization need structural readiness before AI can deliver? Because intelligence without architecture produces noise, not progress. Why does any of this matter now? Because the organizations building this foundation today will out-compete those who aren’t.

What’s Next

I am reopening The Race to Autonomy and elevating it from a content series to the central platform for this entire mission. Here’s what that looks like in practice.

The Race to Autonomy is moving to its own dedicated domain RaceToAutonomy.com. It will become the public front door where leaders land, orient themselves, and understand where they stand. We will offer an Autonomy Diagnostic as a structured assessment that measures where your organization sits on the maturity scale, from organizations that haven’t recognized the race exists to those already building autonomous capability. The diagnostic will give you a clear picture of what phase you’re in and what your next practical steps should be.

The Ragsdale Framework will remain the open-source, governing theory as the grounding anchor. Kaamfu will remain the operational platform I suggest to get started. Prospus will remain the transitional services arm we suggest. My personal site will continue to carry the strategic vision and long-arc thinking. But The Race to Autonomy will be the umbrella that ties all of it together and makes the whole picture accessible to anyone encountering this work for the first time.

This is the structural clarification I should have made months ago. The Race to Autonomy was always the right name for what we’re doing. I just needed to live inside the complexity long enough to see that the answer was sitting in front of me the whole time.

Where We Go From Here

What I’ve learned in the past several years is that the hardest part of this work isn’t the technology or the theory. It’s helping leaders see where they actually stand. Most organizations overestimate their readiness because they’ve adopted tools, and most underestimate the structural work required because no one has shown them what “ready” actually looks like.

The truth is, no one knows everything that is going to happen next. Not every tool we’ll eventually need has been built yet. But we know enough right now to guide organizations on practical things they can do today to prepare: consolidate your data, structure your operations, own your workflows, and build the kind of architectural foundation that any future intelligence layer will require.

The Race to Autonomy exists to help you do exactly that. And as the race evolves, as new capabilities arrive and the landscape shifts, we’ll be here evolving with it, updating the map, and helping you take the next step from wherever you are.

…