The Demo-to-Production Gap
An agent that books a viewing or drafts a lease summary is easy to demo and hard to ship. The demo runs once, on a clean input, with a human watching. Production runs thousands of times a day on messy real-world data with no one watching — and a single bad action can email the wrong tenant, mis-price a property, or trigger a payment that should not have happened.
Closing that gap is an engineering-discipline problem, not a model problem. Below are the practices VSBD builds into every agentic orchestration layer we ship for PropTech clients — the same work behind our PropTech 2026 Awards nomination.
1. Constrain the Decision Space
Full autonomy is rarely what you want. A real estate workflow has a known shape: you almost always classify the document before you extract from it, and you always verify before you act. Encode that shape. Use deterministic routing and explicit state machines for the parts of the workflow that are predictable, and reserve open-ended agent reasoning for the genuinely ambiguous steps.
The rule of thumb: autonomy where it pays off, determinism everywhere else. Every degree of freedom you remove is a class of failure you no longer have to test for.
2. Make Every Tool a Typed Contract
Agents act on the world through tools. If a tool accepts free-form input and returns free-form output, you have no way to catch a malformed action before it hits your database. Give every tool a validated schema for both directions:
(Diagram in the original article.)
This single decision converts a whole category of "the model hallucinated a field" problems into ordinary, catchable validation errors. It also makes your agents portable: swap the underlying model and the contracts still hold.
3. Ground Everything in Retrieved Data
An agent reasoning about a property should never rely on the model's parametric memory for facts. Retrieve the lease, the valuation history, the tenant record, and the policy document, and require the agent to ground its output in what it retrieved. Grounding is what turns a plausible-sounding answer into a defensible one — and in real estate, defensibility is the whole game.
4. Put a Human in the Loop on High-Stakes Actions
Not every action deserves the same level of trust. Reading a document is low-stakes; sending a payment, signing a contract, or messaging a tenant is not. Classify your actions by reversibility and value, and require explicit human approval on the consequential ones.
Done well, this is not friction — it is leverage. The agent does 95% of the work (gathering, drafting, checking) and a person spends ten seconds approving a fully-prepared action instead of ten minutes doing it from scratch. Every approval is logged, giving you a complete audit trail for compliance.
5. Trace, Replay, and Evaluate Every Run
You cannot improve what you cannot see. Instrument every agent step so that a full run can be replayed and inspected: what the agent was asked, what it retrieved, which tools it called, and what it returned. Then score those runs against an evaluation suite — a curated set of real cases with known-good outcomes.
Evals are your regression test for non-deterministic systems. Before any prompt change, model upgrade, or new tool ships, run it against the eval suite and confirm you have not regressed on cases that used to pass. Without this, every change to a production agent is a gamble.
6. Control Cost and Latency Deliberately
Token spend and response time are product features, not afterthoughts. The levers that keep both predictable as volume grows:
Model routing — send simple classification to a small, fast model and reserve the most capable model for genuinely hard reasoning. Most steps in a real estate workflow do not need your largest model.
Prompt caching — cache the stable parts of prompts (system instructions, policy documents, tool definitions) so you are not paying to re-process them on every call.
Bounded context — externalize state and retrieve only what each step needs, instead of growing the prompt unboundedly as a workflow runs.
Fallbacks and circuit breakers — when an agent or model call fails, degrade gracefully to a simpler path or a human queue rather than cascading the failure.
7. Fail Safe, Not Silent
When something goes wrong — a tool errors, validation fails, a model times out — the worst outcome is an agent that quietly does the wrong thing. Design every failure path to stop and escalate rather than guess. A workflow that lands in a human review queue is a minor inconvenience; a workflow that silently corrupts a tenant record is a crisis.
The Payoff
Teams that treat agentic AI as a prompt-engineering exercise ship impressive demos and fragile products. Teams that treat it as a distributed-systems and reliability-engineering problem ship agents that run unattended at scale. The practices above are what let a real estate platform hand a large share of its routine asset operations to agents and still sleep at night.
VSBD builds production-grade agentic orchestration layers for PropTech and real estate companies across Europe and the USA. If you want an agent layer your compliance team trusts and your operators rely on, we can help you build it right the first time.
Originally published on the VSBD blog.
