I thought it would mostly be about features
I thought building Unjam would mostly be about features.
But it’s actually become more about listening.
The more I talk to people, the more I hear the same pattern:
“I know what to do, I just can’t start.”
Feels less like a productivity issue and more like cognitive overload.
Curious if others have seen this too.
If you want to try it:
👉 https://unjam.lovable.app/
This hits hard — especially the part about thinking it’s all about features.
I’ve seen this a lot with early products: founders keep improving the product itself, while the real friction is actually in how people first understand and trust it.
Even when there is traffic, if the value isn’t immediately clear or the first experience feels a bit confusing, it ends up looking like a “distribution problem”.
Curious — did you ever notice moments where users were coming in, but just didn’t convert the way you expected?
Yeah, this is exactly something I’ve been starting to notice.
It’s less about people not finding it, and more about what happens in the first few seconds after they land.
There are definitely moments where people come in, understand the idea loosely, but don’t immediately feel “this will actually help me right now” — and I think that’s where the drop-off happens.
So I’ve been shifting focus from just improving the tool itself to making the first experience clearer and more real (like adding specific scenarios and more concrete first steps).
Trying to close that gap between “this sounds interesting” and “I’ll actually try this”.