How we build forecasts you can defend.
Every step, showable. From which government data we ingest, to how we turn it into features, to the exact formula that produces the forecast, to the test we put the forecast through before shipping. A forecast you can’t explain to an investment committee isn’t worth publishing.
Data ingestion
Eight federal and open sources pulled on their native cadence (daily, weekly, monthly, annual). All raw responses versioned to S3 before any transformation.
Feature engineering
Raw series are cleaned, normalized to MSA boundaries, seasonally adjusted where appropriate, and combined into ~120 features per market per month.
Model fit
Baseline: a mean-reverting momentum blend (local YoY × national drift × national mean). Research track: per-metro regressions on the observable feature panel, refit monthly. All model versions are retained so any historical forecast is reproducible.
Forecast + intervals
12-month-ahead point forecasts with 80% confidence bands. Forecasts are versioned — every historical forecast is recoverable for audit.
Validation
Walk-forward backtests refit the model on data strictly prior to each holdout period, then score MAPE and direction hit-rate against naive-persistence and trailing-mean baselines. Both expanding and rolling-window variants are published per market.
Publication
Forecasts published through the product, API, and research notes. Every number cites its underlying feature weights and data lineage.
We publish our forecast errors.
Out-of-sample mean absolute error against the FHFA HPI release, on 12-month horizons, refreshed monthly.
Terms we use.
One-page summary
The equation, the inputs, the live coefficients, the latest accuracy numbers, the data freshness. For prospects who want the read in 60 seconds.
Full technical spec
Features, training protocol, full accuracy metrics (MAE, RMSE, WMAPE, MdAPE, skill score), and reproducibility instructions.