Scout answers "what is out there", not "what is this one worth". You name a territory and the constraints; it enumerates assessor and parcel rolls and comes back with a longlist of candidates.
243 runs since January, 103 in the last thirty days.
How to run it
Give it a place in plain words — a city, a county, a corridor. Or draw a polygon on the map, which becomes the search geometry exactly.
Set minimum and maximum area or budget. No file is needed.
What comes back
An interactive report listing the candidates with what is known about each — 61% of runs in the last thirty days. It does not produce a deck, and it produces a workbook about once in a hundred runs.
Median 37 minutes, 90th percentile 81. Median 6.1 credits.
Do
- Draw the polygon when the boundary matters. "The corridor north of the river" is a sentence; a polygon is a search area, and the difference shows in the result.
- Set the constraints you actually have. Area and budget bounds do more to improve a longlist than more words describing the area.
- Check coverage before you run, not after — see below.
Do not
- Do not run Scout outside the United States. This is the limit that decides
everything: it enumerates US parcel rolls and nothing else, and the non-US path
is switched off in production.
The failure is quiet and that is what makes it dangerous — a search outside coverage does not error. It comes back empty, which reads exactly like "nothing matches your criteria", and you will conclude the market is empty when in fact our register is. - Do not assume a US state is covered. Coverage is uneven: a statewide roll in 19 states, listed counties only in 23, and nine states not registered at all. Georgia is four counties; California is eleven of fifty-eight. Coverage and data has the lists.
- Do not read a thin longlist as a market finding until you have checked which of those two it is.