For a while I danced around this — talking about structure, hand-written code, doing this the deliberate way since I was a teenager. All true, and none of it the whole picture. The whole picture is that AI does a lot of the actual typing now, and that's something I'd been managing carefully in conversation instead of just saying.

That was the wrong instinct, and probably not the only small studio that's had it. There's a real fear that saying "I use AI" gets heard as "I do less" or "you're paying full price for a shortcut." So the workaround is silence — build the way you always did, quietly faster, and hope nobody asks. I did that for a while. It's a bad trade. Being cagey about a tool that's genuinely useful doesn't read as more capable. It reads like hiding something, which is worse.

Here's what's actually true: AI doesn't decide what your site says about your business, how the pages get organized, or what a stranger sees in the first three seconds that convinces them to stick around. That part's unchanged — same discovery conversation, same structure-first thinking, same photography-led approach this whole studio is built around. What changed is how fast that thinking turns into working code, and how much more time goes to reviewing and refining instead of typing from scratch.

That's a genuine benefit, not a caveat that needs an apology. It means more hours go to the decisions that actually need a person, and fewer go to the parts that don't. If a tool frees up that time, not using it would be doing clients a disservice — and not telling them would be a bigger one.

So: I use AI as part of how I build. Not going to walk you through every tool in the stack any more than you'd get a tour of my code editor's settings — but I won't let anyone assume the site in front of them came out of a black box. Every decision is still mine, and nothing ships until I'm satisfied it's right. The speed is new. The standard isn't.