A readout to a client's leadership team
Case study

Colliers screens 4x more deals a week with an automated valuation model

Valuation data sat across regions and legacy systems, so a first-pass valuation took days and capped how many deals the team could screen.

Colliers

Colliers · Underwriting and risk · L2

4xmore deals screened each week

The workflow before#

Colliers works in more than 70 countries, and its investment teams screen properties for clients every week. The data they needed for that sat in a legacy enterprise warehouse, regional systems and third-party market feeds. Analysts pulled numbers from each and consolidated them in Excel, so a standard report took 2 to 5 days. A first-pass property valuation took 3 to 5 days of gathering comparables and checking figures, which held screening to about 50 deals a week. Replacing the legacy systems wasn't on the table: a full cloud migration was too costly and too risky for systems that still did their jobs.

What we built#

We built Colliers a data lake that sits beside its legacy systems instead of replacing them, then put an automated valuation model on top. The lake pulls valuation, property, market and financial data into one place. The model reads it and returns a first-pass value with a confidence score and the reasons behind it. Analysts spend their time on the deals worth a closer look.

A data lake beside the old systems

Pipelines copy data from the enterprise warehouse, regional systems and market feeds into raw, standardized and business-ready layers, and Snowflake serves data marts for valuation, investment, property and finance. The legacy systems keep running untouched. We chose to build alongside them because it gave Colliers the new capability without betting operations on a migration.

Valuations with their reasons attached

The valuation model combines several machine learning models trained on property characteristics, comparables and alternative data. Every estimate comes with a confidence score and the main drivers, such as nearby comparables or market momentum. We showed the drivers because an analyst won't take a number into a client meeting without being able to explain it.

Reports teams build themselves

Power BI reads the business-ready marts directly, so a standard report that used to take days of Excel consolidation now refreshes in under an hour. Regional teams work from the same definitions, which ends the arguments about whose spreadsheet is right.

A catalog and models that stay honest

A data catalog tracks where each field came from and flags sensitive ones, with a shared business glossary. The valuation models retrain on a schedule and are backtested by property type and region, so accuracy is measured where it matters instead of only on average.

How we delivered it

We stood up the lake first, then the marts and reporting, then the valuation model once the data under it was clean. Old and new ran in parallel during rollout, and analysts compared model values with their own first passes on live deals before relying on them for screening.

Before and after#

MeasureBeforeAfter
First-pass valuation3 to 5 daysUnder 1 hour
Valuation error (MAPE)12 to 15%8 to 10%
Deals screened per weekAbout 50About 200
Standard report generation2 to 5 daysUnder 1 hour

What's next#

The next step is an agent that runs deal screening end to end. It would pull comparables, run the valuation model and draft the screening memo, then hand the analyst only the exceptions and the deals that clear the bar. The lake and the model are the parts it needs.

ShareLinkedInEmail

Azure Data Factory and Azure Synapse run change data capture from the legacy EDW and API pulls from third-party sources into Azure Data Lake Storage Gen2 in bronze (raw), silver (standardized) and gold (business-ready) layers. Snowflake virtual warehouses are sized by workload with auto-suspend and resource monitors, authenticate through Azure AD, and serve valuation, investment, property and financial marts to Power BI.

The valuation model is an ensemble of gradient boosting, random forest and XGBoost models built with scikit-learn, with feature pipelines for geospatial proximity, market momentum and derived ratios. Training, versioning and deployment run through Azure Machine Learning and MLflow, with cross-validation and backtesting by property type and region and alerts on performance drift.

Azure Purview provides the catalog, lineage, classification of PII and financial data, and the shared business glossary. Legacy operational systems were left unchanged, and old and new ran in parallel during rollout.

Next step

Let's build the case study we tell next.