I tested a voice journaling app idea on our own tool. The result was uncomfortable.
Someone on our team had an idea last week.
A voice retrospective app connects to your calendar, and at the end of each day asks "how did today go?" You talk for a few minutes, and it automatically organizes your reflection into structured notes.
Genuinely liked the idea. Felt useful. Felt like something people would actually open every night.
So we ran it through our own competitor research tool to validate it before spending any time building.
The analysis came back with something we didn't want to see.
The space is crowded Reflect, Notion AI, Day One, Rosebud, and a dozen smaller players. Most of them are free or $4/month. The ones trying to charge more are struggling with the same problem: people will use a journaling app for two weeks and then forget it exists.
The insight that stung: the pain isn't "I don't have a way to reflect." It's "I don't actually do it consistently." An app doesn't fix a behavior problem it just adds another app to ignore.
We shelved the idea. Maybe permanently.
The uncomfortable part isn't that the idea was bad. It's that without running this research first, we would have built it. I know we would have. It felt too right not to.
Has anyone here killed an idea that genuinely excited you, just because the research said the market wasn't there? How do you separate "this needs more validation" from "this is just not the right thing to build"?
This is actually a healthy signal, not a failure of the idea.
What you ran into isn’t really “crowded market = don’t build,” it’s more like “surface-level similarity = false signal.” Journaling/retrospective tools look saturated because they all target the same obvious job: capture reflection. But the real question is whether anyone has solved consistency, not collection.
And that’s the key distinction most research tools miss: markets can be crowded and still unsolved if the core behavior problem remains unchanged. In your case, you already identified the real constraint — not tooling, but habit formation.
So the decision isn’t necessarily “kill vs build,” it’s more like:
are you building a journaling app, or are you building a system that changes daily behavior?
Good ideas often feel “too right” early on because they solve the surface problem well. Strong ideas survive when you push past that and see whether they still make sense when you remove the excitement and focus only on sustained usage.
Killing ideas that feel good but don’t survive that test isn’t a loss — it’s usually what keeps teams from building the same product everyone else already abandoned in slightly different packaging.
One thing I'd be careful with:
The research seems to have answered whether people stick with journaling apps.
I'm less certain it answered whether the value of reflection has to come from a journaling app at all.
Those sound related, but they aren't necessarily the same question.
That's what caught my attention.
If you are curious about the detailed analysis, please check it out at https://bunzee.ai/ai/analysis/3d297f2c-1261-48c1-ace0-040765b89a95.