Turn raw population, income, and competition numbers for a candidate site into a clear read on whether it fits your unit model, before you commit to a lease.
Analyze this candidate site against our model and tell me if the demographics fit: [site and trade area], with this data: [population, income, and competition figures].
An illustrative example. Your output will reflect your own sources, data, and prompts.
I've held the Westgate site against the model thresholds in your site-selection criteria. Three of the four drivers clear with room to spare, and there's one flag worth pricing into the forecast.
The demographics clear the model on population and income, with one flag on competitor proximity. Here are the four numbers that drive the decision.
Trade-area population of 78,400 sits comfortably above the 60,000 our units need to hit first-year sales, and it's still climbing, up 4.1% since 2023, the trend we look for rather than a market that has already peaked. Median household income of $71,200 clears the $65,000 floor, and the daytime population of 96,500 is a real asset: this corridor pulls in office and retail workers, so lunch traffic won't depend on residents alone.
Side by side against the model floors, the two make-or-break drivers clear with room to spare: trade-area population of 78,400 against a 60,000 floor, and median income of $71,200 against $65,000.
| Driver | This site | Model floor |
|---|---|---|
| Trade-area population | 78,400 | 60,000 |
| Median income | $71,200 | $65,000 |
Net read: this is a fit. Three of the four drivers clear the model with room to spare, and the one flag, a competitor at 1.8 miles, is a reason to sharpen the sales forecast, not to pass. I'd advance it to a site visit and pull the competitor's traffic pattern before you sign the LOI.
Want me to build the market-opportunity one-pager for this site, or stack it against your other candidate sites using the same trade-area data?
You get census pulls, drive-time reports, and competitor lists for candidate sites, but turning that into a yes-or-no on fit means holding a dozen numbers against your model in your head. So sites either stall waiting for analysis or advance on gut feel.
Paste the trade-area population, median income, daytime population, and competitor distances, or point Joy at the demographic report already in your Knowledge Center. Rough figures are fine.
Ask "Does this site fit our model?" Joy holds each number against the thresholds in your site-selection criteria and flags anything outside the range.
Get a KPI snapshot with good and watch cues, a factor-by-factor breakdown, and a plain verdict on whether to advance the site, pass, or dig deeper.
Copy the read into your site packet, your LOI file, or the deck you take to the real estate committee. Ask follow-ups to compare it against other candidates.
Save this ask as a custom command on the assistant your team already uses (wire in your own model thresholds and wording) so anyone can run it in one step.
Every number is held against the population, income, and distance floors your successful units share, not generic benchmarks.
See at a glance which drivers clear the model with room to spare and which sit inside your caution band and need a closer look.
Factor nearest-competitor distance into the forecast so you model shared trade area honestly instead of assuming exclusivity.
Ask Joy anytime to stack one candidate site against another so you can rank your pipeline by fit, not by which broker called last.
Score the site on a 10-minute drive-time ring instead of a fixed radius for car-dependent markets.
Weight daytime and foot-traffic population heavily for a downtown or transit-hub location.
Frame the read as a clean market-opportunity page for the real estate committee.
Center the analysis on households with children when that segment drives your weekend volume.
Paste the trade-area population, median income, daytime population, and competitor distances for the site into JoySuite. Joy holds each number against your model's thresholds and returns a plain verdict on whether the site fits, which drivers clear, and which to watch.
It depends on your model, but most operators weigh trade-area population, median household income, daytime population, growth trend, and competitor proximity. JoySuite scores each against the floors your successful units share rather than generic industry benchmarks.
Yes. Feed it the data for each site and ask Joy to stack them side by side. You get a ranked read on fit so you can prioritize your pipeline instead of chasing whichever site a broker surfaced most recently.
Yes. Joy factors nearest-competitor distance into the read and flags when a site sits inside your preferred buffer, so you forecast the first year assuming shared trade area rather than assuming exclusivity.
JoySuite works with the data you provide or the demographic reports in your Knowledge Center. It doesn't scrape live census systems. You bring the pulls, and Joy turns them into a defensible fit verdict.
Join the waitlist and be first to try this workflow when JoySuite launches.