How investors read a retail market before a deal

An investor reads a retail market before a deal by measuring the ground around every branch of the target, not just the target's own numbers. For each store: how many competitors sit within a short distance, how many of them are chains, how well they are rated, how many opened or closed lately, and how busy the area is. Laid side by side, those figures show which branches are protected, which are exposed, and whether the management's growth plan fits the streets it names.

This article is for private equity and venture teams, corporate development, lenders' credit analysts and the consultants they hire for commercial due diligence. It covers what to measure, how to read it without being misled, a worked example on a grocery market, the mistakes that slip into data rooms, and how an AI employee keeps the picture current until closing.

What a market read for due diligence covers

A data room gives you the target's sales by store. It rarely gives you the market each store trades in. A location read adds that outside view, branch by branch:

• Competitive density. Rivals of the same type within, say, 500 m and 2 km of each branch, from Nearby places set to count around each incoming place.
• Who the rivals are. The share that belongs to a chain, and which chains. A branch surrounded by independents faces different pressure from one next to a national grocer.
• How customers rate them. The average rating of rivals against the target's own rating at that branch.
• Movement. Openings in the last 12 months nearby, and rivals that closed, from the Opened setting and the What changed block over a few weeks.
• How busy the area is. Footfall per day around each branch from Mobility Footfall, measured in people-hours of presence, where the data covers the city.

How to read it

Read the branches against each other first, then against the market. A branch with twice the rivals of the median branch and falling sales is a different story from one with twice the rivals and rising sales: the second may sit in a strong destination. Ratings matter most where the gap is wide: a target branch rated well below the rivals around it is a churn risk the sales history may not show yet.

A worked example: a grocery chain

Suppose a fund is looking at a mid-sized grocery chain with branches in three cities. City-wide figures first set the scene. xMap's places database lists 1,332 supermarkets within 10 km of the centre of London; of the 437 nearest the centre, 296 (68%) belong to a chain, led by Tesco (110) and Sainsbury's (101). Toronto lists 82 supermarkets in the same circle, 28 of them (34%) chains. Sydney lists 190, with 75 (39%) chains, led by Coles (34) and Woolworths (24).

Within 10 km of each city centre, xMap's places database, November 2026.

These are city figures, not the target's markets, but they frame the questions. A grocer in central London competes mostly with national chains; in Toronto and Sydney the independents are a bigger part of the field. The fund's next step is the branch-level table. In this made-up case, the chain has 40 branches. The read shows 6 branches with no rival supermarket within 500 m, 9 where three or more chain supermarkets opened within 2 km in the last year, and 4 where the branch is rated half a point below the average rival. Those 13 branches become the questions for the management meeting, and the visit list for the site tour.

Mistakes to avoid

• Using one city-wide count for every branch. Competition is local. A city with many supermarkets can still have quiet pockets, and the other way round.
• Treating a listing count as sales. The count says how many stores exist, not how much they sell. It frames the question; the data room answers it.
• Reading the chain share of a big city as if it covered the whole count. For large markets the chain share is worked out from the stores nearest the centre. Say so in the memo.
• Freezing the read at signing. A rival opening next to a key branch between signing and closing matters. Keep the read running until the deal closes.

Doing it with an AI employee

Upload the target's branches as a table in My data and build the read once. The blocks in order: My data (the branches), Nearby places (counting rivals around each branch, chains and independents, ratings, opened in the last 12 months), Mobility Footfall (footfall per day and the trend), an xMap LLM block that writes a one-line comment per branch from those figures and flags the exposed ones, then Make a report for the deal team and a map.

Put it on a weekly Schedule with What changed, and the deal team gets a short note each Monday: rivals that opened or closed near a branch, and ratings that moved. The templates Competitor density around each site and Ratings of my portfolio companies' branches cover most of it, and Store visit route for a due diligence trip plans the site tour.