MARKET SHARE / RESTAURANT
People go out for lunch. Why don’t they come to you?
How we would approach preference and share in a local lunch market, starting with the choice people make each day.
PLEASE NOTEConceptual scenario for a restaurant in an office district. The location, audience, and situations are fictional. No client results are presented.
The situation we would examine
A restaurant is busy on some evenings but has available tables at lunch. Nearby are offices, cafeterias, supermarkets, and delivery services. The owner wants a neighborhood awareness campaign.
We assume the kitchen can support a lunch service and that there is a profitable offer to test. We need to understand what people choose during their work break and why the restaurant does or does not enter that choice.
How we would define the market
We would define the occasion: purchased weekday lunches for people working in a specified area. We would set the time window, geography, and inclusion of dining in, pickup, and delivery. Food brought from home can influence demand but does not automatically belong in the value of the purchased-lunch market.
Transaction share would compare the restaurant’s orders belonging to that market with all comparable orders in the same market and period. If we counted individual meals instead, we would report share of meals, using that unit for both the restaurant and the market total. Value share would use comparable spending. We would keep group orders, meals, and people distinct.
The restaurant’s data shows only its own activity. A denominator would require a compatible external source or appropriate research. A survey of the restaurant’s followers alone cannot represent the entire area.
We would also verify which of the restaurant’s own sales belong to the defined audience. Lunch receipts do not automatically identify where customers work. Missing information would require research or limit the market for which share can be reported.
What we would investigate
We would observe routes, available time, office attendance patterns, and alternatives used. We would speak with customers and people who choose other options, recruiting from the relevant area. We would ask about their last actual choice rather than only general preferences.
Inside the restaurant, we would check the menu, actual service time, availability, capacity by time slot, and order contribution. Online, we would examine how easily someone can find the current menu, full price, opening hours, and ordering or reservation instructions.
Working hypotheses
People may know the restaurant and still not consider it for lunch. It may seem suited only to evenings, take too much time, or offer too little information before someone leaves the office. The local audience may also prefer a different price level or type of food.
We would avoid treating all these situations as an awareness problem. Each changes the offer, message, and appropriate investment.
The proposed concept
We would build a lunch offer that can be understood and delivered consistently: dishes suited to capacity, a visible total price, and a simple path to choosing. A service-time promise would enter the message only after operations can support it, including busy periods.
| Observed need | Response to evaluate | Condition to verify |
|---|---|---|
| Short break | An easy-to-choose menu and an order prepared for pickup. | The kitchen can meet the communicated time window. |
| Lunch with coworkers | Options and arrangements for small groups. | The table and capacity are confirmed. |
| Predictable spending | Total price and included components explained. | The offer maintains the required contribution. |
| Daily routine | An updated menu and consistent communication. | Information matches actual availability. |
The campaign would connect the product with the occasion: lunch during the working day. We would use photography of actual portions, a simple page, and local communication. Partnerships with nearby offices would have clear terms and would not require collecting personal employee lists.
Same restaurant. Different lunch needs.
Change the occasion to see how the offer and operational checks change. These are proposals to test, not proven customer preferences.
Fictional data and situations.A local demonstration, without client results. Your choices do not send data, inquiries, or bookings.
Short break
Someone has limited time to choose and eat lunch.
A short menu, the full price, and clear service information before leaving the office.
What needs checking
Measure actual service times during busy periods before promising a specific duration. Track lunch orders and contribution; local share remains unknown without market data.
Read all variations
Short break
The occasion: Someone has limited time to choose and eat lunch.
An offer to test: A short menu, the full price, and clear service information before leaving the office.
Check: Measure actual service times during busy periods before promising a specific duration. Track lunch orders and contribution; local share remains unknown without market data.
Lunch with coworkers
The occasion: A small group wants compatible options and a table they can rely on.
An offer to test: Visible menu options and a simple way to ask about a table for the group.
Check: Confirm seating, menu availability, and kitchen capacity. A request is not a confirmed reservation.
Pickup
The occasion: Someone wants to collect lunch and return to work.
An offer to test: Current dishes, total price, pickup location, and an agreed collection window.
Check: Check preparation, packaging, and handoff capacity. Menu views indicate interest, not completed orders or market share.
What we would build
We would define the offer with the restaurant team, then produce messages, photography, a lunch page, and in-location materials. We would organize menu updates, the ordering journey, and how the team identifies campaign inquiries.
We could coordinate local media, content, partner communication, and reporting. The restaurant would remain responsible for price, ingredients, availability, and service promises. Repeat choice also depends on the experience delivered after the first visit.
How we would test and measure
We would compare similar days and time windows, accounting for holidays, weather, office attendance, and schedule changes. With sufficient volume, phased activation across office groups can provide a comparison, while allowing for audience overlap. A simple before-and-after comparison does not isolate the campaign’s effect.
| Indicator | Use |
|---|---|
| Lunch orders and contribution | Checks the commercial effect in the target time window. |
| New and returning customers | Shows recruitment and repeat behavior where measured legitimately and consistently. |
| Service time and errors | Checks whether the promise can support expansion. |
| Internal substitution | Checks whether the offer shifts existing orders or adds demand. |
| Estimated local share | Requires research or a source covering the defined market, with sample limitations reported. |
Map clicks, brand searches, and menu views would be interest signals. We would not report them as market share. If we cannot estimate the denominator, the result remains an evaluation of local growth and choice, with share unknown.
What could change the recommendation
If people visit once and do not return, we would examine the experience, taste, portion, and value for money. If the time window is already at capacity, organization or contribution per order may take priority. If the local market is too small, we would evaluate other occasions or areas the restaurant can serve.
At what time of day could you become a natural choice for people nearby?