Building in Public: Why I'm Starting lewie.io

Why Now?

I've been building businesses for years — Bloodstone for AI consulting, Byter for hospitality marketing, Red Cardinal for property, plus SaaS products like Bytable, LittleSpoon, LUFU CRM, and Stoneforms. A publisher network running dozens of sites. Each one has its own brand, its own audience, its own purpose.

What none of them had was a central place where I could talk about all of it — the decisions, the failures, the systems, and the lessons.

That's what lewie.io is for.

The Problem With Multiple Ventures

When you run multiple businesses, people only ever see one slice. Byter clients know me as the marketing guy. Bloodstone clients know me as the AI guy. SaaS users might not know I exist at all.

But the reality is that everything connects. The automation systems I build for Byter inform the product design at LUFU CRM. The property analysis tools at Red Cardinal use the same AI patterns as the content pipeline for the publisher network. The tech stack is shared. The thinking is shared.

I wanted a place where I could show the full picture — not to brag, but because the connections between ventures are where the most interesting lessons live.

What You Can Expect

Here's what I'll be writing about:

• Behind-the-scenes breakdowns — real workflows, real numbers where I can share them, real decisions and why I made them
• Technical deep-dives — how I build with Next.js, Supabase, Claude API, and n8n. Actual code, actual architecture, not theoretical fluff
• Business lessons — what I've learned running multiple ventures simultaneously, including the stuff that went wrong
• AI and automation — practical applications of AI in real businesses, not hype pieces about AGI

Every post will be something I'd want to read myself. Practical, specific, and honest.

Building in Public (My Version)

"Building in public" has become a bit of a cliche. People tweet their MRR numbers and call it transparency.

My version is different. I'm not going to share vanity metrics for engagement. I'm going to share how things actually work — the systems, the thinking, the tradeoffs. If I can write a post that saves someone a week of trial and error, that's a win.

I'm also doing this because writing forces clarity. When I have to explain a system well enough for someone else to understand it, I understand it better myself. Some of my best business decisions have come from the process of writing things down.

Why a Personal Site?

I could have posted on LinkedIn or Medium or Substack. I considered all of them. But I build things for a living, and I wanted this to be mine — my domain, my design, my data.

lewie.io runs on the same stack as everything else I build: Next.js, Supabase, Vercel. The blog posts live in a Postgres database. The site will evolve as I add more features — project showcases, a ventures page, maybe some tools and resources down the line.

It's also a reference implementation. When I write about my tech stack, you can view source on the very site you're reading and see it in action.

What This Isn't

This isn't a course. I'm not selling a community or a coaching programme. There's no funnel here.

It's a place where I write about what I'm building and what I'm learning. If that's useful to you, brilliant. If not, no hard feelings.

Let's Go

First posts are live today. I'll be writing regularly — not on a rigid schedule, but consistently. The best way to keep up is to check back or follow along on socials.

If you're building something too, I'd genuinely love to hear about it. Reach out anytime.

Time to build.