Restaurant Location Analysis: Demand vs Supply Before You Commit

Why is a raw restaurant count nearly meaningless?

For most business categories, counting competitors inside a trade radius is the natural first step. For restaurants it breaks down immediately, because the base rate is so high. US County Business Patterns and industry counts put the national norm at about 28 restaurants per 10,000 residents. Compare that with coffee shops at roughly 4.2 per 10,000 or gyms at about 2.1 per 10,000, and the problem is obvious: by the standards of any other category, every restaurant market in America looks saturated.

Yet restaurants keep opening and plenty keep thriving, often on blocks that already hold a dozen of them. That is because “restaurants” is not one market. It is dozens of overlapping markets segmented by cuisine, price and daypart, and the count that matters is the count inside your segment. The generic version of this exercise, and why counting is harder than it looks, is covered in how to count competitors in your area. Restaurants are the category where doing it naively hurts the most.

Why an 800-meter trade radius?

A restaurant meal is a destination purchase, but only barely. People will cross a few extra blocks for dinner in a way they will not for a routine coffee, yet the large majority of walk-in and lunch demand still comes from within about a 10-minute walk. That is why Denzify uses an 800-meter competition radius for restaurants, wider than the 600 meters used for coffee (an impulse purchase) and far tighter than the 2.5 kilometers used for gyms (a membership decision people will drive for). The full logic of per-category radii is laid out in the coffee-shop saturation article, and the principle carries over directly: judge a restaurant by the competitors it can actually lose a table to, which means the ones within a short walk of the same demand pool.

What actually counts as a competitor for a restaurant?

Here is the central idea of restaurant location analysis: cuisine-level competition. A taqueria, an omakase counter and a sports bar can share a block and barely compete. They serve different occasions, different budgets and often different hours. If your saturation math treats all three as interchangeable “restaurants,” the result is noise.

The honest competitor set for a restaurant concept is the intersection of three filters:

• Same cuisine family. Not identical cuisine, but the family a customer would substitute within. A ramen shop competes with other Asian noodle and rice concepts far more than with the pizzeria next door.
• Adjacent price band. A $14 lunch spot and a $90 tasting menu are not fighting over the same decision, even in the same cuisine. Count places within roughly one price band of yours, above or below.
• Same daypart. A breakfast cafe and a dinner-only steakhouse can sit wall to wall and never take a customer from each other. If a place is closed when you are busy, it is not your competitor.

Building this set by hand is where keyword searches fail. Map listings misfile concepts constantly: an acai bar filed under “smoothies” still competes with an acai concept, and the steakhouse next door does not compete with your breakfast cafe no matter how close it is. Denzify builds the competitor set by reading each candidate’s name, its listed categories and its customer reviews, instead of matching keywords, so a concept gets counted by what it actually serves and when, not by the label someone typed into a directory.

Which daypart does your demand actually come from?

The second half of the analysis is demand, and for restaurants demand is not one number. The same corner can be excellent for one daypart and dead for another, because breakfast, lunch, dinner and late night draw on different populations that public data measures separately:

• Lunch is daytime workers. Census LODES workplace data maps where people work, not where they sleep. An office district with twice as many workers as residents is a lunch machine and a dinner ghost town.
• Dinner is residents and income. ACS data on residential population and median household income inside the radius tells you who is around at 7 p.m. and how often they can afford to eat out.
• Late night is nightlife anchors. Bars, venues and transit that keep people on the street past 10 p.m. No anchors, no late-night trade, regardless of how many people live nearby.

This is why a corner cannot be judged “good for restaurants” in the abstract. It can be good for a lunch counter and terrible for a dinner concept, or the reverse. Match the dayparts you plan to serve against the demand sources that are actually present, then count only the competitors open during those same hours.

How do you read demand vs supply inside the radius?

The workflow, in order:

1. Fix the address, not the neighborhood. Draw the 800-meter circle around the exact storefront you are considering. Neighborhood names and ZIP codes are the wrong geography.
2. Build the honest competitor set. Same cuisine family, adjacent price band, same daypart, inside the circle. Expect this number to be a small fraction of the total restaurant count.
3. Size the demand for your dayparts. Residents and income for dinner, workers for lunch, anchors for breakfast and late night, per the table above.
4. Judge the ratio, not the count. Twelve restaurants around a corner with 3 direct competitors and 10,000 lunchtime workers is a healthier picture than a quiet street with 1 competitor and no daytime population at all.

The rest of the pre-lease homework, rent load, visibility, co-tenancy, the walk-the-block checks, sits on top of this and is covered in the broader site selection checklist for small businesses. But the demand-vs-supply read is the part that kills or confirms a location before you spend a dollar on anything else.

Do 60% of restaurants really fail in the first year?

You will see the statistic everywhere: 60% of restaurants fail in year one, 80% within five years. Treat those numbers with suspicion. They are commonly cited and poorly sourced; the studies behind them are old, narrow or misquoted, and serious attempts to measure restaurant survival find rates that look more like other small businesses than like a catastrophe. Nobody has a clean national number, and anyone quoting one with two decimal places is selling something.

What the honest reading does support: when researchers and operators list why restaurants close, location misreads consistently rank among the top causes. Overestimated foot traffic, a daypart mismatch, a competitor set that was denser than it looked, rent set for a demand level that never materialized. That is the useful takeaway, because unlike your chef’s consistency or next year’s food costs, the location risk is measurable before you sign. You cannot de-risk everything about a restaurant. You can de-risk this part.

Which mistakes should you avoid?

• Counting every restaurant as a competitor. At 28 per 10,000 residents, the raw count condemns every location. Filter to cuisine family, price band and daypart first.
• Judging a lunch concept on residential data. Census population counts people where they sleep. If you sell lunch, the number you need is workers, from LODES.
• Reading “busy at dinner” as “busy.” Visit the corner at your planned service hours, not at the hours it happens to look alive.
• Trusting map categories. Listings misfile concepts; a keyword search both misses real competitors and counts irrelevant ones.
• Anchoring on scary failure statistics. The famous numbers are disputed. The actionable fact is that location is a leading, and measurable, cause of the failures that do happen.

What does this look like in a real report?

Denzify runs this analysis for any US city and any food concept, not just the big categories: competitor set built from names, categories and reviews inside the 800-meter radius, residential and daytime demand from Census ACS and LODES, foot-traffic anchors from transit, offices and schools, and a 0 to 100 grade benchmarked against comparable cities. You can see the full structure in the sample report, built for a food concept in Boston, before spending $149 on your own market.

Walk the block first. Count your honest competitors by hand. Then, before the lease gets signed, run the numbers on your exact market and find out whether the demand for your cuisine, at your price, at your hours, is actually there.