Skip to content
The methodology

Fire Your Web Guy.
Six steps, one AI agent, zero web guys.

I used to be the bottleneck. Someone wanted a header purple or a new show date added, and they had to wait for me. Now every site I build ships with a kit that lets the owner's own AI agent do the routine work — and I become the last resort instead of the help desk.

How a hand-off works
  1. 01

    Build it with Claude

    I build the site or app the normal way — with Claude Code doing the typing, tests and deploys gated so nothing sloppy reaches production.

  2. 02

    Package it for the owner's agent

    My agent writes a setup kit for that exact repository: install the tools, sign in, clone, verify, open a local preview. Setup never deploys.

  3. 03

    The owner ships changes

    They hand the kit to Claude Desktop on their own computer, then just describe changes. Preview, review, publish. I'm the last resort, not the help desk.

The kit

Two files, tailored per project.

A master setup template.The instructions an owner’s agent follows: detect the machine, bootstrap Git and GitHub, clone the project, install exactly the tools it needs, guide each sign-in one step at a time, run a read-only verifier, start a local preview, and write a plain-language report of what is ready and what isn’t.

A customization prompt.What my agent runs inside each repository to turn the template into that project’s kit: real commands from the real code, a verifier script with mock tests, and an honest list of anything it couldn’t resolve. No placeholders, no guessed versions, no secrets.

The verifier reports local readiness separately from deployment permission — being signed in is not proof you can publish — and setup never pushes, deploys or touches production.

fire-your-web-guy.appstart.one
The Fire Your Web Guy page for owners

The owners’ page: a six-step checklist, a progress counter, music, and a Stuck-O-Meter.

The six steps owners follow
  1. 01

    Get an AI agent on your computer

    Claude Desktop or ChatGPT Desktop — the app, not the website, so it can actually run things.

  2. 02

    A heads-up about plans

    The basic plan is fine to start. Active building may need the bigger one; downgrade any time.

  3. 03

    Chrome + the agent extension

    So your agent can see and click around web pages with you.

  4. 04

    Accept the invites

    GitHub for the code, Cloudflare for hosting. Keep logins handy. Never paste a password into chat.

  5. 05

    Hand your agent the setup doc

    “Follow this document to set up this project on my computer, verify it, and open a local preview.”

  6. 06

    Stuck? Ask your agent first

    Then ask it differently. After thirty minutes, the Stuck-O-Meter unlocks me.

The rules

Ask your agent first

It can read errors, look things up and try fixes. This works far more often than people expect.

Never paste passwords in chat

Sign-ins happen in the official browser page. The agent never sees a secret.

Preview before you publish

Every change is checked on a local copy of the site before it goes anywhere.

Setup never deploys

The kit installs, verifies and previews. Publishing is a separate, deliberate step.

The roster

Who has the keys.

Nine kits were delivered in the first week of October 2026. The ones with a page on this site are below; the other three are a second Tailgate repository, the Vault Sports Box 3D viewer, and a friends’ prototype.

ProjectOwnerHand-off
Vault Sports BoxVault Sports Box · Columbia Falls, MontanaOwner-run, live
Acting Studio ChicagoActing Studio Chicago · Chicago, IllinoisOwner-run, local
Dr. Jennifer RomesserNorthern Utah Psychology & Consulting PLLCOnboarded
The AtlantiansA tabletop RPG groupOwner-run, live
TailgateA Notre Dame tailgate crew · not affiliated with the universityOnboarded
Next MoveA friend's prototypeOnboarded
523523 · insurance & retirement guidanceNot yet
The video

The whole idea in one sitting.