Before you start
A short welcome video, so you arrive knowing how the steps run and what to bring.
AI, Built On Paper · how it works
You start with a sentence and finish with a first version of your app, live online. Each stage ends with something you can hold, and you follow one worked example the whole way: a recipe app that cooks from what's already in the house.
The plan at a glance
Paper Day covers steps 1 to 5. The Build cohort picks up at step 6. Self-paced covers all ten, at your own speed.
Your idea in one sentence, what done looks like, and everything it could do, sorted on one page.
Paper Day · steps 1 and 2Self-paced
You leave with: the whole app on one page
A short welcome video, so you arrive knowing how the steps run and what to bring.
Write what done looks like in one line: someone can do one specific thing, without asking you how. Everything after this gets easier.
In the recipe example: done when someone can pick tonight's dinner from what's in the house in under two minutes.
Get everything your app could do out of your head and onto paper. Then sort it, star what matters, and circle the one part you build first.
In the recipe example: pantry, recipes, a shopping list and the household who shares them, sorted on one page.
Every part of your app on paper, one sheet per part, starting where your users start.
Paper DaySelf-paced
You leave with: the product, before spending a dollar
Sketch every part of the app, one sheet per part, starting where your users start. Paper is fast, cheap and easy to throw away, which is the point.
In the recipe example: one sheet each for home, the pantry, a recipe and the shopping list.
Hand it to people who have never seen it, watch where they get lost, and fix the paper.
Paper DaySelf-paced
You leave with: a tested design, in photos
Two people who have never seen your app each try one task per part while you stay quiet and watch. The paper goes back to the start before every task.
In the recipe example: a tester tries to find something to cook with what's in the pantry.
Change what broke, after the tester leaves, then photograph the new version. Finding this on paper costs minutes, not weeks.
In the recipe example: if a tester can't find the pantry, the pantry moves.
Turn the paper into a plan an AI can follow, build it one part at a time, and set up how it takes money.
Build cohortSelf-paced
You leave with: a first version of your app, live
Make a Project in Claude or ChatGPT and write four short documents in it: vision, rules, backlog and parking lot. This is what the AI builds from.
In the recipe example: the four documents for the recipe app, in one Project.
One page on what your app runs on, written in the same Project, so the AI and you agree on the tools before anything gets built.
Build one part per loop, and end every loop by checking it against the "done when" line from your backlog. Home and your first part go live at a web address you can share.
In the recipe example: home and the pantry, built, checked and live.
If your app will charge, set up how it takes money, with the questions to ask an accountant or attorney before you do.
No payment yet. Pick one, leave your email, and you'll get the date, the place and your seat link before anyone else.
No. The course is built for people who don't. You think on paper, test with real people, and then give an AI tool a plan clear enough to build from.
Not every part, and that's on purpose. Your whole app will be designed on paper, tested with real people and planned. Then you build a first working version with an AI tool: real software, live at a web address anyone can open on their phone, with the home screen and your first part working. You leave knowing how to build every other part the same way.
Paper Day, Dallas-Fort Worth. Date and room coming soon. The list gets first pick.