An empty dashboard asks a new restaurant owner to understand the software before the software has understood the restaurant. Plenty takes the opposite approach.
Begin with what already exists
The restaurant website can reveal its platform, menu structure, pages, public ordering path, and useful connection clues. A read-only review reduces questions and creates a more relevant starting point.
Seed setup, not fake activity
A useful workspace contains a checklist, connection state, menu work, restaurant details, and a private-test path. It should not invent orders, customers, revenue, or integration health.
The route changes the work
A WordPress connection, hosted order page, Plenty CMS site, and custom build need different setup tasks. They should still lead into the same menu, customer, order, and Partner foundations.