All solutions
Illustrative example — a representative workflow, not a named-customer case study. The data fields and product capabilities are real; the scenario and any figures are sample composites.
Development · Site selection

Spotting where construction accelerates first

Development decisions reward whoever sees the trend first. Permit activity is one of the earliest hard signals that a submarket is heating up — it precedes completions, absorption, and most published indices. This is how a site-selection team turns a national permit feed into a momentum map.

Place → stateConsistent rollups on one schema
QoQVelocity by market and project type
EarlySignal ahead of completion-based reports

The challenge

Trends show up in the data long after they show up on the ground

By the time a submarket appears in a completions report or an absorption index, the window to act on it has narrowed. A development team needs to read momentum at the leading edge — and permits are about as leading as a hard, public signal gets. The problem is that permits arrive as a fragmented mess of municipal records that resist any consistent rollup.

Without a normalized base, comparing two metros means reconciling two different portal schemas, two different ways of classifying work, and two different municipal geographies. That reconciliation is exactly the work that prevents most teams from watching the whole country at once.

The approach

Roll permit counts and valuations up to a clean geography

Builders Monitor keys every permit to the TIGER municipal universe, so counts and valuations roll up cleanly to place, county, and state on one consistent schema. A site-selection analyst can rank markets by permit velocity, segment by project type, and watch the quarter-over-quarter change — across the whole country, in one view.

The same standardization makes the comparison honest: a residential subdivision permit in one state lines up against the equivalent in another, because both have been normalized into the same work-class taxonomy before they're counted.

The outcome

A shortlist driven by momentum, not memory

The team replaces gut-feel market lists with a momentum-ranked shortlist that updates as new permits land. Instead of defending why a market is on the list, analysts can point to its permit trajectory — and catch the inflection in a submarket while there's still room to move.

Permits are about as leading as a hard, public signal gets — the trick is reading them on one geography so two markets can actually be compared.

Illustrative — site-selection workflow

The workflow

How it runs in the product

  1. 1
    Map

    See momentum geographically

    Visualize permit density and valuation by place and county, then watch how the hot zones shift quarter over quarter across a region or the whole country.

  2. 2
    Search

    Segment by project type

    Slice the feed to the project types you build — single-family, multifamily, commercial — so the momentum signal reflects your actual product, not all construction noise.

  3. 3
    Exports

    Pull the rollups into your model

    Export place/county/state aggregates of counts and valuations and drop them straight into the feasibility model your team already runs.

  4. 4
    API

    Refresh the signal automatically

    Wire the same query to the API so your momentum dashboard re-ranks markets on a schedule instead of on a manual pull.

What powers it

The data behind the workflow

Each field below is a real product capability — normalized across thousands of municipal portals into one schema.

  • permit.issued_dateAnchors velocity and quarter-over-quarter change.
  • permit.valuationWeights activity by project size, not just count.
  • permit.work_classIsolates the project types you actually develop.
  • geography (TIGER place / county / state)Consistent rollups for honest cross-market comparison.
  • jurisdiction coverageNational breadth so no rising market is invisible.

See it for your team

Start free with 50 record lookups a month. Search and browse are always free — you only spend a lookup when you open a full record.