// orientation

New here? Good.
Let me break this down.

This page tells you exactly what this is, who it's for, and what to do first. No email required.

// right fit check

First — is this actually for you?

I'd rather you know upfront than waste your time.

// this is for you if

  • You're a solo entrepreneur, solo founder, or small business owner
  • You've watched content from other creators in this space and thought "I need to do this"
  • You've bought a course on AI or automation and stalled at implementation
  • You want to run your own business with AI — not sell automations to clients
  • You're willing to put in the time to build something that actually runs

// this is NOT for you if

  • You want someone to do it all for you
  • You're looking for passive income with no effort
  • You're an enterprise team (wrong scale, wrong content)
  • You want motivation and mindset content — I do systems, not inspiration

Still here? Good. Let's keep going.

// the concept

What is an AI employee?

Think of it like hiring a very capable assistant — except you build it once and it runs your business operations like a hired staffer.

Not a chatbot. Not a prompt you copy-paste. A system.

Here's what it does:

  • Handles the repetitive, expert-level work you're currently doing by hand
  • Runs your brand operations — content research, drafting, scheduling, monitoring
  • Works while you sleep, without needing to be managed every step

Here's what it doesn't do:

  • Replace your judgment
  • Make decisions for you
  • Run without a plan behind it

You're not removing yourself from the business. You're removing yourself from the systems that run it — so you can focus on the parts that actually need you.

// how the work splits 
AI handles:  ~80% of execution
  — content research
  — drafting
  — scheduling
  — monitoring
  — repetitive expert-level tasks

You handle: ~20%
  — decisions
  — judgment calls
  — the things only you can do
  — final review and publish
// prerequisites

Before you touch a tool, you need three things.

Most people skip straight to the tools. That's why they end up with a half-built workflow sitting in a browser tab for three months.

step 01 / 03

A clear goal.

What do you want the AI employee to do? Be specific. "Help with marketing" is not a goal. "Draft and schedule three Instagram posts per week based on my brand voice" is a goal. Write it down.

step 02 / 03

A one-page plan.

Before you open n8n or Claude, write out what you're building. What goes in, what comes out, what tools connect where. One page. This is the step I skipped once — and I rewrote an entire app multiple times because of it. Don't be me.

step 03 / 03

Patience for the operation layer.

The setup takes a day. Running the system — catching what breaks silently, adjusting the outputs, keeping it tuned — that's the ongoing work. It's not hard once you know what to look for. But you need to know it's coming.

// the curriculum

Here's what you'll learn. All of it.

I don't gate the real stuff. Here's the full map:

// phase 01 — plan
  • How to write a one-page AI employee brief
  • How to map your business operations to AI tasks
  • How to choose the right tools for your stack (and why I use Claude + n8n)
// phase 02 — build
  • How to wire the system together in n8n
  • How to set up Claude as the brain of the operation
  • How to connect it to your actual business (content, research, publishing)
  • Real costs: what it costs to run, broken down
// phase 03 — run
  • What the operation layer looks like week by week
  • What breaks silently and how to catch it
  • How to tune the outputs so they actually sound like you
  • How to scale it without rebuilding everything

This is the part everyone else gates. I publish it because I can — I'm not monetizing by keeping you dependent.

// where to start

Here's what to do right now.

Don't try to do everything at once. Start with one thing.

// option A — watch first

Head to YouTube and watch the first build walkthrough. It'll show you the plan → build → run sequence in real time, with real tools, real costs, and the parts that broke.

// option B — read first

Go to the build log. It's the honest ledger of this brand being built in public — what's working, what's not, and what it actually costs to run an AI employee.

// option C — follow along

If you're not ready to build yet, follow on Instagram or YouTube. I post the builds as they happen. No teaser content — the real thing.

see the build log
// tools I use

The tools I actually build with.

I only recommend what I've personally run. Here's the current stack:

// core stack 
Claude (Anthropic)
  Role: AI brain — content generation, brand research,
        voice matching, copy drafting

n8n (self-hosted)
  Role: workflow automation — the connective tissue
        between every tool in the system

AWS
  Role: infrastructure — hosting, storage, compute

Postgres
  Role: database — storing brand context,
        content history, workflow state

Docker
  Role: containerization — keeps everything
        portable and reproducible
  Cost: $0 (open source)

I'll tell you what each one costs, what it does, and when you'd swap it for something else. No affiliate-driven "best AI tools" roundups — just what's actually running.

// honest context

I'm pre-launch. Here's what that means.

I'm not going to pretend I have a track record of client results. I don't — yet. I'm building this brand right now, in public, using the exact system I teach.

The proof is the build log. Real numbers, real costs, real screenshots — including the ones where things went sideways.

If you want to wait until I have a longer track record, that's fair. Come back in six months.

If you want to watch the build happen in real time — and learn from it as it does — you're in the right place.

// current ledger running
Revenue $0
Monthly burn ~$800–$1,000
12-mo goal $2,000/mo minimum
// there's always a next step

Pick one thing and do it.

Watch a build. Read the log. Follow along. Just don't close this tab and go back to watching without acting — that's the thing I'm trying to help you stop doing.

see the build log