Call or Text (904) 822-1035

I Built the Machines. Now They Run Me.

March 12, 2026
12,Insights

I’ve spent 20 years building things. Websites, systems, teams, processes. Two decades of learning how things work by doing them wrong first and then doing them right.

Now I’m trying to pour all of that into AI. Every system, every shortcut, every lesson learned. Into Obsidian vaults, CLAUDE.md files, agent configs, prompt libraries, daily notes, dashboards, carry-forward lists. Into the machine.

And it’s completely overwhelming.


Here’s the paradox nobody talks about: AI is supposed to speed things up. Organize. Create efficiency. And it does, in flashes. You get these moments where something clicks and you think this is it, this is the future, I’m free.

You build a workflow that saves you hours. You spin up an agent that handles something you used to do manually. You feel the leverage.

Then you wake up the next morning and there’s a new model. A new tool. A new feature that makes yesterday’s setup feel incomplete. And you’re back at the keyboard, reorganizing, restructuring, optimizing the optimizer.

Every day it’s a little bit more.

The paradox: AI promises efficiency and freedom. But every day there’s a new model, a new tool, a new reason to restructure. The thing that’s supposed to speed you up becomes another thing to keep up with.


The Treadmill Never Stops

Let me give you a concrete example. Last month I spent three days setting up a perfect agent workflow. Tony, my chief of staff agent, handles all my task coordination. Sil, my architect, does research and planning. Christopher, my content capo, writes everything.

It was beautiful. Clean handoffs. Clear responsibilities. The kind of system that made me feel like I’d finally cracked the code.

Then OpenClaw updated. New capabilities for agent memory. New ways to structure context. New patterns for delegation that made my three-day setup look like amateur hour.

So I spent another two days rebuilding. Better this time. More sophisticated. And it was, genuinely, an improvement.

Until the next update.

That’s the treadmill. You’re never done. There’s always a better way. A new model that’s 20% faster. A new feature that unlocks something you couldn’t do before. A new workflow someone shared on Twitter that makes your current setup look antiquated.

And if you’re a builder, you can’t ignore it. Because ignoring it means falling behind. And falling behind means watching someone else do in two hours what takes you six.

So you keep running. Faster. Always faster.

The AI treadmill: You’re never done. There’s always a better model, a new feature, a workflow that makes yours look outdated. If you’re a builder, you can’t ignore it. So you keep running. Faster. Always faster.


Outwork Everybody (Even When You Don’t Have To)

I keep telling myself: keep grinding, keep pushing. That’s the muscle memory. That’s the Jersey in me, the part that doesn’t know how to stop. Twenty years of “outwork everybody” doesn’t turn off just because you have a copilot now.

Here’s what that actually looks like:

It’s 11 PM. I just put the kids to bed. I’ve already worked a full day at my day job. Already handled client calls. Already shipped a blog post. Already reorganized my Obsidian vault (again). The logical thing to do would be to close the laptop. Watch TV. Go to sleep.

Instead, I’m setting up a new agent workflow. Building my own tools because I had an idea earlier and if I don’t implement it now, I’ll forget. Or worse, someone else will figure it out first and I’ll feel like I missed an opportunity.

It’s 6 AM on Saturday. The house is quiet. My wife is still sleeping. The kids won’t be up for another hour. I could sleep in. I could make coffee and sit on the porch. I could do nothing.

Instead, I’m at my desk, testing a new prompt structure. Because I couldn’t stop thinking about how to make my research agents more efficient and the only way to know if it works is to try it.

It’s Wednesday afternoon. I have three hours between meetings. I could take a break. Go for a walk. Decompress.

Instead, I’m diving into documentation for a tool I don’t need yet but might need next month. Because staying ahead means learning things before you have to.

That’s what “outwork everybody” looks like. It’s not heroic. It’s not sustainable. It’s just compulsive. The inability to stop. The fear that if you’re not moving forward, you’re falling behind.

And AI doesn’t fix that. If anything, it makes it worse. Because now there’s always something new to learn. Always another optimization to chase. Always a better way just around the corner.

Outwork everybody: It’s 11 PM and you’re setting up workflows instead of sleeping. It’s 6 AM Saturday and you’re testing prompts instead of resting. It’s Wednesday afternoon and you’re learning tools you don’t need yet. It’s not heroic. It’s compulsive. And AI makes it worse.


The Drive That Got You Here

But I’m starting to wonder if that’s the trap.

The drive and the relentlessness that got me here, the same energy that builds client sites at midnight, that ships blog posts at 2 AM, that can’t leave a task list alone, might be the exact thing preventing me from getting to the point where I have breathing room.

AI promises freedom. But freedom requires letting go. And letting go is the one thing builders like me are worst at.

Because what if you let go and someone passes you? What if you take a break and miss the boat? What if you slow down and everything you built becomes irrelevant while you weren’t paying attention?

Those aren’t rational fears. I know that. But they’re real.

I’ve seen what happens to people who stop learning. I’ve seen developers with 20 years of experience become obsolete because they refused to adapt. I’ve cleaned up messes from agencies that got comfortable and stopped innovating. I know what complacency looks like and I’m terrified of becoming that.

So I don’t stop. I can’t stop. The treadmill keeps running and I keep running with it.

Trying to organize 20 years of experience into AI systems right now can be completely overwhelming. You’ve got to give yourself grace. A daily constant reminder of “keep grinding, keep pushing,” but it’s funny at the same time.

I wonder if that ultimate freedom is ever going to come, or if it comes at a cost, or if it’s just my personality. My drive and my relentlessness are actually not allowing me to get to that point where I have a little breathing room.

The trap: The drive that got you here might be the exact thing preventing you from experiencing the freedom AI promises. Freedom requires letting go. That’s the one thing builders are worst at.


What Gets Lost in the Chase

Here’s what I’m realizing: in the rush to capture everything, I might be missing the point.

I spent two hours last week trying to document a process for how I evaluate client sites. The way I can look at a homepage and immediately know what’s wrong. The instinct that comes from seeing a thousand bad sites and learning to recognize the patterns.

Two hours of trying to turn instinct into instructions. Trying to make the implicit explicit. Trying to capture 20 years of pattern recognition in a markdown file.

And at the end of those two hours, I had a document that was technically accurate but completely lifeless. It captured the what but not the why. The steps but not the judgment. The process but not the art.

Because some things don’t translate. Some knowledge lives in your hands, your gut, the way you look at a problem and just know. You can’t teach that to an AI. You probably shouldn’t try.

But the treadmill says you should. The promise of efficiency says if you can’t automate it or document it or systematize it, you’re not doing it right. You’re leaving value on the table.

So you keep trying. Keep documenting. Keep building systems for things that maybe don’t need systems.

And in the meantime, you’re not actually doing the work. You’re building infrastructure to do the work faster later. Except later keeps getting pushed back because there’s always more infrastructure to build.

That’s the other side of the paradox. The tools that are supposed to free you up end up consuming all your time. The systems that are supposed to make you efficient become the thing you spend all your efficiency building.

What gets lost: You spend hours documenting instinct. Trying to capture 20 years of pattern recognition in a markdown file. But some knowledge lives in your hands, your gut. You can’t teach that to AI. And while you’re building systems to work faster later, you’re not doing the actual work now.


Grace (The Thing I Keep Forgetting)

So where does that leave us?

I think it starts with grace. Giving yourself permission to not have it all figured out. Permission to have a messy vault, an incomplete system, an agent that’s been idle for 19 days. Permission to say “I’ll get to that in April” and actually mean it.

The 20 years of experience aren’t going anywhere. They don’t expire because you didn’t capture them in a markdown file today. They’re in your hands, your instincts, the way you look at a client’s site and immediately know what’s wrong. That doesn’t need to be in the machine to be valuable.

Maybe the real efficiency isn’t organizing everything into AI. Maybe it’s knowing what doesn’t need to be organized at all.

But that’s hard for people like me. Because knowing what to skip means trusting that it’s okay to skip it. And trust doesn’t come naturally when you’ve spent 20 years outworking everyone to stay ahead.

Grace means accepting that you’re good enough right now. Not in six months when the system is perfect. Not when you’ve documented everything. Not when every workflow is optimized. Right now. Today. With the messy vault and the incomplete setup and the knowledge that’s still just in your head.

Grace means recognizing that the pursuit of perfect efficiency might be making you less efficient. That the time you spend optimizing could be time you spend building. That the freedom you’re chasing might already be here if you’d just stop running long enough to notice.

Give yourself grace. Permission to have a messy vault. Permission to say “I’ll get to that later” and mean it. The 20 years of experience don’t expire because you didn’t organize them today. They’re in your hands, your instincts. That’s already valuable. Right now. Today.


The Messy Middle

I don’t have this figured out yet. I’m still burning tokens, still reorganizing my vault at midnight, still chasing that perfect setup that probably doesn’t exist.

But I’m learning to be messy, not sloppy. To push hard without losing sight of why I’m pushing in the first place. To remember that the tools are supposed to serve me, not the other way around.

Keep grinding. But also, breathe.

The freedom paradox isn’t going away. The tools will keep getting better. The models will keep updating. There will always be one more thing to optimize. One more workflow to build. One more system to document.

But maybe freedom isn’t on the other side of perfect organization. Maybe it’s in the messy middle, where you’re doing great work with good-enough systems, and you’re okay with that.

Where you can look at an agent that’s been idle for 19 days and not feel guilty. Where you can skip a model update and not feel like you’re falling behind. Where you can close the laptop at 11 PM and trust that tomorrow is soon enough.

That’s where I’m trying to land anyway. Some days I get there. Most days I don’t. But I’m trying.

The messy middle: Freedom isn’t on the other side of perfect organization. It’s in the messy middle. Great work with good-enough systems. An idle agent without guilt. A skipped update without fear. Closing the laptop at 11 PM and trusting tomorrow is soon enough.


What I’m Learning (Slowly)

The experience is already there. It’s already valuable. You don’t have to capture it all to use it.

The instinct that comes from 20 years can’t be documented. It just is. And maybe that’s okay. Maybe some things are supposed to live in your gut instead of your vault.

The tools are incredible. The leverage is real. The efficiency is possible. But only if you can stop optimizing long enough to actually use what you’ve built.

Grace isn’t weakness. It’s wisdom. It’s recognizing that the relentless drive that got you here needs to be balanced with the ability to stop. To rest. To trust that you’re already good enough.

The freedom paradox is real. But it’s not insurmountable. It just requires a different kind of discipline. Not the discipline to keep grinding. The discipline to stop. To breathe. To let go.

That’s the work now. Not building more systems. Learning when to stop building and start living in them.

I’m not there yet. But I’m trying. And maybe trying is enough.

Written by

Will Schmierer

Seasoned developer with 20+ years in digital. I build with WordPress, engineer with Go High Level, and obsess over the details. I have led rebuilds for the NBA, Microsoft, Campbells, and more. After a stroke at 37 and an MS diagnosis, I rebuilt myself from a wheelchair to running marathons. That same mindset drives everything I build. No shortcuts. No nonsense, No Bullshit, No excuses, Just Results!