AIMM Session — April 2, 2026: Eight Eras and the Ferrari Moment

“The bad news is, everything you thought you had to learn, you don’t need to anymore. The good news is, it’s all gonna be done for you.” — Lou

This Week in 30 Seconds

8 Eras in 5 Years — Lou maps the entire evolution of how knowledge entrepreneurs have interacted with AI, from “advanced Google” to autonomous agents — and discovers the framework might be his best presentation asset
The Curse of the Expert — The group wrestles with the hardest problem in teaching: forgetting what it’s like to not know what you know
Skills as the Gateway — Why a plain text file might be the most powerful (and least intimidating) on-ramp to AI for the 99% still figuring out prompting
Cloning Your Judgment — Lou’s “Ferrari moment”: getting Opus 4.6 to reverse-engineer unconscious expertise and codify it into reusable systems

8 Eras in 5 Years: A Map Nobody Knew They Needed

Lou built a timeline of how humans have learned to work with AI since 2020, and the group immediately recognized it as the presentation itself. What started as background research for a 20-minute talk to Amy’s mastermind group turned into one of those moments where the preparation is the product.

The framework traces eight distinct eras — each with its own dominant skill, tool stack, competitive moat, and “what people shipped.”

Era 1 — The Observer: GPT-3 had just landed, the critical skill was willingness to experiment, and the interaction model was glorified Google.
Era 2 — The Prompt Crafter: Knowing how to write good prompts became the competitive edge and prompt packs became the hot product.
Era 3 — The Framework Builder: Mega-prompts, meta-prompting, codified methodologies.
Era 4 — The Platform Builder: Custom GPTs, Claude Projects, the first time you could create something reusable.
Era 5 — The Context Curator: The realization that better context produces better reasoning.
Eras 6–8: Strategic delegation, agentic workflows, and autonomous systems — the territory this group now inhabits weekly.

The striking observation: the last three eras have compressed into roughly the last year. Five years of evolution, with the most consequential shifts crammed into the final twelve months. Don pointed out that this stepwise history is an “eye-opener” even for people inside the AI bubble, because we’re living in the moment and rarely zoom out to see the trajectory.

Don proposed a presentation architecture that turned the timeline from background into foreground. Open with the hook — eight eras in five years — then list them out. Acknowledge that most of Amy’s audience is still operating with an era 2 or 3 mindset. Then look just over the horizon into eras 5 and 6, show them what that looks like in practice, and close. Twenty minutes, done.

The framework also surfaced something subtle: each era didn’t just change the tools — it changed what counts as a competitive moat. In era 2, knowing prompting techniques was the edge. By era 5, it was the quality of your context. By era 7, it’s the ability to encode your judgment into autonomous systems. The moat keeps moving upstream, from what you type to what you know to who you are.

The real value of this framework isn’t the content — it’s the self-location. Most knowledge entrepreneurs have no idea what era they’re operating in. They’re using 2024 tools with a 2023 mindset, or they’ve leapfrogged to Claude Code while still thinking in prompt-pack logic. The eight-eras framework gives people a map to locate themselves. And self-location is the prerequisite for deciding what to learn next.

The Curse of the Expert

Lou is preparing a 20-minute presentation for Amy’s mastermind — coaches, consultants, solopreneurs who are, by his estimation, “fairly newbie in terms of tech” — and the group spent a solid chunk of the session coaching him through the hardest part: remembering what it’s like to not know. The tension is real. Lou’s been leading a weekly AI mastermind for over a year, surrounded by people pushing the frontier of skills, eigenthinking, and ambient intelligence. Resetting to “what is Claude?” territory requires a deliberate cognitive gear shift.

Dirk cut to the core early: “It doesn’t matter what you say. It’s how you say it.” His point wasn’t about delivery polish — it was about the relationship between expertise and connection. People don’t gather around Lou because he’s winning an AI knowledge championship. They gather because of how he explains things. The content is almost secondary to the trust and curiosity his style generates.

Donald framed the audience’s real question with surgical precision: “How to keep up with the rapid development of AI.” He put “keep up” in quotes deliberately — because you can’t, really, but you can feel like you’re not drowning. That reframe matters. The audience doesn’t need to learn everything. They need a framework for deciding what to ignore.

Kasimir brought in the Michael Simmons case study as proof of concept. Simmons didn’t start seriously engaging with AI until late 2025 — remarkably late for someone who became a prominent voice in the space. The point wasn’t how intensely he worked (20 hours a week), but how late he arrived and still became relevant. If Michael Simmons was still a newcomer last year, how many people in Amy’s group are even earlier on the curve?

Bally delivered the reality check from the field. She ran a skills session for her own group recently and assumed attendees would at least be on Claude. They weren’t. “We’re not still there,” they told her. The lesson: even among people who’ve been in an AI-focused cohort for months, platform adoption is uneven and assumptions about baseline knowledge are almost always too generous.

Jamie W anchored the practical advice: “Pick one thing. It’s just 20 minutes. 10 on what you want to talk about. 10 minutes for questions.” And then the key move — if the audience already knows the first thing, offer to level up on the spot. Read the room in real time rather than pre-deciding the altitude.

If you teach, present, or consult on AI topics, Bally’s experience is your canary. The gap between what we consider basic and what our audiences have actually adopted is wider than we think. Before your next presentation, ask yourself: “If I assumed my audience is two full eras behind where I think they are, what would I change?” That’s probably closer to reality.

Skills: The Gateway Drug That Actually Sticks

The group converged on a consensus that surprised no one but validated something important: for the vast majority of knowledge entrepreneurs, skills — not agents, not RAG, not coding — represent the right next step. It’s the Goldilocks zone between “type a prompt and hope” and “architect an autonomous multi-agent system.”

Lou walked through the pitch he’s considering for Amy’s group, and it’s elegant in its simplicity: “All you have to do is talk to the AI for a while until it figures out what you want to do, and then tell it to create the skill for you. From that point on, you never have to perform that process again.” No code. No API keys. No RAG pipeline. A text file that lives in a folder.

The framing matters as much as the content. Lou deliberately plans to avoid the word “agents” with this audience — not because agents aren’t real, but because “agents implies a certain amount of autonomy” that can intimidate. Skills, by contrast, is a word that carries positive associations without the sci-fi overtones. It’s a vocabulary decision with real strategic weight.

Don identified the prerequisite that most people miss: you need to think in systems before skills make sense. His observation that “most people don’t know or use SOPs” hits a nerve. If someone has never articulated their own process — the steps they follow when they onboard a client, write a proposal, or prepare for a sales call — then “turn your process into a skill” is a meaningless instruction. The actual first step is helping people see that they have a process, even if it’s never been written down.

The group sketched out a tiered presentation strategy: start with skills as the entry point, gauge the room, and if they’re already there, transition up to Claude Code and micro-apps. The key insight is that skills are both the destination for beginners and the on-ramp for advanced users. They scale in both directions.

Cloning Your Judgment: The Ferrari Moment

Lou described what he considers the highest-leverage capability he’s discovered recently — and it’s not a tool or a technique. It’s a relationship with the AI. The process: have a natural conversation with Claude where you’re just doing your work — not performing, not demonstrating, just operating on instinct. Then ask Opus 4.6 to go back and analyze why you made the moves you made. Not what you said — why you said it.

“If I say to it, look at what I said, but more importantly, imagine why I said it — it’s pretty darn good at figuring that out.” This is the NLP parallel Lou drew: watching the expert do their thing, then surfacing the micro-decisions they’re not even conscious of. Why did you grip the pistol like that? Why did you stop breathing right there? What were you thinking in that exact moment?

The goal is to separate the doing from the analysis. When Lou is in a conversation, he’s not thinking “I’m applying framework X” or “this is my eigenthinking process.” He’s just doing the thing he’s done thousands of times. The insight comes from the post-hoc analysis — Claude watching the tape and pointing out patterns the player didn’t notice during the game.

This is what Lou called the “Ferrari moment” — and he’s aware it might be too advanced for Amy’s audience. The metaphor is apt: you don’t show someone who just got their learner’s permit how to handle a car at 200 mph. But for this group, the idea that you can systematically extract your unconscious expertise and encode it into a system that applies that judgment autonomously — that’s the frontier. It’s where skills stop being task-completion tools and start becoming judgment-transfer mechanisms.

The practical manifestation: Lou’s AIMM Writing Team skill. It started as manual article writing — research, outline, draft, iterate, fight with Claude for 10 minutes until the tone was right. Then he asked Claude to analyze the process itself, identify the steps, and codify each one as a separate skill. The writing team didn’t emerge from a design session. It emerged from doing the work, then looking back at what the work actually consisted of.

The moat has moved again — and most people haven’t noticed. Every era in Lou’s framework had a different competitive moat. But the moat in the emerging era isn’t your prompts, your context, or even your skills — it’s your judgment encoded as systems. The people who figure out how to extract the reasoning behind their expertise and transfer it into AI workflows will have something that survives every model upgrade, every platform shift, and every new competitor.

Community Corner

Dirk’s pitch deck went from brainstorm to investor meeting in 48 hours. He was working on a startup concept with Claude, built a pitch deck, sent it to a CEO friend for feedback — and the friend put it in front of an investor the next morning. The investor was interested. The team wasn’t assembled yet (minor detail when you’re an executive search professional), but the speed from idea to institutional interest is the kind of story that makes the abstract concrete.

Bally’s field report grounded the group in reality. Her experience running a skills workshop where attendees hadn’t even adopted Claude yet is the kind of data point that’s easy to dismiss from inside the bubble but impossible to ignore when you hear it firsthand. It reshaped the entire conversation about Lou’s presentation strategy.

Donald’s “keep up” reframe deserves its own spotlight. Putting “keep up” in quotes was a small move with big implications — acknowledging that nobody actually keeps up, but you can build a framework for feeling oriented rather than overwhelmed.

Try This Before Next Session

Map one thing you do on autopilot into a skill — using Lou’s extraction method.

Open Claude and have a conversation about a task you perform regularly. Don’t try to be systematic about it. Just talk through how you do it, as if you’re explaining it to a colleague over coffee.
After 10-15 minutes of conversation, paste this: “Now go back through everything I said. Don’t focus on what I told you to do — focus on why I made the choices I made. What patterns do you see in my decision-making? What am I doing unconsciously that I haven’t articulated?”
Read what comes back. You’ll likely find 2-3 judgment calls you make automatically that you’ve never written down.
Pick the one that surprises you most and ask Claude to write it as an instruction in a skill file.