The only content strategy that actually fits 4 hours a week
5 min read · 1,005 words ·
A few months into building Nunlimited, I ran the wrong brand colours for three days before I noticed. The hex code was off by a few digits — the difference between a warm off-white and something slightly clinical — and it had been live on every published post during that stretch. Nobody flagged it. I only caught it because I was doing a design review for something else entirely.
I wrote about it. Took ten minutes. That became a post.
That's the content strategy. Not a formal strategy, really — more like a reframe. Stop trying to manufacture things worth saying and start writing down the things that are already happening.
Where the expert trap actually lives
There's a version of content creation advice that tells you to wait until you're credible enough. Build expertise first, share it second. And for some things, that's right.
Sales Source Code is built on twelve years of B2B enterprise sales. Client Director at Computacenter. Flutter, Entain, procurement reviews, six-figure buying committees, deals that took eight months and ones that closed in a single call. SSC content comes from that. I write about qualification frameworks and buying committee dynamics because I've lived them — and because most sales training content gets that stuff wrong in very specific ways I can name. That's credential-first content, and it works because I'm not a beginner.
Nunlimited is the opposite. I'm building an AI automation business in public whilst holding down a demanding day job and raising a family. I have no track record here. I have no case studies. I don't know yet whether any of this will work.
The expert trap for Nunlimited would be pretending I do.
The difference between a lecture and a dispatch
When I think about the build-in-public series — the Chapters — the ones that land best aren't the ones that explain something I've mastered. They're the ones that describe something I worked out three days ago, or a decision I'm still not sure was right, or a number that hasn't moved the way I expected.
There's a difference between a teacher lecturing from a finished curriculum and a student sharing notes from this week's class. The student version is more honest, more specific, and — if you're in a similar position — often more useful. Not because it's more authoritative. Because it's more current.
Chapter 7 was about building Zo.E. I didn't write it because I'd finished building Zo.E and could now explain the definitive approach. I wrote it in the middle of the build. The webhook that kept timing out. The Telegram approval flow that I wired backwards the first time. The moment when the first end-to-end run completed without me touching it. Those details came from being in it, not from looking back on it.
That's what the Chapters are. Honest dispatches. Not tutorials.
The machine feeding itself
There's a structural reason this approach works beyond just being more authentic.
Building Zo.E generates content about building Zo.E. The struggles with n8n's JSON parsing, the decision to use NocoDB over Airtable, the week I rewrote the content brief prompt four times — all of that is documentation that becomes posts. Not manufactured posts. Not "content ideas." Records of what actually happened.
And the people who find those posts useful are exactly the people building similar things. Entrepreneurs trying to automate on a limited time budget. People who've heard about n8n but haven't committed to learning it. People in a day job wondering whether the side build is worth the effort. Those are the Nunlimited audience.
The loop is: build the thing → document the build → attract the people who want to build the same thing → those people are the audience for everything that comes next.
You can't engineer that loop by sitting down and asking "what content should I create today?" You can only close it by doing the work and writing it down whilst it's still real.
What gets documented
To be concrete about it: the Nunlimited build-in-public series covers build costs, tool choices, what broke, what worked, time invested, and Gumroad revenue — including the zeros. Especially the zeros.
The first Gumroad listing sat at £0 for longer than I expected. I wrote about that. Not to perform humility, but because the gap between "the product exists" and "the product earns" is exactly the territory most build-in-public content skips. Everyone shares the first sale. The silence before it is more instructive.
Failures generate the most useful content anyway. A webhook timing out has a specific cause, a specific fix, and a specific lesson. A post that says "n8n webhooks time out when you do X, here's what I did about it" is more searchable, more useful, and more honest than a post about how powerful n8n is. The polished take on a tool is everywhere. The failure story, properly documented, is rarer.
Why this is the only strategy that survives the time constraint
The reason most content plans collapse isn't lack of ideas. It's that manufactured content requires manufactured insight — and manufactured insight takes time you probably don't have.
If I sat down every Sunday and tried to generate original things to say about entrepreneurship, AI automation, or building a business in public, I'd run dry inside a month. Insights you haven't earned yet don't appear on demand.
But if I spend Tuesday building something, the material for Wednesday's post is already there. If a workflow breaks on Thursday, that's a post. If a pricing decision turns out to be wrong, that's a post. If three months of consistent publishing produces subscriber numbers that are still modest, that's a post.
The build generates the content. The content documents the build. On four to seven hours a week, with a day job and a family, that's not just the best strategy. It's the only one that actually fits.
Ta,
James
Founder | Nunlimited
