Validate a Restaurant Concept With a Dummy Ad Campaign Before You Sign a Lease
Test local demand for a restaurant idea with an honest concept ad, a trackable signup, a fixed budget, and clear limits on what it proves.
A dummy ad can test whether a defined local audience will take a trackable action for a clearly described restaurant concept at a cost you set in advance. It cannot prove that people will like the food, return, spend enough, or make the restaurant profitable, because nobody has experienced the product or completed a real visit yet.
Here, “dummy ad” means an honest demand test for a proposed restaurant, not an ad pretending the business is open. The finished result is a count and cost for eligible local signups, plus a decision to advance, repair, or park the idea before the broader pre-opening marketing plan begins.
| Result from the test | What it supports | What it does not prove |
|---|---|---|
| Ad impressions or reach | The platform says it served the ad | A person noticed, read, or wanted the concept |
| Link clicks | The platform recorded a click on the ad's link | A unique person, proven interest, qualified lead, reservation, or visit |
| Eligible signup | A person in your prewritten market completed the interest form | Willingness to reserve, pay, visit, return, or recommend |
| Reservation request | Intent tied to a possible date or opening | A seated party, completed visit, covers, or sales |
| Prepayment | A paid commitment under stated terms | A completed visit, repeat demand, contribution, or profit |
| Verified completed visit after opening | The identified guest arrived and completed service | The ad caused the visit or the restaurant is profitable |
| Paid, non-voided settled check | Observed sales linked under your written rule | Incremental sales, contribution, repeat behavior, or profit |
Step 1: Write the one demand question the ad must answer
The first artifact is a one-page test card with one concept, one local audience, one action, and one decision threshold. A planning call in December 2025 proposed this exact use of a concept ad: collect signups and gauge interest before an actual business exists. It did not report a result or establish a universal budget.
Write these fields before making an ad:
- Concept: the cuisine, service style, occasion, and price position you are actually considering.
- Market: the neighborhood or travel area the proposed site would need to serve.
- Audience: the specific local diner the concept is designed for.
- Action: join an interest list, request an opening invitation, or answer one concept question.
- Eligible signup: one unique person inside the market who completes the required fields and fits the rule written before launch.
- Budget and window: the maximum media and production spend and the exact start and stop dates.
- Advance rule: the minimum eligible-signup count and maximum full cost per eligible signup you require before paying for deeper research.
- Repair rule: the pattern that earns one revised test rather than an immediate yes or no.
- Stop rule: the result that parks the concept or sends it back for a material change.
Do not change the eligibility or success threshold after seeing the results. That turns a test into an explanation for whatever happened.
Step 2: Build a page that says the restaurant is proposed
The landing page must make the concept appealing without implying that a restaurant, address, menu, opening date, or reservation inventory already exists. Clear disclosure protects the people responding and makes the result more useful: they are raising a hand for the concept as described, not for a false promise.
Include:
- A plain status line: “Proposed restaurant concept” or “Exploring a new restaurant in this area.”
- The concept: cuisine, service format, intended area, likely occasion, and honest price position.
- Representative visuals: only food and room images you created, licensed, or clearly label as concept references. Do not imply a sample dish is already on the menu.
- One action: a short interest form, not a maze of buttons.
- A truthful follow-up promise: say exactly what respondents will receive and how often you expect to contact them.
- Data boundaries: collect only the fields the test needs, state how you will use them, and provide the privacy and opt-out path before any promotional follow-up.
Do not use fake reviews, a made-up opening date, false “last table” language, or a reservation button that cannot create a real reservation. Do not take money during this early concept test. A later prepayment test needs a real item, price, fulfillment plan, date rule, and refund process; payment is a stronger commitment than a signup, but it is still not a completed visit or proof of profit.
Step 3: Make the ad explain the product to someone who has never heard of it
The ad should teach the proposed restaurant in one glance: show the food or experience, name the area, and ask for the one action on the test card. A launch-planning record recommends educating an unaware audience, using a location-based hook, and showing the product visually rather than assuming brand recognition.
Use this brief:
- Opening line: proposed cuisine or occasion plus the intended area.
- Proof: one honest visual and the concrete feature that makes the concept different.
- Status: not open yet; this is an interest test.
- Action: join the local interest list or request an opening invitation.
- Destination: the disclosed concept page from Step 2.
Keep the concept, destination, action, geography, budget, and window fixed while testing a message. If you change all of them at once, a better result cannot tell you which change mattered.
There is no defensible universal radius. Use the actual trade area you are considering, exclude places that would not reasonably support the proposed location, and record the map before launch. A broad citywide response cannot validate one block, rent level, parking pattern, or delivery zone.
Step 4: Set a budget that buys a decision, not a victory story
Feast's internal planning protocol uses $20 per day for 14 days, or $280, as a practical restaurant-ad test. Treat that as a planning protocol, not a minimum every concept needs, a promise of enough leads, or proof that a two-week winner deserves a lease.
The complete test budget is more than media:
Full concept-test cost = ad spend + creative production + landing-page or form cost + allocated software or agency fees + paid test-management labor
Choose one written allocation basis for any shared monthly charge, such as the share of days used by this test, and apply it once. Keep your own management time as a separate planning cost unless you intentionally assign it a dollar value. No food, reward, or service cost belongs in this early test if the page offers only an interest signup.
Full cost per eligible signup = full concept-test cost ÷ unique submitted leads confirmed eligible after duplicate status and market or audience eligibility are reconciled and known
The numerator includes every cost above exactly once. The denominator includes only the successful eligible subset of submitted leads after duplicate and eligibility review. Exclude test records, duplicates, incomplete submissions, known ineligible leads, and unresolved records; report each excluded state separately rather than quietly moving it into a success or failure count. If there are no eligible signups, the cost per eligible signup is undefined, not zero.
If you use the $20-by-14-day protocol, keep its clock and budget fixed unless an ethical, technical, or spend-control problem requires an early stop. The separate day-14 decision framework explains how Feast handles real restaurant ad tests; a concept signup still does not carry the downstream revenue evidence of an operating restaurant.
Step 5: Prove the click-to-signup path before spending
The acceptance test is complete only when a test click creates the exact record the final scorecard needs. Run it from the ad preview on a phone outside your admin session.
Verify, in order:
- The ad clearly says the concept is proposed and shows the correct area.
- The link opens the intended page and preserves the campaign source.
- The page repeats the status, concept, area, and promised follow-up.
- The form blocks a missing required field without creating a false lead.
- A valid test submission creates one record with timestamp, source, geography or eligibility evidence, consent choice, and test status.
- Submitting the same test identity again does not create two eligible people.
- The confirmation does not claim a reservation, table, or opening date.
- The test record can be excluded without deleting the audit trail.
If any join fails, do not launch. A campaign cannot validate demand when its source, eligibility, duplicates, or successful submissions cannot be reconciled.
Step 6: Read the results without upgrading the evidence
The scorecard should preserve every state from platform activity to a known eligible signup. Do not collapse impressions, clicks, leads, reservations, prepayments, and visits into one “conversion” number.
| Scorecard row | Exact record | Decision it supports |
|---|---|---|
| Ad spend | Spend mapped to this campaign and test window | Media budget consumed |
| Creative production | Actual production cost assigned to this test | Creative cost included once |
| Landing page or form | Actual page and form cost assigned to this test | Response-path cost included once |
| Allocated software or agency fees | Shared charges assigned by the written basis from Step 4 | Fixed cost included without double counting |
| Paid test-management labor | Additional paid labor used to build, monitor, reconcile, and report this test | Management cost included once |
| Full concept-test cost | Ad spend plus the four cost rows above | Complete numerator for the cost decision |
| Platform-reported impressions or reach | The platform's reported delivery metric, labeled exactly | Delivery by the platform, not human attention |
| Link clicks | Recorded clicks on the concept ad | Creative and message diagnosis; clicks may repeat or remain anonymous |
| Recorded page visits | Page loads counted under the written rule | Page diagnosis, not a person count |
| Unique submitted leads | Deduplicated people whose form submitted successfully | Total recorded interest before eligibility review |
| Eligible signups used in the cost rate | Successful subset of unique submitted leads whose duplicate status and market or audience eligibility are reconciled and known | Denominator for full cost per eligible signup |
| Ineligible signups | Known submitted leads outside that rule | Market or targeting diagnosis |
| Test, duplicate, or incomplete records | Records confirmed in one of those excluded states | Data-quality count kept outside the denominator |
| Pending or unresolved | Records whose eligibility or duplicate status is not known | Evidence that must remain outside the rate until reconciled |
| Full cost per eligible signup | Full concept-test cost divided by eligible signups used in the cost rate | Compare with the ceiling written in Step 1; undefined when the denominator is zero |
Three common patterns lead to different repairs:
- Few clicks were recorded: the concept, visual, opening line, audience, or area may be wrong. The ad alone cannot identify which one.
- Clicks were recorded but few eligible forms were submitted: the page, promise, form, privacy request, or mismatch between ad and page may be stopping responses.
- Submitted leads mostly failed the prewritten eligibility rule: the geography or audience definition may be too broad, or the concept may appeal outside the trade area you need.
An eligible signup is still a lead, not a reservation or guest. If the restaurant later opens, carry the original source forward and record reservation requests, completed visits, paid checks, and repeat visits as new states. Directly matched settled sales remain observed attribution; only a like-for-like comparison or controlled test can support a stronger incremental claim.
Step 7: Advance only to the next proof, not straight to a lease
A passing concept-ad test earns deeper validation, not a signed lease. Advance when the test reaches the signup count and cost ceiling you wrote in Step 1 and the result is not dependent on unresolved or ineligible records.
The next proof should attack what the ad could not test:
- Food: run tastings or a paid pop-up with the actual product and price.
- Operations: prove prep, service time, labor, waste, and capacity under a real service.
- Economics: build unit economics from actual ingredient, packaging, processing, labor, occupancy, and acquisition costs.
- Site: test the proposed block's access, visibility, parking, delivery area, dayparts, and rent—not the city in general.
- Return behavior: after real guests complete a first visit, give an eligible cohort the same fixed time to return before calculating repeat behavior.
Repair and rerun when the records show one identifiable break, such as clicks without signups or eligible interest outside the required area. Park the idea when a complete test misses the prewritten threshold and no narrow execution failure explains it. “Insufficient evidence” is also a valid result when the budget did not spend, records broke, or unresolved leads could change the decision.
Once the concept advances, an influencer blitz before opening can produce launch content, while a measured restaurant waitlist case study shows what a later pre-opening campaign can evaluate. Neither stage turns the earlier dummy ad into proof of visits or profitability.
Feast belongs after the concept earns a real campaign
Feast becomes relevant after you decide to advance and need an acquisition campaign run and measured. Feast is the full restaurant performance-marketing service that runs Meta campaigns end to end; Remy handles influencer-program operations and is not the product offered here. A dummy ad run before the business exists cannot produce verified restaurant visits, settled checks, or repeat behavior, so do not ask Feast—or any platform—to report those outcomes early.
If the concept has cleared the demand test and you want to plan the measured opening campaign, book a demo of Feast.