Ajay Kumar

Watching PH community use our product in real time is the most terrifying and rewarding thing

by

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.

Someone in a completely different timezone signed up, recorded their screen, and shared a video message. With a product we were still debugging at 2 a.m. last night. I can't describe that feeling.

But here's the part nobody prepares you for: the feedback hits fast, and it hits honest.

Within the first hour, someone told us the flow felt confusing. We evaluated it and shipped a fix in 20 minutes. Someone else said they expected a feature to work differently, that's going into next week's sprint (flagged as P4), and so much more.

Three months of building, and we learned more in the first three hours of being public than we did in the entire month before launch.

I think that's the real point of launching publicly. The moment someone who owes you nothing takes the time to say "hey, this part doesn't make sense", and suddenly your roadmap rewrites itself.

We built Velo to help people turn raw recordings into video messages worth watching. Seeing the PH community support us, actually use it, and PH featuring us in their newsletter, it's overwhelming in the best way.

If you've launched before, what was the one piece of feedback on day one that completely changed your direction? I'm super curious to hear this.

And if you want to try Velo and add to our feedback pile, we're genuinely all ears → https://www.producthunt.com/products/velo-4

253 views

Add a comment

Replies

Best
Oliver Nathan

Launch day really does compress months of assumptions into a few hours. What surprised you most about how people actually used Velo?

Ajay Kumar

@oliver_nathan2 Can't really nail down to one answer as we got different personas using the tool for their own use case and each had their own way to navigate, create a video or edit it. All different flows mostly.

Reid Anderson

That "we learned more in three hours than in a month" line is painfully real. Do you think teams should launch earlier just for the feedback loop?

Ajay Kumar

@reid_anderson3 Not to a very wide audience, not at PH scale. But start a beta or early access, let in people who actually fit your use case. Keep it small, around 50-200 members, and get real feedback before going big.

Joseph Walker

Nailed the feeling, congrats on #1 ! Watching live sign ups is both stressful and validating . I'm prepping my PH launch, and this was motivating to read.

Ajay Kumar

@joseph_walker2 Thanks for the support. You know what, it is okay to be nervous because launches are so unpredictable here, one second things are going your way, and another second it completely changes.

Just ensure to hit a big curve of upvotes in the first 4 hours push. Plan your launch activities accordingly. All the best.

Hailey Brianna

The speed of shipping a fix in 20 min is probably the biggest startup advantage. What kind of issue showed up first, UX confusion or missing expectations?

Ajay Kumar

@hailey_brianna1 Definitely the UX one, if the user just feels friction, they just don't move ahead to test the tool. Our focus was to give them the best experience of using Velo and an awesome output.

Ian Maxwell

It's interesting how public launches test not just the product, but the team's ability to listen under pressure. What feedback was hardest to hear?

Ajay Kumar

@ian_maxwell1 Hardest to hear, nothing really. It is about the mindset, you know you are going to launch in front of the professionals all around the world, something bound to break. Hence, we were ready to take in any feedback users sent to us. Feedback is a blessing for any product if they want to improve. Key is to just not take anything personal.

Leah Josephine

Watching real users interact with something you built last night is such a weird founder moment. Did any behavior completely break your original assumptions?

Ajay Kumar

@leah_josephine None as of now, some frictions in the UX, but as we keep onboarding more and more users, the real deal will start from there.

Chioma Amadi

This is such a real take on launching, @ajaykumar1018 especially the part about learning more in a few hours than in weeks of building. That moment when users interact with your product in ways you didn’t expect is always eye-opening.

What stood out to me is how quickly you turned feedback into action, that speed is a huge advantage, especially this early. Often it’s not even the big features, but those small moments of confusion that shape whether users stick or drop off.

Really cool to see you embracing that feedback loop so actively, that’s usually what separates products that improve fast from those that don’t.

Ajay Kumar

@chi_78 We're trying our best to cater to what our users want the tool to be; they are the ones ultimately using the tool end-to-end.

Chioma Amadi

@ajaykumar1018 That really shows especially how quickly you’re translating feedback into improvements.

Early-stage moments like this are always interesting because it’s not just about collecting feedback, but shaping it into a clear and intentional experience.

Looks like you’re moving fast in the right direction.

Ajay Kumar

@chi_78 We're trying our best. Thanks for your kind words.

Please do give Velo a try, and let us know what you think.

Chioma Amadi

@ajaykumar1018 Absolutely, I’ll give Velo a try! Really excited to interact with it. Its already looking like a polished, thoughtful experience

Dylan

I found the same thing the first time I shared with family and friends.

Real feedback beats team QA 10 times out of 10. Watching session replays on PostHog made me completely change our onboarding flow.

Ajay Kumar

@dylan_fourleaf This has been our entire day, literally. Our eyes are stuck on PostHog too!

Naomi Florence

This is a good reminder that "confusing" feedback is often more valuable than praise. What part of the flow got misunderstood first?

Ajay Kumar

@naomi_florence1 Interesting one, well, some users, after creating the "Velo Twin", couldn't figure out that they had to first approve the twin to be used, and then they went ahead to complete the further step.

An in-app notification or an email was needed; we fixed it with an email and a copy for now. The next changes are coming soon.

Have you tried Velo yet? Any complications you hit or anything you loved?

Lee Jean

This post perfectly captures the feeling! Congrats on the #1 spot. The live sign-up watching is half terrifying, half the best validation you can get. Fellow founder here just getting my PH listing ready, and reading threads like this is genuinely motivating. The video message use case is smart. Async video is massively underused for real communication. Rooting for you!

Ajay Kumar

@leefounder12 Thanks a ton, your words are motivating.

I'd also encourage you to use the Velo as well, and see if you can use it well enough to explain your product to your users. It is just the best, as I have changed my town hall meetings from boring PPTs to playing a Velo instead.

12
Next
Last