Genki Nakamura

Kept adding random feature requests thinking it would stop people from churning. Six months later the app felt way too crowded and new users kept dropping off because it was confusing.

Turns out adding more stuff was actually hurting retention instead of helping it.

How do you decide when to stop shipping new features and just focus on making the core app simpler again?

In the beginning, I thought lower prices would naturally reduce our cancellation rate. But lowering the price tag didn't save a single customer.

The real issue wasn't what we charged; it was that users weren't realizing core value quickly enough during their first week. When people don't hit their "aha moment" fast, even a low monthly subscription feels like wasted money.

For founders who reworked their onboarding: what specific change helped users cross the value threshold fastest?

Hey! I m Ajay, building Vakh for groups whose events, shared work and useful resources get buried in chats.

Organisers can publish a session once, show it as a feed, calendar or map, and let members contribute photos and comments for approval. Here s an interactive example: https://get.vakh.com/for/communi...

I m looking for small pilots with college clubs and creative groups. The decision I m working through is where to start: session updates, feedback on work in progress, or a shared resource collection. If you run a group, which would your members actually return for? Happy to help you try one.