Issue 01: A map of Claude for the operator

01 · THE OPERATOR'S EDGE · WEEKLY · BY MARC KLEINMANN

Yes, I know your inbox is full of AI newsletters. This isn't one of them.

The Operator's Edge is a weekly newsletter for SMB owners and ops leads. The promise: understand AI well enough to outperform your competition and outwork bigger teams. Monday-morning leverage inside the business you already run.

Every Wednesday you get one of two things. Some weeks I break down something about AI you should understand to make better decisions in your business: what to ask before signing a contract, where AI gets things wrong, the vocabulary that does most of the lying. Other weeks I show you a workflow I built or shipped: the architecture, the decisions, what almost broke it, what to ask your builder for if you want one like it. Plus a few things I read worth your time, and a short translation of something from outside the operator's world.

If your inbox is already too full, the unsubscribe link is at the bottom. I won't hold a grudge. Otherwise, here's the first issue.

THE BREAKDOWN

📌 You haven't used most of Claude

The map. Front of house, back of house, and the tools that reach every room.

You've used Claude. You probably haven't used most of it.

Most operators meet Claude in the chat box. They type a question, get an answer, get value, close the tab. That's the front porch of a much bigger house.

The rest of the house has rooms you'd actually run your business out of. Above every room sits an attic full of tools that reach every room. Under the rooms where your team and your builder work, there's a basement with the deeper plumbing.

Here is the whole house, in one cross-section.

MAIN FLOOR

🏠 Five rooms, where you work

Five rooms. Same tool, different state. The reason Claude+Projects beats Claude alone.

Claude.ai chat

The front porch.

What you've already used. A web page, sometimes a desktop app. You type, Claude responds.

Useful for thinking out loud, drafting, summarizing, translating, asking questions about a document you paste in. Anyone walks up. No commitment. Most stop here. That's fine. It's the porch.

And the porch travels with you. Claude in Chrome is a browser extension that puts the same chat behavior inside whatever website you're already on. Available on any paid plan. Install it once; the porch shows up wherever you browse.

Claude.ai + Projects

Your study.

A folder inside Claude.ai that holds your context. Drop in your business plan, your style guide, your service catalog, your three most-asked client questions.

Now the chat happens in a room with your books on the shelf and your binder on the desk. The chat goes from "smart stranger" to "person who knows my business." Same conversation, different room.

This is the single most useful upgrade most owners have never made. If you only do one new Claude thing this month, do this.

In your other tool. ChatGPT has Projects (same name, same idea). Gemini has Gems.

Claude Cowork

The conference room.

Cowork is the conference room. The shared room with the whiteboard, the connectors to Gmail, Slack, Drive, your CRM. Claude works inside your business, not next to it.

Solo operator or full team. It's the same upgrade. Claude stops being a chat window and starts reaching into your calendar, your inbox, your file drives. The work happens where the work lives.

The upgrade isn't more people in the room. It's more of your business in it.

Claude Cowork + Projects

Conference room, prepped for the meeting.

Same conference room. Different state. The whiteboard already has your project on it. The connectors already know which inbox, which drive, which CRM segment to look at. The reference materials are already up.

You're not walking Claude through your setup every time you sit down. The setup is the room.

Claude Code

The workshop.

Where the contractors work. They have tools you don't have: write code, run scripts, hand back finished pieces of work to your spec.

Most owners walk into the workshop to brief a contractor and walk out with the result. You don't have to stay and swing a hammer.

ATTIC

📦 Above every room

Skills, Connectors, and the brief that loads your business into every conversation.

The attic isn't a room you visit. It's the infrastructure that hangs over every room, ready for the room below to pull what it needs.

Skills

The recipes.

Saved instructions Claude follows reliably across rooms. Write one once; every room that needs it has it on the shelf. Your "every-Monday-research-brief" recipe lives here, and any room can call it.

Connectors

The plumbing.

If you've heard "custom Claude agents," they often mean a Skill. The fancy industry words for Connectors are "orchestration" and "enterprise AI integration." Both mean: a connector. Naming things plainly is half the literacy.

Instructions

The brief your business hands to every room.

Write your business plan, your voice, your style guide, your three most-asked client questions into the brief once, and every conversation starts knowing your business.

Every room has a place for it. Different names depending on which room. Project Instructions in the study and the prepped conference room. A CLAUDE.md file in Cowork and in the workshop. Different names, same brief.

BASEMENT

🔧 The basement

Sub-agents, MCP Servers, the loading dock. You probably never visit. But knowing what's down here is what to ask your builder for.

The basement only runs under the team and build rooms (Cowork through Workshop). The porch and the study don't need it; they're chat surfaces. Most owners never walk into the basement at all.

Sub-agents

Parallel workers.

When a job is too big or varied for one conversation, Claude splits it across sub-agents running in parallel. Think of it as the difference between asking one assistant to do five things and hiring five assistants for the afternoon. You see the combined result.

MCP Servers

Plumbing to other systems.

The next layer beyond connectors. A connector is a hose to one tool; MCP is the manifold reaching a whole class of systems with one wiring spec. Most owners never need to know it's there. Your builder cares because it's what makes Claude extensible without rewriting every integration.

API Loading Dock

Where materials come in.

The door to the model itself. Most owners never walk into the loading dock. The API is for engineering teams building Claude into their own product.

THE MAP

📍 The take for an SMB owner

Five rooms on the front of house. Two on the back. That's it.

The porch is where you start. The study is where the chat starts knowing your business. The conference room is where Claude reaches into your inbox, calendar, and file drives. The prepped conference room is the same room with your project pre-loaded. The workshop is where your builder turns spec into custom work.

You don't have to walk into the attic or the basement to use them. You just have to know they're there, and what to ask for.

BEYOND CLAUDE

🧭 The three other models in my stack

Gemini, ChatGPT, Grok. What each one earns its spot for.

While I use Claude as my main driver, here are the three other models in my stack and what each earns its spot for.

Gemini. Lives inside Google Workspace. If your business runs on Gmail and Google Docs, Gemini is the AI sitting one menu away.

ChatGPT. The one your team is already using on their phone. The question isn't whether to use it (that's already happening). The question is what to be careful about.

Grok. Wired into X. When I need to research what an industry is actually saying this week, Grok pulls from X better than the others.

I work primarily in Claude because the depth (Projects, Cowork, Skills, Connectors) is the best-integrated environment for an SMB owner. That's an opinion, not a rule.

VISUAL & AUDIO

🎨 The rest of the content stack

Five categories. Five different jobs. Pick by the job, not the brand.

Here is what I run, and what each one is built for. Pick by the job, not by the brand. The model that wins each job changes every quarter.

📷 Image generation

Five in my stack.

fal.ai is the inference platform. API access to most current image models so I can swap by changing one parameter.

Recraft v3 for vector and brand-illustration. ChatGPT's image gen lives inside the conversation. Nano Banana is Google's Gemini-line model, strong on character consistency. Flux is the open-weight model most platforms host.

🎥 Video generation

Five in rotation.

Veo (Google), Kling (Kuaishou), Luma Dream Machine, Seedance (ByteDance), Wan (Alibaba). Each wins at something different: motion, lip-sync, consistency, run-length, camera control.

The honest workflow: run the same prompt across two or three and pick the output, not the brand.

🎙️ Voice and audio

The most-improved AI category in 2026.

ElevenLabs for voice cloning and high-quality narration. OpenAI's voice models when latency matters more than perfect cloning. What was uncanny six months ago is now indistinguishable from a real voice.

🗣️ Avatar and talking head

The latest-added category in the stack.

HeyGen for talking-head video from a script. Earns its place when you need a face on camera and yours isn't: webinars at scale, multi-language explainers, sales videos where the buyer expects a person. For most SMB owners, this is the latest-added category in the stack, not the first.

🧱 The composition layer

The durable piece. Swap the generative model; the composition stays.

All of the above are generative. They make pixels or sound from a prompt. The durable piece is the layer that wraps the model: the HTML, CSS, and motion code that says "hero image here, headline here, voiceover here."

For this newsletter's images, I render HTML composites via Playwright with Recraft v3 filling the slots. For video, HeyGen HyperFrames does the same: agents write HTML, the renderer outputs frames deterministically. The composition layer is yours to keep; the generative models swap underneath.

The honest rule. The model that wins each job changes every quarter. Build the workflow around the job (cut a 30-second ad, generate a hero image, record a podcast intro, ship a talking-head version of your pitch in three languages), then plug in whichever model wins that job this month.

The workflow is the durable asset. The model is the disposable component.

Want one thing to do this week? Open Claude.ai. Click Projects. Name one after your business. Drop in your service catalog, your last five client emails, your style guide if you have one.

Then ask Claude something you've already asked it before. Ask it inside that Project this time. The answer will be different. That's the first move past the porch.

SIGNAL

🔍 Three things worth your time

Three reads worth your time this week.

SIGNAL 01 · ANTHROPIC · MAY 13

Introducing Claude for Small Business

Anthropic spent the last 30 days shipping packs aimed at specific audiences. Visuals for everyone in April. Creative professionals two weeks later. Finance teams the week after that. Then small business owners on Tuesday. The pattern is the new playbook: stop selling the model, start shipping the workflows.

For us, the May 13 announcement is the one to read. Fifteen workflows already built: invoice follow-up, monthly close prep, weekly business pulse, lead triage. No extra charge if you're already on Claude. A free training tour through ten cities starting in Chicago. Read the announcement; then judge each workflow the way you'd judge any vendor pitch: which one has an honest approval gate, which connector touches your sensitive data, which step you'd still want a human in the loop for.

SIGNAL 02 · CHRIS DONNELLY · LINKEDIN · MAY 12

The customer journey has been split down the middle

Chris Donnelly noticed something most SMB owners haven't priced in yet: half your customers are still Googling you, but the other half are asking Claude or ChatGPT or Perplexity instead. The two halves work nothing alike.

With SEO you compete for ten blue links and the customer does the work; with AEO (Answer Engine Optimization), the AI picks two or three sources and the customer trusts the synthesis. If you're only optimizing for one half, you're invisible in the other. Operator-grade move this week: check whether your business appears in both.

SIGNAL 03 · ANDREW NG · LINKEDIN · MAY 12

There will be no AI jobpocalypse

Andrew Ng, Coursera co-founder and as inside the AI world as anyone, used LinkedIn this week to call out the AI-takes-everyone's-job narrative.

His point: the AI labs have a financial reason to oversell, the SaaS vendors have a pricing reason to talk "replacement," and the executives announcing layoffs have a face-saving reason to blame AI rather than overhiring. The data does not match the panic. If you've been holding off on a hire because "we'll have agents next year," this is the operator-grade reality check.

TRANSLATION

✏️ The view from above

What to read when you want the macro picture, not the next workflow tip.

MELODY KOH · GROUND TRUTH (NEWSLETTER) · MAY 13

Melody Koh runs Ground Truth, a newsletter about how AI restructures markets. Last week she wrote the clearest read I've seen on what happens next at the layer above your business. The frame: AI agents are becoming the new discovery layer that sits above Booking.com, LinkedIn, Amazon, and every other aggregator that currently owns consumer attention. When your agent searches for a hotel, the agent IS the new Booking.com.

Three questions decide which categories get rebuilt: who controls the supply, can that supply be re-aggregated through a different layer, and can the agent stack actually do the work. Where all three hold, agents do what hotels alone couldn't: bypass the discovery layer without having to outspend it. Where any one fails, the move collapses.

Koh names four positions incumbents and startups are taking right now. From below: route around the aggregator (Gondola does this for hotels, and every booking lands as a direct booking with full loyalty credit, even though the consumer touched an agent UI). From beside: build a parallel where the supply IS the network (Boardy for professional connections instead of LinkedIn). From within: go headless on your own terms (Shopify). From above: tollgate the agent traffic (SAP, ServiceNow). The last one feels safe to incumbents and is the worst long-term position: it announces "we are the obstacle."

For an SMB owner: this is the read you do once, then come back to running the business with the picture in your head. The Anthropic announcement up in Signal 01 is the inside view of where Claude is going. Koh is the outside view of the shift that makes those moves rational.

Read it: Melody Koh, "How the Agent Web Gets Built" →

SIGN-OFF

✉️ Talk Wednesday

Reply with what you'd put in your study.

Reply with what you're working on. It lands in my inbox at [email protected]. I read every reply, and it tells me what to write about next.

The setup walkthrough lives at /edge. If you want to take this from map to operational, the playbook is at praxisx.co/edge/get-started-with-claude. Installing Claude, mounting Cowork, wiring the connectors, the about-me file that makes any of this work. Same argument as this issue, one level deeper.

Talk Wednesday.

Marc