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.
The async revolution was supposed to kill meetings, but it did the opposite. Since 2020, weekly meetings have increased 153%, despite every company adopting Loom, Slack, Notion, and a dozen other async tools. The tools multiplied, the meetings stayed. Something structural is broken.
We launched Velo on Product Hunt this morning without expecting anything.
I thought we'd spend the day refreshing the upvote counter. Instead, I got hooked on reading every comment, watching sign-ups roll in, and seeing users create their first Velo in real time.
Velo
