My Journey to Wren Sites, So Far

I didn't start Wren Sites because I had it all figured out. I started it because I'd got to a point where "figuring it out later" wasn't good enough anymore.

For the best part of twenty years I've worked in further and higher education — writing qualifications, assessing, quietly making sure standards actually mean something. It's work I'm good at and work I care about. But somewhere along the way I noticed I was building other people's systems and never my own. Good income, sure. Good pension, eventually. Not a good answer to the question I kept asking myself:

If nothing changes, is this actually the life I want?

That's the honest starting point. Not a lightning bolt, not a five-year plan drawn up on a napkin — just a slow, persistent feeling that I wanted more room to build things myself, more control over my own income, and a life that felt like it was mine rather than one I was renting from a job.

Why now

I've been given a bit of breathing space recently — time that would otherwise disappear into the day job — and I decided to spend it properly rather than just resting. That's what Wren Sites actually is: not a leap off a cliff, but a genuine, deliberate test of whether I can build something of my own while I still have the safety net of my professional background underneath me.

That matters to me, and I think it should matter to anyone reading this who's considering the same thing. You don't have to burn the boats to find out if you've got something. You just have to actually try, properly, with real clients and real deadlines, and see what happens.

What I'm actually building

Wren Sites started as web design — build a site, make it look good, hand it over. It's grown into something closer to websites and systems: I don't just want to make something look right, I want to make the boring parts of running a small business quicker and less painful. A client website manager tool I built recently taught me that the systems side is where I can genuinely differentiate myself — twenty years of understanding how businesses actually operate day to day isn't nothing.

Alongside that, I've been teaching myself everything from deployment pipelines to AI-assisted workflows, mostly by being nosy and taking things apart to see how they work. I'm not from a coding background. I'm from a "notice a problem, get curious, figure it out" background, which turns out to be a surprisingly good foundation for this.

Skills, and the people who go with them

The technical side has been the visible part, but the bigger shift has been professional. Running a business on your own means you have to build a network almost from scratch — other founders, other freelancers, people who understand the specific flavour of uncertainty that comes with client work and inconsistent income. I've been deliberately putting myself in rooms (and inboxes, and courses) with people doing similar things, because it turns out that's how you learn the parts nobody writes documentation for: how to price a job properly, how to spot a client relationship that's about to go wrong, how to say no to work that isn't right for you.

I'm still early in building that network. I expect it to be one of the most valuable things to come out of this whole process — arguably more valuable than any individual client.

Where things actually stand

I won't pretend this is all going smoothly, because it isn't, and I don't think pretending helps anyone. There's genuine uncertainty in this — about income, about whether the current idea I'm scoping is the right next move, about how much of my time should go where. I'm keeping other doors open rather than pretending this is the only path, and I think that's a sign of taking it seriously, not a sign I don't believe in it.

What I do know: I'm building real things, for real clients, and learning faster than I expected to. That's enough to keep going on.

What this blog is

Going forward, I'm going to write here weekly about what's actually happening — the client work, the technical decisions, the wins, the ones that didn't go to plan, and the honest parallel-track thinking about what else this could become. Not a highlight reel. A working record.

If you're a business owner curious about what you're getting when you work with someone who builds things this way, or if you're somewhere in your own version of this journey — welcome. I'm glad you're here.