The feature our users keep asking for is the one we'll never build.
Every week we get the same request: "Can I just talk to the AI?"
They want a chat interface. A back-and-forth. Something that feels like texting a therapist at 2am. And honestly, it would be the easiest feature we could build. The AI is already there. The conversation engine exists. We could ship it in a week.
We won't.
Here's what we've learned building Murror: the moment you give someone a chat interface for emotional reflection, you've changed the activity from "writing to understand yourself" to "talking to get a response." The posture shifts. Instead of sitting with a feeling, you're waiting for validation.
We tested it internally for two weeks. The journal entries got shorter. The reflections got shallower. People started asking the AI "what should I do?" instead of exploring what they actually felt. The AI became a crutch instead of a mirror.
The whole point of Murror is that the AI stays in the background. It notices patterns you can't see yourself. It surfaces insights after you've done the work of writing. It never interrupts your thinking -- it waits until you're done.
A chat interface would make the product stickier. More daily sessions, longer time-on-app, better engagement metrics. Every growth playbook says we should build it.
But we'd be optimizing for the wrong thing. We'd be making people feel heard by an AI instead of helping them hear themselves.
The hardest product decisions aren't about what to build. They're about what to refuse to build, even when users are asking for it and the metrics say yes.
Anyone else held the line on a feature like this? Curious how you explain the "no" to users who genuinely want it.
Replies
the internal test result is the convincing part here, not the principle. anyone can argue in theory that a chat interface would change the posture, but you actually watched entries get shorter and shallower in the same two weeks you'd expect the opposite from a stickier feature. do you say any of that specific data to users who push back, or does explaining the 'no' stay more philosophical in practice?
Murror
@omri_ben_shoham1 We do share the data — not as a sales pitch, but because it surprised us too. When users push back, we show them the before/after: average entry length dropped 40%, and the reflections shifted from exploratory to transactional. Most people get it immediately once they see the pattern. The ones who still want chat usually realize they're looking for a different kind of product, and that's okay. We'd rather lose a user than change what the writing space means.
The move that helped me most here was to stop reading "can I just talk to it" as a feature request and start reading it as a report of a moment. Almost nobody actually wants a chat box, they want something to catch them on a day when writing feels like too much. That is the need sitting under the ask, and you can answer it without the back and forth that would break the posture you described so well. A lighter on ramp for hard days, one gentle prompt that meets people where they are, still keeps the AI a mirror instead of a responder. On explaining the no, it lands completely differently when people can see what you are protecting. "We don't do chat" sounds like a gap. "The writing is the part that changes you, so the AI waits until you are done and stays out of the way" sounds like a spine, and most people respect a product that clearly knows what it is.
Murror
@asadmalik901 "Reading it as a report of a moment" — that reframe is going to stick with me. You're right that it changes everything about how we respond. We've actually started experimenting with exactly what you described: a gentle prompt on harder days that lowers the barrier without switching the mode. And your point about framing is spot on. We've been saying what we don't do instead of what we protect. "The AI waits until you're done" is a much better way to explain it. Thank you for this.
@monatruong_murror This made my day, thank you Mona. The fact that you were already testing the gentle prompt before we talked tells me the instinct was there, you just needed the words for it. One thing I would watch as you build it: the risk with a lighter door is that it quietly becomes the default one, so the real win is if it stays the exception and hands people back to the writing quickly. Rooting for you and the team on this.
Have you thought about offering chat only after someone finishes writing? It could keep the reflection process while giving users another way to explore their thoughts.
Murror
@khaildnaseem We've thought about this a lot, and it's the most tempting version of the idea. The problem we kept running into is that "after writing" is exactly when the reflection has the most value. That's the moment where you sit with what you wrote and the AI surfaces patterns you didn't notice. Adding chat there would pull people out of that sitting-with-it moment and back into seeking. We'd essentially be rewarding the hard work of writing with a shortcut to skip the payoff. That said, we are exploring lighter ways to help people explore after they write — just not through conversation.