I’m working on Reply Safe because I personally hit a breaking point with high-stakes work communication.
As a backend developer working under multiple leaders, I spent months in an environment with constant pressure, ambiguous decisions, and subtle power dynamics. Many important things were discussed informally, then later enforced as if they were documented commitments. Questioning or asking for clarification often felt risky.
The result wasn’t a technical problem — it was psychological.
I started freezing when receiving messages, rereading Slack threads for 30–40 minutes, worrying about tone, timing, and how every word could be interpreted or used against me.
Like many people do, I began pasting messages into ChatGPT or asking trusted colleagues to review replies before sending them. That helped, but it didn’t solve the core issue: the fear of retaliation and escalation when there’s a power imbalance.
That’s when it became clear to me that the problem isn’t “writing better messages”.
It’s deciding how to respond safely.
Reply Safe exists to replace that “trusted colleague review” moment — but instantly, privately, and with context awareness. It’s about helping people respond without escalating conflict, without sounding defensive, and without putting their position at risk.
In short:
Reply Safe exists because in many workplaces, the hardest part of communication isn’t the wording — it’s protecting yourself while you still need the job.
Congrats on the launch, looks solid. How are you currently thinking about acquiring early users and gathering feedback?
Right now we’re focused on learning more than scaling.
We’ve been working on feedback from early beta users and also from discussions on Reddit. The qualitative signals are strong — people clearly relate to the “high-stakes message” problem — but we’re still validating where this pain is most acute.
We haven’t invested in ads yet. Instead, we’re trying a more human approach:
engaging in communities where people naturally talk about workplace tension
sharing context, not links
asking questions and listening
One thing we’re realizing is that highly technical audiences don’t always feel the pain as strongly. The issue seems more emotional/political than linguistic. So now the challenge is identifying channels where people experience power asymmetry, conflict, or anxiety around communication — and are open about it.
This is actually my first time launching something of my own. I’ve always been on the engineering side building for others. Now I’m on the other side trying to understand distribution, positioning, and how to connect with people around a real problem.
It’s been harder than building the product — but also more interesting.
I really like how intentional your approach is, especially focusing on emotional context over pure technical framing. Most founders miss that.
If you're still in the validation phase, one thing that can accelerate it is systematically mapping where those “power asymmetry” conversations are already happening and testing different positioning angles within them.
I’ve helped a few early-stage founders structure that exploration so they don’t rely purely on organic trial-and-error.
If you'd like, I can outline what that would look like specifically for your niche.
This comment was deleted 7 months ago