Skip to content

How I Work

I build with AI. My expertise is the product.

Every success story on this site is a product of the same methodology. This page is how I think about it right now.

Last updated October 26, 2026. This is a living document. I update it when my thinking shifts.

The short version

  • 01

    AI writes the code. I provide the judgment.

  • 02

    My expertise is what you're actually hiring.

  • 03

    Speed is a side effect. Not the pitch.

  • 04

    You could absolutely do this for yourself (I teach people how), but you probably won't want to.

  • 05

    I run my own business through an AIOS, and that's where I think all work is headed.

I build with AI. Not "AI-assisted."

AI writes the code. I don't mean "I use Copilot sometimes." I mean the code for the websites, the systems, the integrations, the automations. The actual implementation is written by AI under my orchestration.

What I do is everything around the code. The strategy. The positioning. The UX decisions. The copy review. The design judgment. The client conversations. The handoff. The hundred small calls between "the client said this" and "the thing exists and works."

That's the job. The code was never the job. It took me a long time to realize that.

My expertise is the product.

AI doesn't know what makes a hero section convert versus fall flat. It doesn't know when a "helpful" feature actively fights the client's sales process. It doesn't know whether to burn budget on a custom integration or point at the existing one and move on.

My expertise comes from having built a lot of things, shipped them, watched them succeed, watched them fail, and paid attention. It isn't a prompt. It isn't a checklist. It's pattern recognition on top of experience, applied in real time to your specific situation.

When you hire me, that's what you're paying for. The build is just how it shows up.

Speed is a side effect. Not the pitch.

I've shipped full websites in under two weeks. I'll probably ship more like that. But speed isn't the thing I want you to remember.

Speed is what happens when someone who knows what to build uses AI to build it. Without the judgment, speed just means you arrive at the wrong answer faster.

The reason I can move fast is the same reason the work is actually good: I've done this before, I know what matters, and I don't waste cycles on decisions that don't need to be made. AI collapses the time between decision and implementation. That's all.

I run my business on an AIOS.

Everything I do runs through one system I built for myself: my business's context, my clients, my money, and my content, all in one place my AI can read and act on. I call it my AIOS. It's how I work now, and it's where I think work is headed for every business.

It's also what I recommend, and what I build toward for clients. Not a pile of AI tools. One system that actually knows your business. See how I run mine.

You could do this yourself.

I'm not going to pretend otherwise to protect a price tag. The reality is that AI has changed the game. If you've ever used a computer, you can probably build a website now. You can build most of the things I build. That's true. Anyone who tells you otherwise is lying to you.

I teach people how to do this. I run a whole community around it at Modern Builders Society. So I'm the last person who's going to tell you that you can't.

But "can" and "should" are different questions.

There's still a quality filter. There are still levels to it. AI plus someone who's never built anything will get you a working website. AI plus someone who's built a lot of websites, sat with clients, watched launches succeed and fail, and knows what matters, will get you a better one. That gap is the whole game now.

So here's the honest deal:

  1. Could you build this yourself? Yes. If that's what you want, go do it. I even have a place for you to do it in, alongside other people doing the same thing: Modern Builders Society.
  2. Will you want to? Probably not, if you're running a business. What's slow isn't the building. What's slow is knowing what to build, and why, and in what order.
  3. That's what you're hiring me for. Not the code. The expertise to know what the code should be.

What a good engagement looks like.

The best engagements I've had share a shape. The client comes in asking for one thing (a website, a funnel, a system) and what they actually need is broader than that. They don't know it yet. They know something is off.

My job is to listen closely enough to hear what they actually need, then make it real before they have to keep explaining it. That means I'll often deliver more than what you asked for, because the thing you asked for only works if three other things are also true.

That isn't scope creep. That's the work.

What I won't do.

  • — Pretend the code is the hard part to protect a price tag.
  • — Build something you asked for that I don't believe will work.
  • — Take on a client I don't think I can actually help.
  • — Hide behind jargon. If I can't explain the decision to you in plain language, the decision is wrong.
  • — Disappear after launch. The work is the relationship, not the deliverable.

Why this page exists.

If you found me through a success story, you already saw what this methodology produces. This page is the why behind it.

If what's on this page resonates, we'll probably work well together. If it doesn't, we probably won't, and both of us save time figuring that out.

I'll update this page as my thinking shifts, because it will. Everything I've built, every client I've worked with, every year in this career has changed the way I think. If I stop changing, I stop evolving. What's written here is what I believe today.

This page is about hiring me. If you want to know how AI touches what I publish, how sponsorships and affiliate links work, or what happens to what you share in the community, that is on the ethics page.

If this resonates, let's talk.

I take on a limited number of builds and partnerships per quarter. If you read this and thought "that's the person I want in my corner," start here.