AI workflows for a real estate development shop

Development is the part of real estate where one misfiled email can cost six months and a million dollars. It is also the part where every principal I talk to is spread across too many active deals, too many entitlements at different stages, too many lender relationships, too many GC’s, and not enough team. The pitch is always the same. “We need to grow but we cannot find the people.”

The thing nobody wants to say out loud is that you do not need more people. You need to stop your existing people from drowning in admin. That is where Claude lands at a development shop. Here is the workflow map, written for principals running 3 to 30 active projects.

The entitlement tracker that does not slip

Entitlements are project management on a 24-month clock with 14 different counterparties and a public comment period in the middle. Planning department, traffic engineer, environmental consultant, civil, MEP, neighborhood association, city council, county recorder. Each one has deadlines. Each one has comment periods. Each one has resubmission cycles. Each one has a contact who responds to email at a different cadence.

Most development shops track this in Smartsheet or Asana. The data is in there. The problem is the data is stale because nobody has time to update it daily. So the principal asks “where are we on the West side entitlement” and the team takes two days to put together the actual answer.

Claude wired to the entitlement folder and inbox does this in real time. It reads every email from every counterparty as it arrives. It updates the project’s status timeline. It flags when a deadline is approaching, when a comment period closes, when a resubmission is due. It generates the principal’s Monday morning entitlement digest across every active project. “City of Costa Mesa called for a continuance to the next planning commission, Buena Park civil engineer flagged a stormwater design comment that needs response by Friday, Tustin neighborhood association president sent an inquiry about parking impacts that requires a response inside seven days.”

The principal walks into Monday already knowing what is on fire. The team gets back the time they used to spend pulling status together.

GC management and the RFI pile

The general contractor is the relationship that consumes the most operational attention on a live project. RFIs come in. Change orders come in. Submittals come in. Pay applications come in. Each one needs a response within a window. Slip a response and you give the GC ammunition for a delay claim.

Claude wired to the project management platform reads every RFI as it lands. It pulls the contract documents, the spec book, the relevant drawings. It drafts a response based on what the contract says. The development manager reviews, edits, sends. The pace of RFI throughput doubles. The contract administrator stops being the bottleneck. The schedule stays cleaner because RFIs do not pile up.

For change orders, Claude reads the proposed change against the original scope and flags whether the GC’s argument that this is a change of scope holds water. The development manager goes into the conversation with the GC armed with a contract-grounded position instead of “let me get back to you.”

Pay applications are the bread and butter use case. Claude reads the pay app against the schedule of values, the prior pay apps, and the lien waivers. It produces the development manager’s review notes in ten minutes instead of an hour. The cumulative effect over the life of a project is real.

Capital stack tracking and the lender reporting cycle

Every active development has a capital stack with at minimum a construction loan, equity from one or more LPs, and sometimes a mezz piece or preferred equity. Every one of those tranches has its own reporting requirements, its own draw process, its own covenant tests, its own communication preferences.

Most shops have one person who knows the capital stack. That person is usually the principal or a senior CFO type. The reporting is built fresh every cycle because nobody else has the institutional memory of who wants what in what format.

Claude takes the institutional memory out of one person’s head and puts it into the workflow. Every lender’s reporting requirements are documented. Every equity partner’s preferred update format is templated. The monthly reporting package is drafted by Claude with the project numbers pulled live from the GL and the construction draw schedule. The CFO reviews, signs, sends. The same workflow handles the loan covenant compliance certificate. The same workflow handles the equity partner’s quarterly update.

The downstream effect is that the principal stops being the bottleneck for capital stack communications. The CFO can grow without losing fidelity. New hires can come in and contribute without spending six months learning who wants what.

The draw package: the workflow nobody wants to own

Construction draws are the most operationally painful workflow in development. The GC submits a draw request with the pay app, the conditional and unconditional lien waivers from every sub, the updated schedule of values, the progress photos. The development manager reviews, the architect inspects, the inspector certifies, the title company runs a date-down. The lender reviews and funds.

This is a two-week cycle every month. Most shops have a development manager and a construction admin who effectively work full time on draws across their active projects. The bottleneck is not the actual review. It is the email coordination, the lien waiver chasing, the document assembly.

Claude as the draw coordinator does the chasing. It reads inbound emails from subs and matches lien waivers to subcontracts. It flags missing waivers and drafts followup emails. It assembles the draw package automatically once all the pieces are in. The development manager spends an hour reviewing instead of a day chasing.

For a shop with five active projects, that is one full FTE recovered. That is real money.

Investor and partnership communications

Most development shops have a few large equity partners, a few smaller co-GP relationships, and sometimes an institutional LP. The communication preferences vary wildly. The institutional LP wants formal quarterly reports with audited financials. The family office wants a one-page narrative twice a year. The co-GP wants weekly check-ins with raw operating data.

Claude reads from the project management tools, the construction draw schedule, and the GL. It generates the right format for each counterparty. The principal reviews and edits the substantive commentary. The mechanical reporting is automated. Every partner gets a level of attention that scales with their preferences, not with the principal’s calendar.

Where I push back on AI in development

A few things I am skeptical of:

Automated construction estimating. The contractor on the other side has decades of intuition for how the work breaks down. A model that estimates from prints does not replace that. Use Claude to review the contractor’s estimate against your own line items, not to replace your estimator.

Site plan automation. “Claude will generate the site plan.” It will not. Site planning is a creative and regulatory exercise that requires a human civil engineer and a human entitlement consultant. The best Claude does here is summarize the comments from the planning department and draft the response letter.

Replacing the development manager. The development manager is the most important relationship layer on a live project. The relationship with the GC, the lender, the architect, the inspector. None of that gets automated. What Claude does is take the admin off the development manager so they can spend their time on the relationships that matter.

The order of operations

For a development shop running 3 to 30 active projects, the order I would tackle is:

First, the draw package workflow. Highest immediate ROI. Frees up the most expensive bottleneck in the operation.

Second, the entitlement tracker. Compounds because every project that does not slip is a project that closes on time and within budget.

Third, RFI and change order management. The GC relationship gets cleaner because responses are faster and contract-grounded.

Fourth, the lender and partnership reporting cycle. Compounds because the principal stops being the bottleneck for capital stack work.

Fifth, the investor and co-GP communications. Save for last because the principal’s voice does the most work here and the SOP takes the longest to write.

The whole thing rolls out in about 90 days. Training, written SOPs, customer support, refinement run as an ongoing loop. The development shop gets sharper every quarter and the work stops piling up on the people who used to drown in it.

If you want to walk through how this would look at your shop, I run a 60-minute working session that pulls a real project of yours and shows the workflow end to end. Calendar link is at the bottom of the page.