An operating system
enough to disappear
behind service.

DineDirector is a single, unhurried surface for the guest table, the floor, the kitchen, the menu, and the manager. Keep the physical menu, give staff faster tools, and let AI stay quietly behind approval gates. Launch from zero, or pilot five tables beside Petpooja, Rista, POSist, AirMenus, MobiGuest, UrbanPiper, WhatsApp, Excel, and printer workflows.

MenuTableFloorKitchenManager
Service pulse
Table 12 command acceptedIdempotency key verifiedKOT FIFO group: tandoorKDS update sentPOS adapter flagged, order preserved
Service pulse

One order moves through the room. The room stays calm.

The hot path is designed like a service choreography: table context, staff speed, kitchen clarity, manager awareness. AI stays outside the rush. The order keeps moving.

01
Table 12 · seated

A table opens without asking the guest to become a user.

The host seats the party, NFC or a table link is ready, the physical menu stays on the table, and staff can still own the moment.

Guest-safe entry
02
Staff pad · 4 items composed

Staff build the order faster than a legacy POS screen can wake up.

Search, repeat rounds, modifier prompts, service notes, hold/fire, and bill requests stay thumb-close for phones and tablets.

Rush-hour ordering
03
KOT 1840 · tandoor

Kitchen gets one clean command, never a duplicate ticket storm.

Every order command is idempotent, routed by station, and replayable. Print bridge, KDS, and POS adapters can fail without losing the room.

Auditable hot path
04
Bandra · POS adapter retry · 1 action

Managers see the exceptions first, not a wall of charts.

Delayed tables, adapter failures, low-stock changes, approvals, and service recovery actions rise to the top with context and audit trail.

Action queue
§ 01
Manifesto

Eight principles, written on the wall above the pass.

DineDirector is opinionated software, shaped by rushes, handoffs, kitchen noise, four-top complications, and a refusal to compromise the room for the database.

No 01

The system disappears behind service.

If a guest notices the software, we failed. The right tools become an extension of the floor, not another object on the table.

No 02

Every surface speaks one role's language.

The guest sees a menu, not a CMS. The kitchen sees fires, not records. The manager sees actions, not dashboard clutter.

No 03

Data only matters when it leads somewhere.

Charts that do not change a decision are noise. Every number on a manager surface should have a verb attached to it.

No 04

AI suggests. The house decides.

Models draft menus, flag delays, and prepare recovery ideas. They never speak over staff, never autopilot service, and never block live ordering.

No 05

Every order is auditable.

Idempotency keys, event logs, KOT queues, retries, and replayable table sessions make the hot path boring in the best way.

No 06

Legacy systems are respected.

Mirror, Sidecar, Bridge, and Replacement modes let a five-table pilot run without disturbing the current POS or printer flow.

No 07

India-first infrastructure.

Restaurant data stays in India regions by default, with Mumbai primary, Hyderabad recovery, tenant isolation, and least-privilege access.

No 08

Progressive power.

New restaurants can launch from zero. Existing restaurants can modernize one section at a time. Both get one calm operating system.

§ 02
Adoption modes

No rip-and-replace. Start with the section that can prove it.

DineDirector can sit beside an existing POS, printer, spreadsheet, or WhatsApp-heavy workflow until the restaurant is ready to move more of the operation.

01

Mirror

Read the current menu and operating signals without writing into the old POS.

02

Sidecar

Run DineDirector for guest and staff flow while the existing system remains billing source.

03

Bridge

Let DineDirector send clean orders into the POS, printer, or KOT adapter.

04

Replacement

Move the house fully when the pilot has earned trust on the floor.

§ 03
Product plates

Eight plates from the kitchen of DineDirector.

A walk through the public menu, staff floor, kitchen pass, manager command center, and Menu Studio. Every surface is designed to feel calm at speed.

House style
Google Sans FlexAa
No 01Director tokens, type, controls, and table languageDesign system
Table 12Ask waiter
TonightHouse Menu

Physical menu supported. Browse quietly.

Browse menuCall staff
No 02Guest menu cover with physical-menu mannersGuest
MenuCart 3
Small platesGrillDrinks
Charred broccoliVeg · 9 min
INR 420
Malai prawnsShellfish · 14 min
INR 780
House lime sodaVeg · 9 min
INR 240
Ask waiterBill
No 03Fast browse, dietary marks, and calm item hierarchyGuest
Modifier prompt

Malai prawns

Regular spiceNo corianderExtra lime +80Allergen: shellfish
Add to table
No 04Modifier sheet with price clarity and allergen warningsGuest
Floor · Section A24 covers
T1T2T3T4T5T6T7T8
3 staff calls2 KOT ready1 bill request
No 05Staff floor map for rush-hour ownershipStaff
KitchenOS · TandoorLive
KOT 1840T122 Malai prawns08:12
KOT 1841T051 Paneer tikka04:28
KOT 1842T033 Butter naan02:05
No 06Kitchen tickets readable from the passKitchenOS
Action-first
Command centerExceptions
MRRINR 18.4LActive clients42Order health99.97%AI spendcapped
POS adapter retry required · Outlet Bandra
No 07Manager command center with exceptions firstServiceOS
Human approves
Menu StudioReview
PDF import confidence87%
Price needs human confirmationAllergen detected: peanutImage variants waiting approval
No 08Menu Studio with import review and approval queuesAI approval
§ 04
Operating surfaces

Five surfaces. One product. One house.

Each role gets a surface that speaks only its language. The guest sees a menu, the kitchen sees fires, staff see the floor, managers see the next action, and owners see the house.

For the guest

A digital menu that does not make the table feel digital.

Guests browse without login, pressure, or app download. NFC, table links, host links, short codes, and QR fallback all open the same fast static menu snapshot.

  • 01Browse before ordering, with Ask waiter always visibleGuest-safe
  • 02Allergens, dietary tags, modifiers, split bill, and feedbackComplete
  • 03Physical menu, staff-assisted ordering, and digital ordering coexistHospitality
MenuCart 3
Small platesGrillDrinks
Charred broccoliVeg · 9 min
INR 420
Malai prawnsShellfish · 14 min
INR 780
House lime sodaVeg · 9 min
INR 240
Ask waiterBill
For the floor

One-hand staff ordering built for the 8:30 rush.

The staff PWA starts from the floor map, not a form. Table state, repeat drinks, hold/fire, modifier prompts, and manager overrides live inside a thumb-friendly flow.

  • 01Offline drafts and queued order commandsRecoverable
  • 02Table ownership, service requests, and waiting timersLive
  • 03Voice capture for rough orders, never in the hot pathAssistive
Floor · Section A24 covers
T1T2T3T4T5T6T7T8
3 staff calls2 KOT ready1 bill request
For the kitchen

KOT and KDS without duplicate tickets or noisy theatrics.

Station queues use FIFO message groups, idempotency checks, and visible reconnect states. The kitchen sees the fire, the modifier, the timer, and the next action.

  • 01Item-level done, remake, refire, hold, and sold-outPrecise
  • 02Print bridge support for thermal workflowsLegacy-ready
  • 03Delay alerts and station performance without clutterReadable
KitchenOS · TandoorLive
KOT 1840T122 Malai prawns08:12
KOT 1841T051 Paneer tikka04:28
KOT 1842T033 Butter naan02:05
For managers and owners

Exceptions first. Charts when they change a decision.

The owner view tracks clients, MRR, features, usage, health, and tenant controls. The restaurant view tracks floor health, revenue, menu performance, and recovery actions.

  • 01RBAC, outlet scoping, approvals, audit logsSecure
  • 02Menu import confidence and AI image approvalsGoverned
  • 03Mirror, Sidecar, Bridge, and Replacement adoption pathsFlexible
Command centerExceptions
MRRINR 18.4LActive clients42Order health99.97%AI spendcapped
POS adapter retry required · Outlet Bandra
Backend promise

The hot order path stays boring.

Validate command, attach tenant and outlet scope, store the event, publish to EventBridge, queue KOT with FIFO grouping, update KDS, persist canonical state, and send analytics async. AI is never in that path.

0guest logins required
4legacy adoption modes
5tables enough for a pilot
700msbackend order accept p95 target
Software should not make a restaurant feel managed by software.

The system is allowed to be powerful. It is not allowed to become the loudest thing in the room.

§ 05
Pricing

Choose how much of your restaurant DineDirector should run.

Start with the menu. Add the table. Run the floor. Operate the house. Scale the group.

MenuTableFloorHouseGroup
MenuModernize the menu

DineDirector Menu

Menus that manage themselves.

₹1,999/ outlet / month
₹19,999 / year

For restaurants with PDF menus, printed-menu chaos, QR-menu tools, AirMenus-style pages, or weekly price changes.

Includes
  • AI menu import from PDF or photo
  • Digital menu plus physical menu print export
  • Menu version history and sold-out toggle
  • AI item descriptions and menu cleanup
  • NFC/TableLink support with QR fallback
  • Basic analytics and 50 AI image/content credits

Start with your menu. DineDirector turns it into a living system: digital, printable, editable, beautiful, and AI-assisted.

Discuss Menu
FloorControl the dining room

DineDirector Floor

Live control for serious service.

₹9,999/ outlet / month
₹99,999 / year

For premium restaurants, high-volume cafés, breweries, pubs, and operators where service quality matters.

Includes
  • Everything in Table
  • Manager command center and AI service recovery
  • Advanced analytics and menu engineering
  • Staff upsell prompts and voice order capture
  • Scheduled menus, multi-menu support, and advanced permissions
  • Custom branded guest menu theme, 400 AI credits, priority support

Floor shows managers what is happening across the dining room before guests complain, before orders get delayed, and before bad service becomes a review.

Discuss Floor
HouseOperate everything

DineDirector House

One operating system for the restaurant.

₹14,999/ outlet / month
₹1,49,999 / year

For new restaurants and existing restaurants ready to replace the POS + QR + WhatsApp + Excel + dashboard stack.

Includes
  • Everything in Floor
  • Reservation/waitlist, CRM, consented guest profiles, and campaigns
  • Loyalty, inventory controls, recipe costing, vendors, and waste log
  • Advanced RevenueOS, multi-device KDS, and payment integration
  • Advanced POS bridge where available and monthly performance review
  • 1,000 AI image/content credits

Instead of POS, QR menu, WhatsApp, Excel, agency work, and random dashboards, run the restaurant from one modern system.

Discuss House
GroupScale the brand

DineDirector Group

Multi-outlet control without multi-outlet chaos.

Custommulti-outlet pricing

For chains, hotels, restaurant groups, cafés with multiple branches, and cloud or hybrid brands.

Includes
  • Central menu governance and HQ approvals
  • Multi-outlet analytics, outlet benchmarking, and custom reporting
  • Centralized AI style guide and group-level CRM
  • Advanced integrations, SLA, and dedicated success manager
  • Role-based outlet access and audit trail
  • Suggested: ₹25k-₹35k base plus per-outlet pricing by group size

One brand, many outlets, one source of truth.

Discuss Group
GST, payment gateway fees, special hardware, and custom integrations are billed separately when applicable. Setup can be waived for selected early Bangalore pilot restaurants.
DineDirector Setup

For existing restaurants.

Setup stays separate from the monthly plan so the subscription names stay clean.

Menu Setup₹4,999
Table Setup₹9,999
Floor Setup₹14,999
House Setup₹24,999
DineDirector Launch

For new restaurants.

Menu setup, AI descriptions, images, table map, staff roles, KOT/KDS, NFC/TableLink, print-ready menu, launch creatives, and staff training.

Launch Essential₹24,999
Launch Full₹49,999
Launch Signature₹99,999+
DineDirector Bridge

For restaurants already running legacy workflows.

We do not rip out your current system. We bridge it, improve the experience, and let you migrate only when ready.

MirrorImport and observe current setup. No changes.
SidecarRun DineDirector on five tables or one section.
BridgeConnect DineDirector to current POS/KOT where possible.
ReplaceMove full operations to DineDirector House.
DineDirector by neuralway.ai

Built for hospitality. Built in India. Built to disappear.

For the rooms where dinner happens, and the people who keep them warm. Keep the room human; let the operating system carry the heavy work.