Dashboard first · Data when you are ready

Start with your restaurant—not a spreadsheet.

Create access with a minimal restaurant profile and operating priorities. Open the dashboard immediately, or add one completed sales period to unlock deeper, data-supported MunchMind guidance from day one.

Fast path · 2–3 minutes

Enter the dashboard with no file upload.

Set the restaurant profile and priorities, then explore the product. Sales, menu, and labor areas remain clearly marked as waiting for data until reports are added.

Guided data path · Optional

Build a stronger first baseline.

Add a completed POS period, menu export, and matching labor total now—or complete any of them later from the dashboard setup checklist.

Step 1 of 7Account & restaurant

Account & restaurant

Start with the first location.

Only the essentials are required for dashboard access. Additional locations and operating details can be added after entry.

Used as provisional context until actual sales are added.

Your priorities

What would make the next 30 days valuable?

Choose one or more. MunchMind will use these priorities to shape the first questions and recommendations.

Choose your setup

How do you want to enter Munch?

Both paths open the same dashboard. The difference is how much restaurant-specific context is available on the first visit.

Your place is saved. If you leave the guided path, return from the dashboard and continue where you stopped.

Optional sales input

Add one completed POS period.

A recent weekly or monthly export is enough. No historical bulk import or live POS connection is required.

  • Detect: date, net sales, item, category, quantity, check, and server fields when available.
  • Confirm: reporting period, net sales, transactions, average check, and category coverage.
  • Repeat: establish the operator's preferred weekly upload cadence after the first baseline.

Optional menu input

Show Munch what you sell—and what the costs mean.

A menu export can add item, category, price, and actual food-cost coverage. Where actual item costs are missing, operators can confirm category-level percentages later.

Actual costItem-level cost wins

When a reliable item cost is present, Munch uses it instead of an estimate.

Estimated costCategory basis is visible

Operator-confirmed category percentages remain labeled until actual cost coverage improves.

CoverageNo zero-cost fallback

Unresolved categories stay incomplete rather than producing misleading margins.

Optional team & labor input

Match labor to the same operating period.

Add the core managers and total gross labor for the sales period. Munch checks period alignment and shows the resulting labor percentage before using it in recommendations.

Review before intelligence. The live flow summarizes the sales, menu, and labor basis, parsing confidence, and exceptions for operator confirmation.

Dashboard handoff

Your dashboard does not wait for a spreadsheet.

Enter now with a guided setup checklist. Munch only makes data-backed claims where the required inputs are present; everything else stays clearly labeled for later completion.

Restaurant profileReady
Sales basisAdd later
Menu cost basisAdd later
Labor basisAdd later
Choose the first question MunchMind should prepare for.
MunchMind will prepare this question now. A data-supported answer appears after matching sales and labor information is available.
  • Dashboard access begins immediately, even when every upload is skipped.
  • Missing inputs appear as setup actions—not zero values or invented conclusions.
  • Subscription options first appear inside Munch on Day 25.

Dashboard handoff ready

Your restaurant can enter without an upload.

This website demonstrates the intended onboarding decision and handoff. The production account service will create the verified user, preserve setup progress, and open the authenticated Munch dashboard. No information entered in this prototype is transmitted or stored.

The exact proof journey

Thirty days that begin before the first upload.

Operators can learn the dashboard immediately, add data at their own pace, and see subscription options only after there has been time to experience meaningful value.

Day 1

Access

Create the profile, choose priorities, and open the dashboard—with or without a spreadsheet.

Days 2–7

First value

Explore the workflow, then optionally add one completed period for the first restaurant-specific baseline.

Days 8–24

Evidence

Return for comparisons, scheduling, inventory context, and the next MunchMind questions.

Day 25

Price reveal

Show the applicable subscription options inside Munch, tied to the restaurant's account and experience.

Days 26–30

Decision

Use in-product reminders and optional human support to choose the continuation path.