What actually determines who wins a leasing surge?
The owner who wins a demand spike is the one whose leasing process can absorb it — capture every tour, track every open lease, and keep broker updates in one place — not the one with the marquee building. Brookfield is buying into the $3.5 billion Hudson Square Properties portfolio as tech and AI tenants push West Side Manhattan rents up roughly 20%, according to Propmodo. That valuation is the visible result of demand meeting a process that held.
When tours triple in a quarter, the buildings don't change. What changes is the volume flowing through your leasing pipeline — the running list of prospects, tours, and proposals from first contact to signed lease. A pipeline that lived comfortably on a spreadsheet at ten active deals starts dropping details at forty. The details it drops are the deals you never knew you lost.
Why does a spreadsheet break under a surge?
A spreadsheet breaks because it has no memory of who did what, and no way to flag what's overdue. Under normal volume that's survivable. Under a surge, the same tool that tracked twelve deals now hides the follow-up nobody sent and the LOI — letter of intent, the non-binding term sheet that precedes a lease — that sat three days past its response date.
Three things go wrong at once:
- Follow-ups slip. More tours mean more people waiting on you. The prospect who toured Tuesday and heard nothing by Friday tours a competitor.
- Broker updates scatter. Outside brokers report deal status by email, text, and voicemail. None of it lands in the record everyone reads.
- Renewals hide. While you chase new demand, a lease expiration you didn't track comes due, and a paying tenant walks.
How do broker updates get lost — and what stops it?
Broker updates get lost because they arrive in the channels people actually use — text, email, a hallway conversation — and none of those channels is the system of record. The fix is to let updates enter where the broker already is, then land them in one shared rent roll and pipeline automatically, so the deal status everyone reads is the current one.
The point isn't to force brokers into new software during the busiest quarter of the year. It's the opposite: capture the voice note or the text, structure it, and file it against the right deal without a data-entry step. A leasing team that can trust the pipeline spends the surge selling space, not reconstructing who said what.
What keeps renewals from slipping while you chase new demand?
A tracked lease-expiration calendar keeps renewals from slipping. During a surge your attention goes to new tenants at higher rents — which is exactly when a quiet renewal window closes and an in-place tenant leaves. The renewal you kept is cheaper than the vacancy you fill twice, even in a hot market.
Every lease in the portfolio needs a visible expiration date, a renewal-notice deadline, and an owner. When those live in the same system as the pipeline, the surge doesn't pull people away from the book of business that already pays.
Four fixes to make before the next surge
The best time to fix a leasing process is before demand tests it. Four concrete moves:
- Put the pipeline in one place. One shared record of every prospect, tour, and proposal — not a spreadsheet per broker.
- Capture broker updates where brokers already are. Text and voice notes that file themselves against the right deal.
- Make lease expirations visible. A portfolio-wide calendar with notice deadlines and named owners.
- Stage the outbound, approve before it sends. Drafted follow-ups a person reviews, so speed never costs you an accuracy mistake in front of a tenant.
Where does governed software fit?
Governed software fits by drafting the work and leaving the decision to a person. Vantrow's principle is propose, never commit: the system stages the follow-up, updates the pipeline, and flags the lease coming due — then a human approves before anything is sent or committed, and every action lands on an audit trail.
During a surge that division of labor matters most. The volume that overwhelms a manual process is exactly what software absorbs well: capturing, structuring, drafting, flagging. The judgment that a surge makes valuable — which prospect to prioritize, what rent to hold — stays with the operator. You get the speed without handing a tenant relationship to an autonomous agent that acts on a guess. The result looks less like a rescue and more like a quarter where nothing fell through.
FAQ
What made the Hudson Square portfolio worth $3.5 billion? Demand did. Tech and AI tenants pushed West Side Manhattan rents up roughly 20%, and Brookfield is buying into the $3.5 billion Hudson Square Properties portfolio on the strength of that leasing, according to Propmodo. The valuation reflects demand meeting a leasing operation that could absorb it.
When does a leasing spreadsheet stop being enough? When volume outgrows a single person's memory. A spreadsheet has no way to flag an overdue follow-up or a lease coming due, so under a surge it quietly drops the details — the missed call-back, the past-due LOI — that turn into lost deals.
How do I keep broker updates from getting lost? Capture them in the channels brokers already use — text, voice note, email — and file them automatically against the right deal in one shared pipeline. The goal is no data-entry step, so the deal status everyone reads is always current.
Does governed software mean AI sends things to my tenants automatically? No. Under a propose-never-commit model the system drafts the follow-up, updates the pipeline, and flags renewals, but a person approves before anything sends. Every action lands on an audit trail, so speed never costs you control of a tenant relationship.