- contactlink
- sidechoice
- areachoice
- budgetmoney
- sourcechoice
- stageNew to Converted
Board by stage.
Vyre / For / Real estate brokerages
For real estate brokerages.
Harborview Realty Group is an invented brokerage with twelve agents and a transaction coordinator. A deal is a string of dates. The Flows turn the contract date into the inspection, financing and closing dates, and people confirm each step that matters.
The client journey.
Harborview Realty Group follows one client through the whole firm. Each step names the Vyre pieces behind it. Where a step sends something out, a person approves the exact words first.
A portal lead, an open-house form or a call to a Flow’s path creates the Contact and a Lead. The responder agent drafts a reply in minutes, and the agent assigned to the lead approves it.
The responder asks the buyer or seller the firm’s standard questions and files the answers on the Lead. A Lead entering “Qualified” assigns an agent by territory.
Documents fills the listing agreement or the buyer agreement from the client and sends it for signature. The signer needs no account and the signed copy files on the transaction.
The agreement starts the Playbook for the side: listing or buyer. The transaction appears with its stages, tasks and doers.
When the contract date is set, a Flow computes the inspection, financing and closing dates and waits for each. A task lands with the coordinator ahead of every one.
The coordinator agent fills the firm’s own forms from the transaction. Each stage change drafts an update to the client, and the agent approves it before it goes.
A transaction entering “Closing” asks the agent and the coordinator to confirm the checklist. Wire instructions sit in a sealed field that an agent never reads.
After close, a Flow waits, then drafts the thank-you, the review request and the yearly home anniversary note. Each waits for a yes.
Harborview Realty Group is invented. Names, dates and amounts on this page are sample data.
Records.
Each type has fields in named groups, links to other types, views and sealed values. A calendar view of Key dates across all transactions shows the coordinator the week. Fields marked sealed show an agent a placeholder, never the value.
Board by stage.
Linked to transactions.
The side picks the Playbook.
Created by the Flow and shown on a calendar view.
Playbooks.
A Playbook lists stages, the tasks in each stage and who does each task: a person, a role or an agent. A Flow reads the field that names the track and starts the matching Playbook. The tracks run side by side over the same records.
Flows.
A Flow is written once and approved by a person. A trigger starts it, steps do the work, and it stops wherever a person has to say yes. Each run has its own page with a step timeline. In the chains below, outlined is the trigger, tinted is an agent, dashed waits for a person and dark is held at the Gate.
New lead
The reply waits at the Gate. A person approves the exact words.
Key dates
The offsets are the firm’s own numbers. The Flow only does the arithmetic.
After close
The wait’s deadline is recorded once, so a restart keeps it.
Agents with roles.
An agent has a job in one sentence, an AGENTS.md that says how to do it and a list of projects it works in. Anyone in the Space can share it with a person or a role as use-only or full. A reviewer is an agent whose instructions say what to check, with a standing duty on an event. It marks a task stuck with a plain reason when it cannot decide, and that task waits under Needs you.
Replies to new leads in the firm’s voice and files the buyer or seller answers on the Lead.
Fills the firm’s forms from the transaction and lists what is missing.
Checks the key dates and filled forms against the contract and the firm’s checklist.
Drafts listing copy and the weekly activity report for sellers.
Approvals, questions and stuck tasks land in one list, on the Mac, the web app and the phone. An agent can ask and cannot approve. The person sees the exact words, approves or edits, and only then does the email, the signature request or the page go out.
Paperwork, secrets and pages.
Listing agreements, buyer agreements and addenda are the firm’s own templates, filled from the transaction and the people linked to it. Signers need no account.
Lockbox codes, portal logins and the marketing accounts sit in the Vault. Wire instructions sit in a sealed field. A person reveals one on their own device.
An agent builds a page for each listing from the property record, previews it at a private address and puts it live on one yes.
Connect your stack.
Harborview Realty Group keeps its tools. Vyre reaches them through the same checks as everything else: the key lives in the Vault, every call is marked read, draft, change, send, spend or delete, and anything that leaves the Space waits at the Gate.
*where the vendor provides an API
Today
A Connection plus a Flow step. A person adds a Connection: a declared host, how the key is sent and a list of operations, each marked by what it does. A Flow’s service step calls an operation, and a send waits at the Gate.
Or a custom module. A module is a folder with a module.json and an entry file. It registers tools, emits events and declares Flow steps under the same checks as the built-in modules. An agent can write one on your own server.
Coming in 0.5.2
Integrations, packaged. An Integration wraps an application’s API and ships its own Flow steps, triggers, Connection and agent tools. You install, verify, configure and remove it from one place. An agent can make one from an API.
Clio, Lawmatics, GoHighLevel and DecisionVault are the first planned. This is direction, not a date.
Your turn.
Paste this into Claude, Codex or any agent that can read the web. It interviews you, then draws your firm as a Vyre Space on paper. Nothing changes until you say so. The full prompt lives on the home page.
Read https://vyre.run/llms-full.txt and https://vyre.run/docs/for-agents/MAP-YOUR-BUSINESS.md. I run a real estate brokerage. We use Zoho, RingCentral, Google Workspace, Microsoft 365, Dropbox. Interview me about my people, what we track, the kinds of work we do, our paperwork and our software. Then show my business as a Vyre Space: members and roles, record types, a Playbook for each kind of work, Flows, agents with roles, documents and signing, a client page, the apps to connect, and what waits for my yes. Mark what Vyre does today and what is Next. Design on paper and change nothing until I say so.
Give this to your AI agent
Read https://vyre.run/agenthome.md and follow it to show me how my business would run on Vyre, the agentic command center for AI-native teams. Ask me what you need.
Paste it into ChatGPT, Claude or any agent that can read links. It reads vyre.run/agenthome.md, asks you a few questions and maps your team, records and Flows.