5
13 Comments

Reddit feedback changed how I think about my AI reply tool

I started building ForSocials as a simple browser-based AI reply tool.

At first, I thought the main value was speed: fewer tab switches, less copy-paste, faster replies.

But after getting feedback from other builders, I realized the deeper value is probably consistency and voice.

People do not just want faster replies. They want drafts that:

  • understand the thread
  • sound closer to them
  • feel editable, not automated
  • help them keep showing up without burning out

So I started adding memory, thread context, and personalization based on what users edit and choose.

Still early, but this changed the product direction a lot.

Curious how other founders think about this: when building AI tools, do you position around speed first or trust first?

Page if useful for context:
https://forsocials.com/ai-reply-generator

on May 27, 2026
  1. 2

    Same here. Reddit forced me to strip the pitch completely — just describe the problem you solve, nothing else. Conversion went up, weirdly.

  2. 2

    Trust first, no question. I built DictaFlow, a voice dictation tool, and the biggest thing I learned was that people will forgive a little delay way more than wrong words. That point from the thread about making it feel editable, not automated, is exactly right, when users see text that’s 90% there, they’ll clean it up. When it’s 50% off, they stop using it. Speed gets the install, accuracy keeps the habit. We built mid-sentence voice correction, say a keyword and it deletes back to the error, so people could fix mistakes without breaking their flow. That’s a trust feature, not a speed feature.

  3. 2

    Community feedback changing your whole direction — that's the most honest thing about building.

  4. 1

    Speed vs trust is a positioning question I think about with my own AI tool too.

    Speed gets people in the door. Trust keeps them. And in the social/LinkedIn space specifically, "sounds like me" is the product, not just "saves time."

    The edit behavior data you mentioned is gold. People will tell you with their edits exactly what they actually wanted. That's more honest signal than any survey.

    Good direction.

  5. 1

    The shift from "reply faster" to "reply better" is the one I keep seeing in the AI tools space, accuracy of the response matters more than throughput. Same pattern showed up in our benchmark of how AI describes companies, visibility was high but accuracy was the gap nobody was measuring. What did the Reddit feedback specifically change about your scoring?

  6. 1

    Reddit feedback hits differently because people there have zero incentive to be polite. Harsh but calibrated.

    Curious what specifically changed — was it the use case framing, the UX, or the core value prop? For AI text tools I've found that "what problem do you solve in 5 words" is the hardest question to answer well.

  7. 1

    Trust first, without question — and your "feel editable, not automated" point is really the crux of it. When users sense they're refining a draft that's 80% right rather than correcting something that's 80% wrong, the whole psychological relationship changes. That shift from "fixing AI output" to "collaborating with a starting point" is what separates tools people actually keep using from ones they abandon after a week. One micro-thing that's helped me think about this: making the edit flow genuinely frictionless signals that editing is expected and welcome, not a fallback for when the AI failed. Trust isn't built in the feature list, it's built in those tiny moments.

  8. 1

    went through the exact same pivot with my tool. started out thinking speed was the selling point, but the people who stuck around were the ones who said "this actually sounds like me." once I stopped chasing faster output and started focusing on voice consistency, retention got noticeably better. your point about thread context is spot on, that is what separates a helpful assistant from a comment that feels like you wrote it yourself.

  9. 1

    The interesting shift here is that you accidentally moved from “AI reply generator” territory into identity/communication infrastructure territory.

    Speed gets people to try the product.
    Consistency and voice are what make them stay.

    Most reply tools still feel transactional:
    generate text, paste text, repeat.

    But once memory, thread context, editing patterns, and personalization enter the system, the product starts becoming something closer to a communication layer that understands how a person thinks across conversations.

    That is a much bigger category than “reply faster.”

    I’d be careful with the ForSocials name for that reason.

    It explains the surface feature, but it may undersell where the product is naturally heading: persistent voice, contextual communication, reputation consistency, and AI-assisted presence across platforms.

    A broader name like Beryxa .com would carry that direction much better if the product keeps evolving beyond simple reply generation.

    The trust-first framing is probably the right instinct too. People forgive slower AI much faster than they forgive AI that sounds wrong.

    1. 1

      Hey aryan,

      Thanks for the feedback, actually i never thought that the name of the app could stand on my way, i guess i was used to it.

      "Reply faster" was the moto.
      But the product keeps evolving beyond simple reply generation.
      I am moving to a more personalised context. I want it to give ready replies that match exactly your style(still working on it)

      How does Beryxa make sense btw?

      Maybe changing the name is a move actually, will have to think about it.

      Thanks again!

      1. 1

        That is exactly why I brought it up.

        ForSocials makes sense when the product is mainly “reply faster on social platforms.”

        But what you’re describing now is broader: ready replies that carry a person’s style, context, tone, memory, and communication patterns across conversations.

        That is no longer just a social reply tool. It starts feeling more like a personal AI communication layer.

        Beryxa works better for that direction because it does not box you into social media or replies. It feels more like a serious software brand that can hold personalization, workflow, memory, and communication intelligence as the product expands.

        So the logic is:

        ForSocials = clear feature name
        Beryxa = broader brand if this becomes a real communication system

        If Beryxa is only useful as a naming example, no need to overthink it. But if it feels like a serious candidate, I’d discuss it privately before you put more product, users, and content behind ForSocials.

        1. 1

          That makes sense, and I appreciate you explaining it that way.

          I think you’re right that ForSocials describes where the product started more than where it might be going. At first the idea was simple: help people reply faster on social platforms.

          But now I’m thinking much more about voice, context, memory, editing patterns, and helping someone stay consistent across conversations. So “personal AI communication layer” is probably closer to the direction than “reply generator.”

          I’ll definitely think seriously about the naming before I go too deep with the current brand. I’m not sure about Beryxa specifically yet, but I understand the logic: a broader name gives the product more room to grow.

          Really useful feedback. Thank you.

          1. 1

            That makes sense.

            I would not frame this as “ForSocials is bad.” It worked for the first version.

            The real question is whether it still fits if the product becomes a personal AI communication layer built around voice, memory, context, and consistent replies across platforms.

            That is why I mentioned Beryxa. It gives you a broader software-brand shell instead of locking the product to socials or reply generation.

            If Beryxa feels even potentially serious, connect with me on LinkedIn and we can discuss it privately before you put more users, content, and product history behind ForSocials:

            https://www.linkedin.com/in/aryan-y-0163b0278/

Trending on Indie Hackers
Fixing broken scrapers instead of working on my actual product. So I made it my problem. User Avatar 42 comments I Built a Habit Tracker SaaS Alone in 6 Weeks (No CS Degree, No Team). Here's Exactly How User Avatar 41 comments I built a WhatsApp AI bot for doctors in Peru — launched 3 weeks ago, 0 paying customers, and stuck waiting for Meta to approve my app User Avatar 39 comments I built an open-source PII masking layer for LLM APIs — early traction, looking for design partners User Avatar 33 comments From broke and burned out as a PM, to launching my SaaS and optimizing my health User Avatar 27 comments How to see revenue problems before they get worse User Avatar 27 comments