Built by Endurance AI Labs for Circa Properties
A brokerage cannot scale
a founder’s attention.
Circa went from zero to 214 agents in four years across four offices. Two brokers of record still carry every judgment call. This is what it looks like when that support becomes a system instead of an inbox.
The problem

What actually breaks at 214 agents

The constraint is not headcount and it is not software. It is that the number of judgment calls a brokerage generates grows with the agent count, while the number of people qualified to make those calls stays at two.

Every one of those calls has three possible outcomes. The agent waits — and a client waits with them. The agent guesses — and compliance finds it later. Or the agent stops asking — which is the outcome nobody sees until the file closes badly or the agent leaves.

Operations has the same shape. Transaction coordination, compliance chase, listing marketing: each is a queue where the work is real but most of the individual items are mechanical. The people doing them are spending their judgment on things that do not require it.

The goal is not to answer more questions. It is to make sure the questions that reach Matt and Abe are the ones that genuinely need them — and that they arrive with the work already done.

What this demonstration shows

Six working surfaces, built on Circa's real structure: four offices, two brokers of record, the leadership team as published, and the live listing inventory. Every operating figure — agents, files, questions, dollars — is simulated.

  • Broker Desk — the agent question queue, with drafted, cited answers and explicit routing logic.
  • Answer Ledger — the audit trail that makes the desk trustworthy: accuracy, corrections, agent ratings.
  • Transactions & Compliance — open files ranked by risk of not closing, and the document audit behind them.
  • Agents — production, support engagement and retention signal in one view.
  • Growth — the recruiting board and the retention watchlist on the same screen.
  • Listings — inventory across all three Circa verticals plus the concierge queue.

Circa Properties

Offices

Leadership & staff

Roles in this demo

Use the name in the top-right to switch roles. Each one sees a different slice — an agent never sees another agent's production, and growth never sees client detail.

Rollout

How this gets built, and in what order

Sequenced so the hardest thing — agent trust — is earned on the easiest surface first. Nothing touches a client, and nothing goes wide until the accuracy numbers are visible to the agents themselves.

01

Ingest what Circa already knows

Circa's written policies, the C.A.R. form set at current revision, the relevant California statutes, and the answers Matt and Abe have already given a hundred times over. Every document gets a named owner. This is the Source Library, and the desk cannot say anything that is not traceable to it.

Weeks 1–3 · no agent sees anything yet
02

Shadow mode — the desk answers, nobody sees it

Real questions come in through the existing channel. The desk drafts an answer for every one; only Matt, Abe and Nina see the drafts alongside what the humans actually replied. The gap between the two is the accuracy baseline, measured before a single agent is asked to believe anything.

Weeks 4–7 · brokers only
03

One office, narrow categories, broker-approved sends

Yorba Linda only. Contract mechanics and approved-snippet categories only. A broker approves every send with one click, which is still an order of magnitude faster than writing the reply. Agents see the citations from day one and are told plainly what the desk will and will not touch.

Weeks 8–13 · ~88 agents
04

Auto-send on proven categories — and publish the error rate

Categories where shadow-mode accuracy held above the threshold move to auto-send. The Answer Ledger opens to every agent on the same day, including the corrections. Publishing the errors is the step most firms skip; it is the step that converts the sceptics.

Weeks 14–20 · all four offices
05

Operations surfaces — transactions, compliance, concierge

Document chase, file risk ranking and the marketing queue. These are lower risk than the Broker Desk and higher volume, but they go second because the desk is what buys the credibility to change how ops works.

Weeks 18–28 · ops team
06

Growth and retention signal

Only once there is enough support-engagement history to make the retention signal real. Built last on purpose — a retention model with three weeks of data is a guess with a progress bar on it.

Month 7 onward
Constraints

What this does not do

Worth stating plainly, because the fastest way to lose a room of agents is to promise something the tool cannot carry.

It does not talk to clients

No client emails, no listing copy sent under an agent's name, no negotiation. The agent is the only voice the client hears. That relationship is what Circa's agents are paid for and it is not something to automate.

It does not replace a broker of record

Matt and Abe carry the licence and the liability. The desk reduces how often they are asked, and improves the state of every question that does reach them. It never makes the call in their place.

It does not pretend to know

Below the confidence threshold it declines and routes. The deferral rate is a published number, not a hidden one. An agent who catches the system bluffing once will not use it again, and they will be right not to.

Prepared by Endurance AI Labs. Circa Properties' name, offices, leadership, DRE licence and published listing inventory are drawn from public sources. All agents, clients, transactions, questions, answers, dollar figures and performance metrics in this environment are simulated for demonstration and do not represent Circa's actual operations.