Sous is not a module you open. It is the intelligence across the whole system. It has read every close, every roster, every invoice, every booking, every review. Ask it about last night. Ask it about last month. Ask it about a specific staff member, a specific supplier, a specific regular. It answers in the language you asked.
Why did last week's labour percent creep up?
Labour hit 25.1 percent, up from 23.5. Two things: Wednesday had a private event that ran two hours long with three extra floor staff, and Saturday's bar was double-covered against the plan. Both are on the roster log. The event will cover its own labour once the close-out lands.
Who is off next week, and does the roster still work?
Three staff on leave: Ari (Wed to Fri), Dewi (Sat), Made (all week). Wednesday and Saturday are the pinch points. The draft roster covers both with existing part timers, labour still lands at 23.8 percent. Widya has been picking up doubles for a month, worth a break.
What broke this month?
Ice machine, twice, both fixed. AC in the back kitchen, still open, callout booked for Thursday. Two closing checklists missed the bar section on Sundays, both by the same closer. Nothing on record for guests missing bookings.
Which regulars have not been in for a while?
Twelve regulars have not been in for over 45 days, all with marketing consent. Six are wine tags, five are family tags, one is a birthday club member overdue. Want me to draft a WhatsApp for the wine group for next Tuesday's tasting?
Ask about last Tuesday's covers, the Wednesday roster three weeks ago, the wine supplier's last five invoices, or Ari's guest history. Sous reads across the whole record, not one module at a time.
By the time you open your phone, Sous has drafted a short paragraph on the shift that just closed. Revenue, labour percent, notable moments, what to watch tonight. In English or Bahasa, whichever you read in.
A one-star review lands or a WhatsApp complaint comes in. Sous drafts a reply in the guest's language with the booking history and the shift context already threaded through. You approve or edit before it sends.
Labour creeping past the plan on a Thursday. An invoice sitting unmatched for eight days. A regular who has not been in for six weeks with marketing consent. Sous surfaces these on the morning brief without being asked.
Generic AI tools have read the internet. They have never seen your venue. They cannot tell you why last Thursday's labour crept up, because they were not there when the roster changed and the private event ran long.
Sous works because HOSPOPS captures the whole record as it happens. Every close locked nightly. Every roster snapshot on the log. Every invoice matched three ways. Every review in one thread with the booking and the shift that produced it. The rhythm feeds the intelligence.
A bolt-on chatbot cannot compete with a system that owns the record. Sous is not an AI feature layered on top. It is the intelligence that sits inside the operations layer that already runs your venue.
Open the demo venue and ask Sous about last week's labour, the wine supplier, a specific regular, or what to watch tonight. Read-only, so you can click anywhere.