Sindeesh, our founder, worked behind the bar at a restaurant in Europe through his MBA. By the time he finished, he figured he'd seen enough of how a restaurant — and the systems meant to run it — actually worked, and thought: why not build the app myself? Back in Bengaluru he spent six months working the floor at a friend's restaurant before writing the first line of Chef·Command. He learned three things. One: every restaurant runs on the same four things — menu, orders, kitchen, billing — but the register, the KOT book, and the Excel sheet never talk to each other. Two: the waiters and the kitchen staff don't have time to learn a complicated new system between tables. Three: the kitchen is hot, busy, and loud — the screen there has to be readable in a glance, not squinted at.
The first version was built over a long Diwali weekend and taken to one restaurant. They asked for table management. We built it. They asked to track cancelled orders. We built that too. We never set out to build a POS — restaurant owners kept asking for the next thing that was slowing their service down, and we kept saying yes.
"We don't sell software. We sell a quiet kitchen and a faster close-out. The software is just how we deliver them."
We're still early days. A handful of restaurants in Bengaluru are running their floor, kitchen, and billing on Chef·Command — and every change we make comes from watching a real Saturday night, not a roadmap meeting. One mark — a forest-green bracket with a brass chevron pointing into it. Command goes in. Service comes out.