Mobile catering
The van is on the road. The office should not need you in it.
What it does
Three things a mobile operation gets wrong on paper
Everything below ships today. Nothing here is a roadmap item.
Where you can be, and when
One resolver decides what a day is and every surface reads the same answer — your public widget, your booking funnel and your own board. A private booking shows as a shape and a time, never who and never where.
Bump in, service, bump out
A job is not its service window. The calendar carries the bump-in and bump-out either side of it, so a 15:00 start that needs the van on site at 13:00 stops you double-booking the afternoon.
What the run actually cost
Crew hours, travel and fuel against the takings, with food cost per head from your own supplier prices. Where a cost cannot be worked out the event names the missing input rather than calling it zero.
The second one, moving
One person's run, on their own phone
Pick a crew member and send them their part of the day. It arrives as a message — no app, no login, and no seat on your bill.
- 07:30Load out — van packed, esky in
- 10:00On site, set up
- 12:00Service
- 15:30Pack down
Message · now
Saturday 26 September
No app. No login. No seat on the bill.
Start
Free to start, and nothing is feature-locked
Every feature is on every plan. The plans differ on volume, not on capability.