Memory is a feature, not a database.
It earns its place in a reply or it should not be kept.
We're building the messaging assistant that should already exist.
The problem we keep hitting.
Every messaging app has notifications. None of them have memory. Your customer asked the same question last month. Your friend told you about her trip. Your supplier promised a delivery date. All of it is in your phone, none of it is connected.
The "AI" in your phone today suggests "Sure thing." That's not assistance. That's autocomplete with confidence.
What we're building.
WhatsAssist is an AI messaging assistant with three things missing from the category:
Memory that carries from one conversation to the next, so a customer never has to explain themselves twice.
Knowledge your business, uploaded once, referenced forever.
Restraint it stops itself whenever a reply needs a person, and one switch stops it entirely.
We start on Android because that's where the people who message most actually are. There is no iOS version, and we are not going to name a date for one until we have built enough of it to know the date is real.
Who we are.
Small team based in Bengaluru, India. Backend on Google Cloud, app in Flutter and Kotlin. We've been building software for a while and got tired of forgetting things.
Our principles.
The reply goes out under your name.
So it has to be one you would have sent, and you can read every one it sent.
Privacy is product design.
If we have to choose between a feature and your data staying yours, your data wins.
Regional prices, not regional features.
Everyone gets the same product.
Hiring
When we open a role, it will be listed here. Until then, reach out at support@opergen.com if you want to help build this.
Try the product.
The pitch is easier to understand once you've used it.
