Architecture · FS-08
Brokerage Transaction Coordinator
ARCHITECTURE · $6K–$12K PROJECT BANDInbound leads scored and routed to an agent with actual capacity, a deal board with a service level per stage so slippage shows the day it happens, every document on the deal card with its status, commission splits computed at execution, and state-required forms checked before close rather than at it.
Every figure in this console is sample data, shown to demonstrate the interface. It is not real client data and not a performance claim.
The problem this is shaped around
A deal slips a stage and nobody notices until the weekly meeting, by which point the contingency date has moved and the form that was missing is now urgent.
How work moves through it
Stage 1
Lead arrives
Scored on intent and urgency, then routed to an agent with capacity rather than round-robin into an already-full pipeline.
Stage 2
Deal opened
Stage entered with its own deadline. Slippage is measured against that stage's service level, not against the deal's age.
Stage 3
Documents attach to the deal
Missing, pending and signed are visible on the card, so the state of the paperwork is a glance rather than an audit.
Stage 4
Forms checked pre-close
State-required forms verified against the relevant board's standard while there is still time to produce a missing one.
Human step
Commission computed at execution
Agent and broker net update from the executed contract rather than being calculated by hand at month end.
Gold marks a step a person takes. There is always at least one, on purpose: the system prepares and displays, a human confirms and executes. That is the rule for money movement and for anything a model extracted from a document, and it is not negotiable on a build.
Decisions taken at the schema, not retrofitted
Stage deadlines belong to the stage
A deal three weeks old is not necessarily late; a deal two days into a stage with a one-day service level is. Measuring against the deal's total age flags the wrong deals and trains everyone to ignore the flag.
Commission splits are versioned
Splits change by agreement, by tier and mid-deal. A single current-split field silently rewrites the history of every closed deal the moment it is edited.
Every file is bound to the record it belongs to
A photo, receipt or signed document is stored with a pointer to the specific job, invoice or claim it belongs to, plus who uploaded it and when. The test is whether searching a transaction a year later surfaces its own proof automatically. A folder of unlinked images fails that test, and it is the state most businesses are in.
One database per client, not shared tables
Each build runs in its own container against its own database with its own credentials. Isolation by table prefix inside a shared database is the mistake this replaces: it works until one missing filter in one query shows a business its competitor's numbers, and by then the whole schema depends on it.
Where it breaks, and what it does about it
Anything can be made to work on a good day. This is the list that decides whether a system survives a bad one — and the honest cost of each answer, because none of them are free.
| When this happens | The system does this | What that costs to build |
|---|---|---|
| The required-forms list changes | Form sets are per board and versioned with an effective date, so a deal is checked against the rules in force when it was written rather than against today's list. | Effective-dated reference data, which is more work than a checklist and is the only version that is correct. |
| An agent is over capacity but keeps getting leads | Routing reads live capacity rather than a static assignment, and an agent at capacity is skipped with the skip recorded so the pattern is visible to the broker. | Capacity has to be a real measured number, not a preference. |
| A deal is closed with a document still pending | It is blocked. Closing is the one place where a warning is not enough, because after close the missing document is a problem with a lawyer attached. | A hard gate people will ask to have removed in month one. |
What this deliberately does not do
- It does not give legal or compliance advice. It checks a form is present, never that it is correctly completed.
- It does not pay commissions. It computes and displays them; disbursement is done by a person through the brokerage's own accounts.
- It does not replace the multiple listing service or the transaction platform a board mandates. It coordinates around them.
Book an architecture scoping session
An hour on your actual operation — where the work currently queues, what gets re-keyed, which step everyone has quietly built a spreadsheet around. You leave with a diagram like the one above drawn for your stack, whether or not you build it here. Scope is written before any payment, always.
The linked walkthrough is an interactive demo, not a deployment: it runs entirely in your browser with sample data and resets when you refresh it. This page describes the architecture built when a business commissions the system — not a claim that this particular one is running anywhere. Systems are built on infrastructure we operate, and your data stays yours and is exportable on request at any time, including if you leave.
FS-08 · real-estate