Cut plan + YouTube package + live walkthrough · your card-by-card review
What this is: your 13-min raw demo recording, cut into one tight promo-style video for YouTube. Built on the locked promo arc (cold open → pain → demo → payoff). Below: the cut plan with the exact words to cut to, then titles/description/thumbnail, then your keys for walking it live tomorrow. Approve each card or tell me what to change.
⚠ CONFIDENTIAL GATE — clear this before it posts
You said that deep-dive page has your personal part / "part two" / your story on it. Before this goes to YouTube: (1) confirm nothing personal or confidential is visible on the live page or anywhere on screen in the recording, and (2) the moment where the AI stops and asks you before publishing + flags confidential content stays IN — it's a trust feature, not filler. I can't see your screen recording. You verify #1.
The cut · in run order (reveal lifts to the front)
COLD OPEN · lift to frontfrom ~11:30–12:08
0. The goosebumps reveal (3–5 sec teaser)
In"this is my live HTML file on my live site right here..." Out"...can you tell the difference? They are identical."
Do: open cold on your reaction + a half-second of the side-by-side. Don't show the full compare yet. Then a branded title card. Tease the feeling, make them wait for the proof.
Approve
Change
Cut
KEEPtrim the self-open00:00–01:36
1. The pain (body opens here)
Cut the weak open"every week I create a ton of HTML files locally that I just love to look at..." (00:00–00:13) — leads with you, not them. In"it's currently live on Cloudflare because I've been using Cloudflare to host my HTML files to share them publicly..." Out"...it lives on their server, not on my server, so when AI is looking to cite me, it's not really part of my website. And I'm going to change that."
Do: lead with the viewer's problem. Keep the WordPress-hoops line (01:10) — that's your "I tried the hard way" trust beat. You hedged it correctly ("not impossible, but a lot of work"). Accurate, keep as-is.
Approve
Change
Cut
KEEP01:52–02:38
2. "Watch this" — the setup
In"what I'm about to show you is how I'm going to host this HTML file... on my own website, PageMotor, by just talking to AI." Keep the beat where it reads PageMotor's own docs first — that's your framework-vibe-coding proof. Name it, don't preach it.
Approve
Change
Cut
KEEP — the trust beat03:20–03:59
3. It asks before it publishes
In"where should this live on PageMotor's site? It's going to confirm with me before it puts it anywhere..." Out"...it always has the rule to ask me first before it publishes anything."
Do: land this clearly. Most tools don't ask. This is the "it won't go rogue on your live site" feature. Strong selling point.
Approve
Change
Cut
CUT / COMPRESS04:14–06:50
4. The back-and-forth log-reading
Cut: the repeated "let it cook, come back in a sec," the "publish it now / what link / show me the link" loop, and you reading the AI's log lines aloud. Keep just one line:"I can design the HTML the way I want and publish it without messing with the page" (05:21) — that's a real value line. And keep ~3 sec of the theme-matching beat (06:13). Drop the spoken jargon (schema, canonical, open graph); keep it on screen, not in your mouth.
Approve
Change
Cut
SPEED-RAMP06:50–09:53 → ~12 sec
5. The 4-minute cook
VO over the ramp"it's your data, your domain, your GEO. It should live where AI can cite you, not on someone else's host." (08:09) + "I just talk to it. I don't even type anymore." (08:30)
Do: speed it to ~12 sec with a "4 minutes, sped up" stamp on screen so it's honest. Lay your thesis line over the ramp. The wait being real is the proof — don't fake it, don't make them live it. Trim the Tariq-on-X riff (08:39–09:16) unless you want ~5 sec of it.
Approve
Change
Cut
KEEP — the payofftrim throat-clearing10:01–12:22
6. The full reveal
Cut"and I hope I can do this correctly..." (10:52) — throat-clearing before the money shot. In"this is my original, and this is the real thing. Can you tell the difference? They are identical." Out"...they even light up the same way. I am blown away. Just blown away."
Do: pause. Let the side-by-side sit in silence before you talk. This is the second, full payoff (the cold open was the tease).
Approve
Change
Cut
KEEP — close12:22–13:09
7. The land
In"it lives here on my site now. I never have to re-upload it..." Out"...all of our deep dives will live on my site now. Join us live tomorrow."
Do: end on the viewer payoff (it's yours, it's found by AI, no re-upload) plus the show CTA. Keep "I can edit it directly on my site by talking." Don't trail off.
Approve
Change
Cut
YouTube package
3 title options (you pick — all lead with viewer value)
A · Put Any HTML Page On Your Own Website By Just Talking To AI (No Code)
B · Your Best Work Is Trapped On Your Laptop. Here's How To Get It On Your Site.
C · How I Publish Interactive Pages To My Own Domain Without A Developer
Note: B leads with the viewer's pain (strongest hook). A is clearest for search/GEO. C still says "I" — weakest per your #1 rule. Your call.
Pick one
Rewrite
Description (promo format)
Opener: the thing you build shouldn't be stuck on your laptop or someone else's server.
One line: watch a non-developer publish a live, interactive page to her own domain by talking to AI.
📌 WHAT YOU'LL LEARN: why HTML beats a doc for sharing · why "your domain = your GEO" · how the AI reads your site's rules before it publishes · the no-code publish flow.
⏱ TIMESTAMPS (fill after export) · 📚 RESOURCES (PageMotor, the show) · 🎙 ABOUT PRACTICAL AI · #PracticalAI + hashtags.
I'll write the full description once you lock the title + cut.
Approve direction
Change
Thumbnail brief
Two pages side by side, visibly identical (the charts).
Your face, genuinely amazed (the goosebumps look).
2–4 words, high contrast: "IDENTICAL. NO CODE." or "I TALKED IT LIVE".
Dark, readable at phone size.
Approve
Change
Walking it live tomorrow
Snapshot-only — do NOT publish live on air
Don't hit publish on the show. A 4-minute cook is dead air on a live stream, and it can fail in front of everyone. That's exactly what your snapshot-only rule is for.
Instead: play this cut video, OR pull up the page already live on your site and tell the story over it.
Your live beats: the pain (trapped on someone else's server) → "so I talked it onto my own site" → the side-by-side already done → why it matters (your data, your GEO, AI cites you) → "all our deep dives live here now."
The one live line that lands: "I never touched code, I never opened an admin page. I just talked to it."
▸ Full demo transcript (your recording, word for word)
[00:00] So every week I create a ton of HTML files locally that I just love to look at as I present information for my different companies.
[00:13] So in this particular case, this was a deep dive I did for the show last week that we didn't get to, so I'm including it in tomorrow's show, and it's currently live on Cloudflare because I've been using Cloudflare to host my HTML files to share them publicly. That was a great solution, but here's the deal: I put a lot of work into creating these beautiful HTML files.
[00:49] In this case it was a deep dive about something Greg Isenberg shared that we're going to riff on and present our takes on. It's really cool, I love it. But it lives on Cloudflare. And if I had a WordPress site, which I don't, but if I did, putting an HTML file on it is not impossible, but it's also a lot of work, a lot of hoops.
[01:22] More and more people are using HTML files to share and present their information. I'm all for it. Cloudflare is a great solution, but it lives on their server, not on my server. So when AI is looking to cite me, it's not really part of my website.
[01:36] And I'm going to change that. What I'm about to show you is how I'm going to host this HTML file the way it is, on my own website, PageMotor, by just talking to AI.
[01:52] I'm going to tell my AI which HTML file I want to place. I'll say: I want to put this HTML file on my PageMotor site, ask me any questions to clarify before you publish anything.
[02:18] So I'm just talking to my Claude about this. It'll probably ask me questions, I hope so, and if not it goes and reads through PageMotor's API documentation. This is what vibe coding with framework is, because there's a lot of framework and documentation in there.
[02:38] Now it's asking me questions, grounded in the real content. It's doing its work, and I'm going to let it cook.
[03:00] Okay, I moved my video to the side so I can read what it says. All I'm doing is talking to AI. That page has more on it than just the thesis, it includes the full brainstorm, it has my story.
[03:20] Now, where should this live on PageMotor's site? It's going to confirm with me before it puts it anywhere on the live site. Standalone deep-dive page on an evergreen URL, or part of the episode 45 page. Yes, part of episode 45.
[03:52] You see, it asks me if it has anything confidential. It always has the rule to ask me first before it publishes anything.
[03:59] Publish as is, keep current title.
[04:14] Log, decision captured. To be straight with you, I have not published anything. The deep dive is cued to go live with the episode 45 page. I do want a standalone version live this week too.
[04:37] I'm going to say: publish it now under episode 45. What link would you use? Show me the link before you publish. I just want to make sure it's nesting it in the correct place, because this is very new, only a couple days, so I'm still training the rules.
[05:21] Another thing I love about HTML: I can design it the way I want and tweak it, and once it's ready I publish it as the HTML file on my site without messing with the page.
[05:36] For your locked page model, the deep dive nests as its own child page under the episode. So the parent is Practical AI, episode 45, second customer.
[06:01] It's confirming the episode 45 page already exists. We created that for the funding I just worked on. Go ahead.
[06:13] We'll see if it looks the same or not. That's important. There's so much work happening behind the scenes. It's matching the theme, because I want my PageMotor HTML to be consistent with the theme.
[06:32] And from the GEO perspective it's using best practices for the AI-native site, so AIs can find the information.
[06:50] Now it's calling PageMotor's API. This is the background magic. It's cooking.
[07:10] Usually when it's cooking I'm doing something else, but I'm here with you. It has the full prepared HTML and now it's hosting it. Status live. It's calling PageMotor.
[07:24] It's been cooking two minutes. It's talking to the site and communicating. I don't have to touch anything, I don't even open the admin page.
[08:09] So for me, with HTMLs and any real data you create for your business, it's your data, your domain, it should be your GEO, and it should live where AI can cite you, not on someone else's host. You just saw me, I was just talking to AI, telling it what I want. I don't even type anymore, I just speak.
[08:39] While we wait for the reveal, I've been playing more and more with HTMLs. Why read MD files if you can do HTML? I like that idea Tariq posted on X a couple weeks ago. Once I started playing with HTMLs I wanted them everywhere.
[09:05] Behind-the-scenes dash reports with my team. Public use where I don't have to protect them. So many uses. And it's another way to be creative with your business and your information.
[09:26] It's done. It cooked for four minutes. Live and confirmed, status live. PageMotor folded in its own head metadata, canonical URL, open graph tags. Your part two is intact. Footer and top-bar links point back to the episode 45 hub.
[10:01] It's live and linked. Let's go look at it. Just to remind you, this is the HTML file publicly shared on Cloudflare that I did last week, and this is PageMotor.
[10:33] It gives me goosebumps. Let's compare side by side. I hope I can do this correctly. This is the HTML site I published with Cloudflare. This is my original.
[11:04] And this is the real thing. Can you tell the difference? They are identical.
[11:30] So this is my HTML file, the original, and this is my live HTML file on my live site right here. You saw how long it took. They are identical. They even light up the same way.
[11:54] I'm lucky, this is amazing. It's identical. It matched everything. I am blown away. Just blown away.
[12:08] And it lives here on my site now. I never have to re-upload it. And I can edit this HTML file directly on my site now, just by talking to AI.
[12:34] PageMotor is winning. I'm winning big time with PageMotor. This is my information and it belongs to me, here, not hosted on anyone else's site.
[12:47] All of our deep dives for the show now are going to live on my site. We're discussing it tomorrow, I hope you join us live. Thanks for listening, we'll see you later.