From one stall to an operating system
We didn't set out to build software. We set out to survive a Friday-night surge with thin margins — and the system we needed didn't exist, so we built it.
Most restaurant software is written by people who have never had to close a kitchen at midnight, count a till that came up short, or watch a public holiday either save the month or break it. We have. NJ Group has run restaurants and hotels in Singapore since 1997 — and everything we now build begins from inside that room, not above it.
This is the story of how a company that started in real kitchens ended up writing an operating system for them. It isn't a tidy arc. It runs through years of thin margins, festive surges, staff who left and staff who stayed, and a slow, stubborn realisation: the tools we were renting were quietly taking the one thing we couldn't afford to lose — the relationship with our own guests.
- NJ Group has operated F&B and hospitality in Singapore since 1997 — the lessons came from service, not slides.
- NJ Intelligence, our tech arm since 2014, was built to solve our own problems first.
- We built the system because nothing on the market let an operator keep their data, demand and brand.
- Simplify.food is the result — an operating system by operators, for operators, at 0% commission.
01 — The room we started in1997: learning the business the only honest way
We began the way most operators do — close to the floor, doing the unglamorous work. Prep before dawn, a lunch rush that decided the day, the long quiet stretch, then dinner. Singapore in the late 1990s was a demanding place to feed people: a city that knew exactly what good food cost and exactly what it should taste like, with a crowd that moved from hawker stall to fine dining without blinking.
Those years taught a lesson no dashboard ever did. Margins in F&B are thin enough to vanish on a bad week, and the difference between a profitable outlet and a painful one is rarely the menu — it's the hundred small decisions around it. When to push a promotion. Who to bring back. How to fill a Tuesday that looks empty by Friday. We made those calls by instinct and aching feet, and we got plenty wrong before we got them right.
02 — The lessons that became a blueprintWhat running real kitchens actually teaches you
By the time we had multiple restaurant and hotel units running, certain truths had stopped being opinions and become operating principles. They are the spine of everything we build now.
- 01
Demand is never flat
Payday peaks, public-holiday swings, festive surges, the dead middle of the week — a restaurant lives and dies by rhythm, and any system that treats every day the same is lying to you.
- 02
The guest is the asset
Not the order, the guest. A regular who comes back on their own is worth more than a stranger you paid an aggregator to deliver to once and never see again.
- 03
Labour is the real cost
The hours that disappear into manual marketing, follow-ups and admin are hours stolen from the floor — and on a thin margin, that time is money you can't get back.
"The line from one stall to an operating system isn't a leap. It's the same instinct, finally given the right tools."
03 — Why we built it ourselves2014: the year we stopped renting our own growth
By the mid-2010s, the tooling on offer had multiplied — a loyalty app here, a delivery marketplace there, a reservations widget, an SMS blaster. We tried them. Each solved a sliver of the problem and quietly created a new one: our guest data scattered across half a dozen systems, none of which we truly owned, and a delivery channel taking 15–30% of every order before we'd paid for a single ingredient.
That was the turning point. We founded NJ Intelligence in 2014 — our own tech arm — not to chase a software market, but because the first and most demanding customer we had to satisfy was ourselves. We were tired of renting demand by the order and surrendering the guest relationship to a logo that wasn't ours. So we started building the layer we wished existed: one place that held the guest, and intelligence sitting on top of it.
It helped, enormously, that we were building inside live restaurants. Every feature was tested against real service, real surges and real failure — the kind of feedback loop a pure software company never gets. The platform took shape on years of live production data from our own venues, because we had no choice but to make it work on a Friday night, not just in a demo.
04 — What it becameSimplify.food: an operating system by operators, for operators
What we built for ourselves became Simplify.food — an AI operating system for restaurant growth, governed by what we call Policy-Driven Intelligence. It isn't a black box that does whatever it likes; it's a decision engine that acts only within the rules an operator sets for pricing, tone, timing and margin. That guardrail comes straight from the floor — because we know exactly how a brand gets cheapened by a discount no one approved.
And it rests on a single conviction, earned over decades rather than argued from a slide: own your data, own your demand, own your brand. Direct orders run at 0% commission through your own branded channel, the guest relationship stays first-party, and the system handles engagement 24/7 so the hours stolen by manual marketing come back to the floor. The compounding that used to happen for the marketplace finally happens for you.
We still think of ourselves as operators who happen to write software, not the other way around. The journey from one stall to an operating system was never about technology for its own sake — it was about giving the next operator the thing we spent years building by hand. The pressure was real. The lessons were real. The system is what we wish we'd had in 1997. That's what it means to own your table.