Kopitiam Saji ordering and ops
A small kopitiam group running paper-and-shouting service. We replaced the chits with a tablet-driven order flow, kitchen ticket printer, and a live ops dashboard.
- Role
- End-to-end design and engineering. Solo founder build.
- Duration
- Two weeks of build, one week of on-site shadowing.
- Team
- Taufik Anuar (founder, solo)
- Stack
- Next.js + Supabase, Tailwind v4 on tablet, ESC/POS kitchen printer driver, Vercel hosting, Cloudflare DNS
The problem
Kopitiam Saji ran the way most kedais run. Order taken on a chit, shouted to the kitchen, calculated on a calculator at checkout. Nothing wrong with it for one outlet. Two outlets and one Sunday they ran out of teh ais cups by 11am because nobody could see what was selling.
They needed something that would not slow down the floor staff. Anything that added more taps than a chit would get abandoned by Wednesday.
What we shipped
A tablet-first order app for the counter. A kitchen ticket printer driven directly from the order app (no cloud round-trip, runs on the local network). A live ops dashboard designed around the three numbers the owner actually checks: revenue today, top 5 items, stock-out risk.
Two weeks from kickoff to first live shift. One more week shadowing the floor to fix the things we got wrong. The big one: the kitchen printer needed a tear-off bell, the original mute-mode was too quiet over the espresso machine.
What we would do differently
Ship the dashboard before the ordering app. The dashboard alone justified the project to the owner. We led with the ordering app and had to keep explaining the ROI for ten days while the data filled in.
If you are building for a kedai or kopitiam: ship the report first, the workflow second.
2 weeks
100%
~280
20 min/person
Have something like this you want built?