Define the first flow to prove
A few QR tables and a full cutover across dine-in, takeout, payment, invoice, and kitchen require very different preparation.
Suggested sequence
- Choose one bounded flow and success condition
- Prepare menu, tables, roles, and merchant setup
- Test orders, cancellations, refunds, and exceptions
- Pilot in a low-risk window before expanding
If someone promises a fixed go-live date before discovery, ask them to define scope and dependencies first.