We watched 14 videos from the three biggest AI educators: Nate Herk, Jack Roberts and Brock Mesarich. Frame by frame, transcript by transcript, including all 8 videos inside Nate's 7 Day Challenge.
This is what makes their teaching stick for non-technical people, how they get information to be retained, and what our Foundations Course does with every lesson learnt.
Kauthar · 15 July 2026 · click through ›
Every single Nate video cold-opens on the thing already working: four agents running his real day, a reminder firing on its own. Only then does he explain a single term.
The payoff earns the attention. The explanation spends it. People give a new idea about ninety seconds of faith, and he uses those seconds to show, not tell.
Ours: the course now opens with the Tuesday film. Watch a working day first, then every lesson explains what you just saw.
Nothing stays abstract. Every concept gets exactly one everyday comparison, usually drawn on a hand-sketched slide, and it never changes:
And they anchor to things people already own: "a skill is just what you put in a custom GPT, in a file." New idea, familiar shelf.
Brock has a four-step reflex he runs on every technical word, and he never leaves one hanging:
The reassurance comes before the definition. That pre-empts the intimidation that makes non-technical people switch off.
When a demo breaks, Nate leaves it in the video and narrates the recovery in plain English. A dead API, a horrible first draft, duplicate rows: he shows the fix happening.
Watching something break and recover builds more trust than a flawless run ever could. It also quietly teaches the one skill owners actually need: say what is wrong, let it go again.
The best videos have a dedicated honest segment: what it costs, what it cannot do, when it forgets, what happens if your laptop sleeps.
Anti-hype is the credibility engine. The educator who names the limitation first is the one people believe about the capability.
Ours already does this: "Week one, it saves you minutes. Honest." is in the course on purpose.
Decision rules collapse to a single question. Two similar features? Nate does not compare specs:
And demos end with the cost, in numbers. "That whole thing used 6% of my free credits." It answers the fear nobody says out loud: what is this costing me?
Nate's challenge does not end with congratulations. It ends with an assignment engineered to build the habit:
Adoption is engineered, not hoped for. Every lesson in our course now ends with one small action for the same reason, and Part II ends with the unattended week.
Nate Herk is the calm peer. "I do not have a technical background" is his credential. Thirty minutes of ideas before a single install step. Why before how, always. The closest to our register.
Jack Roberts is the showman. Named ladders ("the 7 levels"), a hand-drawn card per level, and value framed in pounds saved per day. Brilliant structure, but hype pacing and paywall cliffhangers we will not copy.
Brock Mesarich is the translator. Nobody defuses jargon better. "Not a response, a deliverable." "Most people don't need a developer, they need an employee." That last line is practically our pitch.
Teach beginners with the safety prompts switched off. Skip past key handling. Skip plan mode to look fast, then moralise after the mess. Hand-wave "your laptop must stay awake". Salt the teaching with sales plugs.
Approvals stay on while learning. Keys handled properly as a named step. The plan and the yes-gate shown as the default, then one contained "here is what a snag looks like". Always-on hosting so nothing depends on a laptop lid. Teaching stays clean.
These are not style choices. For clients running real businesses on this, they are the product.