What to expect in a Luminix demo

A Luminix demo is not a generic product tour. It is a working session mapped to your locations, modules, and current back-of-house stack. This guide explains what happens before, during, and after the call so your team can evaluate the platform efficiently.

Why we start with your operation

Restaurant groups evaluate software differently. A three-location independent cares about GM adoption and checklist discipline. A ten-location group cares about consolidated exceptions, HR roll-up, and integration with Toast or QuickBooks. We ask about location count, current tools, pain points, and module priorities before the session so we do not waste time on areas that are not relevant.

If you have not submitted a demo request yet, include:

• Number of locations and how they are organized (single brand vs. multiple concepts)
• Modules you want to prioritize (vendors & AP, scheduling, HR, inventory, food safety, AI insights, etc.)
• Systems you use today (POS, payroll, accounting)
• Timeline — evaluating now vs. planning a Q3 rollout

Who should join

The best demos include the people who will own adoption:

| Role | Why they should attend | |------|------------------------| | Owner / operating partner | Validates multi-location visibility, bundles, and rollout scope | | GM or district manager | Validates daily ops, scheduling, and floor workflows | | HR or people admin | Validates hiring, certifications, and document workflows | | Finance / AP admin | Validates vendor invoices, PO match, and spend analytics workflows | | IT or ops lead | Validates integrations, tenant setup, and security questions |

You do not need every stakeholder on the first call. We can schedule follow-ups for deep dives into integrations or specific modules.

What we show during the demo

We demo from a tenant with realistic restaurant data — schedules with conflicts, vendor invoices with PO variances, inventory exceptions, temp logs with corrective actions, and HR records with certification expiry. You will not see an empty shell.

Typical flow:

1. Organization and access model

We start with how Luminix structures organizations, locations, and role-based access. Owners see consolidated exceptions; GMs see their store. This is foundational — everything else references the same location, people, and vendor model.

2. Vendors & AP (if in scope)

Vendor directory, OCR invoice ingest, PO match wizard, contracts, and spend analytics — connected to inventory purchase orders so variances surface before approval.

3. Daily execution and scheduling

Depending on your priorities, we walk through opening checklists, shift handoffs, and schedule publish workflows with availability and labor rules. This is usually where GMs validate whether the platform matches how they run shifts today.

4. People and HR (if in scope)

Hiring pipeline, onboarding tasks, certification tracking, and how HR records connect to scheduling — without duplicate data entry across systems.

5. Operations pillar

Inventory counts, par levels, transfers, vendor catalog mapping, and exception visibility. If payroll export is in scope, we overview tip pools and export workflows at a high level.

6. Compliance and maintenance

Temperature logs, corrective actions, work orders, and PM schedules — focused on audit-ready records that persist between shifts.

7. AI insights (Complete tier)

Cross-module patterns, anomaly detection, and actionable recommendations — scoped honestly to what is live in your bundle.

8. Integrations and provisioning

We discuss Toast, QuickBooks, email, and webhook integrations relevant to your bundle. We outline provisioning steps: tenant setup, baseline data import, training, and go-live timeline.

See the platform overview and published pricing for how tiers and rollout phases fit together.

What we do not do on the demo call

• Skip your scope. Every group is priced by locations, tier, and rollout complexity — we walk through published tiers and tailor a quote on the call.
• Promise features outside your tier. We show what is included in Core, Operations, or Complete — all eleven modules scoped honestly.
• Replace your POS. Luminix is back-of-house. Your POS stays; we integrate where configured.

After the demo

If there is a fit, we send a summary covering:

• Recommended tier and module scope
• Provisioning and integration checklist
• Suggested rollout timeline (often three weeks — see our go-live checklist)
• Next steps for contract and tenant provisioning

If timing is not right, we stay available for follow-up questions. No pressure sequences.

Questions to bring

Operators who get the most from demos arrive with specific questions:

• How does vendor invoice PO matching work for our procurement flow?
• How does multi-location exception roll-up work for our role structure?
• What does provisioning look like for our HR and certification data?
• How do scheduling conflicts and labor rules behave during a busy week?
• What is the integration path for Toast / QuickBooks in our environment?
• What does support look like after go-live?

Our FAQ covers common evaluation questions. For a structured buyer checklist, see questions to ask in your demo.

Ready to schedule?

Book a demo and tell us about your locations and modules. We respond within one business day.