---
First, the story;
In my previous startup, I was the head of product of a grocery delivery app similar to Instacart. Our main competition was people sending orders to the stores through WhatsApp.
Ordering groceries on WhatsApp is very difficult, especially large (10+ item) ones. Our app was much more convenient because the whole UI was curated for grocery ordering.
However, when it came to small orders of obvious items, e.g. an order consisting of 1 kg tomato, 3 eggs, and 2 breads, consumers preferred WhatsApp over our app!
When we asked why, they said "For a simple order using WhatsApp, all I have to do is send a voice message or a short text to the store. But on your app, I have to open the store, open categories, find each item, add them in the right quantity to cart, open cart, confirm location and press order. A lot of clicking and hassle!"
They were right. Our app contained a listing of 1000s of items all arranged in categories with advanced search. What made it great for browsing the store items and placing large orders also made it inconvenient for small orders of obvious items, which were actually more common.
I couldn't merge the convenience of unstructured WhatsApp-style ordering with the structured experience of our app. This problem is inherent to the GUI and every SaaS must have it. It wasn't fixable, or so I thought.
Enter Chatten...
---
Chatten fixes exactly that problem. Chatten makes it possible for to users read and mutate data, and navigate through a SaaS through chat commands.
It maps the user command to a series of API requests and frontend events that are performed on behalf of the user. The user does not need to do multiple high-precision and attention-demanding clicks on the UI.
Watch the demo to see a PoC in action.
Chatten is currently very early stage. I appreciate all kinds of feedback. If want to be an early adopter, or wanna connect, reach out on my LinkedIn https://www.linkedin.com/in/mohammedshahoe/
Thank you