# Planning an Expansion **Situation C** *** ## Why expansion breaks restaurants Expansion is the most dangerous moment in a restaurant's life. Not because growth is bad, but because the things that made a single location successful are often the things that cannot be replicated. The owner who greets regulars by name. The chef who adjusts every dish before it leaves the pass. The manager who knows which server works best on a Saturday night. These are the reasons the first location works, and none of them transfer to a second location by default. At the same time, the things that did not matter at one location suddenly matter at two. Consistency across outlets. Supply chain at double the volume. Management layers that did not exist before. A brand identity that has to work without the founder in the room. Expansion is not doing what you are already doing, again. It is building a system that can do what you do, without you. Restaurants that treat expansion as a copy-paste exercise — same menu, same layout, similar location, hope for the best — are the ones that struggle. The ones that succeed are the ones that use data and customer insight to make the decision, and then design the new outlet around what the data tells them rather than what they assume. *** ## Use your data to choose a location If you have been running delivery, you already have location intelligence that most restaurants ignore: actual customer addresses. **Delivery order data is your most honest demand map.** Every delivery order comes with an address. Plot them and you can see exactly where demand for your food exists geographically. High order volume from a specific neighbourhood means there are people there who already like your food but cannot dine in easily. A physical presence in that area could convert delivery customers into dine-in regulars — a higher-margin, higher-frequency relationship. Clusters of delivery orders in an area far from your current location are a particularly strong signal. These are customers who like you enough to order despite the distance, longer wait times, and potentially higher delivery fees. A second outlet closer to them removes those barriers and likely increases their frequency. **What delivery data can tell you:** **Demand density.** Which postal codes or neighbourhoods generate the most orders? Where are the hot spots? A heat map of your delivery orders is a readymade shortlist of expansion candidates. **Time-of-day patterns by area.** Do certain neighbourhoods order more at lunch (office districts) versus dinner (residential areas)? This tells you not just where to open, but what daypart the new outlet should be designed around. **Average order value by area.** Are customers in one neighbourhood consistently ordering more? This can signal higher willingness to spend, which affects your format and pricing decisions for the new location. **Frequency by area.** Are customers in a specific area ordering repeatedly, or is it mostly one-time orders? High repeat delivery from an area means established demand. One-time orders might mean curiosity without loyalty — a weaker signal for expansion. **What you will not have (and how to compensate):** Delivery data only covers customers who order delivery. Your dine-in customers, reservation customers, and walk-in customers do not typically share their address. So delivery data gives you a partial picture — it shows you where digital demand exists, but it does not show you where your full customer base lives and works. To fill the gap, you can use your enrolment programme to ask a simple question: what neighbourhood or area do you live in? Not a full address — just a neighbourhood name or postal code prefix. Not every customer will answer, but enough will to give you a directional picture. Combined with delivery data, you get a much richer view of where your customers are concentrated. None of this replaces the traditional location assessment — foot traffic, rental costs, competition, accessibility. But it adds a layer of demand intelligence that most restaurants do not have. You are not guessing where your next customers might be. You are seeing where they already are. *** ## Right-sizing the new outlet Not every outlet needs to be a copy of the first. In fact, it probably should not be. Your first location was designed around a set of assumptions — about the customer, the occasion, the channel mix, the daypart spread. Some of those assumptions turned out to be right. Others did not. And the new location will have its own context that changes the equation. **Start with the local ICP.** Who is the customer at this specific location? A CBD outlet serves office workers at lunch — high volume, fast turnover, weekday-heavy. A suburban outlet serves families and residents — evenings and weekends, larger parties, more leisurely pace. Same brand, different customer, different design requirements. **Match the format to the occasion.** If the new location is primarily a lunch play, you may not need a full dinner setup — a smaller footprint with fast counter service might be more appropriate than a large dining room. If the location is in a food court or hawker centre, the format is entirely different from a standalone restaurant. Let the occasion dictate the format, not the other way around. **Think about channel mix from the start.** Will this location be primarily dine-in, or will delivery and takeaway be significant? If you expect a high off-premise share, the kitchen design, packaging setup, and staffing model should reflect that from day one. Retrofitting a dine-in-focused outlet for delivery later is more expensive and disruptive than building it in from the start. **Capacity planning.** Do not size the outlet for your peak ambition. Size it for your realistic year-one demand, with the flexibility to scale. A too-large outlet with empty tables feels dead and costs more to operate. A slightly constrained outlet that fills up feels alive and creates urgency. You can always expand capacity later if demand justifies it. *** ## Replicate vs. adapt This is the central strategic question of expansion: how much do you keep the same, and how much do you change? **What to keep the same:** **Brand identity.** The name, the visual identity, the tone of voice, the feeling of walking in. A customer who knows your first location should recognise the second immediately. Brand consistency is what turns multiple outlets into a network rather than a collection of unrelated restaurants. **Signature dishes.** Your signatures are your reputation. They are the dishes people recommend, the dishes that drive word of mouth, the dishes that anchor your identity. These should be identical across outlets — same recipe, same quality, same presentation. If a customer orders your signature at the second location and it is not as good, you have damaged the brand at both locations. **Service standards.** The experience should feel consistent even if the format differs. How customers are greeted, how quickly they are served, how issues are handled. These standards need to be documented and trained, because you will not be in every room. **What to adapt:** **The menu.** The core and signatures stay. But the supporting menu can and should adapt to the local context. A CBD outlet might have a stronger lunch set menu. A suburban outlet might have more sharing plates for family dining. A food court outlet might have a streamlined menu focused on speed. Adaptation is not inconsistency — it is relevance. **Daypart emphasis.** Your first location might be a dinner destination. The new one might have stronger lunch potential. Design the operating hours and staffing around the local demand pattern rather than copying the first location's schedule. **Channel priorities.** If the new location is in an area with high delivery demand, make that channel a first-class priority from opening, not an afterthought. If it is in a walk-in-heavy area, invest in the dine-in experience and capture infrastructure rather than delivery logistics. **Pricing.** Rental costs, local competition, and customer price sensitivity may differ. A modest price adjustment — up or down — to match the local context is better than forcing the same price point into a market where it does not fit. *** ## Cross-outlet loyalty and customer flow One of the most underleveraged advantages of multiple outlets is the network effect. A customer who is loyal to one location can become a customer of the entire brand — but only if the infrastructure supports it. **Unified loyalty.** If your loyalty programme recognises a customer at any outlet, you turn every location into a touchpoint for the same relationship. A customer who lunches at the CBD outlet on weekdays and dines at the suburban outlet on weekends is engaging twice as often as they would with either location alone. If the loyalty programme is siloed by location, you miss this entirely — the customer looks like two occasional visitors instead of one frequent one. **Cross-promotion.** When you open a new outlet, your existing customer database is your launch audience. The customers at location one who live near location two are the most likely early adopters of the new outlet. A targeted message — "We're opening near you" — to this segment is the highest-conversion launch marketing you can run, and it costs almost nothing. **Customer flow analysis.** With a unified database, you can track customer movement between outlets. Are customers visiting multiple locations, or is each outlet serving a separate base? Do customers who discover you at one outlet eventually visit others? Understanding this flow tells you whether your network is working as a network or just as a collection of standalone restaurants. *** ## Expansion economics Expansion is an investment, and like any investment, it needs a thesis and a set of metrics to validate it. **The revenue thesis.** Before opening, define what you expect the new outlet to achieve and by when. This is not a detailed financial model — it is a clear statement of what success looks like. "We expect location two to reach X in monthly revenue by month six, with Y percent of revenue from repeat customers." Having a target forces clarity about assumptions and creates accountability. **Break-even timeline.** How long until the new outlet covers its costs? New locations almost always lose money in the early months. That is normal. What matters is the trajectory — are you moving toward break-even, and at what pace? If month three looks the same as month one, something is wrong and you need to diagnose it before month six. **Cannibalisation check.** Is the new outlet growing the total pie, or is it stealing from the existing one? If location one's revenue drops by the same amount that location two generates, you have moved customers, not created them. Some cannibalisation is inevitable if the outlets are geographically close, but it should be a known and accepted trade-off, not a surprise. **Per-outlet health metrics.** Apply the revenue health scorecard from [Chapter 4](/docs/guides/how-to-think/reading-your-revenue.md) to each outlet independently. Customer lifecycle, channel mix, daypart spread, frequency tiers. Each outlet has its own health profile, and comparing them reveals which is performing well and which needs attention. Do not average across outlets — the average hides the problems. **Network-level metrics.** Beyond individual outlet health, track the metrics that only exist at the network level. Cross-outlet visit rate (what percentage of customers visit more than one location). Total unique customers across the network. Network-wide repeat rate. These tell you whether you are building a brand or just running multiple restaurants. *** ## The expansion checklist Before you sign the lease, work through these questions: **Do you have data on where your customers are?** If not, you are guessing on location. Go back to [Situation B](/docs/guides/what-to-do/going-digital.md) and build the data foundation first. **Is your first location's repeat rate healthy?** If you have not solved retention at location one, expansion will multiply the problem, not solve it. Fix the bucket before you add more water. **Can your signatures be replicated?** If the quality of your best dishes depends on one chef or one specific supplier, you have a scaling constraint that needs to be resolved before you open a second kitchen. **Do you have documented standards?** If the experience at location one depends on the founder being in the room, it will not transfer. Service standards, recipes, operational procedures — these need to be written down and trainable. **Is your loyalty and data infrastructure ready for multiple outlets?** A siloed system that treats each location separately will cost you the network effect. Unify before you expand, not after. **Do you have a clear revenue thesis?** Not hope. A thesis. What do you expect, by when, and how will you know if it is working? If you can answer these confidently, you are ready. If not, you know exactly what to work on before you take the leap. *** ## How Oddle helps in this situation **Oddle Shop** — Delivery address data is your demand map for location selection. Demand density, time-of-day patterns, frequency by area — all visible from existing delivery orders. **Oddle Enrolments** — Cross-outlet customer recognition. Unified rewards across all locations. Tracks whether customers visit multiple outlets or just one. **Oddle Reserve** — Per-location demand visibility. Occasion patterns by outlet. Your existing database becomes the launch audience for the new location. **Oddle Terminal** — Per-outlet first-time vs. repeat visualisation. Compare the health of each location side by side. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://www.oddle.me/docs/guides/what-to-do/planning-an-expansion.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.