Start with the guest. Write the menu last.
Moxpitality develops restaurant and food and beverage concepts. Guest, space, peak count, and crew first. The menu waits, because it has to fit all four.
What gets decided before the menu
The guest
When they arrive, how long they stay, standing or sitting. That decides format before anyone talks flavor.
The space
Door to seat. Where a hood can go, how much power there is, how far a plate travels to the table.
The peak hour
Hold times, how many hands touch the dish, what can be prepped the day before. Average covers lie. Peak does not.
The crew you will actually have
What they can run on a Saturday, not what worked at a tasting for eight.
Before the next tasting
- Who is the guest, and how long do they have?
- What happens in this space at its busiest hour?
- What is the peak guest count, and which dishes hold through it?
- What can the kitchen support: venting, power, distance to the table?
- What can this crew run?
Questions we hear
Where should restaurant concept development start?
Guest and space, then volume and crew. The menu comes last.
Why do dishes come off a new menu in the first month?
The menu was locked before anyone knew who was ordering it, where they were standing, how many showed up at once, and who was cooking that night.
How does Moxpitality use AI in concept development?
To stress-test volume, labor, and the room. Chefs keep the recipes.
Have a concept on the table?
Guest, space, opening date. We will say what has to be decided before the menu.