Introducing the Agent Ops Club: Eight AI Agent Employees and a Software Library You Can Deploy for Clients

For four years I have been building AI agents, and along the way I have sold over a million dollars in web and AI solutions. Almost all of that work followed the same shape: I built something for my own business first, watched it run, and then taught it once it had earned the right to be taught.

The Agent Ops Club is that shape turned into a membership. It is the Agent Ops Masterclass plus a library of full stack AI software you can customize, deploy, and sell to clients under your own name.

This post is the introduction. Here is what is in it, what the license actually permits, what it costs, and what I am promising you.

Why I stopped packaging tasks and started packaging roles

For years agents could chat and they could code. Everything else in a business still needed a person, because the real work lives in dashboards, admin panels, and platforms with no API. You cannot automate a job when half of it happens inside an interface nobody exposed programmatically.

Browser and computer use changed that, and not gradually. The public benchmark for this is WebVoyager, which runs agents through hundreds of tasks on real consumer websites rather than a sandbox. On the current WebVoyager leaderboard, the leading browser agent completes 643 tasks across 15 live sites at a success rate above 99%. Reading a dashboard, publishing to a platform with no API, working a real interface: that is agent work now, on a schedule, without ever getting bored.

So I stopped shipping task automations and started shipping whole roles.

The eight Agent Employees

Every role is a set of daily and weekly routines that run at times you set. Each routine is self-contained, so nothing bloats a global context file, and they install on the agent harness you already use rather than asking you to adopt a new one. If you have never run an agent before, the first module gets you from installation to a working skill.

The roster:

• GTM Engineer, go to market and launch

• SEO Employee, search and content

• Web Dev Employee, engineering and maintenance

• Social Media Employee, audience and distribution

• Ad Manager Employee, paid acquisition

• Sales Employee, pipeline and outreach

• Customer Satisfaction Employee, support and retention

• Chief of Staff, oversight and strategy

They draft, you approve. Nothing sends and nothing spends without you, which is the single design decision I would defend hardest. I wrote up the reasoning behind where those gates sit in my approval workflow for agent actions, because getting that line in the wrong place is how people quietly turn their own safeguards off.

Every role can also be customized and sold to your own clients, under your brand, at whatever price you set. You can read the full roster and how each one is wired on the Agent Employees page.

What is in the Agent Ops Masterclass

Nine modules and 44 lessons covering the whole operating model rather than a tool tour. It runs from Agent Ops foundations through getting your agent running, writing skills that do real work, connecting everything with MCPs, building routines, browser and computer use, the Agent Employees themselves, always-on operations on a VPS, and finally customizing and selling what you have built.

The through line is that skills and routines should grow in value as the models underneath them improve. I have written before about what breaks when nobody is watching, and the Masterclass is largely the accumulated answer to that question.

The software library, and exactly what the license permits

The library is full stack systems I run in my own business. They join the library after they have been running in production, not as untested demos, and new systems ship on a regular cadence. Some of what is in there now:

• Claude Domain Factory, one repository running many sites and many separate businesses

• Automated SEO Content Engine

• Domain Network Monorepo

• A GPT-Image-2 powered AI image SaaS app

• Newsletter Autopilot

• GEO Launchpad

The Domain Factory is the one I get asked about most, and I wrote up the business side of running a portfolio that way in how to monetize a domain portfolio.

Now the part I want to be precise about, because vague licensing language is how people end up in trouble. You may customize the software and deploy it for clients, and charge whatever you want for those deployments. You keep every dollar. You may not redistribute the source code, hand the code to a client, or share the downloads. Deployments yes, source redistribution no. That distinction is the whole license, and I would rather state it plainly here than have anyone discover it later.

The software is one revenue line, and it is not the bigger one

This is the thing I most want new members to hear, because it is where the money actually is.

Selling a deployment is good. Being the person who implements, audits, migrates, trains, and then operates the system is better, and it is more durable. The engagements that have worked best in my own business are implementation and setup, agent operations audits, consulting, migration off something brittle, training that you deliver to a client's team, and managed operations where you keep running it.

That is a forward deployed engineer's job description, and the club is set up to make you one. There is no revenue share on any of it. Not a percentage of anything. What you charge your client is yours.

What it costs

The Agent Ops Club is $399 a month, billed annually. $4,788 is charged today for a full year of membership.

That includes the Masterclass, the full software library with the resale license, every new system as it ships, AI Strategy Insights sessions with replays posted inside the club, and the ability to book time with me directly when you are stuck on a customization, a deploy, or a client conversation.

I also build member apps. I take on two builds a month: you own the result outright, it is built on the club stack, and there is an optional launch push behind it.

The first client guarantee

Land your first client within your first 90 days, or I work with you one on one until you do.

I put that in writing because the failure mode for this kind of membership is obvious. People buy the library, watch the lessons, and never make the first call. The guarantee exists to put me on the hook for the part that is hardest, and it is the reason the one on one booking is included rather than sold separately.

What this means for the Accelerator

The Accelerator was the predecessor, and the Club is where my work goes now. It is the main focus, it is what new systems ship into, and it is what I will be pointing at from here on.

Existing Reinventing AI Hub members are grandfathered at their existing rates, and billing continues as it is. Nothing you already pay for goes away.

Membership is sold through the Reinventing AI storefront, which is also what gives you access to session replays and the other member products on the main site. That is deliberate: one account, one place your purchases live.

Frequently asked questions

Do I need to already know how to run an agent?

No. The first module of the Masterclass assumes you have never installed one, and takes you from a fresh install to a working skill in minutes. The harder material comes after, once something of yours is actually running.

Which agent do the Agent Employees run on?

The harness you already use. The roles are built as portable skills and scheduled routines rather than as a product locked to one vendor, so they install on top of your existing setup. If you are starting from nothing, the Claude Code documentation is a reasonable place to understand how permissions and settings work before you hand an agent a schedule.

Can I really sell these to my own clients?

Yes, as deployments. You customize a system, deploy it for a client, brand it as yours, and set your own price. What you may not do is redistribute the source or give the code itself to the client. If you are selling implementation and ongoing operations rather than a zip file, the license and your business model already point the same direction.

How often do new systems ship?

I build on a weekly cadence, and systems land in the library once they have run in my own business. New arrivals carry the same resale license as everything else, so the library you buy access to keeps growing without another charge.

What if I am already a member of something else of yours?

Use the same email your existing subscription is under when you register. Grandfathered and already-subscribed members go through the same registration page, with no second checkout.

Getting started

If you have been following the builds on this blog and wondering where the finished versions live, this is where. The systems I write about here are the same ones in the library, with the training that explains how they were made and the license that lets you put them to work for someone else.

You can see everything, including the full roster and the Masterclass breakdown, at the Agent Ops Club.

One small ask: when you land that first client, come tell me what you sold and what it took. That is the feedback that shapes what I build next, and it is genuinely more useful to me than a testimonial.