better menu — but made by butter (that's me 🧈). A food discovery platform that started with one real problem: my mom's restaurant has no website.
"Every time I wanted to eat out, I had to guess. No menu online. No idea what's good. At some point I stopped waiting for someone else to fix it. First restaurant? The one closest to home— my mom's!"
Every decision here has a reason. This is what separates building a product from building a feature.
I wanted to check a restaurant's menu before going. But most places don't have a website. I'd scroll Google Maps reviews hoping someone photographed the dish I wanted. It was annoying every single time.
She runs the restaurant alone. Foreign tourists can't read Thai menus. She loses customers who give up. She has knee pain and walks to every table to take orders. Two problems, both real, both fixable.
Not DAU. Not revenue. Not conversion rate.
Mum walks less. Mum's knees hurt less.
If that happens — the product works. Everything else
is a bonus.
Cold start kills two-sided platforms. The fix: prove it works for one real user first — then walk into any other restaurant with a live demo. Mum's restaurant is the pitch, not just the prototype.
Updated as features ship. A living record, not a pitch.
Nothing shipped yet —
but that's about to change.
Cold start kills two-sided platforms. The fix: start with one restaurant, prove it, then scale with a live demo in hand.