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.

For the first year of building Murror, we optimized for the same metrics every other app optimizes for: daily active users, session length, screens per visit. The dashboard looked healthy. Usage was growing. We felt good about it.

But something was off. Our most engaged users were not our happiest users. People who spent the most time in the app were often the ones who left the harshest feedback. Meanwhile, users who opened the app twice a week for five minutes were writing us emails about how it changed how they handle difficult conversations.

Hey everybody,

Yigit here! I am developing a personal finance app mainly based on what features I wish an app to have and it is on google play closed test now. Here is a quick summary:
The app's main value proposition is being able to keep track of your expenses 'automatically'. The rationale behind is the fact that in my country banking laws restrict individual's access to open banking apis. That is, you cannot have an API access to your bank to exchange information and keep track of your expenses unless you are corporate. According to my research, this feature is available in US and EU but only with certain restrictions in the latter.

I thought it could be sutaible time to ask the community about their needs about such an app and can guide me a long way before I commit further. Would you be so kind enough to answer below questions? Any replies are appreciated and thanks in advance.

1. Do you use personal finance app?

2. Could you please share your the most essential must-have features of the personal finance app of your choise and tell me why?

3. Under which circumstances would you give another app a try?

4. What would be the ideal price point for such a service in your perspective?

We thought we were ready.

Bigger deals. Fewer customers. Better margins. That was the dream.

So we built enterprise features. SSO. Advanced permissions. Audit logs. A whole new pricing tier starting at $2,000/month.

We spent 6 months. Three engineers. One dedicated product manager. Endless meetings about "enterprise readiness."

I'll take the hit.

AI has no idea when someone is politely furious.

You know the email. "Hi team, just circling back on this again as I haven't heard anything. Thanks for your attention to this matter." Reads like a sweet grandma wrote it.

A human reads that and thinks "oh no, they are about to burn the building down." AI reads it and thinks "great sentiment, very positive, 98% satisfaction score."