Why I build.

Give me a new project and I probably will not touch a keyboard for a while. I will be too busy asking questions.

Where did this start? What is it actually trying to accomplish? What is in the way, and has anyone bothered to ask why it is in the way?

I have come to believe the best solutions almost never come from pure creativity. They come from understanding a problem so well that the answer stops feeling clever and starts feeling obvious.

That has been true no matter what hat I was wearing: helping a leadership team fix operations that had gone sideways, standing between a business owner and a developer trying to translate for both of them, building out a marketing plan, or designing the actual site.

People tend to think building a website is a conversation about colors and fonts and layout. Sure, those matter. But honestly, they are the easy part.

The harder part is understanding the business sitting behind the website. What actually makes you different from the guy down the street doing the same thing? Why do people pick you once they have found you? Where are you right now, growth-wise, and what does the next stretch actually require from you?

It is tangled up with your marketing, your operations, your sales process, how customers experience you, and all of the tiny decisions that shape whether someone trusts you enough to reach out.

So I do not hand people a template with the logo swapped out. The best website is not the one with the trendiest animation. It is the one actually built for your business, your customers, and wherever you are trying to get to next.

The biggest lesson my career taught me has nothing to do with websites. It is about communication, of all things.

Two genuinely smart people can sit through the exact same meeting and walk away believing two different decisions got made. That used to catch me off guard. Now I just expect it.

I have spent years standing in the middle of founders, marketers, and developers, all of them wanting the same outcome, none of them quite speaking the same language.

A business owner describes the feature they think they need. A developer builds exactly that. The project ships and somehow everyone is still frustrated, not because anyone messed up, but because they were solving two different problems the whole time without realizing it.

At some point I stopped thinking of my job as collecting requirements and started thinking of it as digging out the actual problem hiding under the request.

That one question has redirected more projects than I can count, usually toward something better than where the conversation started.

In practice, a lot of my work sounds like: “Okay, here is what I am hearing.” Then I say it back, poke at the part I am not sure about, and ask one more question.

The good ideas almost never come from one person having every answer. They show up once everyone in the room finally agrees on what the actual problem is.

For years, I helped build other people’s businesses. Operations, marketing, technology, finance, all of it. I got a front-row seat to what separates the companies that grow from the ones that stall out.

It is almost never an accident. It is a string of thoughtful decisions, made over and over, by people who keep asking better questions instead of settling for the first answer.

Eventually, I wanted one place to put all of that together. Not another agency. More like a workshop, where strategy and creative work could sit next to each other, and every project could start with curiosity instead of a template someone pulled off a shelf.

That place is Rebel Moon Labs.

Outside of work, I am usually elbow-deep in something unrelated. Building something out of cedar. Baking sourdough that may or may not turn out. Making soap. Working out a crochet pattern. Puttering in the garden because it needed weeding and I needed a break from a screen.

None of it is really about the hobby. It is the same curiosity that shows up in client work, just pointed at something else for a weekend.

If I had grown up knowing more about engineering, I might have ended up on a completely different path. I do not really regret how it went, though. Business turned out to be its own kind of engineering, just with people and incentives and growth instead of steel and code.