Chapter 8: Where It Stands Now
5 min read · 1,008 words ·
At 7am on Monday 11 May 2026, WF5 ran for the first time in the Nunlimited instance. Not manually triggered — scheduled, automatic, the way it's supposed to work. Twenty-two posts queued and ready to go. The Telegram notification came through at 7:04. I was getting ready for work and saw it on my phone.
That's not a victory lap moment. It's a "the plumbing works" moment. Different thing entirely.
What actually exists now
Let me do an honest count, because this is the last chapter and it deserves one.
The Zo.E automation system — ten n8n workflows — is running live across both brands. Sales Source Code has its own instance. Nunlimited has its own instance. Both are pulling from NocoDB, both are posting via Upload Post, both are doing the content generation, approval, scheduling, and publishing loop without me needing to sit in front of a screen. The Telegram approval flow works. The analytics tracking works. The dual-base NocoDB setup — SSC base and Nunlimited base, mirrored table structure — is clean.
The Gumroad listing is live. Ten sanitised workflow JSONs, four supporting documents, a single-page HTML setup guide. Anyone who wants to run this system can buy it right now and have everything they need to do so.
Infrastructure cost: under £30 a month. That's the whole thing.
What doesn't exist
No sales. Gumroad listing has been live for a while. Zero buyers.
No audience to speak of. A LinkedIn profile with a few hundred connections, most of whom know me from Computacenter. The content system is publishing into a void — posts are going out, reach is minimal, the algorithm is largely ignoring it, because that's what algorithms do to new accounts with no engagement history.
The nunlimited.com portfolio site doesn't exist. It's planned, not built.
That's the honest list.
What's changed since Chapter 1
Chapter 1 started with three words: "No audience. No product. No list."
Two of those three are still true. The product exists — it's packaged, documented, and on sale. But the audience and the list are roughly where they were. The content system is generating and distributing posts consistently, which is more than existed before. Whether that constitutes progress on the audience problem or just a more sophisticated way of shouting into a quiet room — it's too early to say.
What's genuinely different is the infrastructure. In Chapter 1 I said I had "the beginning of a system." That system is now complete, tested, documented, and running across two brands simultaneously. The build problem is solved. I am no longer sitting here wondering if this is technically feasible. It is.
The problem has changed. That's the thing to hold onto here. The first problem was "can you build an automated content operation in under £30 a month with 4-7 hours a week?" The answer turns out to be yes. The new problem is slower and less tractable: can you build an audience for it?
What Nunlimited actually is
Sales Source Code is the first company. Enterprise sales education — 25-plus content products, eight locales. The content system is running and the catalogue is real.
But Nunlimited is the parent, and it's worth being clear about what that means. The model is this: take a professional domain where the underlying knowledge is systematically underdocumented, build a content and education business around it, run it on AI-first infrastructure, keep the cost base low. Repeat.
The five planned companies after SSC are Customer Success and Expansion, RevOps, Finance Business Partnering, Talent Acquisition, and Legal Ops. Each one follows the same model. Each one is its own brand with its own content strategy and its own audience. Nunlimited is the holding structure and the methodology — the thing that makes the model repeatable.
The goal is £250,000 a year in combined profit across the portfolio. That number would make it possible to leave full-time employment — not because the day job is bad (it isn't), but because it's not what I want to be doing permanently. That's stated plainly, not as a boast. It's just the direction.
There's no timeline pressure. The portfolio site doesn't exist yet. The five companies don't exist yet. But the infrastructure and the first proof of concept do, and that's the actual foundation.
The audience problem is a different kind of problem
Building Zo.E was hard in the way that learning is hard — effort, iteration, a lot of time reading documentation and debugging workflows, and eventually it works. There's a clear feedback loop. You know when it's right because the thing runs.
Audience-building doesn't work like that. The feedback loop is slow, inconsistent, and largely out of your control. You can post consistently and get nothing for six months. You can post one thing that lands and get a spike that doesn't convert to anything. The algorithm, the timing, the network effects — none of it is as responsive to effort as writing code is.
This is the part that chapters five through seven were about, in different ways. And it's the part that continues beyond this series. I don't have it solved. The content system is running. This build-in-public series — eight chapters — is itself part of the distribution strategy. But the honest summary is that the infrastructure is ahead of the audience, and that gap is the main thing to close.
Where this ends
Eight chapters. The starting point to here.
What I wanted this series to be was a build log — not a success story, not a cautionary tale, just a direct account of what it actually takes to build something like this in the hours left over from a full-time job. I think it's been that.
The machine is running. The product exists. The first sale hasn't happened yet. The audience is small. The next five companies are still on a whiteboard.
That's where it stands.
Ta,
James
Founder | Nunlimited
