Customers · Pilot Cohort 2026
Restaurants who run on NexDine.
A country pub in regional Victoria and a hospitality venue with three kitchens. The cohort is small by design.
Two venues, one pilot site each.
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.
Currently in service
Where the platform is in pilot today: 2 pilot venues, Victoria, 1 login
- Pilot
Ikigailand
Three-kitchen venue · Warrandyte, VIC
A three-kitchen venue in pilot with NexDine as its till, and its kitchen screen on the same login.
- Reservations
- POS
- Kitchen screen
- Pilot
Pig & Whistle Hotel
Country pub · Trentham East, VIC
A country pub in pilot on phone reception, the inbox and a management dashboard, with its own Square till left where it is.
- AI reception
- Unified inbox
- Bookings
- Management dashboard
- Next
Your venue, next
Story · Three-kitchen venue
One ticket from the till to the kitchen screen.
Ikigailand is in pilot with NexDine as its own point of sale, on one login. No Stripe account or card reader is connected to this venue yet. Its checklists and temperature records are not in use yet.
What this pilot has switched on
POS
NexDine is the till. The order, the payment and the kitchen screen share one ticket. Card and cash have both been keyed at the counter.
In pilot. Same shipped codebase as every other pilot. No bespoke fork.
Story · Country pub
The phone answered, the booking taken, the diary straight.
Pig & Whistle Hotel is in pilot on the phone, the inbox and a management dashboard, while the pub keeps running its Square till. Its own line answers and books, Microsoft 365 and SevenRooms are connected, and the kitchen records have not started yet.
What this pilot has switched on
AI phone reception
Answers, books, transfers, and writes messages back to one diary.
Unified inbox
Email threaded per guest, and tagged by the AI before the manager opens it.
Bookings
SevenRooms stays the diary, and its upcoming bookings show on the same dashboard. A booking taken on the phone lands in NexDine.
In pilot. Same shipped codebase as every other pilot. No bespoke fork.
Pilot cohort · by the numbers
Two pilot venues, one shipped platform.
Four numbers, each one you can check against the shipped code or ask the venues about. No future-tense, no marketing maths.
- Pilot venues
- 2
- Sensors to install
- 0
- Months an inspector pack covers
- 3
- Login that opens every screen
- 1
Three shapes of operator.
Same codebase, same login, scope-aware. What changes is the structure on top, not the platform underneath.
Built for the rhythm of a real service
Single venue
Neighbourhood spot
One manager, one chef, fifty covers. You want the phone answered and the books closed by midnight.
- AI reception
- Bookings
- POS
- Daily reconciliation
- Payroll
- HACCP
Multi-venue
Restaurant group · 2-10 venues
Same brand, multiple kitchens, one head office. You need consolidated reporting and per-venue autonomy.
- Consolidated P&L
- Per-venue rosters
- Group-level inventory
- Brand-wide menu sync
- Role-based access
Hospitality group
Multi-brand, multi-region
Several brands, several states, and a different food-safety record to produce in each one.
- Per-state HACCP
- Multi-tenant theming
- Centralised approvals
- Audit trail
- Data export
We're admitting a small cohort. Honest about the seam.
NexDine is in pilot at two venues. We are admitting a deliberately small group of operators in 2026: enough to onboard with care, not enough to dilute the work. If your kitchen still keeps its records on paper, this is the moment with the most leverage on the roadmap.
Programme · 2026 cohort
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.
- Direct access to the team building it, and your requests on the roadmap.
- Priority on the roadmap: integrations and features you need get prioritised.
- Help loading your menu, recipes and suppliers, and connecting the systems you keep.
- 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.
Pilot cohort 2026 · slots are limited
Become the next venue on NexDine.
If your kitchen still keeps its records on paper, we would rather hear about your service than send you a form.
Pilot cohort 2026, onboarding in 4-6 weeks, founder-led