None of those tools are the point. The point is the muscle underneath them — the small set of moves that make AI a posture instead of a treadmill. Almost nobody is teaching that.
AI is the thing that closes the gap when people feel like AI is the gap.
The internet was the same shape, on a slower clock.
The hard part wasn't the browser. It was the muscle of "I don't have to drive to the library."
The people who got there first weren't better at HTML. They'd just changed how they thought about access.
That muscle took a decade. This one has eighteen months.
We don't teach prompts. We don't teach n8n. We don't make you become a developer. We teach the operator's stance — the small handful of moves that make AI a posture instead of a tool.
The whole prompt-engineering industry is selling you a workaround for messy context. Manage your data first; the prompt is the last thing that matters.
When you sit down to do something, instinctively check whether AI can close part of the gap. Not the whole task — just a piece. Background, not foreground.
Once the muscle is there, the tools are interchangeable. Pick whatever's open in front of you. The Tuesday-update treadmill stops being a treadmill.
"I came in convinced I needed to learn n8n. I left realizing I needed to clean up my notes. My output went up 4x in three weeks."
"Dani doesn't teach AI. She teaches a way of paying attention. It survives every model release."
"I was burning out keeping up. Four hours with this group and I cancelled six subscriptions the same week."
A four-hour live working session. Not a lecture, not pre-recorded. You leave with the operator's stance built in your hands — on your data, your stack, your real work.
Monthly letter. One operator move per issue. 12,400+ readers.
Subscribe free →Five-minute Looms. Real work, real moves. Email-gated. Opens this quarter.
Get early access →A small, active room. Not a Slack graveyard. Launching later this year.
Get notified →Each issue starts from something I actually did that month — a problem I solved, a workflow I broke, a way of thinking that shifted. Then I show you the move.
No "ten tools you should try." No AI-news roundup. One good idea per issue. Use it this week.
I built Switchboards because the AI education I needed didn't exist yet.
Two years into the AI shift, every program I saw was a tool class. Prompting class. Frameworks class. Every Tuesday, a new one.
The people getting the most out of AI weren't the ones memorizing tools. They'd quietly changed how they thought. They reframed the question before they wrote the prompt. They cleaned the data and let the model do the rest. They treated AI the way the rest of the office still treats Google — background, not foreground.
There was no school for that. So I built one.

Builder of things she "shouldn't" be able to build. Ships apps without ever opening the code. Runs Switchboards from a small studio in Austin and a long backlog of Looms.
Cohort 03 opens this summer. Drop your email and you'll be the first in.