Keep the System of Record. Automate the Work Above It.

The most expensive AI pilot is the one that quietly becomes a replacement project.

Real estate firms already depend on ledgers, property systems, CRMs, VDRs, models, and document repositories. Those systems have permissions, history, and operating ownership. An agent should earn the right to change them.

Start read-only

The first version should read approved records, complete a defined transformation, and deliver a reviewable output. It should not write back merely because an API allows it.

A read-only proof reveals data quality, identity mismatches, missing definitions, and review requirements before those problems can alter production records.

Reconcile beside the current process

Run the agent and the existing workflow in parallel. Compare source selection, calculations, exceptions, and final output. Record every difference and classify it:

• agent defect;
• current-process defect;
• source conflict;
• ambiguous business rule;
• expected timing difference.

Add narrow write permissions

When the output holds up, add one write action at a time. Examples might include creating a review task, attaching a source packet, updating a non-authoritative status, or drafting a CRM note.

Each action needs authorization, idempotency, audit history, and rollback behavior.

Keep the cutover reversible

If a legacy workflow must eventually move, cut over by route or responsibility, not all at once. Preserve reconciliation and a tested rollback until the new path has completed enough real cycles to be trusted.

Expand through adjacent work

Once one workflow is stable, the evidence and controls can support adjacent tasks. A diligence evidence spine can support an IC draft. A reconciled close can support an LP letter. A qualified call can support a CRM handoff.

The safe operating model is simple: keep authority where it belongs, automate the work above it, and expand only after the record survives review.