01 — Restaurants
FreqDine
Kulcha Singh, Surat — replaced Petpooja after a nine-day parallel run
The problem
Indian restaurant POS is dominated by software that charges per outlet, per module, and increasingly per order. A busy counter needs three things to be instant — punch, KOT, bill — and everything else is a distraction that costs the cashier seconds during the Saturday rush.
What we built
- Tablet-first counter billing: table grid, dine-in / takeaway / delivery, running-order edits
- Live kitchen display over realtime — punch appears, kitchen marks preparing → ready
- GST invoicing with CGST/SGST split, per-tenant sequential bill numbers, 80mm thermal print
- Role separation so a waiter can punch but never see the day's money
- Aggregator orders folded into the same queue as dine-in
- Khatabook module — expenses, staff attendance, salaries and end-of-day cash reconciliation
The nine-day test
Rather than ask the owner to trust a demo, we ran FreqDine in parallel with the incumbent for nine days on the same live counter. Both systems, same bills, same staff. The switch decision came from the comparison, not from a pitch.
Supabase (RLS multi-tenancy) · Realtime · React · Postgres