The AI-Native Operations Playbook

July 28, 2026

Tools used

Download playbook

Enter your email

By clicking download you subscribe to our marketing communications.

A workflow that sets up an enture company around Claude Code, MCPs, a wiki knowledge layer, and reusable skills so 80% of the execution work runs on AI.

Dan Rosenthal

How it works

Step 1: Map high-level processes

Document who does what and which tools power each process.

For every process, map:
- People involved
- Tools used
- Automations and agents
- Related SOPs
Store the process map centrally in Notion or the wiki.
Use this as the blueprint before automating anything downstream.

Step 2: Connect MCPs and CLIs to Claude Code

Wire Claude Code into every tool it needs to act inside.

Connect 25+ MCPs including Slack, HubSpot, Instantly, HeyReach, Apollo, n8n, Notion, GitHub, and Supabase.
Add CLIs for tools without a working MCP.
Test each MCP before rolling it out to the team.

Step 3: Build the knowledge layer

Create an auto-updating company brain in markdown.

Set up a /wiki folder in GitHub.
Document every client, SOP, transcript, and campaign as markdown files.
Update the wiki through commits so the context stays current.

Step 4: Build the behavior layer

Turn SOPs into reusable Claude Code skills.

Set up a /skills folder in GitHub.
Convert every SOP into a Claude Code skill that gets a task 80%+ done.
Maintain around 20 core skills across a total library of 50+.

Step 5: Maintain the folder structure

Keep the company OS organized so Claude Code can navigate it.

Root structure:
- CLAUDE.md
- /wiki
- /clients
- /raw-context
- /.claude
Enforce a naming convention across every folder.
Clean up unused files regularly to keep the structure clean.

Step 6: Give the team access

Open up the system with guardrails so everyone can use it.

Set up strict hooks and guardrails to prevent misuse.
Give team access through:
- Claude Code CLI in Cursor
- Custom frontends deployed on Vercel
Train the team on when to use skills vs writing prompts from scratch.

Step 7: Deliver the outputs

Ship client work with humans owning strategy and quality.

Humans own strategy, review, and every mistake.
Claude Code handles 80%+ of the execution work.
Every deliverable goes through human review before hitting the client.

Scroll to zoom in and out, drag to navigateUse 2 fingers to drag, zoom in and out

The TAM Mapping Playbook

A workflow that turns closed-won data into a validated ICP model, sources a diversified TAM, then enriches and tiers every account before pushing it back into the CRM as the single source of truth.

ABMOutboundRevOps

Dan Rosenthal

July 28, 2026