Gary Vee Was Right. The Execution Layer Was Missing.

Gary Vee stood in front of a room full of business owners and told them to post on eight platforms every day. Most people nodded. Most people went home and did nothing. The advice was right. The execution was the problem.
I watched the clip and had the same reaction most developers do: he is correct about the why, and completely silent on the how. That is not a criticism. It is just an honest description of the gap he was not hired to close.
Gary has VaynerMedia. 800 people producing 412 pieces of content across 81 handles. When he says "just post more," there is an enormous machine behind that sentence. He did not build it overnight, and it cost a lot of money. For most of us, that machine does not exist. We have a phone and good intentions.
He also said something that landed harder: AI is about to eat 20 to 30 percent of Google search traffic. That spikes ad costs even if Google does not die. Organic content is not optional anymore. It is an insurance policy. That part is worth sitting with, because it changes the math on whether showing up consistently is worth the effort. It is not a nice-to-have. It is the hedge.
So I decided to test that premise on myself.
This site is not a media company
benenewton.com is where I write about commerce frontend development, share what I am working on, and document the things I keep having to explain to clients and colleagues. I work in TypeScript, React, Next.js, and Angular. Commerce frontend is a narrow enough niche that consistent writing about it actually compounds over time. Every post is a reference. Every piece of thinking I work through in public saves me time the next time someone asks the same question.
The problem was never ideas. I have notebooks full of half-formed thoughts and things I want to write about. The problem was the distance between a thought and a published post. The friction was not in the writing itself. It was in everything around it. Figuring out what to say and in what format. Adapting the same idea for LinkedIn versus X versus a blog post. Keeping the voice consistent so it actually sounds like me. Copy-pasting between tools. Reformatting. Second-guessing. Three hours later, something that should have taken twenty minutes was still sitting in a draft.
I have shipped production software for years. I have never shipped a feature that way. When something is that slow and that painful, the answer is not to try harder. The answer is to fix the process.
Content is an infrastructure problem
Gary called it "the science of the art." What he meant, I think, is that building an audience is not just about talent or ideas or motivation. It is about the system underneath. Most people fail at consistency not because they are lazy but because they are running a manual process where there should be an automated one.
When I started thinking about it that way, the solution became obvious. I needed to solve for the friction, not push through it.
The system I landed on is straightforward. I have conversations. Most of my best thinking happens when I am talking through a problem, whether that is with Claude, with ChatGPT, or with a client. Those conversations are full of real insight. The problem is that insight usually disappears into a chat window. Now it does not. Those conversations become the raw material for posts. The voice constraints I have set up mean the output sounds like me, not like a generic AI writing assistant. The publishing layer means I do not touch a clipboard or log into five different platforms.
Right now I am on X and LinkedIn, and I am publishing here on the blog. That is not because those are the only platforms that matter. It is because that is where I started, and I wanted to validate the system before expanding it. More platforms are coming. But even at this stage, the difference is real. I am publishing consistently. The posts sound like me. I am not spending my evenings doing repetitive formatting work.
Why I built this on my own site first
The tool I am using is called BlackOps. I built it. That is relevant context, not a disclosure I am trying to bury. benenewton.com is the proof of concept. If this system does not work for a solo developer running his own site, it does not work for anyone. I am not going to sell something I have not tested on myself at full intensity.
The publishing infrastructure lets AI assistants manage content programmatically. That sounds abstract until you see what it means in practice: I can go from a conversation with Claude to a drafted and published post without opening a browser or touching a CMS manually. The voice is constrained so nothing sounds generic. The distribution is handled. The context from what I have already written informs what comes next, so nothing feels random.
That is the execution layer Gary was not talking about. That is the infrastructure most people do not have.
The gap between "I should post more" and "I actually posted something good today" is an engineering problem. Engineering problems have solutions. BlackOps is the solution. The infrastructure I built for myself is the same infrastructure you get when you sign up. You do not have to build anything. You just have to stop running a manual process where there should be an automated one.
What consistent actually looks like at this stage
I want to be specific here, because vague promises about consistency are exactly the noise people are sick of hearing.
I am not producing 412 pieces of content across 81 handles. I do not have 800 people. I am one developer with a specific area of expertise and a system that removes the friction between a thought and a published piece of writing.
What that looks like right now: blog posts go up on this site. Those posts and the conversations behind them feed into threads on X and posts on LinkedIn the same day. The voice is consistent because there are constraints in the system, not because I am carefully editing everything by hand. The ideas are mine because the conversations that generate them are mine. The distribution is handled.
That is the whole system. It is not glamorous. It is engineering.
Gary Vee was right. Organic attention is free. The opportunity is massive. Most people are leaving it on the table not because they do not want it but because they do not have the infrastructure to pursue it. That is the problem I am solving, starting here, on this site, with my own content, before asking anyone else to trust it.
I wrote this post inside BlackOps, my content operating system for thinking, drafting, and refining ideas — with AI assistance.
If you want the behind-the-scenes updates and weekly insights, subscribe to the newsletter.


