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.
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.
Velo is soo cool .. as a founder I've been using a bunch of the products and always thought there was a gap .. y'all solved it ! Made a short explainer video, hope I got it right.
@ragsyme We allow hosting too without any watermarks, you get a URL you can share.
Report
Maker
Building Velo made one thing very clear to us — browser agents don’t fail because they’re weak, they fail because they’re blind. Most tools try to fix this with better models. We went a different route — better grounding. A simple user walkthrough (clicks, intent, flow) becomes the instruction layer for the agent. That single shift reduced unnecessary steps and made the system far more reliable. Still early, but we’re excited about where this can go. Would genuinely love feedback from the community.
@sundeepjoshi This is such an underrated observation. The grounding problem is real and it shows up in coding agents too, not just browser agents.
We ran into a version of this building Grass. Agents running in the cloud with no feedback loop back to the developer. They'd go sideways at minute 10 and just keep going. The fix wasn't a better model either. It was better visibility. Real-time tool call approval, diffs mid-session, the ability to steer before things go wrong.
Different domain, same root problem. Excited to see where you take this.
Report
Maker
@sunnyjoshi This resonates a lot. The “no feedback loop” point is exactly where agents tend to drift.
Also interesting that "better models didn’t help" — better visibility and steering did. Feels like we’re converging on the same idea: grounding helps at the start, but ongoing visibility is what keeps agents reliable.
Different domain, same root problem indeed. Excited to see where this goes.
@ajaykumar1018 If the AI generates a polished script and voiceover that is significantly shorter or longer than my original screen recording, how does the tool handle the visual timing ? Does it automatically speed up/slow down the footage, or does it intelligently use freeze frames or jump cuts to keep the visuals synced to the new audio ?
Yup we handle the entire audio video sync automatically. You should try it out
Report
recording a “quick video” and then re-recording it 5 times is way too real 😅. feels like the hardest part isn’t recording, it’s sounding like a normal human while doing it. if this actually fixes that, it’s a big deal
Congratulations team Velo! Love the focus on closing the gap between raw intent and polished output. Regarding the AI Voiceover sync, if a user decides to edit the generated script after the video is processed, how does the engine handle the re-syncing of the visual timing? Does the browser agent actually "re-record" the sequence to match the new pacing of the speech?
@gayatri_sachdeva Thanks Gayatri, this is a great question! If someone edits the script after the video is generated, we don’t re-record everything. Instead, we adjust the timing of the scenes to match the updated voiceover.
We use visual cues in the video (like clicks, hovers, and page changes) as anchors, and then tweak the pacing so everything stays in sync.
Congrats. Looks neat. Does it allows me to host the videos like Loom does or I need to export the video and host at my end?
Velo
@ragsyme We allow hosting too without any watermarks, you get a URL you can share.
Building Velo made one thing very clear to us — browser agents don’t fail because they’re weak, they fail because they’re blind.
Most tools try to fix this with better models. We went a different route — better grounding.
A simple user walkthrough (clicks, intent, flow) becomes the instruction layer for the agent. That single shift reduced unnecessary steps and made the system far more reliable.
Still early, but we’re excited about where this can go. Would genuinely love feedback from the community.
Velo
@sundeepjoshi That shift to grounding made a huge difference for us.
Feels like this is just the beginning
Grass
@sundeepjoshi This is such an underrated observation. The grounding problem is real and it shows up in coding agents too, not just browser agents.
We ran into a version of this building Grass. Agents running in the cloud with no feedback loop back to the developer. They'd go sideways at minute 10 and just keep going. The fix wasn't a better model either. It was better visibility. Real-time tool call approval, diffs mid-session, the ability to steer before things go wrong.
Different domain, same root problem. Excited to see where you take this.
@sunnyjoshi This resonates a lot. The “no feedback loop” point is exactly where agents tend to drift.
Also interesting that "better models didn’t help" — better visibility and steering did. Feels like we’re converging on the same idea: grounding helps at the start, but ongoing visibility is what keeps agents reliable.
Different domain, same root problem indeed. Excited to see where this goes.
Velo
@sunnyjoshi @sundeepjoshi Couldn't agree more
Velo
@sundeepjoshi @sunnyjoshi You should read this blog we wrote about how we got the browser agent to work. https://www.usevelo.ai/articles/agentic-screen-recording-by-velo
@ajaykumar1018 If the AI generates a polished script and voiceover that is significantly shorter or longer than my original screen recording, how does the tool handle the visual timing ? Does it automatically speed up/slow down the footage, or does it intelligently use freeze frames or jump cuts to keep the visuals synced to the new audio ?
Velo
@ajaykumar1018 @deepali_mathur
Yup we handle the entire audio video sync automatically. You should try it out
recording a “quick video” and then re-recording it 5 times is way too real 😅. feels like the hardest part isn’t recording, it’s sounding like a normal human while doing it. if this actually fixes that, it’s a big deal
Velo
@webappski Would love for you to try it!!
Konfide
Nice idea
A lot of friction to just start using including the Chrome browser install. It would be good a 2-3 clicks max experience for a user to try.
Velo
@felipe_daguila Thanks for your feedback, We're constantly improving the product experience and we'd love for you to keep trying everything we launch.
DronaHQ
Congratulations team Velo! Love the focus on closing the gap between raw intent and polished output.
Regarding the AI Voiceover sync, if a user decides to edit the generated script after the video is processed, how does the engine handle the re-syncing of the visual timing? Does the browser agent actually "re-record" the sequence to match the new pacing of the speech?
Velo
@gayatri_sachdeva Thanks Gayatri, this is a great question! If someone edits the script after the video is generated, we don’t re-record everything. Instead, we adjust the timing of the scenes to match the updated voiceover.
We use visual cues in the video (like clicks, hovers, and page changes) as anchors, and then tweak the pacing so everything stays in sync.
Not bad, time to move away from loom
Velo
@klashkil Spot onnnn