CASE STUDY · SINGAPORE F&B
From manual spreadsheets to a published roster in minutes
How multi-outlet operator Su Yun is moving rota admin off Excel, WhatsApp, and paper — and onto one drag-and-drop schedule the whole team shares.
Customer & industry context
Su Yun PTE LTD is a Singapore food-and-beverage operator running multiple outlets with roughly 305 active staff across ~491 employee profiles (550-seat plan cap) on Slota's launch-partner plan. It's an industry where the hire clock is tight: resident entrants to F&B dropped from 16.1k (2023) to ~14k (2025) while the sector's vacancy rate sat near 18.7% (Mar 2026), and labour typically runs 25–35% of revenue.
Sector figures are cited industry stats, not Su Yun measurements.
The problem — rotas built one outlet at a time
Every outlet manager was building their own rota. Excel, WhatsApp threads, and paper — no single view across outlets, no way to see whether the same person had been double-booked onto two shifts, and no hours-versus-sales check before the schedule went out.
Last-minute swaps and no-shows got chased in chat groups. If someone fell through in a market with F&B vacancy at ~18.7%, that scramble didn't just cost an evening — it burned manager hours every single week.
The solution — drag, drop, publish
Su Yun moved scheduling onto Slota: build a week's rota in minutes by dragging shifts onto a grid, reusing saved templates, or copying last week — then publish, and the whole team is notified automatically. No cutting over outlet by outlet; the same schedule every manager, the same screen.
- Up and running in ~10 minutes — add the team (email or CSV), build the schedule, and staff clock in.
- Live cross-outlet view — see every location on one grid and stop double-booking the same person across outlets.
- One shared source of truth — employees see their shifts in the app, swap and pick up shifts, and clock in one of four ways (web + Android).
- PDPA-aligned and built in Singapore.
Results & expected impact
Slota is launching with Su Yun on 20 September 2026, so the measured before-and-after numbers are being captured now. Two figures are tracked explicitly — with the basis for each stated so the claim stays honest:
| Metric | Status | Figure to use |
|---|---|---|
| Weekly rota-admin hours saved | To be measured | Slota's SG staffing model estimates multi-outlet operators reclaim ~70% of weekly rota admin (≈ 5.6 hr/wk off a typical 8-hr baseline) — modelled benchmark, not yet Su Yun's measured hours. Real Su Yun figures land ~4 weeks post-launch. |
| Roster error rate | To be defined & measured | No baseline exists and no metric definition is agreed yet. Candidates on file: payroll/timesheet discrepancies, double-booked shifts, and last-minute re-publishes. Slota's conflict guard is built to stop double-bookings before publish. |
Modelled benchmark: the ~70% / ~5.6 hr/wk figure is Slota's SG staffing model estimate, not Su Yun's measured outcome. Measured Su Yun figures will replace it ~4 weeks after the 20 September 2026 launch.
Bottom line (honest framing): the mechanism is shipped and verified — the workflow above is live product behaviour. The Su Yun proof is being gathered at launch and will be published here once measured. Contact us for a demo of the workflow today.
“The week's rota used to be copied between three spreadsheets and a WhatsApp group. Now it's one grid — drag, drop, publish, and everyone's notified. That's the part people feel first.”
See it in action — request your 90-second demo
No spreadsheet required. See a real roster built, published, and filled in under two minutes.
Request your demoThis opens your email app — the Slota team replies personally.