Maybe it referenced a tool you stopped using. Maybe it framed suggestions around a business model you abandoned in January. You shrugged it off. Rephrased. Got a better answer the second time and moved on.

But the bad answer wasn’t a glitch.

Claude was working off a stale profile of you the whole time. Old job context, dead projects, outdated positioning, tools you’ve swapped out. All of it sitting in a memory layer that loads into every conversation you have. Every single one. And it was bending your responses toward a version of you that doesn’t exist anymore.

The Uncle at Thanksgiving

Claude kept pitching me a $5,000 service offering. Every business task I brought to it. “Based on your Done-For-You AI Systems package...” followed by suggestions framed around pricing tiers and client onboarding for a service I’d brainstormed for 45 minutes on a Tuesday night back in November. Never built it. Never mentioned it to a single person who might actually pay for it.

Claude remembered it like I’d been running the thing for six months.

My uncle does this. He’s 82. Every Thanksgiving he walks up, puts his hand on my shoulder, and asks how the baseball card collection is going. I stopped collecting when I was 12. I’m 42. Those Upper Deck cards, which oddly enough are still in a box in my basement, but I couldn’t name a single card in there if my life depended on it. In his mind, I’m still the kid at the kitchen table sorting rookies from commons with a price guide.

He’s going to ask again next year.

Claude was doing the same thing, except Claude was using that bad information to shape every response it gave me. Content suggestions built around an offer I didn’t have. Strategy framed for a service model I’d abandoned. Audience targeting pointed at clients I wasn’t serving.

Subscribe now

Eight Wrong Things

When I finally ran a full audit, here’s what I found rotting in there: a dead service offering still listed as active, an old X handle, a subscriber count that was off by 600, four killed projects Claude still thought I was building, a target audience description from six months ago, and my old newsletter name showing up everywhere.

Eight wrong things. All shaping every response I got. For weeks.

I cleaned it up in 10 minutes. The difference was immediate. Responses the next day were tighter, more relevant, built around my actual situation instead of a ghost from last fall.

There are two ways to do this. I’ll walk you through both. (this is a Claude walkthrough, but copy+paste this into your favorite AI and ask it to do the same)

Option 1: The 2-Minute Scan

Settings. Capabilities. “View and edit memory.” That’s the path.

Click it and you’ll see a summary of everything Claude has stored about you. Read it. Delete what’s wrong. Edit what’s shifted. Close it. Done.

Do this every couple weeks. It catches the obvious stuff, like a wrong job title or a tool you dropped two months ago. Fast and surgical.

The limitation: you’re reading a flat list. You’ll catch things that are clearly wrong but you’ll miss contradictions between entries, and you’ll miss deeper context that Claude has picked up from your conversation history that doesn’t even show in the summary view. That layer needs the second approach.

Option 2: The 10-Minute Conversational Audit

This is what I did.

Open a new chat and ask Claude to walk through everything it remembers about you. One category at a time. I use seven: work and role, active projects, tools, audience and business, personal context, preferences, then contradictions.

Claude surfaces what it has. You confirm or kill each item. Batch the corrections at the end and apply them all at once.

Why does this catch more? Two layers. Claude pulls from your explicit memory edits (stuff you’ve told it to remember) and from the accumulated context it has synthesized from months of conversation history. Two different things. The manual settings page only shows you one.

The Seven Categories

Start with work and role. What does Claude think you do? Has your title or company or focus changed since you last paid attention?

• Active projects rot the fastest. I had four dead ones still showing as active. Four. If you brainstormed something exciting for one conversation and never touched it again, Claude probably still thinks you’re building it. That Tuesday night idea you had about a SaaS dashboard? Still in there. Active. Waiting for you to ask about it.

• Tools. I dropped tools and added new ones without ever telling Claude. It kept suggesting workflows around software I hadn’t opened in weeks. Check what it thinks you’re using.

• Audience and business is where things get expensive. Your positioning shifts. Your offer changes. Claude doesn’t know unless you tell it, and the old version keeps informing every piece of content and strategy it gives you. I was getting advice for a target audience I’d moved away from six months prior.

• Personal context is smaller. Family, fitness, hobbies. But it shapes tone and recommendations in ways you won’t notice until something feels off.

• Preferences and style covers rules you’ve given Claude about how to write, how to format, what to avoid. Some of mine were outdated. Probably some of yours are too.

• Bontradictions. After everything else, look at the full set together. Entries that conflict with each other across categories. This is where the conversational approach earns its 10 minutes.

The Schedule

Manual check: every two weeks. Ninety seconds. Scan and cut.

Full conversational audit: once a month. Or whenever something big shifts. New direction, killed project, new tools. Any of those should trigger it.

I spent 10 minutes on mine. Found eight wrong things that had been warping my responses for weeks. The next day everything Claude gave me was sharper. Tighter. Built for the person I actually am right now.

Your AI remembers everything you’ve ever told it. It just doesn’t know when to forget.

Go check your memory. I’ll bet you’ve got some baseball cards in there.

Ryan

P.S. If this kind of stuff is useful to you, I go deeper for paid subscribers. Walkthroughs, systems, the actual workflows I'm building and breaking every week. The free newsletter gives you the what. The paid side gives you the how, with the messy details included.

Subscribe now

I cut the Notion AI subscription. Obsidian. GONE. Gemini sits untouched.

The only tool still open on my computer every single morning is Claude Cowork.

I’m going to show you exactly how I set it up. The full system, the files, the prompts. All of it.

BE WARNED: This is the last AI setup guide you’re going to need. Not because I’m that good at writing tutorials. Because once you build this, you won’t go looking for another tool again. (I say that not, but who knows what will drop next week :)

You’re Probably Still Doing This:

A year ago I was duct-taping four tools together just to get through a normal week. Notion for notes. ChatGPT for drafts. Google Sheets for research links. n8n to move data between all of them. Some days I felt like the AI’s sweaty little meatsuit slowly developing carpal tunnel syndrome… The human API. Copy from here, paste there, reformat, re-explain, repeat.

Most of you are still doing this. And I get it. I did it for a long time.

Then I spent 30 minutes setting up Claude Cowork the way I’m about to show you. And everything changed.

Cowork started writing in my voice. Not “close enough.” My ACTUAL voice. The cadence, the vocabulary, the opinions.

It stopped asking me to re-explain my business every session. It already knew. My clients, my audience and priorities. Every session picked up where context left off.

It connects to my Gmail, my Google Drive, my Notion. It pulls context from the tools I already use and acts on it. No more copying between tabs.

And it runs tasks while I sleep. Every morning, there’s a fresh AI news briefing with content ideas already sitting in my outputs folder. I scheduled it once. It runs every night.

Here’s the problem.

If you don’t set it up RIGHT, none of that happens.

You open Cowork and start typing away. Claude doesn’t know who you are, your business, clients or voice. What are your standards? It has ZERO idea so it guesses. For all you know, you end up with a business plan for a hot yoga llama farm.

You close the tab. Go back to Chat. Assume Cowork was overhyped.

That’s where 99% of people stop. Right at the gap.

The tool works. It just needs your context.

This article fixes that. Permanently. I’m going to give you the exact folder structure, the exact prompts, and the exact instructions I use. Copy and paste the whole thing. 30 minutes.

Or 10 if you grab the plugin I built... More on that at the end.

Let’s build it.

Step 1: Build the Folder

(PAID SUBSCRIBER? SKIP ALL THESE STEPS, JUMP TO THE END, I HAVE A SPECIAL TOOL SO YOU DON’T NEED TO DO THESE STEPS)

60 seconds. Seriously.

Stop thinking in prompts. Start thinking in workspaces.

Every piece of context Claude needs about you, your business, and your rules is going to live inside files in ONE folder on your computer. You open Cowork, you point it at this folder, and Claude reads those files before doing anything. Every. Single. Session.

No more re-explaining yourself. No more “I’m a consultant who works with...” at the top of every conversation. That’s over.

Here’s the structure. Go create this right now. I’ll wait.

OPERATOR-HQ/
├── context/
│   ├── operator-profile.md
│   └── voice-rules.md
├── ground-rules/
│   └── ground-rules.md
├── projects/
│   └── (one subfolder per active project)
└── outputs/
    └── (Claude delivers finished work here)

Four folders.

context/ is the stable stuff. Who you are. How you sound. Doesn’t change often. Maybe once a quarter when your priorities shift.

ground-rules/ is how Claude should behave inside your workspace. When to ask questions. When to just shut up and execute. What it should NEVER assume about your work.

projects/ is the live work. One subfolder per project. Drop your brief in there, any reference material, prior drafts. When you tell Claude to work on that project, it reads the whole subfolder.

outputs/ is where Claude delivers finished work. The ONLY folder Claude writes to. Everything it creates lands here. Named properly. Organized. Ready to send.

DO NOT MISS THIS:

context/ and ground-rules/ are READ-ONLY for Claude. It reads them but never touches them. outputs/ is WRITE-ONLY. Claude delivers work there but doesn’t mess with your existing files. projects/ is read-only unless you specifically tell Claude to edit something inside it.

That separation matters. When you give an AI agent read/write access to your files, you want clear boundaries between what it learns from and what it creates. Period.

Go build the folder. Four subfolders. We’ll fill them next.

Step 2: Build Your Operator Profile

About 10 minutes.

This is the file that turns Claude from a stranger into someone who already sat through your onboarding week.

BUT. Do not write this file yourself.

I know. You’re going to want to open a blank document and start typing. “I’m a business consultant who specializes in...” Don’t. When people write their own context files, they produce LinkedIn bios. Polished. Aspirational. Completely disconnected from how they actually operate at 6 AM on a Tuesday with a half-empty coffee and an email they’ve been ignoring since Friday.

Claude doesn’t need the conference version of you. It needs the real version.

So we’re going to let Claude interview you instead.

Open Claude Chat (not Cowork. Regular Chat). Paste this prompt:

You are going to interview me to build a context file called operator-profile.md.

This file will be used inside Claude Cowork so that every session starts with full context about who I am, what I do, and how I work.

Ask me questions one at a time. Cover these areas:

1. What I do for work (role, business, industry)
2. Who I serve (clients, customers, audience)
3. What I'm building right now (current projects, priorities)
4. How I think through problems (analytical, intuitive, data-first, gut-first)
5. What tools I use daily
6. What "good work" looks like to me
7. What I hate seeing in AI output

Ask 12-15 questions total. One at a time. If my answer is vague, push back and ask for a specific example.

When done, compile everything into a clean markdown file I can save as operator-profile.md.

Do not flatter me. Do not say "great answer." Just ask the next question.

Claude asks. You answer. It pushes back when you’re being vague. It asks for specifics. After about 12 questions, it compiles everything into a clean markdown file that actually captures how you work.

Copy the output. Save it to OPERATOR-HQ/context/operator-profile.md.

Do this once. Revisit it when your business changes or your priorities shift. Maybe once a quarter. Maybe less.

Step 3: Build Your Voice Rules

About 5 minutes.

This is the file most people skip. And then they wonder why Claude sounds like a corporate press release generator.

Every piece of content Claude produces for you will sound like it was written by a robot unless you tell it exactly how YOU sound. What words you use. What words make you cringe. Whether you curse. Whether you use humor or keep it dry. How you structure your thinking.

This is the difference between output you delete and output you publish.

Same process. New Chat session. Paste this:

You are going to interview me to build a voice and style file called voice-rules.md.

This file will be used inside Claude Cowork so that everything it writes sounds like me.

Ask me questions one at a time. Cover these areas:

1. How would you describe your writing tone? (direct, casual, academic, warm, blunt)
2. Show me a paragraph you've written that you're proud of. (I'll paste one)
3. Show me a sentence that sounds nothing like you. (I'll paste one)
4. What words or phrases do you never want to see in your content?
5. Do you use contractions? Slang? Humor? Profanity?
6. How do you feel about bullet points vs. paragraphs?
7. Do you write differently for different audiences? How?
8. What's the worst AI writing habit you've noticed?

Ask 8-10 questions. One at a time. Push back on vague answers.

When done, compile into a markdown file I can save as voice-rules.md.

Include a "never do" section and a "always do" section based on my answers.

Here’s what separates a decent voice file from a great one: REAL SAMPLES.

When Claude asks you to show it writing you’re proud of, don’t describe your style. Paste an actual paragraph. A newsletter you wrote. A client email you nailed. A Substack Note that got 400 restacks. Give it concrete examples and it will pattern-match against the real thing instead of guessing based on adjectives.

Save the output to OPERATOR-HQ/context/voice-rules.md.

Step 4: Build Your Ground Rules

About 5 minutes.

You’ve told Claude who you are. You’ve told it how you sound. Now you need to tell it how to BEHAVE.

Without this file, you get a different Claude every session. Sometimes it asks clarifying questions before starting work. Sometimes it just barrels ahead and builds something you never asked for. Sometimes it reads your context files. Sometimes it decides it already knows enough and skips them entirely.

That inconsistency is what makes people give up on Cowork. They think the tool is unreliable. The tool is fine. It just doesn’t have operating rules.

Last interview. New Chat session. Paste this:

You are going to interview me to build an operating rules file called ground-rules.md.

This file will be used inside Claude Cowork to control how Claude behaves during every session.

Ask me questions one at a time. Cover these areas:

1. Should Claude ask clarifying questions before starting, or just go?
2. When should Claude ask for permission vs. just execute?
3. What should Claude never assume about your work?
4. What file formats do you prefer for deliverables?
5. How detailed should responses be? (concise vs. thorough)
6. What does a "finished" deliverable look like to you?
7. What mistakes has AI made for you in the past that you want to prevent?
8. Are there any topics, tools, or approaches Claude should avoid?

Ask 8-10 questions. One at a time.

When done, compile into a markdown file with clear sections:
- Before every task (what Claude must do first)
- During execution (how Claude should work)
- Delivery (where and how to save output)
- Hard boundaries (what Claude should never do)

Save as ground-rules.md.

Save to OPERATOR-HQ/ground-rules/ground-rules.md.

You now have three files sitting in your workspace. Your operator profile. Your voice rules. Your ground rules.

These three files are the ENTIRE reason your Cowork experience will be different from everyone else’s. They’re the gap between generic output and work that sounds like you built it yourself.

One more step.

Step 5: Paste Your Global Instructions

2 minutes. Copy. Paste. Save.

Global Instructions are the command layer sitting on top of everything.

They’re a persistent set of rules Claude reads BEFORE every Cowork session. Before it opens your files. Before it touches anything. These instructions tell Claude exactly where to look, what to read first, and how to handle your workspace. Without them, Claude might read your files. Might not. Might ask questions. Might guess. You’ve seen this behavior if you’ve used Cowork without setup. It’s inconsistent because there’s no protocol.

This fixes that.

Open Claude Desktop. Go to Settings > Cowork > Edit Global Instructions.

Paste this EXACTLY:

# GLOBAL INSTRUCTIONS

## BEFORE EVERY TASK
1. Read everything in context/. No task starts without this.
2. Read ground-rules/ground-rules.md.
3. If the task relates to a project, read the matching subfolder in projects/.

## FOLDER RULES
Read-only (never create, edit, or delete files here):
- context/
- ground-rules/
- projects/

Write-only (all deliverables go here):
- outputs/

## FILE NAMING
All files you create: project-name_content-type_v1.ext
Examples: newsletter_draft_v1.md, client-proposal_report_v1.docx
Increment version if a file with the same name exists.

## OPERATING RULES
- If the task is unclear, ask questions first. Don't fill gaps with guesses.
- Deliver the work. Skip the commentary unless I ask for it.
- Never delete files anywhere.

Save.

That’s it. You’re done.

Five steps. One folder. Three interviews. One block of instructions pasted into settings. Under 30 minutes total.

Every single Cowork session from this point forward starts with Claude reading your profile, your voice, your rules, and your project files before it writes a word. Your prompts can be two lines long now. The workspace does the heavy lifting.

But before you go run your first task, read this next section. Because I’ve watched people do everything above perfectly and STILL get mediocre results.

The 5 Mistakes That Keep People in the 99%

You built the workspace. Good.

Now here’s what kills it.

1. Giving Cowork the keys to your entire computer.

Good way to nuke your entire file system. Someone reads about Cowork, gets excited, and selects their entire Documents folder. Or their Desktop. Or their home directory. Claude now has read/write access to 14,000 files it doesn’t need and can’t make sense of. If something goes wrong, the blast radius is your entire machine. You built OPERATOR-HQ for a reason. One dedicated folder. Four subfolders inside it. That’s the perimeter. Stay inside it.

2. Writing your context files by hand.

I said it in Step 2 and I’ll say it here again because people STILL do this. They skip the interview prompts, open a blank .md file, and start typing a description of themselves. What comes out is a conference speaker bio. Looks great on a slide. Useless for an AI that needs to understand how you actually make decisions, what frustrates you, and what “finished work” means to you specifically. The interview prompts exist because humans are terrible self-reporters. Use them.

3. Writing 500-word prompts because that’s what ChatGPT trained you to do.

The ChatGPT hangover is real. You spent a year front-loading every single prompt with background information, tone guidance, constraints, formatting rules, examples of what you want, examples of what you don’t want. You had to. ChatGPT didn’t know anything about you. With the workspace you just built, your context files carry all that weight permanently. Your prompts shrink to two sentences. If you’re still writing novels into the prompt box, your context files aren’t pulling their weight. Go back and tighten them up.

The Shortcut

Everything above works. Completely. You can run through all five steps manually and have a fully operational workspace in about 30 minutes.

But I built something faster - one download - 10 minutes later everything is structured.

The Operator Onboarding Plugin is a Cowork plugin that runs one structured interview and generates EVERYTHING for you.

About 10 minutes. You answer 15-18 questions. It does the rest.

It generates operator-profile.md, voice-rules.md, and ground-rules.md. Writes your Global Instructions. Drops everything into the right folders.

Once you install it, Cowork loads the plugin automatically whenever it recognizes a relevant task. You install it once. You forget about it. It just works in the background.

The guide above gives you the full manual setup. Nothing is missing. Nothing is held back. The plugin compresses 30 minutes into 10 and removes the assembly step.

Join as a paid subscriber and get your CoWork setup the fastest way in the next 10 minutes, download below \/

Read more

Ask yourself: what did I spend real time on today that I couldn’t fully account for? Not a client call. Not a strategy session. The other stuff. The in-between work that fills the gaps between everything that actually matters.

If you’ve used AI before, you already know it can write things. You’ve probably used it to draft an email or clean up a paragraph. Maybe you’ve tossed a question at it when Google wasn’t cutting it.

But you haven’t systematized it. It lives in a browser tab you open when you think of it, not a workflow you actually rely on. That’s the gap this newsletter exists to close.

Today we’re going after a specific category of work. The kind that’s too small to delegate, too tedious to enjoy, and just frequent enough to quietly drain you. Call it the Tab-Switching Tax.

What the Tab-Switching Tax Actually Costs You

You’re not losing hours to this. You’re losing 15 minutes here, 25 minutes there, a focused morning that never quite got started.

The work itself is easy. That’s the trap. Because easy work still consumes working memory. You’re holding context, cross-referencing details, formatting things by hand, double-checking names and dates. None of it requires judgment. All of it requires attention.

And attention is the one resource you can’t buy back.

Here are four places it’s bleeding out of your day right now.

1. The Meeting Dump

You just finished a 45-minute call. Real things happened. Decisions were made, someone volunteered for something, a deadline got floated in the last five minutes when everyone was half-checked out.

Now you’re back at your desk with a notes doc that looks like it was written during an earthquake. Half-sentences. Initials instead of names. A date that might be a due date or might be when something happened.

Your job: turn it into a clean action list before you forget the context sitting in your short-term memory.

Without AI, that’s 20 minutes of reconstruction work. Piecing together who said what, formatting a table, writing out full names, guessing at the deadline nobody wrote down clearly.

The prompt:

“I’m going to paste my raw meeting notes below. Act as my Executive Assistant.

1. Summarize the key decisions made.

2. List every action item with a Person Responsible and Deadline. If a deadline wasn’t stated, flag it as TBD.

3. Note any open questions that still need an answer.

Use plain, professional language. No filler.”

Paste the notes. Read the output. Fix anything that’s off. You’re done in under two minutes.

2. The Email Thread You’ve Been Avoiding

There’s a thread in your inbox right now that you’ve opened at least four times without responding to. Not because it’s hard. Because it’s long, it’s scattered, and summarizing it in your head before you can reply takes more energy than you want to spend on it.

Reply threads are particularly brutal. The context is buried in the middle. Someone changed the ask on day three. The attachment in the original email is different from the one someone re-sent on Thursday.

The prompt:

“I’m going to paste an email thread below. Read the full thread in order and then:

1. Tell me what the original ask was.

2. Tell me what changed, if anything.

3. Tell me what’s actually being asked of me right now.

4. Draft a reply that answers the current ask directly. Keep it under 100 words unless the situation genuinely requires more.”

You’re not outsourcing your judgment. You’re outsourcing the reconstruction work so your judgment has something clean to operate on.

3. The CRM Update You Keep Putting Off

Sales calls, discovery calls, check-ins with existing clients. They all generate information that needs to live somewhere. But after a full day of calls, the last thing anyone wants to do is sit down and manually update five CRM records.

So they don’t. Or they do it at 9pm with one eye on the TV and half the details already fuzzy.

The prompt:

“I’m going to paste my rough notes from a sales call below. Extract the following and format it as a CRM update:

• Company name and contact name

• Current situation / pain point they described

• What they said they’ve already tried

• Next step agreed on, with date if mentioned

• Any objections or hesitations they raised

Keep each field to two sentences max.”

Paste your voice memo transcript or your scribbled notes. The output drops straight into your CRM. Fifteen seconds of copy-paste and you’re current.

4. The Weekly Report Nobody Wants to Write

Status updates. Progress reports. End-of-week summaries for clients or leadership. Useful information, terrible use of a Friday afternoon.

The problem with these isn’t finding the information. It’s translating a week of scattered activity into something that sounds coherent and professional when you’re already mentally done for the week.

The prompt:

“I’m going to paste my raw notes and task list from this week. Write a concise weekly status update that covers:

1. What got completed

2. What’s still in progress and where it stands

3. Blockers or decisions that need input

4. Priorities for next week

Tone should be direct and professional. Assume the reader is busy. No fluff.”

Paste your task manager export, your brain dump, whatever you have. What comes back reads like something you spent an hour on. You spent four minutes.

What Actually Shifts When You Do This

Each one of those prompts does the same thing underneath.

It converts construction work into review work.

Construction requires you to hold the raw material in your head, figure out the structure, produce the output, and then check it. Review just asks you to read something and confirm it’s right. The cognitive load isn’t even close.

People who’ve dabbled with AI tend to use it for one-off tasks and then go back to their regular workflow. The ones who start pulling ahead aren’t using better prompts. They’ve built a short list of recurring tasks where AI handles the construction and they handle the final call.

That’s the shift worth making.

Not “use AI more.” Build a short stack of reliable prompts for the work you repeat every single week. Four is enough to start. Those four alone can give you back two hours by Friday.

The tab-switching tax doesn’t disappear on its own. You have to decide to stop paying it.

Blank doc. Blinking cursor. That low-grade dread in your stomach because you’re pretty sure the coach two niches over already published the exact post you were planning.

So you check. You open their newsletter. Their LinkedIn. Their podcast. And now you feel behind. The content calendar you were about to fill stays empty.

The cursor wins again.

This is the core problem for every coach, consultant, agency owner, and service provider trying to publish consistently. You’re making content decisions with ZERO visibility into what the people around you are doing. You don’t know what competitors published this week. You can’t see which angles are played out, which ones nobody has touched, where the gaps are wide enough to own.

So you guess.

And guessing is why your publishing schedule keeps dying.

I built a system that ends this. Every Friday morning, a one-page brief lands in my inbox. What my competitors published. What they changed. What gaps exist in their coverage. What I should write next, and where I should be positioning my offers differently. Runs automatically. Costs about $0.10 a week. Took two hours to set up on a Saturday morning while my kids were still asleep.

Three steps. Full build below.

Step 1: Build your watchlist (30 minutes)

Two categories. Direct competitors and adjacent competitors.

Direct competitors sell what you sell to the people you sell it to. You know who they are. The coaches in your space. The consultants targeting your same buyer. The service providers whose names keep showing up in your DMs.

Adjacent competitors are more interesting.

They solve a similar problem with a different method, or they serve a slightly different audience with a similar offer. These are the ones that tell you where demand is MOVING. Direct competitors tell you where demand already sits.

Open a Google Sheet. Four columns: Name, URL, Content Channel, Monitoring Priority.

Five direct. Five adjacent. Ten total.

That’s it. I know you want to add more.

Don’t.

I’ve watched people build 40-competitor spreadsheets that never get opened after the first week. The spreadsheet sits in a browser tab behind Gmail, collecting digital dust while the person wonders why they feel overwhelmed. Ten competitors. Maximum. If you can’t stay disciplined on the watchlist, the rest of this system falls apart before it starts.

For each competitor, identify their PRIMARY content channel. The one where they put their best thinking. Newsletter. YouTube. LinkedIn. Podcast. Pick ONE per competitor. Everything else is repurposed noise.

Step 2: Set up automated collection AND analysis (90 minutes)

This is the step where most people would tell you to open Feedly, scan RSS feeds twice a week, copy interesting stuff into a Google Doc, then paste it into ChatGPT on Friday.

That’s not a system. That’s a chore list. And chore lists die by week three.

Collection and analysis belong in the SAME automated pipeline. Signals come in, get processed by Claude, and a finished brief lands in your inbox. You read one document on Friday morning.

That’s your only job.

The tool that makes this work is n8n. Free, self-hosted workflow automation. If you’ve never used it, the learning curve is about an hour. Worth every minute.

The pipeline is actually TWO workflows, not one. This is important.

Workflow 1 runs daily. It collects signals and stores them. Workflow 2 runs every Friday morning. It reads the stored signals, sends them to Claude, and delivers your brief.

Workflow 1 (daily collection):

RSS Read nodes pull your competitor feeds automatically. Substack feeds use the format yourcompetitor.substack.com/feed. YouTube channels have RSS feeds in their page source. WordPress blogs almost always have one at /feed. Set up one RSS node per competitor. n8n checks them daily.

Google Alerts get forwarded to a dedicated Gmail address or label. n8n pulls them via the Gmail node.

Visualping handles page monitoring. Set it on competitor pricing pages, feature pages, about pages, landing pages tied to their core offer. When something changes, Visualping sends an email notification. That email routes into n8n through the same Gmail node.

Every signal from all three sources gets written to a Google Sheet. One row per signal. Date, source, competitor name, content. The sheet is your holding tank. Signals accumulate there all week while you do absolutely nothing.

Workflow 2 (Friday analysis):

A scheduled trigger fires every Friday at 8 AM. It reads every row added to the Google Sheet in the last seven days, compiles them into a single text block, and sends the whole batch to Claude using n8n’s native Anthropic node. (You don’t need to build a raw HTTP request anymore. n8n has a built-in Claude node that handles the API key and prompt formatting for you.)

Your analysis prompt includes your content pillars, your audience profile, your positioning, and a competitor watchlist with notes on each player. Claude reads every signal from that week, cross-references against YOUR specific context, and outputs a competitive brief.

The brief lands in your inbox. Or a Slack channel. Or a Google Doc. Total cost per week: roughly $0.10 in API calls. Then the workflow clears the sheet for next week’s signals.

You never copy-paste anything. You never open Feedly. You never manually check a pricing page. Friday morning you open one document and it tells you what changed, what gaps exist, and what to publish next week.

The prompt skeleton I load into the Claude node:

“You are a competitive intelligence analyst for a [your niche] business. Here is the competitor watchlist: [loaded from a stored file]. Here are this week’s signals: [piped in from RSS + Gmail nodes].

Analyze for: 1. New content topics or angles I haven’t covered 2. Pricing, packaging, or positioning changes 3. Gaps in their coverage that align with my content pillars 4. Shifts in messaging, offers, or audience targeting

Output a one-page competitive brief with specific action items for next week’s content.”

I keep a competitor watchlist file that the Friday workflow references. Names, URLs, content channels, a short note on each competitor’s current positioning. Claude reads it every time the workflow runs. The briefs get sharper every week because the context file accumulates your notes and observations. By week four, it catches shifts you would have missed scanning feeds manually.

If n8n feels like too much on day one, start with the manual version. Dump your RSS reader and Google Alerts into a Claude Project on Friday, run the prompt by hand. But build toward the automated pipeline.

The manual version works. The automated version works WITHOUT you.

Step 3: The monthly debrief (15 minutes)

Once a month, zoom out.

Open your competitive brief archive. (You ARE saving those, right?) Look for patterns across four weeks.

Who published the most? Who changed direction? Who went quiet? Did anyone launch something new or change their pricing?

Now look at the weekly gaps. If the same gap keeps showing up week after week, nobody in your space wants to own that territory.

Take it.

Write one paragraph. What changed. What it means for you. What you’re doing about it. What you’re deliberately ignoring. Pin it at the top of your content planning doc. Read it before you plan anything for the month ahead.

Why you stopped publishing (and how to fix it)

You stopped publishing consistently because you lost conviction.

That feeling of “I KNOW this is the right topic for this week” dried up. And without it, the blank doc won every time. You’d open the calendar, stare at it, feel that familiar weight, close the laptop.

This system brings conviction back.

When you can see the whole board every Friday, content planning stops being a guessing game. You know what angles are overplayed because you watched four competitors cover them this month. The topics with zero coverage jump off the page because the gap showed up in your brief three weeks running. Your energy goes exactly where it should.

And it goes beyond content. When you see a competitor change their pricing or launch a new offer, you can respond in days instead of finding out six months later from a client who almost hired them instead.

Your calendar fills because you’re not sitting there wondering what to write. You already know.

Something I didn’t expect when I first built this: I stopped dreading Monday mornings. The anxiety about what to write, whether someone already said it better, whether I was wasting time on the wrong topics. Gone. Replaced by a one-page brief that tells me exactly where the openings are.

Maybe 30 minutes of active work per week once everything is wired up. Less time than you spend scrolling a competitor’s Instagram on a Tuesday night and feeling worse afterward.

Build it. Run it for 30 days.

Your content calendar will never be blank again.

• Open a new chat.

• Type out who you are, what you do, how you write, what the context is.

• Get something back that’s 70% right.

• Fix the rest by hand.

• Close the window.

Tomorrow, same drill.

A treadmill with a better-looking screen.

THE MATH IS BRUTAL

Five minutes per task re-explaining yourself. Ten tasks a week. Fifty minutes on orientation alone. Every week.

Over a year: 43 hours.

Just re-introducing yourself to a tool that was supposed to save you time.

The conservative number. Run it at 30, 40, 50 tasks a week and the number gets ugly fast.

THE FIXES EVERYONE TRIES

Better prompts come first. You find a mega-prompt on X. “Act as a world-class strategist with 30 years of experience.” The output improves. You feel progress. Then a new chat opens and the slate is clean again. A faster wheel. Still a wheel.

Next comes the Custom GPT or Claude Project. An afternoon uploading samples, writing instructions. Works for a week. Then you notice you’re still copy-pasting everything out of the window. Still the last step before anything gets done.

Then someone tells you to learn Python.

Six months later the APIs changed. The models changed. The course you bought covers tools that don’t exist anymore.

The wheel just spins faster.

Subscribe now

THE ROOT

Every new chat window, you walk in cold.

Your voice. Your audience. Your standards. Your red lines. You rebuild the whole picture from scratch, every session, on a keyboard that’s been sitting there since 6 AM.

Renting effort looks like productivity. Output delivered. Task complete. The tenth session costs exactly what the first one did. The fiftieth costs the same as the tenth.

Ownership compounds. The setup you do once makes every session after it faster, sharper, cheaper. A machine that knows you before you type a word.

WHERE THIS CHANGES

In intelligence work, no one walks into a briefing room and re-introduces themselves.

Before any serious operation runs, there’s a brief. One document. Everything the team needs to function without burning time on orientation. Objectives. Context. What good looks like. Everybody reads it once. The work starts.

Nobody stops mid-operation to explain who they are.

Same logic applies to your AI workflow.

The Briefing Framework is one document you build once.

It holds your voice, your audience, your positioning, your rules, your non-negotiables. Load it at the top of any session, any tool, any task. The AI walks in knowing exactly who it’s working with.

Context is the only variable that actually matters.

How to build that framework is below.

Read more

Outlined it. Rewrote the hook twice. Edited it until the sentences felt tight. Hit publish. Checked the numbers an hour later.

Nothing.

No likes. No comments. No shares. The engagement counter sitting at zero like a dead gas gauge on a parked car.

So you did what most people do. You told yourself the algorithm buried it. Bad timing. Wrong day. The platform is broken. Your audience wasn’t online.

Here’s the part that stings: it probably wasn’t any of those things.

The post died because something specific was broken. And you have no system for figuring out what. So you’ll sit down tomorrow, write another post from scratch, and gamble again.

Write. Publish. Hope. Check. Disappointment. Repeat.

Most creators run this loop for months. Some run it for years. They never stop to cut the dead post open on the table and look at what killed it.

I did. And what I found changed how I create content permanently.

Your Posts Are Failing for a Reason You Refuse to See

I used to think engagement was mostly luck. Some posts hit, some posts don’t, the algorithm decides, you keep swinging.

Comforting. Also dead wrong.

When I started treating dead posts like cold cases instead of bad luck, the patterns were so obvious I felt embarrassed for not catching them sooner.

I fed my worst-performing posts into Claude alongside my top performers. Asked it to compare them structurally.

My best posts almost always did four things:

The hook created a tension the reader needed to resolve.

Within two lines, the reader felt personally called out.

One single clear through line held the entire piece together. Not two ideas competing. Not three threads woven. One.

By the end, the reader had something specific to do, say, or think differently.

My dead posts? They failed on the first sentence. The hook was generic (”Here’s how I grew my newsletter”) or it was interesting to ME but created zero tension for the reader.

The post wasn’t bad. The first sentence was bad. And on social media, the first sentence IS the post.

Most Creators Treat Dead Posts Like a Gas Leak They Refuse to Smell

There’s a coffee mug sitting on your desk right now. You’ve stared at it a hundred mornings while scrolling past your dead posts thinking “maybe the next one.”

The next one isn’t the answer.

YOUR LAST ONE IS THE ANSWER.

What people THINK kills their posts: algorithm changes, bad timing, low follower count, the wrong day of the week.

What ACTUALLY kills their posts: vague hooks, no emotional trigger in the first two lines, wandering structure with no throughline, and a CTA so soft it reads like a suggestion from your least confrontational coworker.

Those are fixable problems. Every single one.

But you’ll never fix them if you never look.

Subscribe now

The Post Autopsy System (Copy This Exactly)

Here’s the exact process I use now when something dies. It takes 15 minutes and I run it every single week.

Step 1: Collect the Evidence

Pull your 5 best-performing posts from the last 90 days. Copy the full text into one document. Then grab your dead post and put it in the same document.

You need them side by side. Same screen. Same file. Like a police lineup.

Step 2: Run the Diagnostic

Drop this prompt into Claude:

“I’m giving you two groups of posts. Perform a structural autopsy on the failed post by comparing it against my winners.

=== SUCCESSFUL POSTS (these performed well) === [PASTE YOUR 5 BEST-PERFORMING POSTS HERE, separated by ---]

=== FAILED POST (zero engagement) === [PASTE YOUR DEAD POST HERE]

For each of the 5 successful posts, analyze:

The hook structure (what tension or curiosity does the first line create?)

The emotional trigger (what feeling does the reader experience in the first 3 lines?)

The structural pattern (how is the argument built?)

The vocabulary density (how specific vs. generic is the language?)

The CTA or closing mechanic

Now analyze the failed post using the same framework. Compare them directly. Tell me specifically where the failed post breaks from the patterns that made the successful posts work. Be blunt. I don’t want encouragement. I want a diagnosis.”

Step 3: Read It Without Your Ego

This is where most people quit.

The model is going to tell you things you don’t want to hear. Your hook was vague. Your structure wandered. You buried the point under three paragraphs of setup nobody asked for. The emotional trigger was missing entirely.

Let it hit.

Step 4: Rebuild the Post

Once you have the diagnosis, run this follow-up:

“Based on your analysis, rewrite the failed post using the structural patterns, hook mechanics, and emotional triggers from my top 5 performers. Keep my original idea and core argument intact. Match my voice and vocabulary from the successful posts. Do not soften it. Do not make it generic. Make it hit the way the top 5 hit.”

You’ll get back a version that feels uncomfortably close to what you should have written the first time. That sting? Good. Remember it. Let it rewire how you approach the next post.

Why This Is a System and Not a One-Time Fix

Saving one dead post doesn’t matter.

What matters is building a feedback loop that actually teaches you what works. Over time. Consistently. Without guessing.

When I started running autopsies on my worst content, my hit rate changed completely. I stopped staring at the analytics dashboard refreshing the page like some kind of slot machine addict. Started seeing the mechanical patterns underneath engagement.

Your best posts already contain your playbook. You wrote it. The data is sitting in your drafts folder right now. You never thought to reverse-engineer it because nobody told you to.

UNTIL NOW.

This is what I mean when I talk about AI as leverage. You’re not asking AI to write your posts for you. You’re using AI the way an analyst uses a database. To find patterns in your own data that your ego won’t let you see.

One More Thing

I want to personally invite you to something.

Creating content alone with no feedback loop is brutal.

It gets a lot easier when you have a room full of people who’ve already built the audience you’re working towards.

People who will look at your draft and say “your hook is weak, try this” or “move this paragraph to the top” before a single person in your audience ever sees it.

That room is Masterclass 24/7. I’m personally inviting you to join.

There is a free trial. No risk. Get inside and see how it works.

PLUS once you’re inside, send me a DM and I’ll send you the complete Post Autopsy Prompt Pack. Three copy-paste prompts that run the entire system from this newsletter. The diagnostic, the rebuild, and a pre-publish check you run before you ever hit post.

No more guessing alone at 5 AM whether the hook lands.

You get REAL feedback on your work before it goes live.

Click below and join:

MasterClass 24/7

See you inside.

Ryan

Their morning routine IS content creation. Their calendar is built around production.

And their advice sounds like this: “Be consistent.”

Now tell me how to do that when I’m pulling 8-hour days at work and helping my daughters with homework at the kitchen table while trying to remember if I ate lunch.

I write this newsletter at 5am before the house wakes up. I edit between 8 and 10pm after bedtime stories are done. I build in the margins around a full-time career and two kids who don’t care about my publishing schedule.

And I haven’t missed a week.

I engineered my way out of the consistency problem. And today I’m breaking down the system that keeps your content alive when your life tries to kill it.

If you want the actual AI prompts that power this system, those are waiting at the bottom.

Your Content System Has a Single Point of Failure

Here’s what most creators do every week.

Sit down. Stare at a blank page. Come up with a topic. Outline. Draft. Edit. Format. Schedule. Publish.

Each step requires their brain, their energy, their decision-making, their full presence.

DEPENDENCY IS THE PROBLEM.

Remove any one of those inputs and the whole machine stops. The newsletter doesn’t go out. Guilt shows up next. Then silence. Then you’re starting over from zero.

I watched this cycle destroy a dozen promising newsletters from people smarter than me. They publish strong for eight, maybe twelve weeks. Then one bad stretch at work. And the gap opens.

And you might be VERY close to this.

That gap compounds fast. Your audience stops expecting your name in their inbox. The algorithm stops promoting your content. You didn’t press pause. You pressed rewind.

15 Hours Before a Family Vacation

Last year I wanted to take a two-week family vacation. We have property with no cell phone access, no Starlink connection. Fully unplugged and present with my family.

Work had other plans. The weeks before the trip got brutal. Deadlines stacking. By the time I looked up, I had ZERO content prepped and a flight in four days.

So I spent 15 hours across those four days in a content sprint. Writing drafts at midnight. Scheduling posts during lunch breaks. Setting up automations between meetings. Testing every send.

The content went out. Nobody knew I was on a beach. Metrics held.

But a 15-hour scramble to compensate for a fragile system was a warning sign, not a win. My entire operation was built on the assumption that I would always be available to run it.

The Content Battery

After that vacation I rebuilt everything around one concept: THE CONTENT BATTERY.

You’re always 2-3 weeks ahead. You batch smarter and template the repeatable parts so AI handles the blank-page problem while you handle the thinking.

Monthly Batching Over Weekly Scrambling

Once a month, I block out one focused session. Usually a Saturday morning. Coffee getting cold on the desk. Quiet house. No Slack notifications pinging in the corner of my screen.

In that session, I generate the raw material for an entire month of newsletters. Topics. Outlines. Hooks. Draft scaffolding. Voice notes I talk through like I’m explaining the idea to a friend at a bar.

One session. Four weeks of content foundations.

The rest of the month, I’m refining and editing. Adding personality back in. 30-45 minutes per piece instead of building from scratch.

Templates and the Emergency Vault

Every newsletter follows a structural template. I rotate between four or five frameworks depending on the topic. The bones are already there before I type a single word. All my mental energy goes toward insight and voice instead of structure.

On top of that, I keep a running Google Doc of “break glass” content:

• Ideas sitting at 70% done

• Evergreen pieces that don’t depend on current events

• Old frameworks from past posts that still hit

• Half-written drafts with strong hooks that need 20 minutes of polish

When a week goes sideways and even the battery runs low, I pull from the vault. Polish. Publish. Nobody knows the difference.

AI Handles Structure. You Handle Voice.

Most people get this wrong in one of two directions. They either refuse to use AI entirely, or they let the machine write everything and publish robot slop with their name on it.

I use AI for the parts that don’t require my brain:

• Generating structural outlines from a topic

• Expanding bullet points into rough paragraph drafts

• Pulling research and data points I can verify

• Reformatting content for different platforms

The AI never writes the final product. I do. My voice, my stories, my opinions, my edge. AI saves me from staring at a blank page at 5am with the cursor blinking. A 3-hour task compressed into 40 minutes.

Build the system once. Feed it during your high-energy windows. Let it run when your job and your family need all of you.

If this hit home, share it with a creator you know who keeps going dark.

For paid subscribers: below are the actual AI prompts that power this system. One for monthly batching. One for emergency weeks. One for turning old content into new newsletters.

Read more

I wasted two weeks building a product that was dead on arrival.

I could have figured that out in 30 minutes. One browser tab. One Terms of Service page. That’s all it would have taken.

Instead I had a working prototype, a validated use case, a clean UI, and absolutely zero future.

And today I’m going to tell you exactly what happened so you don’t make the same mistake.

Let me show you where it all went wrong.

Subscribe now

What I Built (and Why It Mattered)

I built a Substack discovery tool for content creators.

The idea was straightforward. Creators on Substack have no efficient way to find similar publications in their niche. No way to track what their peers are writing about. No way to get a pulse on trending topics across their category on any given day.

My tool solved that.

You tell it your niche, it curates articles from similar publications and generates daily trending reports. It shows you what fellow creators are publishing so you can stay ahead of the conversation instead of guessing what to write about next.

I validated the idea. Talked to creators. Confirmed the pain point. The demand was real.

I would lay awake at night thinking of what I could fix to make it better. How I would market it. I even started onboarding beta testers.

And I had it working. The screens looked clean. The reports were pulling real data. Leaning back in my chair watching it all populate across the screen in real time.

That feeling when something you built actually WORKS???

You know the feeling.

I could smell the dolla bills

Then the cracks started showing.

The Foundation Was Quicksand

I need to be upfront with you here.

I knew going in that Substack doesn’t have a public API. No developer program. No official documentation for building tools on top of it.

I KNEW ALL OF THIS.

And I built anyway.

Why? Because AI makes building so fast that you start thinking you can outrun structural problems. You tell yourself you’ll figure it out as you go. You’ll find a workaround. Somebody on GitHub has already solved it.

So I started pulling data through the unofficial, undocumented endpoints that Substack’s own website uses behind the scenes. And at first, it worked.

Sort of.

The responses were inconsistent. Data would come back incomplete. Fields that populated fine one hour would return empty the next. Nothing was reliable enough to run a real product on top of.

I was building a house and the lumber kept changing shape.

That’s when I finally stopped building and started doing the research I should have done BEFORE I wrote my first line of code.

I pulled up Substack’s Terms of Service on my laptop. Right there in plain language:

They prohibit crawling, scraping, or spidering any page, data, or portion of Substack through manual or automated means.

They prohibit copying or storing any significant portion of content.

They ban reverse engineering or attempting to obtain underlying source code or information.

FACT: Substack’s TOS was last updated April 21, 2025. This language is current and enforceable. I confirmed it myself.

That covers EVERYTHING.

The scraping I’d need to do to pull article data. The database I’d need to build to store content for trend analysis. The reverse-engineered API endpoints I was already using.

All of it violates their Terms of Service.

The RSS feeds don’t give enough data either. To do real trend analysis across publications, I’d need full article content stored in my own database. Which is exactly what the TOS prohibits.

Dead end after dead end.

The Two-Week Lesson

Here’s where I have to be brutally honest with myself and with you.

I validated the product. The demand was real. Creators want this tool. The market wasn’t the problem.

THE PLATFORM WAS THE PROBLEM.

Even if the responses had been perfectly consistent. Even if Substack had a well-documented developer program with official API keys and rate limits and dedicated support.

I would STILL be building a business that lives or dies based on another company’s decisions.

They change an endpoint. Your product breaks.

They update their TOS. Your product is illegal.

They revoke your API access. Your product vanishes overnight.

They get acquired. Your product is someone else’s problem now.

FACT: 42% of startups fail because they build products that don’t meet market demand. But there’s a subset of that number nobody tracks. The products that had REAL demand but were built on foundations that couldn’t support them.

I didn’t misread the market.

I misread the map.

The Startup Genome Project found that founders overestimate the value of their IP before product-market fit by 255%. They also found that market validation takes 2-3x longer than most founders expect.

I had the opposite problem. I validated fast. I built fast. I skipped the part where you check whether the building has a foundation before you start decorating the rooms.

Research would have taken 30 minutes. Building took two weeks.

You tell me which one was actually slow.

The lesson is simple. A long-term business is not built on top of another product.

If your entire product only works for Substack, or only works for X, or only works inside one platform’s ecosystem, you are not building a business. You’re building a feature inside someone else’s house.

Build tools that solve problems ACROSS platforms whenever possible. Or at minimum, build your system so the data layer is modular. When one source dries up you plug in another without tearing down the walls.

If you read nothing else in this article, go back and read that paragraph again.

How to Use AI for Research BEFORE You Build

If you still insist on building on top of another platform or using their tools as a core dependency, here’s how to protect yourself. This is the framework I’m using going forward. And it’s what I should have done before I touched a single line of code.

Step 1: Read the Terms of Service.

This is the most boring, most important 20 minutes you’ll spend before any build. You’re looking for language around scraping, crawling, data storage, reverse engineering, API usage, and third-party applications.

Substack’s TOS would have killed my project on Day One.

I didn’t read it until I was already knee-deep in code on Day Twelve.

Use AI here. Drop the TOS into Gemini or Claude and ask: “What restrictions does this platform place on third-party developers, automated data collection, and content storage?”

You’ll get a clear breakdown in under two minutes.

Step 2: Verify the API landscape.

Does the platform offer a public, documented, supported API? Is there an official developer program with real documentation?

If the answer to both questions is no, you’re not building on a platform. You’re building on a rumor.

Undocumented internal APIs are fun for side projects. They’re terrible for businesses. An afternoon of research using AI to search for “[Platform Name] developer API” and “[Platform Name] developer program” will tell you everything you need to know about whether your technical foundation is real or duct-taped together by strangers on GitHub.

Step 3: Map your data dependencies.

Open a blank doc. Write down every piece of data your product needs to function. Next to each one, write down where that data comes from.

Then ask one question for each line item:

“Can the source of this data cut me off?”

If the answer is yes for the core data your product runs on, you don’t have a product. You have a countdown timer.

My tool needed article content from Substack publications. Substack controls that content. Substack’s TOS prohibits me from collecting it.

I could have mapped this out on a napkin at my kitchen table in fifteen minutes.

Step 4: Stress-test with AI before you commit.

Before you invest real dev time, run these prompts through a deep research tool like Gemini:

“What are the known risks of building third-party tools on [Platform]?”

“Have any products been shut down for violating [Platform’s] terms of service?”

“What data access limitations exist for [Platform] and how have other developers worked around them?”

“What is the technical feasibility of [your specific product idea] given [Platform’s] current infrastructure?”

Most people use AI to speed up the build.

Operators use AI to speed up the decision about WHETHER to build.

That distinction is worth more than any coding shortcut you’ll ever find.

The Real Takeaway

AI made it possible for me to build in two weeks what used to take two months.

But the speed didn’t make the product more viable.

It made the failure faster.

The people who will win in this era aren’t the fastest builders. They’re the ones who spend two hours researching before spending two weeks building. The ones with a notepad open on the desk, mapping dependencies BEFORE they open the code editor.

I learned this the hard way so you don’t have to.

Before you build your next tool, run the framework above. Spend one afternoon. Save yourself weeks of wasted effort. This is the kind of thinking we do inside The AI Operator Handbook every single week.

Not chasing shiny tools. Not building for the sake of building.

Thinking clearly about what’s worth building in the first place, what foundation to build it on, and how to avoid the traps that eat your most valuable resource: your time.

If that sounds like the kind of newsletter you need in your inbox, hit subscribe and join us.

Subscribe now

Talk soon,

Ryan

P.S. Paid subscribers get early access to every framework, prompt template, and workflow breakdown I publish. Including the full AI research workflow I now run before starting any new build. If you’re building in the margins around a 9-5, you need systems that prevent wasted weeks, not create more of them. The link to upgrade is below.

You’ve got the newsletter. You’ve got the content. You’re publishing consistently. But your subscriber growth looks like a heart monitor flatlining. And somewhere along the way, someone told you the answer was a lead magnet.

So you spent two weeks building a 30-page e-book. You launched it. And 14 people downloaded it. Six of them were your mom using different email addresses.

I know because I did the same thing.

10 months and 2,200 subscribers later, I’ve tested enough lead magnets to know exactly why most of them fail and what the ones that convert have in common. The answer took me a while to figure out, but the execution takes about two hours.

This skill has two applications, and the second one is where the real money lives.

Application one: Build lead magnets for your own newsletter and watch your list grow while you sleep.

Application two: Sell lead magnet creation as a service to other creators who don’t have the time, the system, or the AI fluency to do it themselves.

I’m going to walk you through both today.

If you love this article, share it with a friend and subscribe below to join the conversation.

Subscribe now

Most Lead Magnets Suck

This is the uncomfortable truth.

The average creator knows they need a lead magnet. They’ve heard it on every podcast. They’ve seen the tweets. They understand, intellectually, that email ownership beats algorithmic dependence.

And they still don’t have one.

Because building a lead magnet requires four different skills stacked on top of each other: audience psychology, copywriting, content architecture, and design. Most creators are strong in one. Decent in another. And completely lost on the rest.

So they stare at a blank Canva template for 45 minutes. They resize a text box eight times. They close the tab and tell themselves they’ll finish it next week.

The half-built PDF sits in their Google Drive like a car on blocks in the front yard.

This is a gap in the market the size of the Grand Canyon.

And the creators who figure out how to build these fast using AI are sitting on two assets: a growth engine for their own list AND a service they can sell to every creator in their network who’s stuck at the same wall.

Why Lead Magnets Built by AI Convert Better

I need to kill a misconception before we go further.

People hear “AI-generated” and think “generic slop.” And they’re right, most of the time.

Most AI-generated content is garbage because people treat AI like a vending machine. Put in a vague prompt, get out vague content. You know the type. You’ve seen those lead magnets floating around that read like a ChatGPT fever dream wrapped in a Canva template.

The system I use is different.

AI handles the architecture and the first-draft heavy lifting. The creator adds the opinion and the lived experience. The result is a lead magnet that’s structurally airtight and personally authentic because you layered yourself back in.

FUN FACT: The lead magnets I build using this system take two hours. The ones most creators try to build manually? They take two weeks and they STILL end up worse. Because structure is the hard part, and AI does structure terrifyingly well.

The pattern is clear from everything I’ve tested: the lead magnets that get used are short and built around a single decision point.

Your reader doesn’t need a textbook. They need the right framework at the right moment.

The System (Free Framework, Paid Prompts)

I’m giving you the full framework here. The structure. The thinking. The phases. The filters. Everything you need to understand HOW this works and WHY each step matters.

The exact prompts, the copy-paste templates, and my revision notes are inside the paid subscriber vault. That’s the implementation layer.

What you got above is the starter set. Enough to build your first lead magnet today.

If you’re someone who wants to build this today or start selling it to clients this week, that’s where you go.

Here’s the system.

Read more

And I’m about to tell you that AI isn’t your problem.

Every person reading this has access to the same models, the same prompts, the same tutorials, the same free tiers. So why are some people printing money while you’re still tweaking workflows at midnight?

Twenty years in criminal intelligence taught me the answer. And it has nothing to do with technology.

The Solo-Entrepreneur Trap

Most people building with AI right now are building alone.

Collecting tools.
Hoarding prompts.
Bookmarking threads they’ll never open again.
Consuming tutorials at 11pm that they forget by morning.

And confusing all that motion with progress.

Subscribe now

Every analyst I worked with had access to the same databases and the same financial records. Same data patterns across every case file on every desk. We were all drinking from the same firehose.

The raw data never separated the good analysts from the great ones.

The ones who cracked cases first were embedded in networks. Human networks. Informants and partner agencies sharing observations before anything hit an official report. Analysts who had tracked a money laundering pipeline through Eastern European syndicates and could look at a new case file and say “I’ve seen this structure before” while everyone else was still running queries.

The AI world works the same way. Thousands of new tools launch every week. If your edge is a prompt you figured out on a Tuesday, someone else has it by Thursday.

And yet most people keep searching for the next tool when the answer is in the next room.

The Room Changed Everything

I built The AI Operator Handbook solo for months. 5am sessions with black coffee going cold on my desk. Figured out prompts, automations, content systems, audience research workflows. Built custom tools inside Gemini instead of paying for subscriptions.

I was staring at the same four walls of my home office before sunrise, building things nobody was seeing, with no one to tell me if I was headed in the right direction or off a cliff.

Twenty browser tabs open. Docs full of saved prompts. A bookmarks folder called “AI Tools” with 200 links in it. And the same revenue number at the end of every month.

I’ve seen creators with 100K, 200K followers who have all the tools, all the reach, and still can’t turn attention into income. Same panicked look at every event. “Hey man... I have all these followers. How do I actually make money from this?”

In intelligence, we called it “all-source fusion.” No single discipline gives you the full picture. You need multiple sources feeding into the same room, at the same time, with people who can see connections between them.

That’s exactly what happened when I joined Masterclass 24/7.

I expected a group chat with some tips. What I found was a room full of creators (many with 100K+ followers) openly sharing what was working THIS WEEK. Distribution strategies that were producing results that month. Monetization playbooks. Who was testing what. Live results from people who were shipping every single day.

Within my first few weeks, I picked up a content strategy from one of the coaches that I would have NEVER found on my own. It wasn’t in any YouTube video. It wasn’t in any thread. The kind of insight that only surfaces inside a room where people will rip apart your landing page on a Tuesday night group call and then DM you a better version by Wednesday morning.

Here’s the mental model from my intelligence career that explains why this works:

• Tools give you capability. Networks give you context.

• Tools are available to everyone. The right network is not.

• Tools depreciate. Relationships compound.

• Tools tell you what’s possible. The right room tells you what’s worth doing.

You can build the best automation in the world. If it’s sitting in a Google Doc that only you have open at 5am, what’s the point?

Masterclass 24/7 is where you stop guessing and start getting real feedback from people who’ve already done millions of views. Where you stop building in silence and start building alongside creators who challenge your ideas, hold you accountable, share what’s working this week, and call you out when you’re playing small.

Cultivate Your Network

When AI tools become fully commoditized (and they will), the people who built networks and distribution will be the ones still standing.

Masterclass 24/7 has a 7-day free trial. A full week to see the room, attend a live session, and connect with other builders who are on the same path.

If the room doesn’t change how you operate, leave. No risk.

And if you stick around past the seven days, I’ll give you two free months of paid access to The AI Operator Handbook. The full prompt stacks, the systems, the frameworks, all of it. Consider it my way of welcoming you into the room.

But if you’re anything like me, you’ll realize in the first 48 hours what you’ve been missing.

JOIN MASTERCLASS 24/7 - 7 DAY FREE TRIAL

If this resonated, share it with someone who’s building alone. They need to see this.

Build systems. Remove friction. Execute.

Ryan

P.S. The 7-day free trial costs you nothing except the assumption that you can figure everything out alone. I held onto that assumption too long. Don’t make my mistake. Try it here.

I was at my desk in the dark. Screen glowing on my face. A half finished cup of black coffee next to my keyboard that I’d reheated twice and forgotten about both times. My Substack editor was open with an empty draft and a blinking cursor.

I had a newsletter due. And I had nothing.

Not because of writer’s block. I had plenty to say. The problem was I had no idea what my audience was hungry for RIGHT NOW.

Every single time I sat down to write, the question was never “can I write?” It was always “what do people care about today?” And I was answering that question the same way every time: scrolling through feeds for 45 minutes before typing a single word.

That morning, something clicked.

Subscribe now

I closed everything, opened a fresh Claude Code instance, and started building a tool that would fix this problem for me permanently.

One week later I had working software that scans trending topics on Substack within my niche and shows me what readers are engaging with right now. Built with AI. No coding background. No developer.

I built it for myself. Then I mentioned it casually to a few people on Substack and my DMs were flooded with writers asking for access. (access is coming soon, there’s a lot more building to do when you open these tools up to the public)

The most reliable path to building something people want is solving a problem you already have.

And that’s what this entire article is about. YOU.

I’m going to show you why the most profitable software ideas are hiding inside your daily workflow right now. I’m going to give you the exact AI prompt you can use to excavate business ideas out of your own blind spots.

And I’m going to walk you through how to build your own tool with zero technical skills, zero startup capital, and zero permission from anyone.

Every Great Tool Started as Someone’s Annoyance

Basecamp exists because a web design agency got tired of managing projects through email threads.

Slack started because a gaming company needed a better internal chat tool.

Calendly was born because someone was sick of the back and forth emails to schedule a single meeting.

None of these started as

“I want to build a billion dollar company.”

They all started the same way:

“This is annoying. There has to be a better way.”

My tool started the same way. Sitting at my desk at 5am, coffee in hand, frustrated that I was spending more time figuring out WHAT to write than actually writing.

The friction was so normalized I didn’t even recognize it as a solvable problem for months.

I thought the scrolling WAS the process.

You are doing this right now with something in your own life. I guarantee it.

There is a task you do every single day that takes 20 minutes when it should take 20 seconds. You have accepted it. You have worked around it. Your brain filed it under “normal” a long time ago.

That task is your goldmine.

Why You Can’t See Your Own Opportunities

There’s a psychological phenomenon called habituation.

Your brain stops registering things you encounter repeatedly. The same way you stop hearing the refrigerator hum after living in your house for a month.

Your workflow frustrations work the exact same way.

You have been doing tedious, repetitive things for so long that your brain stopped questioning them. You stopped even noticing them.

FACT: Research from the Harvard Business Review found that knowledge workers spend an estimated 41% of their time on tasks that could be automated or eliminated.

Four out of every ten hours. wtf?

If you work 40 hours a week, you are spending roughly 16 of those hours on tasks that a tool or piece of software could handle for you.

TWENTY HOURS.

That is a product roadmap sitting in plain sight.

What’s Happening Right Now While You Scroll

You are walking past the same broken step in your workflow every single morning. Stepping over it. Going on with your day.

And someone in a different industry with the exact same type of broken step is going to build a tool that fixes it and charge people $49/month for the privilege.

Why shouldn’t that person be you???

The AI Excavation Prompt

Here’s what I’ve learned from 20 years in intelligence work: the best analysts don’t find new information. They find patterns hiding in information everyone already has.

AI does the same thing with your workflow.

When you describe your daily process to a machine that has ingested millions of business models and operational frameworks, the machine spots friction you physically cannot see anymore.

Your blind spots are visible to the AI because the AI never habituated to them.

Here is a prompt framework you can paste into Gemini or Claude right now and walk away with real product ideas by the end of the conversation.

START WITH THIS:

I want you to act as a product strategist and business analyst. I’m going to describe my daily workflow across my professional and personal life. Your job is to listen carefully, then identify friction points, repetitive tasks, manual processes, and inefficiencies that I might have become blind to.

For each friction point you identify, I want you to:

Name the specific problem

Explain why I’ve likely habituated to it

Suggest a simple software tool that would solve it

Rate the market opportunity on a scale of 1 to 10 based on how many other people face the same problem

After I describe my workflow, ask me follow-up questions to dig deeper into areas where you suspect hidden friction exists. Push me. Challenge my assumptions about what’s ‘normal’ in my process.

Here is my workflow: [DESCRIBE YOUR TYPICAL DAY, WEEK, OR PROCESS IN DETAIL]

Why This Prompt Works

The follow up questions are where it gets good.

The AI will probe areas you glossed over:

• The 30 second task you didn’t even mention because you forgot it existed

• The manual copy paste step you do 15 times a day without thinking about it

• The workaround you invented two years ago that you now treat as standard procedure

• The thing you complain about to coworkers but never thought to fix

THAT is where the gold is buried.

You Already Have the Skills to Build It

Once the AI identifies friction in your workflow, you have something most “idea guys” never get. A problem you personally understand at a cellular level.

You are not guessing what the market wants. You ARE the market. You live in the problem every day. You know the edge cases and the workarounds. You know the exact moment where you lean back in your chair and think, “Why is this so annoying?”

Now here’s the part that would have been impossible even two years ago.

You take that idea and you build it.

Tools like Claude Code, Gemini, Cursor, and Replit let you describe what you want in plain English and the machine writes the code. You sit down, tell the AI what the tool needs to do, and the AI builds it while you guide it. That is how I built mine. One week. Early mornings. Late nights. No engineering degree.

You do not need a computer science degree. You do not need to hire a $150/hour developer. You do not need to raise money. You do not need to ask anyone for permission.

The barriers are gone. Every single one of them.

You do not need to build the next Slack. You do not need venture capital or a pitch deck.

You need 200 people willing to pay you $49 a month.

200 x $49 = $9,800/month

That is close to $120K a year. From 200 customers.

Micro SaaS. Small tools that solve specific problems for specific people. The internet is FULL of these businesses running quietly in the background:

• A scheduling tool for dog groomers

• An invoicing system for freelance translators

• A client portal for personal trainers

• A trend tracker for newsletter writers

Built by one person. Generating six figures a year. No employees. No office. No investors. No board meetings.

Nobody writes about these on TechCrunch.

They also do not fail at the rate that VC backed startups do. Because they were built by someone sitting at their own kitchen table at 5am, solving a problem they personally felt in their chest every single day.

The Window Will Not Stay Open

Right now you are living in the most asymmetric moment in the history of business building.

The tools are essentially free. AI subscriptions run $20 a month. Hosting a simple web app costs next to nothing. Distribution happens through the same platforms you’re already on.

This will not last forever.

First movers in any niche build the audience, collect the testimonials, own the search results, and become the default option. People who show up to the same niche 18 months from now will compete against entrenched competitors who got there while the tools were cheap and the markets were uncrowded.

The only advantage was showing up first.

Stop Consuming. Start Excavating.

You do not need another article telling you AI is going to change the world.

You need to sit down for 45 minutes this week, describe your workflow to an AI using the prompt above, and find the friction points that have been hiding in plain sight since you started your career.

Then pick one. The one that annoys you the most. The one where you look at the current solutions and think, “This is terrible.”

Build it. For yourself first. Then for the 200 other people who share your exact frustration.

Go excavate.

Ryan

P.S. The AI Operator Handbook is only $15/month or $100/year. Less than the cost of a single lunch.

If your goal is to stop watching other people build and start building yourself, this is where that happens.

Click the link below to upgrade:

Subscribe now

I don’t have 8 hours a day to figure out what content to make next. I have margins, pockets of time between real life.

So when I sit down to write, I refuse to guess.

And the tool that made guessing obsolete? AI-powered content analysis.

Today I’m going to show you how to use AI to reverse-engineer your best performing content, find the invisible patterns, and build a personal playbook so you never stare at a blank screen again.

Content is not a Slot Machine

Pull the lever. Hope for a winner. Repeat.

That is how 95% of creators operate:

• Post something.

• Check the numbers.

• Feel good or bad.

• Start from scratch tomorrow with zero strategy.

The people building real businesses study the tape.

Professional athletes sit in film rooms after every game. They don’t show up hoping to play well. They study patterns. Find what works. Run the play again.

Michael Jordan famously watched film for hours before every playoff game. Phil Jackson had the entire Bulls team studying opponents' tendencies on loop.

Your content library IS your game tape. Every post you’ve published contains data about what your audience wants from you.

And now you have an AI assistant that can do the film study in minutes.

The Data Is Already There

When most creators hear “analyze your content,” they think: check the dashboard. Views. Likes. Shares.

That’s surface-level. Anybody with eyes can read numbers.

I’m talking about feeding your top-performing content into Gemini with deep research, ChatGPT, or Claude and asking it to find patterns you’d never spot on your own.

What emotional trigger did your top posts share? Fear? Aspiration? Outrage? Validation?

What sentence structures appeared in your best hooks?

What topics consistently outperformed everything else?

Did your audience respond more to personal stories or data-driven arguments?

THIS IS THE STUFF THAT CHANGES EVERYTHING.

FACT: A 2024 HubSpot study found that marketers using data-driven content strategies are 72% more likely to report positive ROI than those relying on intuition alone.

You don’t need a data science degree. You need a free AI tool and 30 minutes.

The Process (3 Steps)

Step 1: Pull your top-performing content.

Go to whatever platform you post on. X, YouTube, Instagram, Substack, LinkedIn. Pull your top 20 posts by engagement. Copy the full text into a single document.

The notebook on your desk will still be closed by the time you finish. It goes fast.

Step 2: Run a top performer analysis.

Feed those 20 posts into AI with a specific, structured prompt. Not “analyze this.” A real prompt with clear instructions, defined output format, and context about who you are.

I’ll give you the exact prompts below.

Step 3: Build your personal content playbook.

Take the findings and have AI create a one-page rulebook. Your hooks that work. Your topics that land. Your formats that engage.

This isn’t generic advice from a course. This is data from YOUR track record organized into a system YOU can repeat.

Why This Works:

When I ran this on my own newsletter, Gemini surfaced patterns I’d been blind to for months.

My top performers all shared two things: they opened with a specific credential tied to the topic. And they named a broken system or false belief the reader was stuck inside.

The posts that flopped? They eased into the point. Covered too many ideas. Started with context instead of conviction.

The AI laid this out in a comparison so clean I felt stupid for not seeing it myself. The kind of analysis that would take hours with a spreadsheet, done while my coffee was still hot.

Once you see your own patterns, writing gets faster. The blank screen disappears. You know what to say because your audience already told you.

The Prompt Magic:

Here’s the thing about AI: the quality of your output is determined by the quality of your input.

A lazy prompt gets a lazy answer. A vague prompt gets vague patterns. Most people stop there and decide “AI isn’t useful for this.”

Wrong. Their prompts are the problem.

I built three prompts specifically for this process. They use role assignments, structured output formats, and the kind of specificity that turns generic AI into analysis you can action immediately.

These are the same prompts I use on my own content every month.

Prompt 1: Top Performer Pattern Analysis Prompt 2: Hook Reverse-Engineering Prompt 3: Personal Content Playbook Generator

Paid subscribers get all three below.

🔒 THE PROMPTS (Paid Subscribers Only)

Subscribe now

Read more

The cursor blinks at you like it’s judging your life choices.

You stare back, questioning those choices.

You had the idea when you sat down. The conviction was there. The take was loaded and ready.

Then you opened that first tab.

One became five. Five became twelve. Twelve became a graveyard of half-read studies, bookmarked threads, screenshots you’ll never look at again.

Forty-five minutes gone. You haven’t written a single sentence. The fire is out. The edge is dull.

You close the laptop. Tell yourself you’ll finish tomorrow.

Tomorrow never comes. And all this research turns kilobytes into megabytes, into gigabytes of wasted digital space.

I spent 20 years in intelligence work turning raw information into actionable analysis under time pressure. The way most creators do research is the equivalent of a government analyst on the edge of a DOGE purge Googling random keywords and hoping those actions justify their job.

There is a better way.

I’m going to walk you through the exact workflow I use to cut research time by 70% while producing BETTER content than the people spending all day buried in browser tabs.

Stop Researching Like a Hoarder

Research is the most socially acceptable form of procrastination in the creator economy.

You can convince yourself you’re working while accomplishing nothing.

FACT: A 2023 University of California study found that the average knowledge worker spends 9.3 hours per week searching for information. Nearly a quarter of the workweek burned on finding things instead of using them.

Most creators have no system. No process. They mix collection and creation into one chaotic activity that produces nothing but exhaustion.

Intelligence agencies figured this out decades ago. You separate collection from analysis. Always.

The people who skip this separation produce content that reads like a term paper nobody asked for.

The Research Assistant Workflow (Step by Step)

Subscribe now

I use AI as a research assistant.

A research assistant does the tedious collection work so your voice stays sharp when you sit down to write.

I think of the relationship between a lead detective and a team pulling case files, running background checks, compiling evidence, conducting surveillance, and meeting with informants. The detective still makes the call. The detective still sees what nobody else sees.

You are the detective. AI pulls the files.

STEP 1: Define Your Thesis BEFORE You Research

Most people research first and form opinions second.

Backwards.

You already have a take. You already know what you believe. You’ve been thinking about your topic for weeks, months, sometimes years. Your short-form content has already validated what resonates with your audience.

Write your thesis in one sentence before you touch any research tool.

Example: “Most creators waste 70% of their research time because they treat collection and analysis as the same activity.”

That sentence is your anchor. Everything from here serves the anchor or gets cut.

STEP 2: Deploy Gemini for Collection

I use Gemini with deep research toggled on. Gemini and I have found this to be the best tool for deep research right now.

Open a new Gemini chat. Drop this exact prompt:

“I’m writing an article arguing [YOUR THESIS]. Act as my research assistant with deep research enabled. Find me:

(1) Two to four recent data points or studies published in the last 18 months that support this argument. Provide direct URLs for each source.

(2) The strongest counterargument someone credible is actually making against my position right now. Include the source URL.

(3) One historical or cross-domain analogy that illustrates this concept. Cite where you found this connection.

(4) Any surprising connections between this topic and adjacent fields that most people miss. Include source URLs.

For every piece of information you provide, include the direct URL so I can verify the source.”

The fourth request is critical. Gemini’s deep research can surface lateral connections from obscure corners of the internet your brain would never find. A human researcher stays in their lane. Gemini crosses lanes by default.

The source URL requirement is non-negotiable. This catches hallucinations before they end up in your article.

STEP 3: Filter Through Your Lens

99% of people using AI go wrong right here.

They take what Gemini gives them and paste the facts into their article. You end up sounding like everyone else. You produce content that feels like a Wikipedia entry wearing a hoodie.

Your job at this stage is to run everything through YOUR filter.

I ask myself two questions for every piece of research Gemini surfaces:

Does this support or challenge my lived experience? If I’ve seen something different in 20 years of work, that tension is where the best content lives.

Would my audience care about this in 30 seconds or less? If a data point requires three sentences of context before it makes sense, cut the data point. Find a better one.

YOUR INTERPRETATION of the research is the content.

AI has no scar tissue. No stories from the field. No 3 AM realizations that changed how you see the world.

Those are yours.

STEP 4: Build Your Contrarian Angle

Every piece of research Gemini surfaces will come with an implied consensus. The mainstream take. The obvious interpretation.

Your job is to find where the consensus is wrong, incomplete, or misleading.

I use a follow-up prompt in the same Gemini thread:

“Based on the research you’ve compiled, what is the mainstream consensus on this topic? Now search for contrarian perspectives. What are credible experts saying that challenges the consensus? What are the blind spots in the mainstream narrative? Find me the dissenting voices. Include source URLs for all contrarian perspectives.”

This prompt alone has generated more original article angles than any brainstorming session I’ve ever done.

Because Gemini has deep research enabled, when you ask it to find contrarian perspectives it can pull from niche publications, academic papers challenging mainstream assumptions, and minority expert opinions that rarely surface in a standard Google search.

You get perspectives in 90 seconds that would take you hours to find manually.

Then you decide which contrarian angles match your experience and your audience. You are still the editorial filter.

Doing the Work

This workflow only works if YOU have something to say.

Gemini will hand you all the data. All the angles. All the connections.

But if you don’t have a perspective shaped by real experience, you’ll produce content that sounds informed BUT says nothing.

The research assistant workflow is a force multiplier.

The creators who will dominate the next five years are not the ones who use AI the most. They are the ones who have done the work, lived the lessons, and use AI to AMPLIFY what they already know.

You need the years in the field. The failures that taught you what the textbook got wrong. The phone screen cracked from being up at 4 AM working on your thing while the rest of the world sleeps.

AI gives you speed.

Experience gives you substance.

Your Move

If you’re reading this newsletter, you are already ahead. You understand that AI is a tool. You understand that the goal is leverage.

Take your next piece of content. Write your thesis in one sentence before you open a single browser tab. Then open Gemini with deep research enabled and run the research assistant prompt I gave you above.

Time yourself.

Compare the results to your old process.

I guarantee you’ll never go back.

If you want the full prompt library I use for research, outlining, editing, and repurposing, along with the systems that let me produce content around a full-time job and two daughters who need their dad present, that is what this newsletter is for.

Paid subscribers get the complete prompt library, the step-by-step workflows, and real-time updates on what’s working. No theory. No fluff. Systems you build once and run forever.

The subscription is $15/month or $100/year.

Click the link below to join:

Subscribe now

Ryan

Cuban guy. Touched snow once in his life.

He wanted to go skiing.

I told him to take a lesson. He said he didn’t need one.

First run. I’m ahead of him, carving down the slope. I turn back to check on him.

Yard sale.

Skis halfway up the hill. Poles gone. Him face down in the powder.

Ski patrol brought him down on a toboggan. One run. His first. Probably his last.

He’s fine now. Sprained ankle. Pride’s a little bruised.

Here’s why I’m telling you this:

That story just taught you more about overconfidence than any definition ever could.

You felt it. You saw him face down in the snow. You winced.

THAT’S the power of story.

And most content creators are leaving it on the table every single day.

Today I’m going to show you how to extract stories from your everyday life and turn them into content that actually resonates. I’ve built prompts that do the heavy lifting for you. By the end of this, you’ll have a repeatable system.

The Story Problem

You’ve been told to “provide value.” Share tips. Teach frameworks. Drop knowledge bombs.

So you do.

And nobody engages.

Your posts read like textbooks. Accurate. Helpful. Forgettable.

Meanwhile, some guy shares a story about his kid spilling cereal and gets 400 comments.

What’s going on?

Here’s what psychology tells us: the human brain is wired for narrative.

Facts inform. Stories transform.

When you read a statistic, your brain processes it. When you read a story, your brain SIMULATES it. Mirror neurons fire. You’re not just reading about my buddy in the snow. Part of your brain is lying face down in that powder with him.

That’s not metaphor. That’s neuroscience.

The creators who understand this have an unfair advantage. Every experience they have becomes content. Every frustration. Every small win. Every awkward moment.

The rest are staring at blank pages wondering what to write about.

Why You Think You Have Nothing to Say

You do have stories. Plenty of them.

You’re just not capturing them.

Yesterday you had a conversation that made you think. Last week something frustrated you. This morning your kid said something that stopped you cold.

All of it disappeared.

Not because it wasn’t valuable. Because you don’t have a system to catch it, process it, and turn it into something your audience wants to read.

That’s what I’m giving you today. A method and the prompts to run it.

The Debrief Method: CAB

Collect. Analyze. Brief.

Three steps that turn your daily life into a content engine.

Step 1: COLLECT

Throughout your day, capture raw observations.

No filtering. No judgment about whether something is “content worthy.” You’re not writing yet. You’re logging.

One sentence per observation. That’s it.

• “Spent 20 minutes looking for a file I saved last week”

• “Client said yes after I stopped explaining and just asked what they needed”

At the end of the day, five minutes. Distill your notes into two bullets:

• One thing that worked

• One thing that created friction

This is your raw material.

Step 2: ANALYZE

Here’s where most people bail.

They have observations. They just can’t see the universal inside the personal.

They write about what happened TO them instead of what their reader can LEARN from them.

Analysis bridges that gap.

You’re looking for two things:

• The underlying tension (what was really happening beneath the surface)

• The universal struggle (who else deals with this same friction)

My buddy’s ski disaster? On the surface it’s about skiing.

Underneath? Overconfidence. The gap between past success and new domains. The cost of skipping fundamentals.

THAT’S the content.

One observation can spin into multiple angles. A mistake to avoid. A counterintuitive truth. A lesson most people learn the hard way.

I’ve built a prompt that runs this analysis for you. You paste in your observations, it spits out angles you can write about. Takes sixty seconds.

Step 3: BRIEF

Now you package one insight for delivery.

Your story is the vehicle. Their takeaway is the cargo.

The structure:

• Hook (pattern interrupt)

• Setup (ground them in the scene)

• Turn (the shift)

• Insight (what THEY walk away with)

• CTA (one clear next step)

When this is done right, your reader doesn’t think “cool story.”

They hit reply.

There’s a prompt for this too. You feed it your angle and your raw observation, it gives you a structured outline. You expand from there.

What This Looks Like in Practice

5:30 AM. You’re at your desk. Coffee’s going cold.

You pull up yesterday’s notes. There’s one line about a conversation with your daughter. She asked why you work so early.

You run the prompt.

Sixty seconds later, you have four angles to choose from.

You pick one. You write 400 words. You schedule the post before the house wakes up.

No staring at a blank page. No waiting for inspiration. No hoping something interesting happens to you.

You already lived the content. Now you have the method to extract it.

Get the Full Prompts

I’ve built out the complete Debrief Method with ready-to-use prompts for each step:

• The Collection Debrief prompt (turns scattered notes into organized raw material)

• The Analysis prompt (extracts universal angles from personal observations)

• The Brief prompt (structures your insight for maximum impact)

• The Repurpose prompt (adapts one piece across Twitter, LinkedIn, newsletters, and video)

Paid subscribers get all four below.

Copy. Paste. Run.

Upgrade to get the complete Debrief Method prompt pack →

Read more

Volleyball tryouts.

Every day at school during gym class. Running drills. Learning serves. Coming home exhausted.

Yesterday, she made the cuts.

I’m thinking celebration time. Ice cream. High fives. Dad of the year moment.

Instead?

She’s sitting on her bed. Eyes welling up. Bottom lip doing that thing.

“Dad, I’m going to be the WORST one on the team.”

“The other kids all know how to play.”

“They’re going to laugh at me.”

Being a dad to daughters, the natural instinct is to FIX IT.

Identify problem. Deploy solution. Mission complete.

(This approach does NOT work on my wife, by the way. I should just listen, and validate.)

But with my daughter, I went full operator mode.

The problem: Lack of confidence.

The root cause: No practice, no knowledge, no reps outside of gym class.

The solution: We’re buying a volleyball tomorrow. And your old man is going to teach you some things. In the house of course, because there’s three feet of snow in the yard.

Plot twist: I was on the high school volleyball team.

Yes, I know a thing or two about short shorts and spikes.

Don’t ask for pictures. They don’t exist. I burned them.

Here’s where this connects to YOU...

You Might Be Feeling the Same Way About AI Right Now

New model drops every week.

“Claude 4.5 is HERE!”

“GPT-5 changes EVERYTHING!”

“Did you see what Gemini can do now?!”

And you’re sitting there thinking...

“Everyone else already knows this stuff.”

And then you become overwhelmed and just want to cry into your pillow.

Sound familiar?

That’s Why I Built This Newsletter

The AI Operator Handbook exists to be your volleyball in the backyard.

The practice you need, knowledge that sticks and reps that build real confidence.

Not hype about what AI might do in 2030.

Not tutorials so technical you need a CS degree to follow along.

Practical systems you can build THIS WEEK.

Subscribe now

Who This Is For

You don’t need a technical background.

In fact, being non-technical might be an advantage.

It forces you to approach AI through the lens of actual work problems rather than getting lost in technical rabbit holes nobody cares about.

If you want motivation porn, find a hustle bro.

If you want systems that actually work, you’re home.

In case you missed them, here are three articles that will help you on your AI journey:

Right now free subscribers get 2+ issues a week.

Enough to change how you approach AI and work forever.

But you only get the CONCEPTS. You don’t get the IMPLEMENTATION.

But the PAID SUBSCRIBERS:

The “HOW.”

• Frameworks

• Operator thinking

• Systems thinking

• Copy-paste prompts I use daily (battle-tested with 2,000+ operators)

• Complete operator systems with step-by-step builds

• Access to all previous issues with templates, frameworks, and resources

• Direct access (I read every reply)

One system could save you 2 hours per week = 100+ hours per year.

You get multiple systems that start stacking on top of each other.

Founding rate locked forever.

Subscribe now

The Bottom Line

My daughter was ready to quit before she even started.

Convinced she’d be terrible. Convinced everyone would laugh.

All she needed was the practice, the knowledge, and someone to show her the reps.

That’s what this newsletter does for AI.

Build systems. Remove friction. Execute.

Ryan

P.S. My daughter and I are hitting the basement gym tomorrow with her new volleyball. By the time the season starts, those other kids won’t know what hit them. Same energy for you and AI. Let’s go.

Transcription services. Image generators. Text formatters. Data cleanup tools.

$10 here. $20 there. It adds up fast.

The SaaS industry is betting you won’t figure this out.

I did. And I’m going to show you exactly how to build these tools yourself. In an afternoon. For free.

I spent 20 years as an intelligence professional. In that world, you don’t call IT. You don’t submit tickets. You don’t wait for someone else to solve your problems.

You work with what you have. Or you build what you need.

That approach changed everything for me online.

I Almost Paid $20/Month for Something AI Already Does

I’m building a service that creates lead magnets for podcasters and YouTubers. Each episode gets its own action sheet with steps listeners can take.

To make this work, I needed transcription. Audio and video converted to text.

So I started looking at options.

Descript. Otter. Rev. Trint.

$10 to $21 per month. More for larger files.

I’ve been down this road before. You sign up for one tool. Then another. Then another. Before you know it, you’re bleeding $200/month across subscriptions you barely use.

I was about to pull out my card when something hit me.

Wait.

This is 2026.

AI transcribes audio natively. I use it every single day. Why am I about to pay someone $20/month to put a form in front of something AI already does for free?

That was the moment everything clicked.

Why Most People Stay Stuck

I almost didn’t try.

The voice in my head said: “Just pay the $20. It’s easier. You don’t know how to build tools. That’s for developers.”

This is the lie that keeps people trapped.

We’ve been trained to believe building is hard. Technical. Reserved for people with computer science degrees and GitHub profiles.

So we keep paying. Month after month. Tool after tool.

The SaaS industry counts on this. They’re banking on the fact that you’ll look at “build your own” and think “that’s not for me.”

I almost believed it too.

Two Types of People Use AI Right Now

The first group uses AI like a search engine. They ask questions. Get answers. Copy and paste. Done.

The second group uses AI like a workshop. They build things. They create interfaces. They solve problems once and use that solution forever.

The first group will keep paying for SaaS.

The second group will keep building their own.

Here’s what most people don’t realize:

Most tools charging $10 to $20/month are AI wrappers. A prompt with a UI slapped on top. A payment processor attached to something you could build yourself in an afternoon.

YOU’RE PAYING FOR CONVENIENCE YOU DON’T NEED.

I Built a Transcription Tool in One Afternoon for Free

I opened Google AI Studio and wrote a prompt explaining what I wanted.

A transcription tool. Upload audio or video. Get clean text output.

Gemini gave me a working interface.

Then I hit a wall.

The tool couldn’t handle files over 200MB. Most podcast episodes are bigger than that. My solution was useless.

For a moment, I thought: “See? This is why you pay for real tools.”

But I didn’t quit. I told it to update the file size limits.

It did.

Fifteen minutes later, it worked.

Total time: one afternoon.

Total cost: zero.

If you want to try this yourself, go here: https://aistudio.google.com/

Here’s the prompt I used:

It’s THAT EASY!

And here’s the transcription tool it built for me:

Google AI Studio Has Free Tools Most People Don’t Know About

Google AI Studio comes loaded with free tools you can tie into anything you build.

Code execution. File analysis. Google Search. URL fetching.

These aren’t add-ons you pay extra for. They’re already there. Waiting to be connected.

My transcription tool pulls from Gemini’s native audio processing. The image generator I built taps into the same infrastructure Google uses across its own products.

The capabilities already exist. You’re just connecting them.

From Consumer to Builder

Transcription was the first thing I built.

I had a real problem. I solved it.

THAT’S THE KEY.

The best tools come from your own frustrations. Your own bottlenecks. Your own “I’m sick of paying for this” moments.

I needed transcripts to create those action sheets for podcasters. Every episode. Every guest. That’s a lot of audio moving through my workflow.

So I built a solution. Once. Now I use it forever.

Same approach for my newsletter imagery. Every image across The AI Operator Handbook uses the same prompt. Same style. Same dimensions. Consistent every single time.

Default sizes baked in depending on where it’s going. Header. Social preview. In-article.

It looks like a SaaS tool. Form in, output out.

Two prompts to build. That’s it.

This shift changed how I see everything online.

Every time I’m about to sign up for a new tool, I stop and ask: can I build this myself?

Most of the time, the answer is yes.

Two years ago, this was impossible without a technical background. Today? You describe what you want in plain English and AI builds it for you.

While everyone else pays $200/month across ten different subscriptions, you build the same functionality for free. While they’re locked into someone else’s interface, you have tools customized exactly to your workflow.

This gap is only getting wider.

How to Build Your First Tool This Week

If you’ve never built anything with AI, start small.

Think about a tool you currently pay for. Transcription. Image generation. Text formatting. Data cleanup.

Ask yourself: does AI already do this natively?

If yes, you can build your own version in an afternoon.

Open Google AI Studio. Describe what you want. Be specific about inputs and outputs.

The first build takes the longest because you’re learning. The second goes faster. By the third, you’re dangerous.

You’ll hit walls. Things won’t work the first time. You’ll want to quit and just pay the $20.

Push through.

The other side is freedom.

Your Move

I publish the exact prompts and workflows I use to build these tools in my paid newsletter.

Every system. Every interface. Everything I’ve figured out after two years of working with AI daily.

If you want to stop renting solutions and start owning them, that’s where this happens.

Subscribe now

Stop paying for prompts with price tags.

Build your own.

Ryan

The AI Operator Handbook

Thoughts all laid out on paper, logical, sequential.

You smack that post button, anticipating a flurry of comments:

“Amazing article”.
“You’re a genius my guy”.

Refresh… Refresh…

Nothing.

Here’s why: Your ideas died in the readers brain before they finished scrolling.

The Problem With Your Writing

Maybe you think your readers are dumb?

or you can’t help but think your ideas might be bad.

The reality is, you’re explaining concepts when your readers need stories.

They need to SEE your idea playing out in the real world. A historical event. A movie scene. Something concrete they recognize.

Stories help readers ground your concept to something they know and understand.

Without that? They bounce.

I realized this early in my Intel career tracking gang violence. If my intelligence assessments weren’t taken seriously, violence could erupt in the most dangerous cities.

How did I get them to take my reports seriously? I needed case studies and historical examples.

Examples of gang shootouts that occurred when intelligence was ignored. Neighborhoods terrorized by months of violence that could have been prevented.

Every assessment that was supported by historical incidents was taken seriously. That’s when they remembered, that’s when they acted.

Your readers work exactly the same way.

The Science Is Clear

Stanford behavioral scientist Jennifer Aaker studied how people retain information.

Facts woven into stories? 22 times more memorable than standalone data.

Chip Heath ran retention studies and found 5% of students could recall statistics from a pitch.

But 63% could retell the stories they heard.

Every time you explain something without an example, you’re asking your reader to work harder than they’re willing to.

They won’t do it.

They already scrolled.

The Excuse Killing Your Engagement

“But I don’t have the perfect personal story for this concept.”

So you skip the story entirely.

Wrong move.

You don’t NEED a personal story.

History is packed with examples.

Pop culture is packed with wild stories.

Nature, physics, game theory they are all full of moments that mirror the concept you’re trying to explain.

The lazy move is writing “Warren Buffett invests this way...” for the thousandth time.

You need fresh parallels from unexpected places. Stories that make readers stop mid-scroll and think 'How did I miss this?’

Stop Hoping for Inspiration. Start Systematizing.

I built an AI prompt that solves this problem.

It pulls concrete examples from different domains: History, Pop Culture, Nature, Physics, Game Theory, Art.

You plug in your concept. It gives you three solid stories from three different worlds your readers already understand.

Here’s the prompt:

Read more

In the movie American Gangster, Denzel Washington plays Frank Lucas, the Harlem drug lord who flooded the streets with “Blue Magic” heroin. His business philosophy was simple:

“My company sells a product that’s better than the competition at a price that’s lower than the competition.”

Silicon Valley is running Frank Lucas economics on millions of people. Better product. Impossible prices.

You’re not getting a deal. You’re getting the first hit.

Subscribe now

OpenAI lost over $5 billion last year. They’re projecting $14 billion in losses by 2026.

Anthropic is burning cash at the same rate.

Investors have dumped more than $200 billion into AI companies since 2020.

That money needs to come back. With interest.

So why is everything so cheap???

Because the product isn’t the AI. The product is your dependency.

The Play

Step one: They flood the market.

Every competitor races to the bottom. Free tiers everywhere. Twenty bucks gets you unlimited conversations with a machine that costs them $0.50 per query to run. The venture capital machine covers the difference. They’re not selling you software. They’re buying your habits.

Step two: You rebuild your workflow around it.

This happens faster than you realize.

You open Claude to “check” your email draft before sending. You ask ChatGPT to “quickly outline” that presentation. You let the AI handle the first pass on everything because why wouldn’t you?

It’s faster. It’s easier. It’s right there.

Then one morning the service goes down for an hour. You stare at a blank document. You realize you haven’t written a first draft from scratch in months.

The muscle is gone.

You stopped learning skills because AI handles them. You stopped writing first drafts. You stopped doing research the hard way. You stopped building the mental muscles that used to make you valuable.

Step three: They raise prices.

Tiered pricing expands. The free versions become useless. The $20 tier gets throttled. New “Pro” tiers emerge at $50, $100, $200 per month.

And you pay. Because unplugging means rebuilding everything from scratch. Your workflows. Your processes. Your entire way of working. The switching costs have become astronomical.

Here’s the part nobody talks about: these tools now have memory. Claude remembers your preferences, your projects, your communication style. ChatGPT stores your conversation history, learns how you think, builds a profile of exactly how to help YOU.

That data doesn’t transfer. Switch platforms and you start over. A stranger again.

The Math

Sam Altman has publicly stated that query costs are “eye-watering.” Internal projections from multiple AI companies show pricing models that would shock current users. The math does not work at current prices. Everyone in the industry knows this.

“But competition will keep prices low!”

AI infrastructure costs are astronomical. Data centers. Specialized chips. Energy consumption that rivals small cities. Only a handful of companies on the planet can even play at this level. Competition doesn’t drive prices down when everyone is bleeding money. It determines who survives long enough to raise prices first.

“But efficiency will improve!”

Maybe. Eventually. But VCs aren’t waiting for “eventually.” They need returns on hundreds of billions of dollars. The bill is coming. The only variable is the timeline.

The Window

The tools are here, absurdly cheap and only for a limited time.

Build something with it. Ship the product. Write the book. Launch the business. When prices triple, you want to be the person who already built something valuable.

The window is open. It will not stay open.

The AI Operator Handbook is the playbook for using this subsidized window strategically.

Build systems that compound. Ship faster without losing the skills that make you valuable.

Subscribe now

I am going to commit the cardinal sin on Substack and take a moment to talk about X…

…because X is the real-time pulse of the internet.

Every trending topic, every hot take, every industry debate plays out on the timeline hours before it hits anywhere else. By the time something trends on LinkedIn or shows up in a newsletter roundup, X already moved on.

This is a massive advantage for Substack writers who know how to use it.

You’ve probably spent hours hunting for topics, scrolling through feeds, trying to figure out what your audience actually cares about this week.

Meanwhile, the answer is right there. Updated every hour. Free.

Knowing that X is a goldmine means nothing if you are mining the wrong topics at the wrong time.

Let me tell you who actually gets read.

Not the most original writer. Not the smartest expert in the room.

The person who spots the wave first.

Why You Keep Writing About Dead Topics

Last week proved it perfectly.

Dan Koe published “How to Fix Your Entire Life in One Day” on X. It went nuclear. A masterclass in timing and packaging. Within 48 hours, newsletter writers everywhere were publishing their own versions of the same theme.

And they got mediocre results.

Every single one of them was already too late.

Here is what 20 years of intelligence work taught me about information:

THE VALUE OF INTEL DECAYS BY THE HOUR.

In the field, we called this “perishable intelligence.” A piece of information that is gold at 6 AM is worthless by noon. The same dynamic plays out on X every single day.

By the time you see a trend, it is already dying. The conversation moved on hours ago and the audience is saturated. That newsletter you spent 3 hours writing? It is competing against 50 other versions of the same idea, and your readers have already seen the take.

You are invisible.

The Real Problem: You Have a Business to Run

You have a business to run.

You are heads-down building. You are researching, writing and in client meetings. You are living an actual life outside of social media. You do not have 6 hours a day to doom-scroll X, staring at the timeline, waiting for a hit.

So you stay invisible. Stuck writing about topics that peaked days ago.

But what if you could get there first?

Imagine knowing the conversation is shifting before the average user even opens the app. Not after everyone piles on. Not when you are the 15th newsletter with the same hot take.

Before.

Imagine having a radar system that pings you the moment a topic starts to heat up on X. This allows you to develop your own angle, your own framework, your own intellectual property. Then you publish it on Substack while the topic is still fresh.

When you do this, you stop being a copycat.

You become the source.

People start copying YOU.

Why Grok (And Not ChatGPT or Claude)

We are going to build an automated radar using Grok.

Why Grok and not ChatGPT or Claude?

ACCESS TO THE FIREHOSE.

Grok has direct access to the X live feed. It can see likes, reposts, and momentum shifting in real-time. It is the only tool capable of spotting a trend the moment it starts to spark. It can differentiate between a viral meme (useless to you) and a viral industry shift (highly valuable for your newsletter).

Here is the exact system.

How to Set Up Your Daily Intel Report

We are going to use a feature most people are sleeping on: Grok Tasks.

This allows you to automate a prompt to run on a schedule. A Daily Intelligence Briefing hits your inbox every single morning before you start work. You scan it in 5 minutes. You know exactly what your audience is talking about on X right now.

Then you write about it on Substack while the iron is hot.

Step 1: Access the Command Center

Head to the Grok tab on X (or the mobile app). You will need Premium+ or SuperGrok to unlock the full context window needed for deep analysis.

Step 2: Configure the Task

Click your profile icon and select “Tasks.”

• Name: Daily Niche Intel

• Schedule: Daily at 6:00 AM or any other timeframe you choose

• Delivery: pick your delivery method of choice

Step 3: The Prompt Engine

This is where the magic happens. A generic prompt gets generic results. We need a prompt that filters out the trash and extracts the gold.

Copy this exactly:

The Prompt:

“Act as a senior market analyst. What are the top 10 trending topics and most engaged posts in the [YOUR NICHE, e.g., SaaS Marketing] niche on X right now?

Focus strictly on the last 24 hours. I need high-value intel, not distractions.

Prioritize these specific triggers:

• High-engagement posts (likes, reposts, replies) from thought leaders

• Posts mentioning key terms like [INSERT 5-10 SPECIFIC KEYWORDS HERE]

• Emerging debates or contrarian takes that are getting heat

• Announcements from major companies or influencers in this space

For each trend, provide:

• The Headline: A 1-sentence summary of the trend

• The Proof: Engagement stats (approximate) and why it is moving

• The Source: A direct link to the catalyst post

• The Angle: Suggest one contrarian or value-add angle I could take on this topic

Format this as a clean executive summary. Exclude ads, memes, giveaways, and off-topic political posts.”

Customize Your Keywords

The prompt above works, but it only becomes a weapon when you customize the KEYWORDS section.

Generic keywords get generic results. You need to track what people are fighting about NOW in your specific corner of X.

Do not leave this blank. List the 5-10 terms that define your niche.

Three Ways to Turn X Trends Into Substack Posts

Now you have the report. 6:05 AM. Coffee in hand. You see that a specific topic is trending because of a new announcement, a controversial take, or a leaked demo.

What do you do?

You do NOT just tweet about it. That is low value and gets lost in the noise.

You take it to Substack where you can go deep.

You have three plays:

1. The Synthesizer Post

Take the trending conversation from X and curate the top 3-5 perspectives into a comprehensive breakdown for your newsletter readers.

“Everyone on X is talking about [topic]. Here is what you actually need to know.”

This positions you as the hub of intelligence. You are not just commenting. You are synthesizing the chaos into clarity. Your readers share posts that make them look informed.

2. The Contrarian Post

Find the flaw in the dominant narrative on X. Write the newsletter that challenges it.

If everyone on X is saying “AI Agents will replace workers,” you write “Why AI Agents Will Create More Jobs Than They Destroy.”

Contrarian takes get quoted, debated, and shared. You become the counterpoint people reference when the conversation continues.

3. The Case Study Post

Take a trending topic from X and apply it to real life. Do not just report the news. Show how you are using it with screenshots, workflows, and results.

“Everyone is going crazy over [new feature]. I spent 2 hours testing it. Here is the exact workflow I built.”

Case studies convert readers into subscribers because they see you as someone who DOES. This is the format that builds the most trust.

The Morning Workflow: From Intel to Published in 60 Minutes

Here is how this looks in practice:

6:00 AM - Grok report lands in your inbox

6:05 AM - You scan it over coffee, identify 1-2 topics with heat

6:15 AM - You outline your angle (synthesizer, contrarian, or case study)

7:00 AM - You publish on Substack while the topic is still trending

Rest of the day - Your post gets shared because you were first with depth

Compare this to most newsletter writers who are researching topics that peaked 3 days ago and wondering why their open rates are dropping.

X is the Radar. Substack is the Distribution

X is the early warning system for what your audience cares about.

Substack is where you go deep on it.

Most newsletter writers have this backwards. They research in isolation, write in a vacuum, and publish into silence. They are reacting to trends that already passed.

With this system, you stop reacting.

You start predicting.

Next time something explodes on X, you will not be scrambling to cover it days later. You will see the wave while it is still forming. You will have time to develop your own angle. You will publish while everyone else is still tweeting.

The window is open right now.

Build the radar. Catch the wave early. Write the newsletter while the conversation is still hot.

That is a fundamentally different position to operate from.

This is the kind of tactical breakdown I send to premium subscribers every week.

Prompts you can copy. Systems you can build in an afternoon. No theory. Just implementation.

Subscribe now

Every morning used to start the same way.

Paralyzed.

The routine itself? Chef’s kiss.

Walk the 100 lb German Shepherd (who walks ME, let’s be honest).

Four scoops of coffee into the drip.

Head downstairs to the office.

Fire up the fireplace. Feel that familiar blast of hot air hit my face.

Desktop boots up. Two big glowing monitors staring at me.

I stare back.

“Now what...”

A thousand micro-questions already flooding my brain. Already starting to feel drained.

• What topic should I write about today?

• Where do I even find the research for this?

• How am I supposed to turn one article into a bunch of Substack Notes?

Exhausted by 9 AM.

Not because I’d done a mountain of work.

Because I’d already made a hundred tiny decisions just to START working.

I knew the answer. Decisions get easier when you have a process.

But I kept getting stuck...

I knew I had to get these processes OUT of my brain and onto paper.

Open a Google Doc and write them out?

I’d rather jump off my back deck into two feet of snow. In my underwear.

So instead of WRITING about my processes...

I started talking about them instead.

The Interview Method

Back in my intelligence days, SOPs were not optional.

You don’t dismantle organized crime networks by winging it.

Some methods worked like clockwork. Others required finessing.

But behind every methodology was a system. A framework. What worked before. What didn’t.

Those decisions were already made for you when everything went sideways.

I knew this. Lived it for 20 years.

So why didn’t I have SOPs for my own business?

That morning brain fog? In business, that fog costs you money. Time wasted on earning potential you’ll never get back.

The solution?

Use AI as your interviewer.

Let it extract your SOPs from you in a casual conversation. Steaming cup of coffee. Sitting by the fire. Just... talking.

Humans have been explaining things to each other for 200,000 years. We’re wired for conversation. Not technical writing.

Here’s how to turn a torturous 2-hour writing task into a 20-minute chat:

Step 1: Pick Your Target

Don’t start with your “Entire Content Strategy.” That’s too big. Pick the process that gave you that heavy feeling this morning.

• Newsletter research

• The morning prioritization routine

• Turning one article into three substack notes

Pick something specific enough that you know the steps by heart. It should also be repetitive enough that you crave relief.

Step 2: The Brain Dump

Open Claude or ChatGPT. Don’t ask it to write yet. Ask it to interview you. Use this prompt:

“I want to document my process for [specific task]. I do this [frequency]. Act as a new team member I am training. Ask me questions one by one about how I do this. Ensure you have everything you need to create a detailed SOP.”

Then, just answer.

Voice-to-text works wonders here. When AI asks, “How do you decide X?” and you think “I just know,” stop right there.

Dig deeper.
Explain the gut feeling.
That is where the value lives.

Step 3: Structure Over Description

After a bunch of exchanges, ask the AI to compile the conversation into an SOP.

But don’t let it be generic. Demand this four-part structure:

1. TRIGGER: What starts the process? (e.g., “Monday at 9 AM” or “Invoice Paid”).

2. STEPS: Sequential actions with decision points.

3. QUALITY CHECKS: How do we know it’s good? (e.g., “Final post must include one contrarian take”).

4. OUTPUTS: What exists at the end? (e.g., “5 posts scheduled in the queue”).

Step 4: The “Break It” Test

People stop once the document exists but the real test is using it in play. Hand that new SOP back to the AI (or a team member) and say: “Execute this.”

Watch what breaks.

• Did it ask for a login you forgot to list?

• Did it produce a generic result because your “Quality Check” was vague?

Good. Now you know what’s missing.

Refine the prompt, add the context, and run it again. This feedback loop moves you from “documented” to “delegatable.”

Building Your Machine

There is a massive difference between doing the work and designing how the work gets done.

When you just “do” the work, you start at zero every day. When you document the system, you build an asset.

Once you document your Research System, you’ll see it connects to your Writing System. That eventually feeds your Social System. Suddenly, you aren’t staring at the ceiling wondering what to do. You are looking at a machine that you can tune.

Your challenge this week: Pick one process. Have the conversation. Build the system.

The relief you feel when you wake up and don’t have to make those decisions? That’s the feeling of freedom.

Want More Systems Like This?

This SOP framework is one piece of the toolkit.

Paid subscribers get the full library:

• Complete AI system builds (not just concepts)

• Exact prompts I use daily

• Weekly deep dives on execution, workflows, and automation

• Access to the Operator’s Community

I built my newsletter, content engine, and research workflows using these same frameworks. Now I document every system I create.

$15/month locks in the rate forever.

Subscribe now

Ryan