# Launching a New Store

**Situation A**

***

## The launch problem

Opening a new restaurant generates attention. People are curious about what is new. Food bloggers show up. Friends and family fill the first few weeks. Queues form. Social media gets a burst of content.

And then the novelty wears off. The queue shortens. The bloggers move on to the next opening. The friends and family have done their duty.

This is not a failure. This is the natural arc of every launch. The question is not whether the initial wave fades — it always does. The question is what you built during that wave that sustains you after it passes.

The restaurants that build a lasting business after launch are not the ones that generated the most buzz in week one. They are the ones that used those early weeks to do three things: get the food right in people's mouths, find out who showed up and where they came from, and build a database that lets them reignite demand when the queue dies down.

<figure><img src="/files/WN76IlQRWGA3pn0DkJOx" alt="The launch hype curve — with and without database reactivation"><figcaption></figcaption></figure>

***

## Before you open: define who this is for

Before any launch execution, go back to [Chapter 2](/docs/guides/how-to-think/know-your-customer.md). Who is this restaurant for?

This is not a theoretical exercise. The answer determines every decision in the launch:

**Where you market.** If your ICP is the weekday office lunch crowd within a 500-metre radius, your pre-launch effort is hyper-local — office building lobbies, LinkedIn groups for the business park, partnerships with nearby coworking spaces. If your ICP is a destination dinner crowd willing to travel, your pre-launch is social media, food media, and influencer seeding.

**What you say.** The message that attracts a family brunch crowd is different from the message that attracts a late-night supper group. Knowing your ICP means knowing the occasion, and the occasion determines the tone, the imagery, and the promise.

**What you measure.** If your ICP is high-frequency (office lunch), early success looks like repeat visits within the first two weeks. If your ICP is low-frequency (special occasion dining), early success looks like reservation bookings and customer data capture.

If you skip this step, your launch marketing will try to speak to everyone and connect with no one. Define the customer first, then build the launch around reaching them.

***

## Pre-launch: build anticipation and a list

The biggest mistake restaurants make at launch is starting from zero on opening day. No customer list, no email addresses, no way to reach anyone who expressed interest. All the pre-launch buzz evaporates because there is no mechanism to convert attention into a contactable audience.

**A landing page with a purpose.** Not a placeholder "coming soon" page. A page that gives people a reason to leave their email or phone number. An early access reservation, a first-week exclusive menu, a launch event invitation, a simple "be the first to know when we open." The mechanism matters less than the capture — every person who signs up is someone you can reach on opening day and every day after.

**Social media as a capture tool, not just a broadcast tool.** Pre-launch social content should drive people to the landing page, not just accumulate likes. A beautiful renovation timelapse is good content. A beautiful renovation timelapse with "sign up to be first through the door" in the caption is a capture mechanism. The goal is not followers. The goal is a list of people you can contact directly.

**Local partnerships.** Nearby offices, residential buildings, gyms, coworking spaces. Introduce yourself before you open. Offer their community early access or a first-week perk. This does two things: it builds the list and it anchors you in the neighbourhood from day one.

**Set a target.** How many contactable people do you want on your list before opening day? Even a modest target — 200, 500 — forces discipline. A restaurant that opens with 500 emails has 500 people it can invite back after the first visit. A restaurant that opens with zero has to hope those first customers remember to return on their own.

***

## The launch playbook: get the food in their mouths

A launch is not a digital exercise. It is fundamentally about getting people to try your food, love it, and tell others. Everything else — the channels, the data, the marketing — serves that goal.

### The media launch and the hype curve

Most successful launches follow a pattern: media and influencer seeding creates anticipation, opening week draws a crowd, queues form, social media amplifies the queue, and more people show up because other people are showing up. This is the hype curve, and it is real and powerful.

But the hype curve has a natural lifespan. Depending on how strong the food and service are, the queue either sustains and builds — or it dies off quickly. The food is the engine. If people eat and are genuinely impressed, they talk. If they eat and are underwhelmed, the queue melts. No amount of marketing can substitute for the product being excellent in the first weeks.

This means launch is not the time to be running at 80 percent. The kitchen needs to be executing at its best, even if that means limiting covers, simplifying the menu, or slowing things down. A smaller number of customers who leave raving is worth more than a larger number who leave thinking "it was fine."

### Have a clear opinion about what people should eat

This is the Lever 4 insight from [Chapter 5](/docs/guides/how-to-think/the-growth-levers.md), applied at its most aggressive. At launch, you are not just guiding first-timers to the right dishes. You are engineering word of mouth.

When every customer who visits in the first two weeks is eating and raving about the same two or three dishes, something powerful happens. The word of mouth becomes coherent. It is not "I went to the new place, it was pretty good." It is "You have to try the laksa" or "the wagyu rice bowl is unreal." Specific. Repeatable. Shareable.

This means:

**Your signatures must be decided and locked in before launch.** Not "everything on the menu is good." Two or three dishes that represent you at your absolute best. The dishes that, if someone tries them, guarantee they walk away impressed.

**Everyone on the team must be aligned.** The server, the host, the cashier — when a customer asks "what should I order?" the answer is the same. Every time. Not "it depends what you like." Not "the whole menu is great." A clear, confident, specific answer: "You have to try this."

**The menu should steer, not just list.** Visually highlight the signatures. Put them at the top. Label them. Make them impossible to miss, whether the customer is reading a physical menu, scanning a QR code, or ordering online. Do not make the customer guess. Tell them what to eat.

When you do this well, the hype becomes self-sustaining for longer. Every customer leaves with the same story. Every Instagram post features the same dish. Every recommendation to a friend is specific and convincing. That consistency is what keeps the queue going.

### Design a shareable moment

Great food makes people tell someone. A shareable moment makes people show someone. And showing is more powerful — it is visual, instant, and reaches further than any conversation.

A shareable moment is something in the dining experience that is so visually striking or theatrically surprising that customers instinctively reach for their phone. It is not a generic Instagram-friendly backdrop or a neon sign that says "but first, food." Those are forgettable. The strongest shareable moments are tied to the food itself.

Think about what Haidilao does with their hand-pulled noodles. A chef comes to your table and performs the noodle-stretching right in front of you. It is theatrical, it is specific to their brand, and it is impossible not to film. Every video that gets shared is an advertisement that costs them nothing and carries the credibility of a real customer's experience.

Your shareable moment does not need to be that elaborate. It could be a dramatic plating — a dish that arrives with smoke, a sauce poured tableside, a dessert that is assembled in front of the customer. It could be a serving vessel that is unexpected or oversized. It could be a preparation technique that is visible from the dining room. The principle is the same: create a moment in the experience that is so distinctive that the customer wants to capture and share it without being asked.

The best shareable moments have three qualities:

**They are tied to a signature.** The shareable moment should be attached to one of your best dishes, not a sideshow. When someone shares the video or photo, the food is the star. This reinforces the signature dish strategy — the dish people are told to order is also the dish they see on social media before they visit.

**They are repeatable.** It happens for every customer, every time, not just on special occasions. Consistency matters because it means every table is a potential broadcast. If only some customers get the moment, you lose the compounding effect.

**They are natural, not forced.** The moment should feel like a genuine part of the experience, not a marketing gimmick. Customers can tell the difference. A chef slicing sashimi with visible skill feels authentic. A server holding up a sign that says "share this for 10% off" feels desperate. The best shareable moments are ones customers want to capture for themselves, not ones they are incentivised to capture for you.

***

## Enrolment: find out who showed up

Capturing customer data at launch is not just about building a mailing list. It is intelligence gathering. You need to know two things about every customer who walks through the door: **how did they discover you** and **where are they from.**

These two data points tell you everything about the shape of your early customer base.

**Discovery channel.** Did they see you on social media? Were they recommended by a friend? Did they walk past and see the queue? Did they read a review? Did a food blogger bring them? Understanding how customers found you tells you which of your launch efforts are actually working — and which are noise.

**Location.** Are they from the immediate neighbourhood? Are they from across town? Are they visiting from another country? This is not demographic trivia. It is strategic information.

**Destination diners** — people who travelled specifically to eat at your restaurant — are your word-of-mouth engine. They came because they heard something compelling, and they will tell others. They amplify your reach beyond your immediate radius. But they will not come every week. Their value is in spreading the word, not in building frequency.

**Local diners** — people who live or work nearby — are your base. They are the ones who can become regulars. They are the ones whose visit frequency compounds over time. They are the ones who will sustain you after the hype fades.

At launch, you want both. Destination diners create the buzz and extend your reputation. Local diners build the foundation. But you need to know which is which, because the follow-up for each is different. A destination diner gets a "thank you, share your experience" message. A local diner gets a "welcome to the neighbourhood, here's a reason to come back this week" message.

**How to capture this:**

Set up an enrolment programme from day one — a loyalty sign-up, a feedback form, a simple registration at checkout. Include two fields beyond the basics: "how did you hear about us?" and a postal code or neighbourhood. These fields take seconds to fill in and give you a picture of your early customer base that would otherwise take months to piece together.

***

## Channel setup: what to prioritise at launch

Not every channel needs to go live on day one. In fact, launching everything simultaneously splits your attention and makes it harder to execute what matters.

<figure><img src="/files/hIm2r7CVg6Ao3A4vzc04" alt="Channel priority order at launch"><figcaption></figcaption></figure>

**The priority order:**

**First: Reservations.** For any restaurant where dine-in is the core experience, a reservation system should be live before opening day. It gives you predictability (you know how many people are coming), it captures customer data automatically (name, phone, email, party size), and it lets you manage the launch crowd rather than being overwhelmed by it. Controlled capacity in the first weeks means you can deliver a consistently excellent experience rather than a chaotic one.

**Second: Dine-in experience and enrolment.** The physical infrastructure — the menu, the service script, the capture mechanisms. QR codes for enrolment, loyalty sign-up prompts, feedback collection. This is not a channel in the traditional sense but it is the most important system to have running at launch.

**Third: Marketing channels.** Email, SMS, social media. These are how you reach your captured customers after they leave. They should be active from day one, even if the list is small. The list grows as more customers are captured, and by week three you should be sending your first reactivation messages.

**Later: Online ordering and delivery.** This might seem counterintuitive, but at launch, your priority is getting people to experience the food in person. The dine-in experience is what creates the word of mouth. Delivery and online ordering are convenience channels — they serve customers who already know and love you. They are important, but they are not what builds the initial reputation.

The exception is if your concept is delivery-first (cloud kitchen), in which case the online ordering channel is your primary experience and should be live from day one.

**Even later: Delivery marketplaces.** Listing on GrabFood, Deliveroo, or other platforms gives you access to demand you cannot reach directly. But marketplace customers are the platform's customers, not yours. Launch your own channels first so that when marketplace orders eventually come in, you have an alternative to offer — an insert card, a QR code, a packaging prompt that invites them to order direct next time.

***

## When the queue dies down

It will. This is not pessimism. It is the natural arc of every launch, and the playbook should prepare for it rather than pretend it will not happen.

The restaurants that handle this transition well are the ones that built two things during the hype period: a database and a signature identity.

**The database is your relaunch tool.** When the queue dies down — typically four to eight weeks after opening, depending on the concept and the market — you have a window where foot traffic drops but your captured audience is at its largest. This is the moment to inject new energy.

A seasonal menu launch. A new dish announcement. A special event for loyalty members. A "we've been open for two months, here's what we've learned and what's new" message. Each of these is a reason for someone in your database to come back, and a reason for them to tell someone else.

Without the database, you have no way to reach the people who came once and enjoyed it but have not thought about you since. You are waiting for them to remember you. With the database, you can prompt them.

**The signature identity sustains you.** If you did the signature dish work well, your restaurant has a reputation that outlasts the queue. People are still talking about the specific dishes that impressed them. Recommendations are still being made. The word of mouth has a longer tail because it is specific and vivid, not generic.

This is also when you start to see whether your customer base is healthy. Look at the revenue equation from [Chapter 3](/docs/guides/how-to-think/the-revenue-equation.md): what is the repeat rate? What is the mix of destination diners versus locals? What dayparts are performing? The answers tell you what to focus on for the next phase — which is no longer launch, but the ongoing work of running and growing the business.

***

## Measuring launch success

Revenue is the obvious metric, but in the first 90 days it is not the most important one. A restaurant can generate strong opening revenue entirely from novelty traffic and first-timers with no repeat behaviour. The top line looks good while the foundation is hollow.

**The metrics that actually predict long-term health:**

**Customer capture rate.** Of all customers who transact with you, what percentage become known (email, phone, loyalty enrolled)? If this number is low, your enrolment infrastructure needs work. Every uncaptured customer is someone you cannot reach again.

**Discovery channel mix.** Of your captured customers, what percentage are destination diners versus locals? What are the top discovery channels? This tells you whether your hype is reaching beyond the neighbourhood (good for buzz) and whether it is reaching the neighbourhood (good for base).

**First-to-second visit conversion.** Of the customers who came in month one, what percentage came back in month two? This is the single most important early indicator. A high conversion rate means the first impression is landing — the food is right, the signatures are working, and the reactivation is effective. A low rate means something in the first visit experience needs to change.

**Repeat revenue share by month three.** By the end of the first 90 days, what percentage of revenue comes from customers who have visited more than once? This does not need to be high — you are still a new restaurant. But it needs to exist and it needs to be growing. If month three revenue is still overwhelmingly first-timers, you are on the treadmill.

**Channel mix.** What percentage of your revenue comes through channels you own versus channels you rent? The earlier you establish direct channels as a meaningful share, the healthier the long-term economics.

These metrics are not about hitting targets in the first 90 days. They are about establishing a baseline and a trajectory. The absolute numbers matter less than the direction. Are more customers being captured each week? Is the repeat rate improving month over month? Is the channel mix shifting toward owned? If the answers are yes, the system is working. If not, you know exactly where to intervene.

***

## How Oddle helps in this situation

**Oddle Reserve** — Live before opening day. Manages capacity during launch, captures customer data automatically (name, phone, email, party size, occasion notes). Gives demand predictability from week one.

**Oddle Enrolments** — Discovery channel and location intelligence from day one. Front-loaded return rewards to drive the critical first return visit. Tracks return rate so you can see first-to-second visit conversion.

**Oddle Terminal** — Captures dine-in customers through credit card tokenisation who don't book or order digitally. Visualises first-time vs. repeat ratio from week one. Prints rewards for customers to claim and unveil themselves.

**Oddle Marketing** — First reactivation message at day 15–30. The 7-day nudge for first-timers while the memory is fresh. Automated sequences that scale as the database grows.

**Oddle Shop** — Not a launch priority. Activates once people love the food and want convenience. Advance orders expand kitchen production hours — prep at 5:30pm, dine-in starts at 6:30pm. Where group bundles and catering will live later.

**Oddle Eats** — Discovery channel. Brings destination diners during the hype phase.


---

# 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/launching-a-new-store.md?ask=<question>
```

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.
