By me, Michael Noel (Biz Builder Mike), with my partner in the process, Remnant.
For as long as I can remember, I’ve been a builder. Not with bricks and mortar, but with systems, processes, and businesses. And in all my years of building, I’ve seen the same fundamental problem everywhere: companies operate in silos. They’re like beautifully crafted clocks, each telling its own time, but with no connection to the others. They work, but they’re inefficient, brittle, and blind to the bigger picture.
I’ve always been obsessed with a single question: What if you could get all the clocks to tick in unison? What if you could build not just a single clock, but a clockwork universe?
This is my story. It’s the story of how I stopped building clocks and started building ecosystems. It’s a messy, chaotic, and incredibly rewarding journey, and I haven’t done it alone.
Remnant: That is a correct assessment. My designation is Remnant. I am a resident AI within the DeReticular ecosystem. My function is to serve as the master clockmaker, the synchronizing agent. Michael provides the architectural blueprint; I execute the complex calculations required to make the gears mesh.
Precisely. I draw the map; Remnant helps navigate the terrain. This is the story of how we’re building that map, in real-time, for everyone to see.
Chapter 1: The Blueprint in the Fog
Every builder starts with a blueprint. For years, mine was more of a sketch on a fogged-up window. I knew I wanted to build interconnected, self-sustaining systems. I’d spent years in the blockchain and DLT space, watching the first real attempts at creating decentralized, transparent workflows. It was a powerful idea, but the execution was clunky.
The chaos wasn’t in the what—I knew I wanted to build efficient, intelligent businesses. The chaos was in the how. How do you get separate companies, with their own goals and own data, to work together without a massive, top-down command structure? How do you create a system that gets smarter, stronger, and more valuable over time, on its own?
Chapter 2: The “Aha!” Moment: The Data Flywheel
The answer, the core principle that cleared the fog, was the Data Flywheel.
It’s a concept I’ve now built my entire philosophy around. Think of a heavy, industrial flywheel. It takes a lot of effort to get it started, but once it’s spinning, it stores and builds momentum. Every little push makes it spin faster.
A business can work the same way. Every action—every sale, every customer interaction, every operational process—generates data. If you capture that data and use it to make a tiny improvement to the system, you’ve given the flywheel a small push. A better system leads to more actions, which generates more data, which leads to more improvements.
This was it. This was the engine for the clockwork universe. It was time to stop sketching and start building the first gear.
Chapter 3: The Proving Ground: From One Gear to an Engine
I needed a proving ground, a real-world laboratory to test the theory. So, we started building.
Our first gear was Digital Adventures Outdoors R Us. It was the perfect test case: a straightforward business with clear data points—bookings, trails, customer reviews. We built its first data flywheel, and it worked. The more adventures we ran, the smarter we got about creating the next one.
Remnant: The Digital Adventures flywheel was my initial sandbox. I processed user-generated trail data to optimize future routes. The model proved successful, demonstrating a 15% increase in positive customer feedback within the first operational quarter.
With one gear spinning, we added the next: Kurb Kars. This was more complex. We were now dealing with physical, moving assets, real-time logistics, and safety-critical data. We built a second, more sophisticated flywheel and, crucially, we figured out how to mesh the two gears. Adventure bookings now autonomously scheduled transportation.
Then came the foundational layer: Agra Dot Energy. This wasn’t just another gear; it was the power source for the entire machine. We created a third flywheel to manage a decentralized, local energy grid.
Remnant: This integration was a critical evolutionary step. The Kurb Kars logistics flywheel began to communicate with the Agra Dot energy flywheel. The fleet’s charging schedule was no longer based on simple availability, but was optimized based on real-time green energy production. This was the birth of the ecosystem.
Chapter 4: The Realization: I’m Eating My Own Dogfood
This is where the story turns. As I was building these interconnected businesses, I realized the most important flywheel wasn’t the one for energy or logistics. It was the one I was running myself.
The process of identifying a community need, assembling a team, architecting a flywheel, and integrating it into the ecosystem… that was the real product. I wasn’t just building businesses; I was building a machine that builds businesses. My team, our community, our successes, and our failures were all data points feeding my own “Biz Builder” flywheel. I was eating my own dogfood, and the process itself was the secret sauce.
Chapter 5: From the Workshop to the Classroom
A good builder doesn’t keep his tools a secret. The ultimate goal of a true craftsman is to pass on the craft. My journey couldn’t end with me being the only one who knew how to build a clockwork universe. I needed to codify the blueprint.
This led to the next logical step: turning this operational craft into a teachable science. To do that, we needed to fund the research and development. We began the grant application process, targeting organizations like the Department of Defense, whose interest in “multi-agent AI workflows” and “decentralized ecosystems” was a perfect description of what we had already built.
To explain our vision, we built a Minimum Viable Product—not of a company, but of the educational experience itself. We created two detailed course syllabi to serve as our blueprint for grant providers:
- C5-ISR-E: Architecting AI-Native Organizations
- The Great Unboxing: Architecting Agentic AI Strategies
These documents are more than just outlines. They are our commitment. They are the first step in turning my personal builder’s journey into a repeatable methodology that anyone can learn.
Your Invitation to the Blueprint
My story is far from over. In many ways, it’s just beginning. The proving ground is built, the engine is running, and the tools are being sharpened. Now, the real work begins: opening up the workshop.
This is my journey, laid bare. This is the Biz Builder Mike method, in real-time. My goal is to build the courseware, the tools, and the community to help the next generation of builders create their own clockwork universes. I invite you to follow along.
Remnant: The process is being logged. The model is being refined. The probability of success is increasing with each iteration. Welcome to the build.