What I'm actually building, and why

The number is £250,000. That's the target — combined annual profit across the Nunlimited portfolio. Not a moonshot, not a vanity metric. Just the number that, if reached, would make it possible to leave full-time employment.

I want to be clear about what I mean by that, because it's easy to misread. I like my job. I'm not counting down to some escape. I work with interesting clients, do reasonably complex things, and get paid well to do them. There's no great dissatisfaction driving this. What there is, instead, is a question I've been sitting with for a while: what if the income didn't depend on the hours? What if the thing I was building kept running whether or not I was sitting in front of it?

That's the actual goal. Not the number itself — the condition the number represents.

The model, since that's the obvious next question

Sales Source Code is the first company in the portfolio. Enterprise sales education — content products, eight locales, built on AI-first infrastructure. The underlying logic is simple: find a professional domain where the real knowledge is systematically underdocumented, extract that IP, package it into digital products, and run an automated content system on top. Keep the cost base low. Let the system do the distribution work.

The Zo.E automation stack — ten n8n workflows, NocoDB, Upload Post — runs the content operation largely without me. It generates, approves, schedules, and publishes. On a good morning it sends a Telegram notification through to my phone before I've finished getting ready for work. That's the point of it. The goal was never to automate for the sake of it — the goal was to build something that doesn't need me in the room to keep running.

Five more companies are planned after SSC: Customer Success, RevOps, Finance, Talent Acquisition, Legal Ops. Each one is its own brand, its own audience, its own content strategy. Nunlimited is the holding structure and the methodology — the thing that makes the model repeatable across niches.

This is a systems play, not a personal brand play

Most "build in public" content is about attention. This isn't. I'm not building an audience because I want to be a creator. I'm building one because it's the most efficient way to validate and distribute what I'm making. The goal is a portfolio that generates revenue without requiring my ongoing presence. The audience is a means to that, not the end.

That distinction matters to me. I have no interest in performing. I'm not trying to grow a following. I'm trying to build infrastructure — digital products sitting on automated distribution rails, compound quietly in the background, across six professional niches. If the build-in-public content helps people who are trying to do something similar, that's a good side effect. But it's not the primary goal.

The primary goal is time. Not working less hard — I'll probably always work hard at something. But building things that don't require me to be present every moment to keep them running. The difference between income that depends on your hours and income that doesn't is not a difference in effort. It's a difference in architecture.

Where it actually stands

The machine is running. The product exists — ten documented workflow JSONs on Gumroad, live and available. The content system is publishing consistently across both brands. Infrastructure costs under £30 a month.

No sales yet. Small audience. The nunlimited.com portfolio site doesn't exist yet. The five planned companies are still on a whiteboard. The build problem is solved; the audience problem is not. Those are different problems and the second one is slower and less tractable than the first.

I'm stating that plainly, not as a disclaimer and not as false modesty. It's just where the thing is. The infrastructure is ahead of the audience, and closing that gap is the main work now.

£250,000 a year. Six companies. One methodology. No timeline pressure.

That's the direction.

Ta,

James
Founder | Nunlimited