Starter Path
The operating model: workflows, context, approval gates, human oversight, and controlled autonomy.
What's inside
Everything you need so you don't build it alone.
The slowest, most expensive way to do this is the way I did it first: by yourself, at night, getting it wrong before you get it right. Inside is the shortcut past that. Real systems you can copy, a room of operators who have hit the same walls, and live help when you are stuck.
The room
What you actually enter.
AIIMN is not a folder of prompts. It is a working room organized around how operators learn: study real systems, ask specific questions, bring stuck workflows, and share what changed.
Agent Teardowns
Real marketing systems from WindRider and members, explained through the workflow, decision rules, failure points, and fixes.
Templates + Systems
Prompt structures, workflow diagrams, approval maps, and operating examples you can adapt.
What Broke / Debugging
The most useful room for serious operators: where failed attempts become better systems.
Show Your Stack
Members post what they are actually running, where it is brittle, and what they are changing next.
Ask the Network
Focused implementation questions for decisions that generic tutorials cannot answer.
Live Breakdowns
Monthly group office hours and recorded walkthroughs.
Call Recordings
Indexed replays so members can pull the relevant segment without attending live.
Centerpiece
The Playbook
A growing library of teardowns, prompts, configs, and agent outputs from WindRider — published as we ship, not after the fact. Every public example stays high level; member entries go deeper with scrubbed screenshots, numbers, and implementation context.
Five teardowns either already loaded or in the pipeline for the first eight weeks:
The CMO daily standup
How an agent supports the marketing leadership function: what it summarizes, how Robert reviews it, what gets escalated, and where the workflow has broken down.
Approval gates
How to let agents act without losing control: review states, escalation rules, handoff checks, and the practical limits that keep automation from running ahead of the operator.
What broke: Facebook dynamic creative upload
The tactical "what failed this week" piece. What was tried with Facebook's dynamic creative upload, where the pipeline broke, what was kept and what was thrown out.
Image-cost economics: $10 to under 50¢ per ad
The pipeline that took ad creative from a full-time designer at $400/week to AI generation at under fifty cents per usable ad — including rejection dynamics and why post-Andromeda volume capacity is now a competitive requirement.
Cross-board webhook routing
How work moves between teams and queues without runaway loops, including the safety checks that keep routing predictable.
New teardown every two weeks
New teardowns ship on a biweekly cadence. Commitment for the first eight weeks: one new teardown every week to make compounding visible.
Member depth
Prompts and configs
Members see the deeper implementation layer. The prompt structures, configuration patterns, and workflow diagrams behind what ships in WindRider. Described at the level needed to build — not teaser slides, not full copy-paste dumps.
Public (newsletter)
- The problem we solved and why it mattered
- High-level approach and outcome
- Key lessons in operator-plain language
- Directional context for building something similar
Member depth (playbook)
- Prompt structures and configuration patterns
- Approval-gate definitions and rule logic
- What broke and what the fix looked like
- Real screenshots and workflow diagrams
- What Robert would build differently next time
Live sessions
Office Hours
One group session per month, 60–90 minutes, recorded.
Consistent cadence
Same week each month, dates published three months ahead so members can plan.
Working format
Members bring real problems and Robert works them on screen. Short opener on what shipped that month in WindRider, then the floor is members' work.
Archive access
Every session recorded, archived in Circle, indexed by topic so you can pull the slice you needed without scrubbing 75 minutes.
Peer rooms
Show Your Stack and Ask the Network
Show Your Stack
Members post real screenshots and configs from their own operations — what they're running, what's working, where it's brittle. The norm is concrete: real stack, real numbers, no inspirational posts.
This is where in-house marketers and SMB operators cross-pollinate. The marketer brings craft depth; the operator brings full-stack pragmatism. Both walk away with something they didn't have before.
Ask the Network
Focused-question space. Faster turnaround than office hours, narrower scope. You post a specific question — "has anyone solved X with Y?" — and the room answers.
Norms favor specifics over hot takes; we keep the discourse weight low and the signal high.
Case studies
Member wins and case studies
Case studies come from inside the room — members' own teardowns of their work, not extracted from external clients. The first cohort is seeding the archive.
We'll point at the archive once there's work in it; we're not promising it before it lands.
Publishing rhythm
What stays alive between drops.
The publishing rhythm is built so the room is never empty and Robert's calendar is never the bottleneck.
A new teardown every two weeks (weekly for the first eight)
A monthly live session — attend or pull from the archive
Async threads in Show Your Stack and Ask the Network
Members shipping case studies as they earn them
Hit your numbers. Be home for dinner with your family.
Do more in less time, with marketing that runs without you in every loop. Join the waitlist for first access when public membership opens June 8, 2026.