I used the production line by @Ry Mac to make my second YouTube video, and I want to share how it went. I started the gameplan Saturday morning. By the end of the night the video was on YouTube, the blog post was live on my site, and the lesson was in my Skool classroom. That included the recording and the edit. The line has 9 stages, and it will not let you skip one. Gameplan, script, spec, reader, storyboard, a 90 second test render, the full render, the package, and the blog. I wanted to skip the spec at one point. It stopped me, and it was right, because the spec is where the problems showed up before I recorded anything. A few things that stood out for me: The reader is a slide page I record my voice from. One line at a time, with a hold marker when I need to pause. I recorded the whole script in one take and only had to fix one line. Everything is timed to my real voice. It listened to the recording and lined every slide up to the words I actually said. When I said a line a little differently than the script, it changed the caption to match me. It checks its own work. Before it showed me the final video, it went through every cut and found 3 captions that came up a beat late, and a banner in one of my screen recordings that should not have been public. It fixed them before I saw them. The renders run in the cloud. My laptop stayed free, and all of the rendering for the day cost less than a dollar. It is built as a folder system, the same ICM idea we talk about here. Every stage is a file I can open, so I always knew where it was at. Thank you @Ry Mac . The production-line is amazing!!!