← Back to the homepageGet a Leak Map →
Case study · Commercial real estate

A NYC CRE firm found five leaks. Three were fixed in the first eight weeks.

A 6-person owner-operated firm running commercial real estate in New York. Underwriting rebuilt by hand on every deal. A controller pinned to one asset. Broker outreach going out through a mail merge with nothing coming back. This is what the Leak Map surfaced, and what shipped against it. One line item alone — a controller 80% absorbed — runs $64K–96K a year in absorbed labor.

Staff
6
Leaks found
5
Fixed
3
Elapsed
8 wks
The leak map · as delivered
YARDILEASE DOCSBROKER EMAILCLOSE · COMPSTHECONTROLLERLEAK

The five leaks

01
Underwriting rebuilt by hand, every deal
No standard model. Every new deal started from a blank sheet and an analyst's memory of the last one.
Fixed
02
Broker outreach with zero engagement tracking
150 emails through an Excel mail merge. Half bounced. Nobody could evidence which brokers saw a listing.
Fixed
03
One controller ~80% absorbed by a single asset
Manual reconciliation between lease documents and Yardi. A 6-person firm running a 5-person team, at $64K–96K a year in absorbed labor.
Fixed
04
Reactive lease expiration management
Expirations surfaced when a tenant raised them, not before. No forward calendar.
Queued
05
Hand-scraped rent comps
Comps assembled deal by deal from listing sites, then discarded. Nothing accumulated.
Queued

What shipped

Lease abstraction agent
Reads the lease, extracts the terms, feeds Yardi reconciliation. The controller reviews instead of re-keying.
HubSpot CRM with engagement tracking
Every broker touch logged. Opens and clicks attributed to a listing. Follow-up has a trail.
Standardized underwriting model
One template, one data pipeline. A new deal starts populated, not blank.

Pending measurement

Controller capacity reclaimed
Baseline captured at deployment. First read at the next quarterly review.
Year-end close cycle time
Measured against last year's close, same scope.
Broker engagement rate delta
Against a mail-merge baseline of 150 sent and nothing tracked.
Nothing on this page is a claimed outcome. Measured results are published when they are measured.
Take the one-pager

Enter your email and I'll send you the one-pager.

One page: the five leaks, what shipped against each, and what's still being measured. The same format every Leak Map conversation produces.

One email. No list. No sequence.

Your five are different. The pattern isn't.

DM me and I'll build you a Leak Map: 30 minutes, and you leave with a table of your operational leaks — hours per week, cost per month, impact — plus totals and your next step.

Get a Leak Map →Back to the homepage