What I'm for
Knowing more was never your problem.
You've read the books and taken the courses. You could teach the theory to someone at dinner. And you still have thousands of notes and almost nothing published.
That gap isn't a discipline failure. Everyone teaching this stops at the idea, right where the wiring starts, and leaves you to figure out the rest alone. I do the other half. I build the thing in front of you and say why while I'm doing it.
If this is you
You've stopped being willing to settle for some things.
I'm not writing for beginners. I'm writing for people who've done the reading and got tired of the gap between what they know and what they've made.
Another tutorial that stops at the concept
You can explain the theory better than most people teaching it. The video always ends right where the real work starts.
A folder system dressed up as progress
You have reorganized the same notes four times. Reorganizing is not shipping, and some part of you has always known that.
Renting your thinking to whatever app is trending
You have migrated before. You are not doing it again because a company changed its pricing page.
Being the smartest person nobody can find
People with half your depth publish twice a week and get the calls that should be yours.
What I believe
Six things I'd argue for in public.
01
Your notes are not your knowledge.
A folder of clippings is a pile of other people's thinking. Knowledge is what survives you writing it in your own words and using it on something real. Most systems optimize the pile.
02
Storage was never the bottleneck.
You do not have a capture problem. You have 10,000 notes and nothing published. The missing half is the part that turns what you collected into something someone else can read.
03
Own the ground you build on.
Plain files on your own disk. If a company dies, changes its terms or triples its price, your work does not move. This is the whole reason I use Markdown for everything I own.
04
AI is a bad oracle and a great apprentice.
Asking a model what to think produces the same beige answer everyone else gets. Pointing it at your own material and giving it a job produces work only you could have made.
05
The last click stays yours.
Every agent I run drafts and stops. Nothing sends, publishes or submits on my behalf. The last mile is the habit being trained, so I keep it.
06
A system you cannot rebuild is a system you do not own.
If it only works because one clever setup is still standing, it is a trick. I write mine down so a stranger could restore it, and so could you.
The part I do that nobody else is doing
I sit in the gap between the teachers and the engineers.
There are excellent teachers who've never wired up the thing they describe. There are excellent engineers who can build it and cannot explain a single step of it to a person who doesn't write code. Both groups are full of talented people, and neither one can hand you a working system.
I trained as a teacher inside the program that shaped how people think about this work, and I spent the last stretch building the software instead of talking about it. So I can show you the wiring and tell you why it's wired that way, in language you'd use with a colleague.
That translation is the job. Everything below is downstream of it.
Not a theory
I run all of this before I teach any of it.
Everything here is running on my own machine today. The numbers are measured, and this website is one of the outputs.
82.3%
less noise reaching the model
I built a tool that filters command output before an AI ever sees it. Measured across 12,414 real commands: 37 million tokens in, 30.5 million saved. Then I audited where it failed and rerouted those cases instead of assuming it worked.
60,032
searchable pieces of my own work
A search engine over everything I have written, running on my own machine with no cloud. 1,499 files, keyword and meaning search fused together. It reindexes itself when a work session ends.
11
assistants that hand off to each other
They share one board, so what my inbox assistant learns on Monday reaches my planning assistant on Friday. All eleven are plain text files. Every one drafts and stops.
3
pieces of software I ship and use daily
An infinite canvas, a map of everything in my notes, and a bullet journal — real Obsidian plugins at versions 1.42, 0.52 and 0.23, all storing plain Markdown. Not demos.
How we'd work together
Four doors. Each one solves a different problem.
Start at whichever line describes your week. You can move up whenever you want, and nothing here needs the one below it.
The Creator Vault
Free
- The problem
- Ideas land in six places and none of them is a system.
- What it is
- A working setup, already built. You open it and start, instead of watching someone build theirs.
- Your first win
- Every idea has one home by tonight.
The Bridge Kit
$297
- The problem
- The setup is done, the notes are filed, and still nothing ships.
- What it is
- The whole operation packaged — the rules, three working assistants, and the pipeline that makes publishing the default. Self-install over a weekend.
- Your first win
- One finished piece published, from your own material.
One-time. Checkout opens shortly.
See what's inside →The AI Builders Workshop
$47
- The problem
- You have read all of it and never once watched the thing get built.
- What it is
- Live hands-on sessions each month. I build in front of you and say why out loud, then you build yours while I am in the room. No code.
- Your first win
- One system working, in your first session.
Per month, or $470 a year. Founding price for the first 50 builders — the standing price is $97/mo. You keep the price you join at. Cancel anytime.
Join the Workshop →The Bridge Install
By application
- The problem
- You want it running and you are never going to build it yourself.
- What it is
- I build it into your business, in your own accounts, and hand it over documented. Two to three weeks.
- Your first win
- It is running, and your team can run it without me.
Two a month.
Apply for an Install →I spent years collecting instead of making, and I told myself the collecting was the work. It wasn't. The day something I'd written went out and someone replied to it, the whole thing changed, and no amount of reorganizing had ever done that.
Your expertise is real. Being invisible is the part you can fix.
— Frank
You are here
Start where you are.
The Vault is free and takes one evening. If you'd rather watch it get built first, the Workshop meets live every month.