A modern restaurant group running reservations, POS, accounting, comms, payroll, and compliance on a single screen.
Restaurants who run onNexDine.
From a Melbourne neighbourhood pub to a multi-venue hospitality group — two operators chose one platform over a stack of eight tabs. The cohort is small by design.
Where the platform lives in service today
Two venues. One platform. Same data layer.
Both pilots run on the same shipped codebase, the same integrations, and the same daily release train. No bespoke fork, no "enterprise build" hidden behind a feature flag.
A neighbourhood pub running AI phone reception, unified inbox, reservations, prep & ordering, and daily reconciliation on one login.
One screen instead of eight tabs.
Ikigailand runs the full NexDine surface — front of house, back of house, the books, comms, people, and compliance — on the same login. The manager opens one screen and sees tonight's floor, prep, payroll, and the inbox reconciling to the same numbers.
Reservations
Native booking engine with SevenRooms sync. Bookings, walk-ins, and the floor plan live on one screen.
POS
Square via direct integration plus a Doshii bridge for the broader POS estate. Orders, payments, and the KDS share one ticket.
Books
Daily Xero sync. Stripe payouts, cash totals, and POS sales reconcile against the GL before service opens.
Comms
Gmail and Microsoft 365 in one inbox. The AI chief-of-staff tags, drafts, and surfaces what actually needs a human reply.
People
Hiring, onboarding, certifications, rostering, and STP payroll on one record per staff member.
Compliance
HACCP, temperature, RSA, and cleaning logs — live, dated, and exportable for any inspection.
One platform answered the phone, took the booking, closed the till.
Pig & Whistle runs the modules a small-team venue actually needs every shift — the phone gets answered, the inbox triaged, the diary stays accurate, the kitchen prep matches forecast, and the till reconciles before lock-up.
AI phone reception
Answers, books, transfers, and writes messages back to one diary. Handles overflow when the kitchen is on the line.
Unified inbox
Email and SMS threaded per guest. Drafts and tags from the AI chief-of-staff before the manager opens it.
Bookings
Native engine on their own domain. No paper diary, no double-books, no lost names.
Prep & ordering
Forecast-driven prep sheets, supplier orders, and three-way invoice match against goods received.
Daily reconciliation
Stripe payouts, cash count, and POS totals matched automatically into Xero before lock-up.
Daily manager brief
Covers, weather, variance, and what to chase — summarised every morning before service opens.
Real venues, real shifts, same shipped platform.
Everything below is what's actually in production for the pilot cohort today. No future-tense, no marketing maths.
Three shapes of operator. One platform.
Same codebase, same login, scope-aware. What changes is the structure on top — not the platform underneath.
Neighbourhood spot
One manager, one chef, fifty covers. You want the phone answered and the books closed by midnight.
Restaurant group · 2–10 venues
Same brand, multiple kitchens, one head office. You need consolidated reporting and per-venue autonomy.
Multi-brand, multi-region
Several brands, several states, jurisdiction-aware compliance. Tired of paying eight vendors per venue.
Programme · 2026 cohort
We're admitting a small cohort. Honest about the seam.
NexDine is live in two venues. We're admitting a deliberately small group of operators in 2026 — enough to onboard with care, not enough to dilute the work. If you've been waiting for one platform instead of a stack of subscriptions, this is the moment with the most leverage on the roadmap.
What you get as a pilot
- Founder-led onboarding — on-site if you're in AU, end-to-end either way.
- Direct access to the founders — a shared channel, not a ticket queue.
- Locked-in pricing — today's pricing stays for the life of the platform.
- Priority on the roadmap — integrations and features you need get prioritised.
- Migration from your current stack — SevenRooms, Square, Xero, roster, inbox.
- A dedicated engineer on the success seat — not a CS rep.
What we ask in return
- Candour about the edges — tell us what's broken, in detail.
- A thirty-minute weekly call for the first ninety days.
- Permission to write about your story — with your sign-off on every word.
- Willingness to co-design — we ship together, not at you.
- A trial of new modules before they go to general release.
- An introduction to one operator who'd benefit from seeing it in service.
Become the next venue on NexDine.
If you're tired of running a restaurant from eight tabs, we'd rather hear about your service than send you a form.
Pilot cohort 2026 · onboarding in 4–6 weeks · founder-led