Freya Madison

The problem at MindPal was pretty simple: we have hundreds of AI templates to share. We know videos of these templates work - some have gotten us tens of thousands of views. But actually making them was a total nightmare.
We tried everything. At one point, we even hired a freelancer, but the feedback loop was exhausting. It actually took longer to give feedback and wait for revisions than it did to just make the video ourselves. It was slow, expensive, and impossible to scale.
When we did it ourselves, it was a massive grind:
Record the screen of the behind-the-scene agent builder
Record a demo of the agent working
Write a script that didn't sound like a robot
Record a voiceover or an avatar
Spend hours editing everything together
If my co-founder or I were tired or busy, the videos just didn't happen. I assumed this was just the "manual tax" you had to pay for quality.
Last weekend, I got fed up and asked Claude if I could just automate the whole damn thing.
Turns out, I can.
So I spent the weekend cooking something - an internal AI SOP to turn any workflow URL (yes, from just a single URL) into a publish-ready use case video that passes all quality standards in ONE GO.
Here is the new setup:
Playwright: Records the screen and even moves the mouse like a human
@Claude by Anthropic: Writes the narrative based on our actual product info
@HeyGen: Creates the avatar and voiceover
@Remotion: Programs the entire edit - syncing everything into a final file
@Zernio + @Railway: Automatically publishes the video and saves the assets.
Now, I just give the system a URL and a finished video comes out. I don't even have to click "upload."
I just wrote a post sharing the full behind-the-scenes build, the architecture, and the logic behind of this AI video agent. Check it out here if you think this could be helpful for your company: https://mindpal.space/article/ai...

P/s: This is what I wake up to every day now

Over the past few months, we ve been talking to a lot of you using Velo.
Real conversations, and people trying it out, sending clips, pointing things out.
And almost everyone said some version of the same thing: It sounds like me but something feels missing.
At first, we thought it was about accuracy. Maybe the voice wasn t close enough. But the more we listened, the clearer it became - that wasn t the issue.
The issue was how it felt. The tone stays a bit too samey. The emphasis doesn t always land where you expect it to. And the little natural shifts that make your voice yours just aren t fully there yet. It sounds right, but it doesn t feel alive.
So we went back and started reworking how we think about voice cloning at Velo. Not just matching how you sound, but capturing how you express. The way your voice changes when you re explaining something, when you re just talking casually, or when you actually care about what you re saying.
That s what we re building now. The next version of Velo is focused on higher fidelity voice cloning. More nuance. Better pacing. More natural expression.
Something that doesn t feel like a generated voice reading your script, but closer to you actually speaking.
We re still building it, but it s coming together fast. We re planning to ship this soon.
If you ve used Velo before, we d love to know - what do you think about Velo's voice cloning or other workflows? What would make it feel right?
We re listening.

Road to 1,000,000 #Votap users Day 65 | Current: 1348