8
14 Comments

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"?

on June 22, 2026
  1. 1

    Your line nails it: "an app doesn't fix a behavior problem, it just adds another app to ignore."

    Journaling apps are good at saving what you write. They don't solve the hard part: getting you to do it. Nothing reminds you, and the payoff comes too late to build a habit. Everyone makes reflection easier once you've opened the app. The drop-off happens before that.

    The distinction I'd make is this: "needs validation" means you're not sure people want the result. "Not the right thing to build" means they want the result, but your product can't change the behavior behind it.

    Voice journaling feels closer to the second category. Better input methods make journaling easier, but they don't necessarily make people journal.

    So the opportunity probably isn't a better journal. It's whatever gets you to start. The calendar hook is the interesting part, not the voice recording.

  2. 1

    I completely relate to this. Even when a routine is interesting and genuinely useful, I often just forget or simply don't do it. It's the same with journaling for me. If you want to stick with it permanently, sometimes the full routine feels like too much, and it's better to just have a single entry like "the day went good."

    But maybe shelfing it was wrong - this thing will find it's users. Same as journals

  3. 1

    The research answered the right question but maybe stopped one step too early. "People don't stick with journaling apps" is a retention insight, not a category verdict. The real constraint you identified — behavior change, not tooling — is actually the more interesting product surface. Most of the crowded players are solving capture. Nobody's solved the trigger. That's a different problem, and usually a less crowded one.

  4. 1

    When you shift the mindset from "Is this market full?" to "Is this market satisfied?", you stop competing on their terms and start competing on their shortcomings. Are you currently using this approach to refine the positioning for your upcoming sites, or are you looking to apply this logic to the Tamable strategy?

  5. 1

    I'd be careful not to confuse a crowded category with a dead opportunity.

    The research seems to show people don't stick with journaling apps. But maybe the real question is whether this is actually a journaling app, or something else that happens to start with reflection.

    Sometimes the insight isn't "don't build it"—it's "you're solving the right problem with the wrong framing."

    1. 1

      Thanks for the reply!

      Before taking a "saturated market" as a sign to just "stop building," I think it's better to look at it through the lens of opportunity. By validating the existing market, we can figure out what pain points are still out there and what kind of niche we might be able to tap into.

      I really appreciate your advice!

      1. 1

        Absolutely. A crowded market often means there's proven demand, it just takes finding the gap that existing solutions aren't addressing.

        I think your approach of using competitor research to identify unmet needs is the right one. Sometimes the best opportunities come from improving adoption, retention, or a specific workflow rather than creating something entirely new.

        If you decide to revisit the idea and explore an MVP, I'd be happy to connect you with a professional developer who could help validate and build it efficiently.

  6. 1

    I hit the same wall building DictaFlow, a hold-to-talk dictation app. The pattern is usually simple: people know what they should do, they just don't do it. With voice capture, the gap between actually using it and deleting it after 3 days usually comes down to whether the first step feels invisible. If opening an app and waiting is part of the flow, the habit dies right there. Curious, when your team was evaluating the voice journaling idea, did you spend any time on the capture UX, or was the debate mostly about the reflection and organization side?

    1. 1

      Thanks for the reply! Ultimately, our team just wanted to run a little experiment. Whenever an idea like, "Wouldn't it be cool if this service existed?" popped up, we wanted to plug it into our market validation tool, Bunzee, just to see what kind of results it would spit out.

      Since the whole point was early-stage validation testing the market impact and making sure the direction made sense before actually developing anything we didn't really dive into the nitty-gritty details like you mentioned.

      That being said... if this idea had scored over 90 out of 100, we probably would have started building it right then and there!

  7. 1

    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.

    1. 1

      Thanks for the great insight! A good idea might seem awesome at first, but if we overlook the user's actual pain points and brush off early market validation, it will just remain a 'good' idea rather than a 'great' one, exactly like you said.

  8. 1

    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.

    1. 1

      I couldn't agree with you more. It seems like they just couldn't convince users that the value of reflection has to come strictly from a journaling app. Plus, there are tons of similar services out there, but none of them have really managed to crack that problem either.

      Actually, I think this is a perfect example of just how crucial early market validation iswhich is exactly what happens when you plug a spontaneous idea right into our service, Bunzee.

      By analyzing real data to uncover our blind spots, I feel like Bunzee can really help us validate market trends, flows, and even future strategies that we hadn't even considered.

  9. 1

    If you are curious about the detailed analysis, please check it out at https://bunzee.ai/ai/analysis/3d297f2c-1261-48c1-ace0-040765b89a95.

Trending on Indie Hackers
Priorities for launching a SaaS solo, with no budget User Avatar 169 comments I thought I was building a news visualization tool. Users thought it was a catch-up tool. User Avatar 41 comments I Rejected a $15K Acquisition Offer for My Multi-Agent IDE — Here's the Full Breakdown User Avatar 29 comments I built a tool directory that doesn't pretend every founder has the same needs User Avatar 20 comments 5 Books, Make Smarter User Avatar 10 comments Why founder-led outbound breaks the moment you try to delegate it User Avatar 7 comments