Operators Win

Hey,

This is a special edition.

Normally I keep The Pulse to Sundays. But something happened this week that I can't sit on for three more days.

I posted a single thought on LinkedIn on Monday — a guess at the next big role to emerge inside organizations — and the response broke my notifications. McKinsey people. Founders. CTOs. HR directors. Heads of Sales. All replying with their own version of the same idea.

So this week's Pulse is one story, told properly.

It's the most important shift I've watched happen in 10 years. And if you're reading this newsletter, it's directly about you.

Here is the signal.

Every ~20 years, work reorganizes around a single new role.

→ The 1990s gave us the Product Manager — born to translate business goals into shipped software during the dot-com build-out. Before PMs, you had engineers and you had executives, and they didn't speak to each other. The PM became the indispensable translator. By 2010, every meaningful tech company had one in every product team.

→ The 2000s gave us the Business Analyst — born to bridge business processes and data systems during the SaaS build-out. Before BAs, ERP rollouts failed. With BAs, they merely ran over budget. The role compounded into "data analyst," "product analyst," "ops analyst" — and is now in roughly 1.4 million job titles in the U.S. alone.

→ Today, we're getting the Agent Operator — born to translate business problems into autonomous agent execution.

I want to be precise about what this person actually does, because most takes I've seen are wrong.

An Agent Operator is not "someone who uses ChatGPT well."

An Agent Operator is the person who:

→ Designs how agents interact with real workflows. Not chat sessions. Multi-step pipelines that touch real systems and ship real outcomes.
→ Connects tools, data, and systems into agent pipelines. Email, calendar, CRM, deal flow, content engines, support — all stitched together so an agent can actually finish a job, not just generate a draft.
→ Translates business problems into executable agent behavior. "Book me 5 qualified calls this week" → an actual system that researches, qualifies, drafts, sends, follows up, and reports.
→ Monitors, corrects, and improves agent performance over time. Treating the agent like an employee with a learning curve, not a feature with a roadmap.

Most people are still thinking about AI as a tool. That framing is already outdated.

The shift is from humans using software → humans managing autonomous agents that execute work.

This is not a productivity upgrade. It is operational transformation.

Here is what nobody is telling you about how to position yourself for this role.

The top 5 skills are not the ones you've been told to learn.

→ MCPs (Model Context Protocols). How agents access tools, memory, and structured context. If you don't know what an MCP is in May 2026, you are 6 months behind.

→ CLIs (Command-Line Interfaces). Because serious agent workflows will not live in a dashboard. They will run in programmable environments — terminals, scripts, scheduled jobs, headless containers. The GUI is for end users. The operator works in code.

→ Writing skills (the file kind). Not blog posts. Specs. Instructions. Structured documents that an agent reads and acts on. Agents run on precision, not vibes. The Agent Operator who writes the cleanest spec ships the most reliable system.

→ AGENTS.md fluency. The ability to define agent roles, constraints, memory, and tool usage in persistent formats. This is a real file, with real conventions, that the best operators are mastering right now while everyone else is still pasting prompts into a chat box.

→ Business acumen. This is the one nobody talks about, and it's the most important. Knowing where automation creates leverage versus where it just creates noise. Most "AI projects" fail because the operator picked the wrong workflow to automate. A great operator picks the right one before they write a single line of agent code.

This is not the next "prompt engineer" hype role. Prompt engineers don't ship work. Agent Operators ship outcomes.

And there will be specialists. Marketing Agent Operators. Sales Agent Operators. Product Agent Operators. Dev Agent Operators. But every one of them shares the same five-skill core stack above.

Because this LinkedIn comment thread told me something I needed to test in writing.

The role is real. The market is converging on it from a dozen different directions. Some are calling it "AI Architect." Some "Bot Driver." Some "Agent Success Manager." Some — like me — Agent Operator.

But every reply was describing the same person.

When the same role gets named simultaneously by people who don't know each other, that's not a fad. That's the role announcing itself.

What this means practically:

The career window between "I use AI" and "I operate agents" is the biggest career arbitrage of the next 5 years. We are inside it right now. Most people haven't noticed it's open.

Including, possibly, your manager.

This newsletter has two readers. Both of them have an immediate next move.

If you want to see what an Agent Operator actually does:

Tomorrow (Friday, May 1, 2 PM EST), I'm running a free live workshop showing exactly that. The setup is the Zevari AI agent — Claude operating LinkedIn for me 24/7. Posting. Commenting. DMing the right people at the right time. Not a chatbot. An employee.

I'll show the architecture, the failure modes, the safeguards, and the actual deployed agent running in real time. If you've wanted to watch a real Agent Operator at work — not a demo, not a slide — this is the one.

→ Register: https://luma.com/1crcmj7c

If you want to become one:

I run two communities for exactly this transition.

→ Agent J (Free). Weekly live builds, Claude Code sessions, an AI Prompting Masterclass, and Office Hours. Plus the LinkedIn Growth Operator skill (free), the Voice DNA workflow, and 1,700+ members already in the room. https://www.skool.com/agent-j

→ Agent J+ ($127/mo, 90-day money-back guarantee). Daily live sessions, the full curriculum, implementation guides, and direct help from operators who already do this for a living. The instructors — myself, Alex, Balázs — are not teaching theory. We are full-time Agent Operators showing you the systems we actually run. https://www.skool.com/agent-j-plus

If you've been on the fence about either, this week is the one.

The people who win the next 5 years are not the people who got fastest at writing prompts.

They are the people who learned to design, deploy, and operate agent systems before everyone else realized that was the job.

The role is real. The window is open. The names will shake out later.

Pick a side of the line.

—

See you Friday,
John

P.S. I'm collecting examples of Agent Operators in the wild — people doing this work today, regardless of their official job title. If that's you, hit reply with one sentence about what you're operating. I'll feature the best ones in next Sunday's edition.