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.

One thing became obvious while we were building over the last few months.
Knowledge is only useful if people can actually understand it.
That s why we taught every Velo to speak 37 languages.
The goal wasn t just translation.
It was making the exact same message accessible to teams, customers, and partners anywhere.
Looking forward to showing what we ve been working on.

Every company already has the knowledge.
It s spread across documents, help centers, PDFs, slack messages and thousands of everyday conversations.
We ve been building around that idea for a while now.
Almost time to show you where it led us.

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.

I thought we were redesigning a website.
Looking back, we were really redesigning how we explain ourselves.
We started trying to answer one question:
If someone couldn t read a single word, would they still understand what Velo is?
That changed everything.
We realized our old brand explained what Velo does, it didn t explain how we think.
We ve always believed companies already have everything they need to explain themselves.
Product docs, meeting recordings, support tickets, internal knowledge.
On their own, they re just fragments but together, they become clarity.
Somewhere along the way, we realised our logo should tell that story too.
We d been trying to describe the company for weeks.
But physics had already done it.
A vector isn t just speed, it s speed with direction.
That s the company we re trying to build.
And once we found that idea, everything else fell into place.
The pixels, grids, layers, straight lines.
They were never just design decisions.
They were expressions of the same belief.
Because the best brands don t just show you what a company makes.
They show you how a company thinks.
Check out our new website here www.usevelo.ai

The rebrand is finished.
Now the fun begins.

The meeting paradox

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.

A few weeks after launching @Velo , we noticed something interesting.
People weren't using it alone.
They'd clone a voice, generate a few videos, then immediately ask:
"Can my co-founder use this too?"
"Can my editor access these assets?"
"Can the whole team share credits?"
At first, we thought they were edge cases.
They weren't.
The more people used Velo, the more obvious it became that content creation wasn't an individual workflow anymore.
The AI could move at incredible speed.
The bottleneck was collaboration.
Assets lived in different accounts.
Brand kits got recreated.
Teams shared logins.
The same voice clone got uploaded again and again.
The technology was solving creation.
It wasn't solving coordination.
So for the last month, that's what we've been focused on.
Today we're rolling out Velo for Teams

• Shared workspaces for brand kits, resources, and pooled credits

• Clone your voice and face once, then make them available to the whole team

• Shared libraries to organise videos and assets in one place

• Admin controls and member roles without the usual account-sharing headaches

One person sets it up.

The whole team can start creating minutes later.
We're doing a bigger launch push next week, but the Product Hunt community has supported us since day one, so I wanted to share it here first.
Curious - if you had a shared AI video workspace for your team, what's the first thing you'd use it for?
Watch our demo