Your analysts open a browser, pull up CoStar, copy rent comps into a spreadsheet, switch to ESRI, grab demographics, switch to your PM system, pull portfolio data, then manually type all of it into your acquisition model. For every deal.
By the time the model is populated, reviewed, and presented to your investment committee, half the inputs are already outdated. A new comp hit the market. Demographics data refreshed. A lease in your portfolio renewed at different terms. Your model does not know any of this because it is frozen at the moment someone last typed numbers into it.
The Problem with Static Models
Every acquisition team has a model they are proud of. The financial logic is solid. The waterfall works. The sensitivity tables are well-built. But the data feeding that model is the weak link.
Manual data entry creates three problems. First, it is slow. An analyst spends 2 to 4 hours per deal just gathering and entering external data before they even start analyzing the opportunity. Multiply that by 10 to 15 deals per week during an active screening period and you are burning 20 to 60 hours a week on data entry, not analysis.
Second, it is error-prone. Copy a rent comp from CoStar, paste it into your model, and now you have a number that lives in two places with no connection between them. If the comp gets updated, your model does not know. If someone fat-fingers a number during entry, you might not catch it until IC.
Third, the data goes stale immediately. The moment you type a number into a cell, it starts aging. Demographics data from last quarter is already old. Rent comps from two weeks ago might not reflect the latest leasing activity. Your model presents a snapshot of a moment in time, not the current state of the market.
If your IC is making decisions based on data that was manually entered a week ago, they are not looking at the deal as it exists today.
What a Connected Model Looks Like
Imagine opening your acquisition model, entering the property address, and watching the rest populate. Demographics for the 3-mile radius pull from ESRI automatically. Rent comps within your defined parameters pull from CoStar. Your existing portfolio data (if you own nearby assets) feeds from your cloud lakehouse. Tax records, flood zone data, and walk scores fill in without anyone touching a browser.
The analyst's job shifts from data entry to data review. They look at the comps the model pulled and decide which ones are truly comparable. They review the demographics and adjust growth assumptions. They examine portfolio performance data and use it to inform underwriting. The judgment calls remain with the analyst. The tedious data gathering does not.
And here is the important part: when you re-open that model two weeks later for IC, the data refreshes. New comps are included. Updated demographics are reflected. Your model shows the deal as it looks today, not as it looked when someone first built the file.
How It Works (Without the Jargon)
The technical architecture is simpler than it sounds. There are three layers.
First, the data connections. Services like CoStar, ESRI, and your PM system all have ways to share data programmatically (called APIs). Instead of your analyst logging into each platform and copying data manually, a connection pulls that data automatically when requested.
Second, the data layer. This is a centralized place where all that external data gets stored, organized, and kept current. We build this on Microsoft Azure, deployed inside your tenant. It acts as the single source of truth that your models, dashboards, and reports all draw from.
Third, the Excel integration. Your acquisition model connects to the data layer using built-in Excel functionality (Power Query). When you enter a property address, the model queries the data layer, which in turn pulls the latest from CoStar, ESRI, and your internal systems. The data lands directly in your model, in the cells where it belongs.
No new software to learn. No platform to log into. Your team still works in Excel. The data just arrives differently.
What Changes for Your Team
Deal screening time drops from hours to minutes per property.
Data entry errors are eliminated because there is no data entry.
IC presentations use current market data, not last month's.
Analysts spend time on analysis, not on toggling between browser tabs.
Is This Worth It for Your Firm?
If your acquisition team screens more than 5 deals per week, the time savings alone justify the investment. If you have ever caught a data entry error in an IC memo, the risk reduction justifies it further.
The firms where this creates the most impact are the ones evaluating a high volume of deals with lean teams. When you are screening 50 to 100 opportunities per month with 2 to 3 analysts, every hour counts. Eliminating 2 to 4 hours of data gathering per deal means your team can either screen more deals or go deeper on the ones that matter.
This is not about replacing your analysts or your model. It is about removing the lowest-value work from their plate so they can focus on what you actually hired them to do: evaluate investment opportunities.
Connect Your Models to Live Data
We build connected acquisition models, Power BI dashboards, and AI agents on top of your data layer. Start with our Operate engagement or explore our Tool Library.