Launch
Restaurant Concept Development in Dubai: What a Concept Has to Contain Before a Designer or a Chef Is Briefed
Concept development is not a mood board. The seven decisions a restaurant concept must settle — guest, occasion, price architecture, menu economics, room, channel mix and the number it has to hit — before design or menu work begins.
“Concept development” is one of the phrases people search for when they are about to spend real money on a restaurant, and it is one of the least defined services in the market. For some firms it means a name, a logo and a mood board. For some chefs it means a menu. For a design studio it means a room. Each of those is a piece of a concept, and each is commissioned too early if the concept itself has not been settled. This is what a restaurant concept has to contain before anyone is briefed to design or cook it, and why the order matters more in Dubai than almost anywhere. It sits beside the estate’s standing guide to restaurant concept development in Dubai; that piece covers the service, this one covers the brief.
A concept is a set of decisions, not a feeling
Strip the word of its glamour and a concept is seven decisions, made in writing and tested in numbers. Until they are made, every brief you issue — to a designer, a chef, a brand studio, a kitchen consultant — is a brief to guess.
1 · The guest. Not “everyone who likes good food”. Who, specifically, will sit in this room: the office crowd within walking distance at lunch, the families of a residential district on a Friday, the visitors who are already in the mall, the drivers who will never see the room because the concept lives on the aggregator apps. Each guest arrives at a different hour, spends a different amount, stays a different length of time and tolerates a different price. The guest decides most of what follows.
2 · The occasion. The same guest eats differently at a working lunch and a celebratory dinner. The occasion sets the dwell time, the number of courses, the beverage share and the day-of-week shape of the revenue. A concept built for two occasions that do not share a room is two concepts sharing a rent.
3 · The price architecture. Not a single average spend but the shape of it: the entry price that gets a guest to sit down, the anchor dishes that carry the margin, the ceiling that the guest and the district will bear. In Dubai the district sets that ceiling harder than the concept does, and a concept priced above its district is a concept that will be re-priced by its guests.
4 · The menu economics. Before a chef writes a dish, the concept has to say what the menu is allowed to cost: the food-cost band the format typically holds, the number of items the kitchen can execute at the quality the price implies, the share of the menu that carries margin against the share that carries the brand. The published operating bands — food, labour and the prime-cost ceiling they add up to — are the frame here; the menu engineering instrument is where a proposed menu is read against them before it is printed.
5 · The room. Seats, and therefore covers per service, and therefore the revenue the room can physically produce at the price architecture and the turn the occasion allows. The room is where concept meets rent: a room that cannot produce the revenue the rent requires is not a design problem, and no designer will solve it.
6 · The channel mix. Dine-in, delivery, takeaway, catering, events. Each channel carries its own margin — delivery carries the aggregator’s commission, which is a structural line, not a marketing cost — and the concept has to say what share of revenue it expects from each and whether the kitchen is being built for that mix. A dine-in concept that ends up half delivery has a kitchen and a margin designed for a different business.
7 · The number. The break-even, read against the rent the site actually asks. This is the decision that tests the other six. A concept that cannot show a plausible path to break-even at the site’s rent is not a bad concept; it is a concept for a different site, or a different rent, or a different room.
Why the order matters in Dubai
Three features of the Dubai market make sequencing the concept before the briefs unusually expensive to get wrong.
Rent is decided early and binds for years, so the room-versus-revenue test has to be run before the lease, not after the opening. Fit-out is capital-heavy and contractor-led, so a design brief issued before the seat count and the price architecture are settled produces a room that is redesigned once the numbers arrive — usually after the contract is signed. And the delivery channel is large enough that a concept which has not decided its channel mix builds the wrong kitchen.
In our experience across 45+ F&B concepts developed and launched, the concepts that opened cleanly were the ones whose seven decisions existed on paper before the first external brief. The concepts that struggled had briefed a designer with a feeling and a chef with a cuisine, and discovered the number last.
What “concept development” should deliver
If you commission concept development as a service — from GGB or anyone — this is what the deliverable should contain, and what to ask for if it does not.
- A written guest and occasion definition, specific enough to be wrong.
- A price architecture with an entry price, anchor dishes and a ceiling, read against the district.
- A menu economics brief: the food-cost band, the item count the kitchen can execute, the margin structure — the frame the chef designs inside, not the menu itself.
- A room brief: seats, turns, covers per service, and the revenue that implies at the price architecture.
- A channel mix with a margin per channel and the kitchen implications.
- A break-even read against the site’s actual rent, with the sensitivity of the model to landing short.
- Only then: the brand, name and design direction, briefed from the six decisions above.
A deliverable that arrives as a mood board and a name has skipped the first six and delivered the seventh. It will look finished and it will be the most expensive document in the project.
Where this sits in a development
Inside a GGB development mandate, concept, brand and menu development are one workstream among the seven the mandate runs as development principal, and the concept is tested against the Feasibility & Investment Case before any design or menu work is briefed. That is not a process preference; it is the order in which the money is at risk. The study decides whether the project should exist; the concept decides what it is; the briefs follow. Reverse the order and the briefs decide the concept, and the study is written after the lease to justify it.
Start with the number
If you are at the beginning, do the seventh decision first. Take the rent the site asks, the seats the room allows, the price the district will bear, and read the break-even. If it holds, the other six decisions have a frame. If it does not, you have saved the design fee, the menu fee and the lease — which is the cheapest concept development there is.
GGB Consulting · the register Launch · 15 Sept 2026 · 6 min
P. Dayaparan
Founder of GGB Consulting — 28+ years in hospitality leadership, PMP, and a branded-resort background. He writes from the P&L, not the brochure. More about Dayaparan →