Starting Soren Lab: What I'm Building, and Why

There's nothing to click on yet. No live site, no case studies, no finished product. What I do have is a plan, a goal, and the first real evidence that I've started, so that's what this post is.

I want to document this from the actual beginning, not just drop a finished site one day with no context behind it.

What Soren Lab is

Soren Lab is a full-stack web studio. I build complete websites and digital systems front end, back end, the systems that keep a site running well after launch for people and businesses that need more than a template with their name on it.

Right now, that's the core of it: full-stack websites, built properly, for clients who need someone to handle the whole thing.

The bigger goal

The website work is the starting point, not the ceiling.

The goal is to grow Soren Lab into a more serious full-stack development company one that can work with people and businesses across a much wider range than just "small business needs a website." That means being equipped to support everything from a solo founder building their first idea, to a growing startup that needs real infrastructure, to company-to-company work where the client is already a serious operation with its own technical bar to meet.

Different stages, different needs, different levels of complexity, and building Soren Lab in a way that can actually meet people where they are, instead of having one rigid offering that only fits one type of client.

That's the direction. This is the beginning of actually walking toward it.

Where I'm actually starting

Before any of that, I'm starting where it always has to start: planning the foundation properly instead of rushing into code.

Right now that means mapping out the site structure in Obsidian using Canvas, laying out the header, the navigation, the account system, all of it as connected pieces I can see and adjust before any of it becomes harder-to-change code.

Here's where that's at right now:

It's not exciting yet. It's boxes and arrows. But it's the real first step in understanding exactly what needs to exist and how it connects, before building any of it for real.

Why document this at all

Because building this in public, from the actual start, means the story is real instead of a highlight reel that starts at "and then we launched." If the goal is eventually doing serious, company-to-company level work, I'd rather the foundation of that story be honest, starting with planning on a whiteboard, like everyone else actually does.

More posts coming as this moves forward: the brand and visual side, the homepage itself, and the thinking behind some of the bigger decisions along the way.

If you're building something solo right now too, I'd genuinely like to hear where you're at.