Launched this week
Shavely
Group chat where every message speaks your language
61 followers
Group chat where every message speaks your language
61 followers
Shavely is a mobile group chat built for multilingual teams and communities.Messages are translated automatically into each user’s language across 29 languages — with translation visible in real time, no manual action required.
Shavely
Nice, do you plan to integrate this to other tools that are widely used? I understand that the focus lays on internal teams but I think this is something useful for everyone and sooner or later we will have such options on the majority of the platforms.
Shavely
@viktorgems Thanks so much for the thoughtful feedback, Victor 🙏
You're absolutely right — we believe real-time translation should be available wherever people communicate, not just inside Shavely.
We're currently working on opening up our API so other platforms and tools can integrate our translation capabilities. One of the first areas we're exploring is cross-border e-commerce customer support, where multilingual communication is especially critical.Really excited about what's ahead.
Are there any specific tools or platforms you'd personally love to see Shavely integrate with?
Many Thanks,
@tatsuya_murakami are you planning to do it solely for communication, I mean messages only or will the future API be aplicable to let's say blocks of texts and so on?
Shavely
@viktorgems Great question. While our core focus is real-time messaging, we're designing the API to support longer blocks of text as well — such as customer support tickets, knowledge base articles, internal documentation, and other structured content.
So it definitely won’t be limited to chat messages. Our goal is to make multilingual communication seamless across different formats and use cases.
Shavely
@masebuilds @Mason Bachmann Thanks so much, Mason — really appreciate that Sales teams working across regions like Asia and Europe are exactly the kind of teams we had in mind when building Shavely.
Yes — messages are encrypted in transit, and we’re continuing to strengthen our security architecture as we grow. Because messages are processed for real-time translation, we currently prioritize secure transmission and responsible handling of message data.
Security and privacy are very important to us, especially for business use cases like international sales teams, so this is an area we’re actively improving.
This solves a very real problem that most team chat tools completely ignore.
WhatsApp groups with international teams are a mess, half the conversation gets lost because people default to their comfort language and others just stop engaging. Automatic per-user translation without any manual action is the right UX call.
29 languages on launch is a strong foundation. Would love to see Hinglish or regional Indian language support down the road, massive multilingual user base there.
Congrats on the launch!
Shavely
@alamenigma Thank you so much for the thoughtful feedback — you nailed it.
The WhatsApp international group problem is exactly what inspired us. When people go silent because they can’t keep up, teams lose valuable voices. We wanted to remove that friction entirely.
Great call on Indian language support as well! We already support Hindi and Bengali at launch, but Hinglish is a really interesting challenge — code-switching is such a natural way people communicate in India. Regional Indian languages are definitely on our roadmap as we grow. The multilingual ecosystem there is too important to ignore.
Really appreciate the encouragement and insights!
Shavely
One more real-world story we’d love to share:
A hotel cleaning company with staff from multiple Southeast Asian countries started using Shavely for daily coordination. Before, instructions often had to be repeated in different languages, and small misunderstandings would slow things down.
After introducing automatic per-user translation, they reported fewer clarification messages and smoother task handoffs between shifts. Seeing Shavely work in a fast-paced, multilingual environment like that reinforced why we’re building this.
It’s a small example, but it shows how invisible language friction can impact real operations.
Where else do you think this kind of friction exists?
@tatsuya_murakami Shift handoffs are where translations go sideways, so Shavely showing the original first then auto-translating is smart. In WhatsApp it's a long-press translate step or copy-paste. A room glossary plus a do not translate list would seal it.
Shavely
@piroune_balachandran This is such a sharp observation — shift handoffs are exactly where things tend to break down.
That’s why we intentionally show the original message first, so people can always see the source before the translation.
Your idea about a room glossary + “do not translate” list is really interesting. In real workplaces there are always terms like room numbers, internal codes, product names, etc. that shouldn’t be translated.
Definitely something worth exploring as Shavely grows. Really appreciate the thoughtful feedback 🙏
Hey @tatsuya_murakami
Quick thought on Shavely after seeing it on PH. the homepage doesn’t currently tie its value to a specific paying segment like PM/PMM or UX writers, which is where structured output has clear revenue impact.
I sketched a short hypothesis doc if you want it.
Shavely
@paul91z Really appreciate this perspective — that's a great point. Right now the homepage focuses more on the problem (language friction in teams) than on a specific paying segment, but you're absolutely right that tying the value to clearer user groups could make the value proposition much stronger.
I'd definitely be interested in seeing the hypothesis doc you mentioned. Always curious to learn how others are thinking about positioning and segments.
Thanks a lot for taking the time to share this!
Useful for international teams, especially international sales and GTM teams
Shavely
@abhinavramesh Thanks!
International sales and GTM teams were actually one of the main use cases we had in mind when building Shavely. When teams operate across regions, even small language friction can slow down deals — we're hoping to remove that completely.