At a glance

  • Start with one bounded package when it fits
  • A platform plan shares context, not record ownership
  • Know the commercial roster

Start with one bounded package when it fits

A focused package can address one defined operating need while including its necessary supporting apps. Confirm identity, restaurant/location scope, data ownership, dependencies, providers, training, recovery, and written terms for every included workflow.

A platform plan shares context, not record ownership

Shared identity and selected restaurant/location context can reduce repeated setup. Schedule, HETable, POS, Ops, Finance, Label, Marketing, and Jobs still keep their defined records and authority; synchronization and cross-app reads remain explicit connections.

Know the commercial roster

The connected platform covers eight working applications grouped into Schedule, POS, HETable, and Label packages. Jobs, Finance, Marketing, and Ops are included where their source workflow makes them useful; Master AI remains a separately licensed add-on.

Adding an app is a bounded implementation step

Each added application needs accepted entitlement, data and migration scope, restaurant/location mapping, provider configuration, role access, training, synchronization, recovery, and support ownership. A platform purchase does not prove that every workflow is live.

Choose with restaurant evidence

Compare the specific workflow gap, required locations, current systems, hardware, providers, rollout risk, and written total scope. Start where the restaurant can verify value, then expand only after the next connection and operating owner are clear.