Scaling commercial real estate deal operations

Doubling deal volume sounds like a win. It almost always is, eventually. But the transition from running ten concurrent deals to running twenty (or twenty to forty) is where most commercial real estate teams discover that their operational system was held together by institutional knowledge rather than by structure. The cracks show up quickly, and they show up in patterns that every scaling CRE team recognizes.

The first thing that breaks is the spreadsheet. A spreadsheet that tracks ten deals can be maintained by one analyst with a Sunday night routine. A spreadsheet that tracks twenty deals requires either multiple people updating it (which causes conflicts) or an analyst who is now spending a full day a week on maintenance instead of underwriting. At twenty deals the spreadsheet becomes a trailing indicator. At thirty it becomes aspirational. At forty it is abandoned in favor of individual team members keeping their own working copies.

The second thing that breaks is file organization. The existing shared drive structure was built for the volume the team used to have. Doubling the volume doubles the number of files, which exposes every weakness in the naming convention and folder structure. Files that were 'mostly organized' become genuinely disorganized. Rent rolls get misfiled. Environmental reports end up in the wrong deal folder. The analyst who knew where everything was becomes a bottleneck on every file request.

The third thing that breaks is ownership. At ten deals the acquisitions principal can hold the status of every workstream on every deal in their head. At twenty deals they cannot. Things start slipping because nobody is watching them. An environmental report takes six weeks instead of three because nobody followed up. A lender commitment expires because nobody tracked the deadline. A closing date gets missed because the title commitment sat in someone's inbox for a week.

The fourth thing that breaks is the weekly pipeline meeting. When the team was running ten deals, the Monday meeting could walk through every deal and take an hour. At twenty deals, walking through every deal takes three hours and nobody shows up for the whole thing. The meeting transitions to 'let's focus on the active ones' which is shorthand for 'let's stop tracking the ones that are drifting.'

The fifth thing that breaks is hiring. The team hires new analysts and associates to handle the volume, but the new hires cannot get up to speed because the operational system is tacit. They spend their first month asking questions that would have answers if the system were explicit. The team's productivity per person drops even as headcount grows.

The pattern is consistent across asset classes and geographies. Doubling deal volume exposes operational gaps that were invisible at the previous volume. The gaps were always there, but the team was working around them through institutional knowledge and overtime. At the new volume, there is no room to work around them.

Scaling deal operations is a forcing function. It requires making the operational system explicit rather than tacit, and it requires doing the work before the volume arrives rather than after. Here is what has to change.

1. Install a real deal management system before you scale

The spreadsheet has to go. Not because spreadsheets are bad, but because they cannot support the structure that scale requires. The team needs a system where the deal is a real object with documents, tasks, contacts, and workstream status attached to it. Ideally, this change happens when the team is running fewer than ten deals, not fifteen, because installing a new system while you are already over capacity is painful.

2. Make workstream ownership explicit

Each active workstream on each active deal needs a named owner who is accountable for moving it forward. 'Owned by the team' is not an answer. When an environmental report is late, the system should show whose name is on it. When a lender has not come back with a revised term sheet, there should be one person whose job is to chase it.

3. Write down what was tacit

The knowledge that lives in the acquisitions principal's head has to move into the system. Deal history, decisions, rationale, contacts, and workflows all need to be captured in a way that new team members can consume. This is the hardest part of scaling because the principal usually does not want to spend time on it, and the analyst does not have the authority to do it. It has to be treated as a specific initiative with time allocated to it.

4. Hire around the system, not around the bottleneck

When the team hires, the new hires should be onboarded onto the deal management system, not onto the tacit knowledge of the existing team. This means the system has to exist and be reliable before the new hires arrive. A common failure mode is hiring first and then trying to install the system around the new people, which creates chaos.

5. Shift the weekly meeting from deal review to filter review

At scale, walking through every deal in the weekly meeting is impossible. Shift the meeting to filter reviews: deals in DD, deals under LOI, deals closing this month, deals with stuck workstreams. Each filter becomes a five-minute conversation instead of a fifteen-minute deal walk. The meeting becomes productive again.

6. Create reporting that does not require a person

At low volume, the analyst can build investor updates, committee reports, and partner briefings manually. At scale, manual reporting is a full-time job. Reporting needs to become a derived view of the deal management system, generated on demand.

MotionCRE is built for teams that are scaling or expect to scale. The deal is a real object. Workstreams have named owners. Updates happen in real time. New hires get onboarded in an afternoon because the system is the documentation. Reporting is a derived view, not a parallel system.

Teams that install MotionCRE before the scale forcing function hits have a much easier transition than teams that wait. The install itself is an opportunity to make the operational system explicit: naming conventions, ownership, process, and deal stages all get written down as the team configures the product. By the time deal volume doubles, the structure is already in place and the team just runs more deals through the same system.

For teams that are already scaling and feeling the pain, MotionCRE is still a clean path forward. Migration takes an afternoon, and the structure that was missing becomes available immediately.