Practical AI Builder Program
A sprint program for people who already use AI and want to build real things with it.
This program is for people who are done collecting tutorials and want a structure for working on real problems instead.
AI has so much to offer, and it’s very easy to get lost. New tools launch every week. Every announcement creates a little more urgency, a little more noise, a little more catching up to do. In the meantime, the actual problem you’re sitting with is still there.
This is where practical AI building becomes useful: you stop chasing what’s new and start solving what’s real.
Next sprint, Friday, August 14 at 12pm ET: Hermes Agents.
You set up Hermes on your own machine, hand it its first real job, and leave with an agent that's still working after you log off. Included with a paid subscription.
How the program works
Each sprint runs for seven days. One live session. One problem you’ll actually build through.
Each 1-hr live session follows the same structure:
15 min — Context and tools. I introduce the problem, the first principles underneath it, and the tools we’ll use.
40 min — Live build. I build it in front of you, real setup, real workflow, real decisions as they happen. You see the thinking unfold, then take it wherever makes sense for you.
5 min — Discussion and Q&A. Open discussion on what we just covered, questions that came up, and how to take it further in your own work.
Before the live session: When you join, you receive a diagnostic. Fill it out and submit it. You receive a personalized assessment within 2 days after submission. It’s how I understand where you are and what you’re working on.
During the session (1 hour): Live build. You see the thinking unfold in real time, not a polished after-the-fact demo.
After the session (7 days): You stay in the inner circle. Ask questions, share what you’re building, get feedback from me and the group while the work is still active. After seven days, you leave with something built.
Past sprints
Sprint 1: Research
Get clarity on what opportunity to pursue in the AI space, and how to research it without drowning in tabs. You leave with a 5-stage research framework applied to one real question from your work, ending with a structured output you can act on.
How to Do Research With AI Effectively
You build a research brief using 3+ AI tools.
Sprint 2: Make Money With AI
Stop collecting income strategies. Build a system that turns them into decisions. You leave with a digital mentor built from a top creator’s public content: their frameworks and decision logic loaded into NotebookLM, plus a tracking skill and scheduled task that keep it current automatically.
How to Make Money With AI: From Research to Act in One Loop
You build a pipeline that flows
Sprint 3: Build Your AI Workflow Stack
Stop stacking tools you never wire together. You install one MCP live, from zero to working, then walk out with three real workflow demos built from real data and the templates to rebuild them yourself.
3 Levels of Claude Workflow Stack That Close the Knowledge Work Loop
Sprint 4: Grow Your Substack
Hand your Substack growth to Claude. Eight workflows set up live in your own Claude, from digesting your inbox and sizing a niche to studying top creators, drafting and scheduling notes in your voice, and scoring what works, so the growth engine runs itself.
How to Grow Your Substack Growth with Claude Workflows
Paid subscribers keep the inner circle access between sprints.
Between sprints, the building never stops
On Mondays, a build that already runs in my own work.
It could be an agent that reads four inboxes and briefs me every morning, an AI that writes and schedules my posts for the week, or a night-shift routine that finishes work while I sleep.
On Wednesdays, the complete guide behind that kind of system, with the exact settings.
Free readers see every build and what it does.
Paid subscribers get the full guides, the files, and a seat at every sprint. The sprint is where the month’s best build becomes yours.
What you get
Jenny’s personal feedback on your assessment. Before the live session, you submit where you are and what you’re working on. You get a direct response, not a template.
Clarity on the tools and method. You leave the session knowing what to use, in what order, and why. No more “I watched it but I’m not sure where to start.”
7-day async window. After the live hour, you stay in the community for a week. Ask questions, share what you’re building, get feedback from me and the group while the work is still live.
Pricing
Paid Build to Launch subscribers: included.
The paid membership is the program.
Every sprint, all year, part of your subscription. Each with the assessment, the recording, and the 7-day window, plus the full builds and guides between them.
Annual subscribers also get the inner circle:
166 ready-to-use resources, 76 prompts, 65 guides, 25 workflows, plus the self-paced courses.
The annual plan costs less than two sprints would on their own.
Not a subscriber?
A single sprint is $97, everything included, no subscription required.
This is also the easy path if your company is paying: one invoice, and I have reimbursement templates you can send your employer (reply to any email and I’ll share them).
Want my eyes on your work between sprints?
For a small group, there’s a deeper track: monthly feedback on what you built, what would make it stronger, and what to build next.
It runs on application, because feedback only works in a group small enough that I read everything.
Reply to any email from me with the word BUILDER and one sentence about what you’re working on.
Common questions
What is the assessment?
When you join a sprint, you receive a short set of questions about where you are and what you’re working on. Submit your answers at least two days before the live session. I read every response and send you personal feedback. It shapes how the session lands for you specifically, not just the group.
What’s the time commitment for a sprint?
One hour live, plus however much time you want in the 7-day window. Some people spend two hours total, some spend ten. You control it.
I’m not technical. Is this for me?
No coding required. No technical background needed.
The tools we use have no-code interfaces, you write instructions, not code. The skill this program builds is knowing what to ask for and how to evaluate what you get back. That doesn’t require a technical background.
I happen to be technical, but 80% of what I’ve built had nothing to do with code. I didn’t know how to launch a Gumroad product. I didn’t know how to publish on different platforms. I didn’t know how to put together free resources people would actually want. I didn’t know how to sell, how to write consistently, or how to create images. Most of what I’ve built lives in areas where I had no idea what I was doing, just curiosity and the need to move forward.
The hesitation is the starting point. AI gets you past it. That ability compounds over the next year, five years, ten years.
Do I have to attend live?
No. Live sessions are great for real-time feedback and community, but recordings are available if you can’t make it. All materials are shared async, so you won’t miss anything.
What tools do I need?
Whatever you already use is a fine starting point. This program isn’t tied to any specific tool, we work with whatever makes sense for what you’re trying to build. Most AI tools have free tiers, so you can get started without spending anything. I’ll share what I’d reach for each sprint and why, but you adapt from there. You don’t need to buy anything before Day 1.
Can my company pay for this?
If you want to expense this sprint or your Build to Launch subscription, I have email templates you can use to request reimbursement from your employer. Reply and I’ll send them over. I’m also a CPD-verified trainer (verification: 789656, verify at thecpdregister.com), which may help with your reimbursement request.
**Is this program CPD-accredited?
**Not yet. I’m a CPD-verified trainer, but the program itself is not currently CPD-accredited. If enough participants need that, I’ll pursue it.
Will I get a certificate?
Yes. You’ll get a Certificate of Completion from Build to Launch when you finish the program and complete your capstone. It could be an app, automation, workflow, digital product, or whatever you shipped.
Questions not answered here? Reply to any post or message me directly.
Why now
The builders who develop this reflex early will have a significant advantage over the next few years. They are those who stop chasing tools and start with practical AI building. Not because they know more, but because they can move faster, with less friction, on problems that actually matter to them.
You already use AI. This is the year you make changes with it.