Features
Five things, done properly, by text.
Status answers, source-backed deadlines, missing-document follow-ups, direct confirmation of every message, and a complete record at the end. Everything else waits until these are proven.
- 01
Transaction-status answers
Text status, deadlines, what's due this week, or what's missing. The assistant answers from your file in seconds. Nothing is sent to anyone else, so answers are immediate and always labeled as answers.
- Works on every file, including read-only ones
- Answers name the file and the date it was verified
- Ambiguous questions get a clarifying question, not a guess
- 02
Source-backed deadline tracking
Dates are proposed from the executed contract with the paragraph each came from. You verify them. Until then they are labeled proposed and never treated as contractual. Every change is kept.
- Source and page on every deadline
- Proposed versus verified, always visible
- Contingencies shown, never interpreted or recalculated
- 03
Missing-document tracking and follow-ups
A checklist per side of the deal, with who owes what. Text a received document and the checklist updates. Ask for the gaps, then ask the assistant to draft the request in your name.
- Owed-by on every document
- Overdue items flagged on the file and in your weekly text
- Requests drafted for you to confirm
- 04
Direct confirmation of outbound messages
Every draft shows the recipient, the sender, the exact text, and any files. Confirm by replying CONFIRM plus the draft number, or on screen. Edit it and the confirmation is void until you confirm the new version.
- Confirmed by, when, and which version, recorded
- Drafted, confirmed, sent, delivered, recipient-confirmed shown separately
- Unconfirmed drafts expire after 24 hours; opt-outs are honored
- 05
Complete closing export
At closing, one export: parties and consent, every deadline with its source and history, documents and when they arrived, every message with its confirmation record and sending status, and the activity log.
- Per file, on demand
- Same records the file ran on, nothing re-typed
- Brokerage-wide export on team plans
Sample output
See what the export looks like.
A full closing export rendered from the demo's 412 Oak Street file: parties, deadlines with sources, documents, every message with its confirmation record, and the log.
Open the sample export
What works today
Demo, pilot, planned.
Nothing on this list is described as more than it is. The demo runs on fictional data; the pilot runs on real files in a launch state; planned means not built.
| Capability | Where it stands | Status |
|---|---|---|
| Status, deadline, and missing-document answers | Fully working in the demo on fictional files. | In the demo now |
| Drafting, editing, and confirming messages | Working in the demo. Sending is simulated; sent, delivered, and reply states are shown as they would be reported. | In the demo now |
| Ambiguity checks and duplicate protection | Working in the demo and covered by tests. | In the demo now |
| Closing export | A sample export renders from demo records. | In the demo now |
| Your own SMS number and real delivery | Pilot agents text a dedicated number; messages go out under their name after carrier registration. | Pilot scope |
| Contract import from PDF | Pilot files are opened from the executed contract; proposed dates are checked against it with you. | Pilot scope |
| Sign-in, data isolation, audit log | Built for the pilot, not present on this site. See the security page for status by control. | Pilot scope |
| Automatic routine follow-ups | A future setting you would turn on yourself, only after the permitted scope has been validated. Not part of this change. | Planned |
| Team dashboards, permissions, reporting | Optional team and brokerage plan. | Planned |
| Marketing kits | Deliberately later, after the core workflow is proven. | Planned |
| MLS integration | No MLS integration exists today. If built, it will be per board and per user, with no shared passwords and no scraping. | Planned |
Command vocabulary
Short texts. Labeled replies.
Each command is one of three kinds. The kind is always shown on the reply, so you never wonder whether something went out.
| Text | Kind | What happens |
|---|---|---|
| status 412 oak | answer | Where the file stands right now: stage, next deadline, open items. |
| deadlines 412 oak | answer | Every tracked date with its source document and whether you have verified it. |
| what's due this week | answer | Everything due across your files in the next seven days. |
| missing docs 412 oak | answer | The checklist gaps on a file, with who owes each document. |
| request lead paint 412 oak | draft | Drafts a request to whoever owes the document. You read it and confirm before it is sent. |
| chase EM 412 oak | draft | Drafts a reminder to the responsible party about the earnest-money deposit. You confirm before it is sent. |
| schedule inspection Thu 2pm | clarify | Asks which file, which recipients, and which time zone, then drafts an invitation. An invitation is not a confirmed appointment until the other side replies. |
| send intro 412 oak | draft | Drafts the transaction introduction to a party under your name. You confirm before it is sent. |
| CONFIRM 1041 | confirm | Sends draft M-1041 exactly as shown, as the version you read. EDIT 1041 changes it; DISCARD 1041 drops it. |