How to Market a New Restaurant Before Opening: Build Demand You Can Serve
Market a new restaurant before opening with a sequenced plan for listings, audience capture, content, a soft opening, launch, and return visits.
Market a new restaurant before opening by building one working path from discovery to a completed visit: accurate location information, a clear opening promise, a permissioned waitlist, real food and room content, and a tested way to book or claim the offer. Build that path in order, rehearse it during a soft opening, release demand only as fast as the restaurant can serve it, and measure responses, arrivals, settled checks, and return visits separately.
That is the pre-opening piece of restaurant marketing. Posts and ads can create attention, but the opening plan works only when a guest can find you, take the next step, show up, get served, and know why to come back.
| Stage | Keep this record | It is ready when |
|---|---|---|
| Concept | One-page concept card | The guest, experience, location, price position, and next action are clear |
| Findability | Listing and website QA sheet | A guest can find the correct address, hours, opening date, menu, and working link |
| Audience | Permission, source, and message-state ledger | Every signup has a source, timestamp, and permission record; every send separates attempted, delivered, failed, opted-out, suppressed, and pending recipients |
| Content | Approved launch folder and calendar | Every post uses current food, room, date, location, and action details |
| Soft opening | End-to-end test log | A real test guest can respond, arrive, be recognized, and close a paid check |
| Launch | Capacity and release sheet | Each audience group has a send time, seat limit, owner, and stop rule |
| Return | Return-path test and matured first-visit list | The return path works before launch; later cohorts use the same return window and outcome rules |
1. Test the concept before you market an opening date
If the concept, location, or lease is still unsettled, test the promise before you present the restaurant as open. A proposed-concept landing page and clearly labeled test ad can measure whether nearby people will join an interest list; an earlier restaurant project used a “dummy” concept campaign to collect signups and gauge interest before launch.
Write the proposed cuisine, neighborhood, experience, expected price position, and one action such as “join the opening list.” Do not take paid reservations or imply that an uncommitted address and date are final. Give each ad or community post its own source name so you can see which message produced each completed signup.
The result is evidence of interest, not proof of future covers, sales, or profit. Decide in advance what response would justify keeping the idea, changing the promise, testing another audience, or stopping. If the concept and lease are already final, record that decision and move to the opening plan. The dummy-ad validation process covers this earlier decision in depth.
2. Freeze one promise before you build pages and posts
Your opening card must settle what every later listing, form, ad, and staff script will say. Record the restaurant name, target guest, signature experience, neighborhood, address confidence, opening window, primary action, service capacity, first-visit reason, return reason, and the person who approves changes.
If your schedule allows, a Feast pre-opening playbook starts four to six weeks before launch, but that is a planning reference rather than a universal deadline. Start only when the concept card is stable enough that a person will not join for one promise and arrive to find another.
Lead with the food, hospitality, and experience. Put any opening offer after that story so it helps an interested guest act instead of making the restaurant sound like a coupon. That order came from a fine-dining sales conversation about protecting the brand while encouraging trial.
This step is done when the owner, marketing lead, and floor lead can read the same card and give the same answer to: “What is opening, for whom, when, and what should I do next?”
3. Make the restaurant findable before you send attention
Publish one reliable destination before sending anyone to search for you. The website and Google Business Profile should use the same public restaurant name, address, phone, opening date or window, hours, menu, and reservation, ordering, or waitlist link wherever those fields are available.
Keep a short access record with the profile owner, website editor, reservation or ordering login owner, working URL, and date each item was checked. If profile access or verification is delayed, send pre-opening traffic to the working restaurant landing page while the access issue is recovered; do not send people to a broken profile and hope they find another way.
Test the guest path on a phone and in a private browser. Search the restaurant name and address, open every visible link, submit the form, confirm the response arrives, and check the map pin and directions. Save the test date and the person responsible for correcting each failure. This step is complete only when someone outside the project can find the same facts and finish the intended action without help.
4. Capture an audience you can contact on purpose
The opening list needs a specific promise and a permission record, not just a pile of phone numbers or email addresses. Tell people what they are joining, what kind of updates they will receive, and how the restaurant will contact them; retain the source, timestamp, and permission language tied to each signup.
A useful landing page answers five questions without a scroll hunt: What is the restaurant? Where is it? When is it opening? Why should I care? What should I do now? For an audience that has never heard of the restaurant, use the neighborhood in the hook and show the food or experience rather than relying on brand recognition.
Count a completed, eligible signup once. Keep page visits, form starts, completed signups, failed confirmations, unsubscribes, and suppressed contacts separate. A signup is a response; it is not a reservation, an arrival, a check, or a regular.
For every email or text release, record unique eligible recipients, attempted sends, provider-reported deliveries, failures, opt-outs, contacts suppressed before sending, and pending or unknown outcomes as separate states. A provider-reported delivery does not prove that a person read the message. Keep pre-send suppressions and failed sends out of delivery-based denominators; if you report an opt-out rate, divide opted-out recipients by delivered recipients rather than the original list size.
A documented opening case used a waitlist as the bridge between pre-opening advertising and day-one demand. The opening waitlist case study reports its own scope and results; use it as an example, not a promise for your restaurant.
5. Build content from what a guest will actually experience
Create launch content only after the important details are real enough to photograph and repeat. Start with the signature dishes, room, service style, people behind the restaurant, neighborhood, directions, opening window, and one next action. A construction update can build interest, but it cannot replace proof of the food and experience guests will buy.
Every asset needs an owner, final caption, current date and location, approval status, intended channel, and posting date. For work made by an outside photographer or food influencer, retain the agreed deliverables, due date, posting plan, file handoff, and usage permission instead of trying to reconstruct the agreement after opening.
If food influencers are part of the launch, start their sourcing before the soft opening so approval, booking, the visit, and file delivery happen in sequence. Use two to three weeks before the soft opening as a planning window, not as a guaranteed delivery time. A larger food-influencer push is a separate operating job; the grand-opening food-influencer blitz explains that high-volume version.
“I have a lot of plans, I have a lot of ideas, but I just can’t do everything by myself.”
A restaurant owner preparing to open a boba shop
The content calendar is ready when every scheduled post points to the same verified guest path and no asset depends on a dish, room, date, or offer the team cannot deliver.
6. Build and test the second-visit path before launch
The launch plan is incomplete until a first-time guest has a reason to return and you have permission to send it. Before the soft opening, decide how staff will identify a first-time guest, invite them into the return path, record permission, explain the next milestone or invitation, and recognize the later visit.
Test that full sequence before releasing the launch audience: enroll a test guest, send the intended return message, have that person complete a later visit, and match that return transaction to its own paid, non-voided settled check. First observe the successful second-check match. Then void or refund that second test transaction and verify that it disappears from the final settled-return view. The first-visit check cannot prove that the later return happened.
“We definitely need return business. I want new guests, but ideally I want them to become continuous guests, regulars.”
A restaurant owner explaining the finish line
After launch, keep enrollment, attempted messages, provider-reported deliveries, failed sends, opt-outs, suppressions, pending outcomes, reward claims, completed return visits, and settled return checks separate. Choose one return window before launch. The denominator is unique eligible identified first-time guests who completed the initial verified in-person visit with their own matched paid, non-voided settled check, received the entire return window, and have a reconciled known return outcome. The numerator is the subset of that exact denominator who completed a later verified in-person visit with a separate matched paid, non-voided settled check inside the window. Hold early returns out until their cohort matures, and report open, immature, ineligible, and unresolved records separately.
7. Make the soft opening prove the whole guest path
A soft opening should prove the marketing promise and the restaurant operation together. Run at least one test from each live source: open the post or ad, complete the waitlist or reservation action, receive the confirmation, follow the directions, arrive, have staff recognize the action, complete service, close a paid non-voided check, and confirm the source and check appear in the retained record.
Also record the problems that marketing can magnify: unclear parking, a bad map pin, a sold-out featured dish, a missed reservation, slow ticket flow, a confusing redemption, or staff who never received the opening script. Set your own acceptable capacity and service limits before the test. There is no useful universal threshold for every concept.
Do not open the full audience while a critical path is failing. Name the owner and retest date for each failure. This stage is complete when the guest path succeeds, the team can handle the promised experience, and a voided or refunded test check is excluded from the final settled-sales view.
8. Release launch demand in waves the restaurant can serve
Send opening traffic in controlled groups tied to real capacity. Start with the audience and partners most likely to respond, watch completed arrivals and service conditions, then release the next group only when the floor and kitchen can absorb it.
Give each email, text, community partner, food influencer, and ad its own retained source. Platform reach and video views show exposure. Link clicks, signups, offer claims, and reservations show responses. Only verified arrivals are visits, and only paid non-voided checks are settled sales. None of those measures alone proves the campaign caused an incremental sale or produced profit.
No post or food-influencer wave guarantees virality. The controllable goal is enough accurate local proof and enough completed guest paths to learn which message brings the right response without breaking service. If a delivery marketplace will carry a large share of launch orders, keep those orders separate from in-person visits and evaluate that channel separately.
Pause the next release when the listing becomes inaccurate, the promoted item is unavailable, staff miss the guest action, or service crosses the limit set during the soft opening. Fix and retest the failed step before buying more attention.
9. Let the first broken checkpoint choose the next move
Read the opening scorecard from left to right: accurate discovery, completed response, verified arrival, settled check, and matured return. The first weak or unverified transition tells you what to repair next.
- If people cannot find correct information or finish the form, repair the listing, page, or action before adding reach.
- If plenty of eligible people reach the page but few complete the action, test the promise, proof, or form.
- If responses are healthy but verified arrivals are weak, inspect confirmation, directions, dates, availability, and reservation handling.
- If arrivals are healthy but service breaks, reduce the next release and fix the operation.
- If completed first visits are healthy but matured return is weak, inspect the experience and return invitation before buying more first visits.
- If the records cannot connect a source to an identified guest and completed check, the honest answer is insufficient evidence.
A forecast can show how many new guests, returns, dollars, and time a goal would require. It cannot prove that a future campaign will create them or that one launch activity caused a before-and-after change. Keep direct matches, observed lift against a comparable baseline, and modeled opportunity as three separate views.
The right pre-opening plan does not end at “make noise.” It ends with a restaurant people can find, a promise the team can keep, a completed first visit you can verify, and a return path you can measure.
When food-influencer coordination is the part you cannot staff
Remy solves the food-influencer coordination slice of this plan: recruiting local influencers, booking visits, sending reminders, and chasing delivered files. You still decide whom to approve, what the visit promises, which work is usable, and how the rest of the opening plan runs.
Learn more about Remy if you want that repeated coordination handled in one place. The tracked blog offer makes the first month $100; the standard price is $150 per location per month after that. Plan about $5 a day for recruitment ads; food, any paid-ad-use bonus owed only when the restaurant actually uses the content in paid advertising under the written terms, and restaurant time remain separate.