Site Selection Intelligence
A geospatial-and-economic data platform that fuses zoning, transit, demographic, employment, and permit-activity data — produces investment-scoring heatmaps at parcel and neighborhood granularity, configured to the fund's investment thesis.
- Engagement
- 8–12 week build · ongoing per-market refresh
- Built for
- Developers · RE-focused PE · REIT acquisitions
Site selection is part data work, part instinct — developers and acquirers know roughly where to look, but the data layer that filters thousands of parcels down to the dozens worth visiting is built ad hoc per deal.
What this is
A geospatial intelligence platform for site selection at scale. Three layers:
- Data fusion. Public and licensed data layers — zoning, transit, demographics, employment, permits, comparable transactions — joined at parcel and submarket granularity.
- Scoring. Per-fund thesis encoded as a configurable rubric. Per-market calibration to reflect local-context patterns.
- Visualization. Interactive heatmaps at multiple granularities. Drill-down from market to neighborhood to parcel.
How it's built
PostGIS as the spatial backbone, dbt for transformation logic, Mapbox or MapLibre for visualization. Per-jurisdiction permit-data ingestion is the labor-intensive piece — we maintain a corpus of jurisdiction adapters and add new jurisdictions per engagement.
What you get
- Per-fund scoring rubric, configured and versioned.
- Interactive map UI with multi-granularity drill-down.
- Per-jurisdiction permit-feed coverage in the fund's target markets.
- Quarterly per-market refresh.
- Export-able heatmaps for partner decks.
Engagement is shape, not list.
Length and price are functions of the data and the destination. The shape below is the typical engagement.
- Length
- 8–12 week build · ongoing per-market refresh
- Lead
- Bogdan
- Cadence
- Async, weekly
- Bar
- Production
Scoped during the discovery call against the actual data and the operation it integrates with.
Principal engineer. Architecture and most code ships through one keyboard.
Written updates between, calls when the decision needs the room.
Async correctness, capacity under burst, observability at every boundary.
Products this composes with.
Same suite, or vertical-specialized versions in another.
What buyers ask about this one.
What data layers do you integrate?
Zoning and entitlement (per-jurisdiction from public records), transit (GTFS feeds, walkability scoring), demographic trajectory (Census ACS plus higher-frequency American Community Survey-class panels), employment (BLS QCEW, regional commuter flow), permit activity (per-jurisdiction permit-application history as a leading indicator). Per-fund, the weighting is configured.
How is the scoring built?
Per-fund thesis encoded as a scoring rubric — sector affinity (multifamily, industrial, retail), submarket characteristics, growth signal weighting. The rubric is auditable and versioned. Outputs are heatmaps at the right granularity (parcel, census tract, or neighborhood depending on the deal type) plus underlying scoring data.
Can it identify under-the-radar markets?
The product surfaces markets where the leading-indicator signals (permit activity acceleration, employment-base shifting, demographic trajectory) suggest re-rating before it's visible in cap-rate compression. We're upfront that 'under-the-radar' is partly a function of what your fund already covers — the engine adds signal weight to markets you haven't traditionally looked at, not to markets nobody has looked at.
What about international markets?
US is the primary coverage. UK, Canada, Australia supported where the public-data infrastructure permits. Other markets per-engagement, with explicit caveat about data depth.
Pricing?
Scoped to market coverage and the depth of per-market data integration. Discovery call covers both.
If the deliverable matches the gap, the next step is one call.
We'll scope length and price against your data and the operation it integrates with. No retainer, no fishing.
Bogdan and team · async-first · OP—2026