Site Selection Tools: How Many Does One Store Take?

Most retail site decisions we see pass through eight to twelve separate tools before anyone votes on them. The count is not really the problem. The handoffs between those tools are, because each one is a place where a person exports a number, retypes it somewhere else, and breaks the trail back to where it came from.

Ask a real estate director how many tools they use and you will get a shrug and a guess. Ask them to walk through the last site they took to committee, naming every file and app it touched on the way, and the list gets long fast. Most teams have never counted, because no single tool feels unreasonable on its own. The mapping software earns its keep. So does the demographics subscription. The cost hides in the seams.

The industry has noticed. JLL's 2025 Global Real Estate Technology Survey, which polled more than 1,000 senior commercial real estate decision-makers across 16 markets, found 81% of firms running at least three existing systems that are not generating the results they expected, and 88% putting budget toward upgrading legacy technology.

Count the tools on your last deal

Here is the chain a single candidate site walks through at a typical multi-location operator. Yours will differ in the details. The shape will not.

Two things stand out when you draw it. The first is that almost every arrow is a person. Data does not flow between these tools, it gets carried. The second is that the chain ends open. Actual sales from the opened store sit in a reporting system that has no path back to the forecast model that justified the site, so the one piece of feedback that would make the next forecast better never arrives. We wrote about what that does to a scoring model in why the highest-scoring site can become your worst store.

The cost sits in the handoffs, not the licenses

When teams try to price this, they add up subscriptions. That is the wrong ledger.

A 2022 Harvard Business Review study by Rohan Narayana Murty, Sandeep Dadlani, and Rajath B. Das tracked 137 people across three Fortune 500 companies and found they toggled between applications nearly 1,200 times a day, spending just under four hours a week reorienting themselves after each switch. That works out to about 9% of their annual time at work. One transaction in that dataset took roughly 350 toggles across 22 different applications and websites. Different industry, same chain.

Three costs matter more than the subscriptions, and none of them show up on an invoice.

Re-keying. Every manual handoff is a transcription. A population figure gets read off one screen and typed into another. A trade area gets redrawn by eye because the second tool cannot import the first one's boundary. Nobody catches these, because a plausible wrong number looks exactly like a right one. Ray Panko's compiled spreadsheet research puts cell error rates in controlled experiments at roughly 1% to 6%, and separate audits of real working spreadsheets found at least one error in 83% to 91% of them, depending on the study set.

Version drift. The comp table lives in a spreadsheet, the spreadsheet gets emailed, and the person who updated the rent assumption on Tuesday is not the person presenting on Thursday. By committee, at least two versions of the analysis exist and the room is arguing about which is current instead of whether the site is good.

Elapsed time. This is the expensive one. The work itself might be six hours. The calendar time is nine days, because each stop waits on someone to get to it. A broker who has to wait nine days for a yes has already shown the space to two other tenants. The full sequence of that work is laid out in our site selection process guide, and every phase in it is a place the chain can stall.

Four places the stack breaks

Fragmentation does not announce itself. It shows up as four specific failures that real estate teams tend to blame on other things.

The number nobody can trace. Someone in committee asks where the sales forecast came from. The honest answer involves four tools, two exports, and a spreadsheet tab from a model built by an analyst who left last year. The forecast might be right. It is not defensible, and defensibility is what the room is actually voting on.

The refresh you will never do. Suppose the criteria change. Minimum daytime population moves, or a competitor announces forty new units in your region. Re-scoring the forty sites in your pipeline against the new bar means walking the entire chain forty times, so it does not happen. The pipeline keeps running on assumptions the business already abandoned.

Cannibalization caught late. Checking whether a new site steals from an existing one requires the trade area, your current store locations, and customer overlap in the same view at the same time. When those live in three tools, the check becomes a special project rather than a default, and it tends to get done after the LOI instead of before. Our guide to cannibalization analysis covers the mechanics; the workflow question is whether anyone can run it in an afternoon.

The bus factor. One person knows the chain. They know which tab holds the real assumptions, which export needs cleaning first, which map layer is out of date. When that person is on vacation, site evaluation stops. At a one-to-three-person real estate team, which is what most 100-unit operators run, this is not a hypothetical.

What changes when the evaluation lives in one place

The payoff shows up in the week, not on the software bill.

Cavender's cut analyst time per site evaluation by 50% and has run more than 2,000 sites through the platform across new and existing markets, going from 9 new stores in 2024 to 27 in 2025, with every new location performing at or better than expected. Lil Sweet Treat, a two-person founding team with no analysts on staff, went from three weeks per site evaluation to two days and now reviews 120-plus sites a month. Books-A-Million, the number two book retailer in the US at 260 stores, freed up about 25 hours a week per analyst and moved from roughly 5 to 10 site evaluations a week to more than 3,000 a year.

Those numbers are the same story told three ways. When the trade area, the demographics, the foot traffic, the competitor set, and the score sit in one place, the analysis stops being an assembly job. The committee packet stops being rebuilt from scratch. And the deal record keeps the inputs attached to it, so when someone asks in month eight why you picked this site, the answer is still there. That is also what makes the deal pipeline worth having in the same system as the scoring, rather than as a separate tracker somebody updates on Fridays.

The honest version of the spreadsheet story is a little more nuanced than "spreadsheets are bad." Spreadsheets are a fine calculator and a poor workflow, and we went through where exactly that line sits in the case against spreadsheet-based site selection.

What you should not consolidate

Consolidation gets oversold. Most of your software is not part of this problem, and moving it would cost you a migration for no return.

Your GIS and your demographics subscription both describe the same trade area, so keeping them apart means somebody reconciles them by hand every time. Your lease administration system and your accounting system describe different things at different times, and they should stay where they are.

The same logic applies to input data you already pay for. If you have an Esri license your team knows well, or a foot traffic subscription with two years left on it, those are inputs and they can keep feeding an evaluation workflow. Ripping them out is not a prerequisite for fixing the handoffs, and a team that insists it is usually wants the contract more than the outcome. If you are shopping the category rather than auditing your own process, our retail site selection software comparison covers the platforms directly.

Audit your own stack in an afternoon

You do not need a consultant for this. Take your last closed deal and walk it backward.

1. List every surface the site touched. Inbox, spreadsheet, map, data subscription, model, deck, tracker, drive. Include the ones that feel too small to count, like the group chat where the rent got renegotiated.
2. Mark every manual handoff. Anywhere a human moved a number between two of those surfaces, put a mark. This is your real count, and it is the one that costs money.
3. Find the numbers you cannot trace. Pick three figures from the final committee packet and try to get back to their source in under two minutes each. Whatever you cannot reach is a defensibility gap.
4. Compare hours worked to days elapsed. Add up the actual working hours, then count calendar days from broker email to decision. The ratio tells you how much of your cycle time is waiting rather than working.
5. Ask what a criteria change would cost. If your minimum trade area population moved next week, how many hours to re-score the live pipeline? If the answer is more than a day, your pipeline will go stale the next time the business shifts and nobody will notice until a committee meeting.
6. Name the single point of failure. Who is the one person who can run the whole chain? Write the name down. That is your bus factor, and it is a staffing risk, not a software one.

Six answers, one afternoon. You will come out of it with a handoff count instead of a tool count, and a short list of which handoffs are worth removing first.

Frequently Asked Questions about site selection tools