The Problem Nobody Admits Out Loud
VTS is the system of record for commercial real estate leasing. Every major Class-A landlord is on it. The pipeline, the lease expirations, the encumbrances it all lives in VTS.
And yet, the data inside VTS is only as good as the broker who last updated it.
"The dashboard says we have twelve active deals. I called three of those tenants last week. Two have already signed elsewhere. The system just hasn't been updated."
The platform is excellent at holding leasing intelligence. It was never designed to collect it automatically, share it with the construction teams who need to execute on it, or connect it to the financial systems that need to report on it.
What It Actually Feels Like
"Brokers update deal stages when they remember to. The dashboard is a best-guess, not a live picture.""IRR modelling always ends up in Excel anyway. VTS gets us to a point and then we export.""The mobile app is a different product. On-the-go brokers stop logging activity because it's too clunky.""Legal and third-party brokers are outside the system entirely. The collaboration breaks at the boundary.""We have a niche industrial portfolio. The standard fields don't fit. We've been working around it for two years."
The Tech Reality
1. Data lag from manual input VTS depends on brokers updating deal stages in the platform. In practice, updates happen when brokers have time — which means dashboards reflect last week's reality, not today's.
2. Financial modelling exits the system IRR, NER, and lease economics modelling frequently require adjustments that VTS's native tools don't accommodate cleanly. The work moves to Excel. Now there are two versions of the financial truth.
3. Mobile friction breaks field logging The gap between VTS's desktop capability and its mobile experience is significant enough that on-the-go activity logging stops happening.
4. External collaboration breaks at the boundary Legal teams, third-party brokers, and joint venture partners don't have VTS access. The moment a deal requires external collaboration, the workflow reverts to email chains.
5. Rigid field structure for niche assets Specialised industrial properties, data centres, life science facilities don't map cleanly to VTS's standard field structure.
The Construction Reality
For a construction team, every signed lease in VTS represents a Tenant Improvement project waiting to happen. And the information that determines the scope, budget, and timeline of that project is locked inside a leasing platform that construction has no access to.
The scope gap silo The estimator who prices the TI allowance works from the lease's Work Letter. The PM who executes the build inherits the project with whatever assumptions were made during leasing.
Version control hell Drawing revisions happen during the design and leasing process before construction begins. Estimators pricing from Rev 2 while the PM is already coordinating with subs on Rev 4 is a coordination failure.
Manual data re-entry When a lease executes in VTS, someone manually creates the project in Procore, sets up the job in Sage, and transcribes the Work Letter requirements into a construction scope document.
Reactive forecasting Without a live connection between VTS deal timelines and construction resource planning, project managers find out about upcoming TI projects when the lease is already executed.
Fragmented communication Change order decisions that affect both the lease economics and the construction budget get made in email threads that neither VTS nor Procore captures.
The Economic Layer
Leasing velocity determines cash flow timing. When VTS dashboards are stale, occupancy forecasts are wrong. When occupancy forecasts are wrong, distribution timing is wrong.
Tenant improvement costs are the largest variable in asset-level returns during lease-up. When the construction cost for a TI project isn't connected to the lease economics in VTS, the asset manager is making capital deployment decisions without knowing the full cost of the lease they just signed.
Lease expiration management is the core function of VTS and when the data isn't current, the window to re-engage a tenant before their expiration becomes actionable intelligence too late.
Building the Right System Around VTS
Automated lease-to-project workflow When a lease is marked Executed in VTS, an automation workflow creates the project in Procore and the job in Sage Intacct automatically. The Work Letter gets parsed by an AI agent and the TI scope items are flagged for the estimator to price.
Live deal stage synchronisation Instead of depending on broker manual updates, we connect VTS deal stage triggers to external data sources executed documents, legal sign-offs, financial approvals that update deal status automatically.
Automated floor plan digitalisation Static AutoCAD floor plans convert to VTS-ready interactive digital assets that update automatically as leases are signed and TI work changes the floor plate configuration.
Financial model integration Lease economics from VTS sync directly into the asset-level financial model. TI cost actuals from Procore and Sage feed back into the same model.
Lease expiration intelligence Expiration timelines in VTS trigger automated re-engagement workflows internal alerts to the leasing team, CRM tasks for tenant outreach, and asset manager dashboards showing occupancy risk by timeline.
Before vs. After
Before
- VTS dashboards reflect manual updates, not deal reality
- Lease execution triggers a manual project setup process in Procore and Sage
- TI scope assumptions diverge from field reality with no connection point
- Financial modelling lives in Excel, disconnected from the live lease record
- Lease expirations surface as urgent problems instead of planned opportunities
After
- Deal stages update from external triggers — the dashboard is live
- Lease execution automatically creates projects in Procore and Sage with scope pre-populated
- TI actuals feed back into lease economics in real time
- Financial model stays connected to live lease and construction data
- Expiration intelligence triggers proactive re-engagement workflows automatically
Project Lifecycle Orchestration (Northspyre Integration)
For real estate owners and developers managing active TI construction programmes alongside a live leasing pipeline, Monexo implements a full Project Lifecycle Orchestration layer connecting VTS, Procore, and Northspyre. Northspyre acts as the intelligence layer above the construction stack tracking every budget line item, contract, and change order against the original TI estimate in real time, and using predictive AI to identify cost overruns thirty to sixty days before they appear in a month-end report.
The Real Insight
VTS is where leasing intelligence lives. Procore is where construction execution happens. Sage is where the financial truth is recorded. Northspyre is where the investment returns are tracked.
None of these systems were designed to talk to each other. And in the space between them between the signed lease and the completed TI, between the occupancy forecast and the actual cash flow is where asset returns get eroded.
We build the system.