What does Adam Roozen do?

Adam Roozen builds technology systems and trades his own capital. He is CEO of Isotropic Solutions, which builds governed agent workforces for businesses, enterprises and national institutions. He also runs business automation experiments testing how much can operate without people, and takes a small number of advisory engagements each year.

What is Adam Roozen's background in trading?

Adam has traded his own capital for ten years, and it is his primary income. He started in forex around 2016, added crypto in 2018, and crypto became the main focus from 2021, with equities and index futures alongside it. He trades theses rather than tickers, and has built software around his own research process. He trades only his own capital. He does not manage outside money, is not a financial adviser or fund manager, and publishes no performance figures.

What is Adam Roozen's background in digital technology?

Adam has worked through every consumer technology wave since the mid-nineties. He built transactional websites in high school, before payment processors existed, and had to write his own card encryption. He joined Walmart as a programmer analyst during the early dot-com build-out, ran e-commerce marketing at Sam's Club through the mobile wave, scaled a global commerce agency through the social and cloud waves, worked in tokenized and blockchain systems, and now builds autonomous agent systems.

What is Isotropic Solutions?

Isotropic Solutions was founded by Seran Devaraj, and Adam Roozen joined afterward as CEO. The company builds governed agent workforces: agents do operational work, a person signs off, and every decision keeps its evidence. Autonomy is earned a rung at a time, from drafting, to recommending, to acting under review, to running inside written limits. The second half of the work is preparing businesses to be read and transacted with by other companies' AI systems.

How is Adam different from a traditional technology consultant?

Adam runs the systems he would otherwise be advising about. Two of his companies operate with no employees, his trading runs on software he wrote, and Isotropic Solutions ships agent systems into banks and commodity traders. He has also spent nearly 30 years operating: building early e-commerce at Walmart, running e-commerce marketing for a $700M to $1B channel at Sam's Club, and co-founding a 200-person agency.

What is Adam Roozen's background in e-commerce?

Adam led e-commerce marketing and operations at Sam's Club (Walmart) while the channel grew from $700M to $1B in annual revenue. He then co-founded Echidna and scaled it to more than 200 people, serving blue-chip retailers including Kohl's, Michael Kors, Toys 'r Us, Lowe's, Cracker Barrel, Aveda, Jelly Belly, Wolters Kluwer, Dubai Duty Free, Liverpool in Mexico and Mr. Price in South Africa.

Who does Adam work with?

The work spans four sizes. One person, in the zero-employee companies he runs himself. Owner-operated businesses between $5M and $50M, through W3 Strategic Management Services. Enterprises, such as ETG, a global agricultural commodity trader turning over $8B across 250 business units. And national institutions, including the Central Bank of Oman and Vietnam International Bank.

How do I start working with Adam?

Adam takes a small number of advisory engagements each year, and works directly with whoever is accountable rather than through a team of associates. When an owner-operator needs the cash more than he needs the invoice, he will take revenue share instead of a fee. The best first step is a short note through the contact page describing what you are up against.

The Clock Gap

On boards, technology transformation, and the trouble with watching long work on a short clock

Boards are supposed to oversee technology transformation. From what I can tell, a lot of the time they end up overseeing a quarterly report about technology transformation. The second is what usually ends up in front of them.

Here's how it usually seems to go. The technology decisions get handed over, whole, to the CTO or the CIO. The spend gets carried as a cost center, so the work mostly shows up on the books as money leaving. And the build itself runs long - transformation works on a horizon that sits well outside the board's reporting rhythm. An AI infrastructure build started today might not turn into advantage until something like 18 months from now. The board's measuring, meanwhile, is typically quarterly. None of those habits is strange on its own. I keep finding all of them in the same room, though, and I think they add up to one pattern.

Let's look at how that works, and then take it off boards.

The Clock Gap

Delegation, cost framing, and timing look like three separate habits. I think they're one habit in three outfits. The one habit is this:

"the clock gap - the distance between the clock the work runs on and the clock the watcher runs on"

Every long project runs on its own clock - how long until the thing actually becomes valuable. And every watcher runs on a clock too - how often they check, and what they're able to see when they do. The trouble isn't either clock by itself. It's the distance between them, especially when the watcher has handed away the context they'd need to interpret what they're seeing.

The Boardroom

Let's put two people inside it and walk through how it runs. Dana is the CTO. Marcus sits on the board. The company is building AI infrastructure.

(a) Dana brings the transformation plan to the board. Marcus and the other directors approve it, then hand the technology decisions back to Dana entirely. The material is deep and the board has plenty of other things to watch.

(b) Dana starts building. On the books, her build sits in a cost center, so everything she does shows up as money going out.

(d) The advantage shows up something like 18 months after Dana's build starts. So for a long stretch of Marcus's reporting cycles, he's staring at a number that only moves one direction.

Notice that nothing has gone wrong yet. Dana's build might be going great. The problem is that Marcus can't easily tell good progress from bad progress, because the context to read the middle of an 18-month arc was handed to Dana back in step (a). The quarterly report quietly becomes the whole picture. It shows rising cost and no visible benefit, so the board may start treating the build as waste. I'd expect a decent number of good builds get defunded somewhere inside the gap. (I'm guessing there, tbh. But the shape seems familiar.)

The Pattern Elsewhere

Alright. Let's back out away from the boardroom and isolate the clock gap so we can use it elsewhere. Here's a couple non-board examples. First, fitness. You hire a trainer and hand them the decisions - delegation again. Training runs on a long clock; real adaptation takes months. Your measuring, though, is probably weekly, maybe daily: the scale, the mirror, how your jeans fit. People quit inside the gap all the time. The weekly scale shows mostly soreness and expense, not adaptation, so they stop.

Or take a farm rebuilding its soil. Cover crops, lighter tillage, that sort of thing. The first seasons can look worse on paper, with extra seed and messier-looking fields, while the payoff sits years out on the work's clock. An owner checking each season the way a board checks a quarter would see a cost center with a persuasive agronomist attached, not a soil rebuild in progress.

One more. Reading to a kid at night. Any single night shows nothing measurable. The advantage, things like language and attention and comfort with books, lands years later, and you probably couldn't say exactly when it landed. If you measured by the night, you'd probably stop. Maybe that's the point. I'm not sure.

In all three, let's notice what seems to be doing the damage. It isn't the long clock. Skills run long. Soil runs long. Kids run long. That's fine. It's the pairing: short-cycle measuring wrapped around long-cycle work, with just enough context handed away that the short-cycle numbers can't be read properly. I'm still figuring out what to do with that pairing.

Who owns the fix, the builder or the watcher, is the part I can't call. Should Dana get better at translating an 18-month build into pieces Marcus's quarterly report can see, or should Marcus stretch his own clock toward the work's? I suspect the delegation piece matters more than it looks, honestly - a board that kept enough context to read the middle of a build might not need to stretch anything at all. But I don't actually know. It seems like the kind of thing each side only learns by living through the gap once, and I'm not sure there's much of a shortcut around that.