9 min read
Webapp2026 — Founder, Product & GTM

Hangry: Putting Restaurants Best Food Forward

Role
Founder — product design & GTM
Team
Kaizer Studios
Timeline
Jun 2026 — present
Platform
Web app

Executive summary

60-second read
Problem
Independent Klang Valley restaurants are invisible for the one thing they are actually known for. Google Maps holds the location but no menu, GrabFood sells delivery rather than discovery, Eatclub sells deals rather than dishes. Nobody connects dish-level search to promotions.
Hypothesis
If the supply side is built by hand before a line of product code, the dataset becomes the moat rather than the algorithm — and an owner will trade a free listing for measurable footfall.
Solution
A manually curated, dish-level directory launched scraped-first, with provenance shown on every listing and “claim this listing” as the conversion mechanism instead of an onboarding gate.
What changed
80 venues tracked, 6 onboarded, 5 verified. But only 2 of those 6 have offered a promotion — and the promotion is the entire ROI story we sell to a restaurant.

01 — Context

Hangry is the deliberate pivot from Onz, which I closed in June 2026. Onz built an AI recommendation engine before it had the users whose data the engine needed. Hangry takes the same problem — decision fatigue in food — and inverts the order of operations: collect the supply by hand first, write the product second. I run it out of Kaizer Studios as founder, doing the product design and the restaurant conversations myself.

02 — The problem, from the restaurant's side

An independent operator with a genuinely good signature dish has no way to be found for it. A great matcha or a standout satay gets buried under a generic map pin or a forgettable Instagram post. Every existing route to visibility costs the operator something they did not choose: a discount set by a deals platform, a commission on delivery, or marketing work they have no time to do. The gap is not that these restaurants are undiscovered — it is that they are discovered as a location rather than as a dish.

Fig 01Before state — Different platforms Malaysians use to discover food

03 — Constraints

  • Nobody pays before the platform proves value. Listings are free; the upgrade is control — live menu edits, promotion scheduling, analytics — and it only exists once there is traffic worth controlling.
  • Onboarding could not be the launch gate. A directory needs to look inhabited before an owner will join it, which means supply has to exist before the first restaurant says yes.
  • Hawkers and kopitiams do not use technology or know how to manage it so getting them to operate their own Digital Storefront is going to be difficult as visibility is the ROI they need.
  • No revenue before the self-serve portal ships, so runway has to reach December's evaluation gate on its own.

04 — What we learned

Eighty venues tracked, twenty-one emailed, six onboarded. For cold outreach that funnel is unremarkable. The composition of the six is the finding: the partners who say yes are cafés, not kopitiams — four of the six are cafés, one is a local restaurant. Not one kopitiam or hawker has onboarded, and those are exactly the venues a nasi-lemak-first launch depends on. A café already thinks in brand, photography and Instagram, so a curated dish listing reads as free marketing it would otherwise pay for. A kopitiam has none of that frame, does not discount, and does not feel the absence of another channel. The launch thesis and the supply that actually converts are pulling in opposite directions.

Fig 02The pipeline as it actually stands, and the venue types hiding inside the last column.

05 — The move

So on 28 June I dropped the onboarding gate and decided to launch scraped-first — I control the supply outright through manual collection, every listing carries a visible provenance flag and a last-verified date, and onboarding runs alongside launch rather than in front of it. That reverses the sales conversation: instead of asking an owner to imagine a listing, I show them one that already exists, already ranks, and is one “claim this listing” away from being theirs to edit.

06 — What shipped

  1. AThe Restaurant Detail Page first, before search. It is the digital storefront, but more usefully it is the thing I put on a phone in front of an owner — the pitch is a page, not a deck.
  2. BDish-level search with promotions attached to menu items rather than venues, so a deal surfaces against the plate someone is actually looking for.
  3. CAn Admin page that takes the Notion CMS live in minutes with full control of the listed restaurants on the platform.
  4. DProvenance in the product, not just the database. Scraped listings are dated and labelled rather than silently stale, which is what makes an unclaimed listing defensible when the owner finally sees it.
Fig 03Shipped UI — Homepage, search, storefront that is the dish first search engine

07 — Tradeoffs

Scraped-first buys supply at the cost of consent. A listing an owner never asked for is a weaker starting position than one they signed up for, and the listing agreement that would formalise it is still an open item rather than a shipped one. I took the trade because a directory with six venues does not work and a directory with eighty does — but it means the first conversation with an operator is now about something already published, not something proposed, and I have to be able to defend that in the room.

08 — Where the numbers stand

80
venues tracked across the Klang Valley pipeline
6
onboarded, 5 of them owner-verified, against a target of 20 by 15 September
2
of those 6 have offered a promotion — the mechanic the whole ROI pitch rests on

09 — What's still open

The promotion loop is the whole ROI argument I make to a restaurant — list them as their proxy website, we distribute it, you see footfall. Until that number moves, the pitch is a hypothesis with six data points, not a proven mechanic. Pricing is untested for the same reason: nobody has been asked to pay yet, so what an owner will actually part with is still unknown. And the September gate is twenty onboarded by the fifteenth. At six, with twelve days left, the honest thing is to present the gap rather than the target.