<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/4158cfcfc12c41a4b3bffc0ce2a10020&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/4158cfcfc12c41a4b3bffc0ce2a10020-04ed65f1ac938913.gif</thumbnail_url><duration>298.731</duration><title>Real Estate Price Model Lessons Learned ⚡</title><description>Hi guys, I wanted to share a proof of concept solution for a real estate company and the lessons I learned from it. We only had a little over 2,000 transactions to train a model to predict property price, and the simulations did not fully mimic real life due to poor location data, unrealistic temporal patterns, and asset value issues. Because asset value was not available for customer searches, I built two models, a fallback model without asset value for customers and an assessment aware one for agents to reduce workload. The agents can also see similarity property ranking for nearby price matches. No specific action was requested, I just wanted to document what we would need to improve for large scale.</description></oembed>