I didn't set out to build software. I set out to stop losing money.
SureTill was written by a restaurant owner in Lahore, in the gaps between services, and tested in the only place that counts, a real dining room on a real Friday night. It is a founder-led restaurant POS software from Pakistan, built by someone who still runs the counter.
I run Flavourz, a restaurant, a cafe and a lounge, across three branches. For years I did what every owner here does: bought the POS that came recommended, paid the setup fee, trained the staff, and then spent the next eighteen months working around it.
The failures were never dramatic. They were just relentless. The internet would go at 8:40pm and the system would show a spinner while sixty people waited for their bills, so we'd write orders on a notepad and reconstruct the evening from memory at midnight. A thermal printer would jam at 9pm and there'd be no way to reprint a kitchen ticket without re-billing the whole table. Our best customers, offices nearby, families with monthly accounts, ran khata, and the software had no concept of it, so their credit lived in a register in the drawer and ended in an argument roughly once a quarter.
And every month, the cash count at 2am wouldn't match the report. Not by much. Enough that I knew something was wrong and not enough to prove what. Nobody could tell me whether it was portioning, wastage, price rises or theft, because the system that was supposed to tell me had spent half the month offline.
So I taught myself to build one. Badly, at first. The first version could barely take an order. But I had something no software company has: a restaurant to break it in, three branches to break it in harder, and no way to hide from the consequences on Monday morning. Every feature in SureTill, the offline-first billing, the recipe inventory, the khata and credit management, exists because something went wrong at Flavourz and I refused to work around it a second time.
We ran it live for months before I offered it to anyone else. Not a pilot, our only system, on all three branches, through Ramadan, through load-shedding, through month-end closings, at over a thousand orders per branch a day. Today it also runs at Ziafat Restaurant in Kamalia. It is still what Flavourz runs on. If it breaks, it breaks for me first.
That's the whole pitch, really. I'm not selling you a platform. I'm selling you the offline restaurant POS software I built because I needed it.
How it actually happened
Nights and closed Mondays. The offline-first architecture came first, because that was the problem that cost the most.
No parallel system to fall back on. Every gap showed up within a week, in front of paying customers.
Khata, recipe inventory, delivery and multi-branch reporting, each added because we needed it, in that order.
Only once it had survived long enough that I'd stopped worrying about it. That felt like the honest threshold.
Three things we won't compromise on
Features get built because a restaurant needed them, not because a competitor's brochure listed them. When the two conflict, the restaurant wins.
Exportable in open formats on any plan, any time, including if you leave. Self-hosted, cloud-optional deployments keep the database in your building permanently.
This is the founding constraint, not a feature we added later. Any change that would make the system depend on connectivity does not ship.
Where it runs
Live every day at Flavourz in Lahore and Ziafat Restaurant in Kamalia, dine-in, cafe, lounge, takeaway and delivery.
See it running live, book a demo at our restaurant.
Come to Flavourz during service. Talk to the waiters, watch the kitchen, and ask me anything you like about what it cost to get here.