Feature design · the transaction workspace
The dealroom.
Communication and compliance, between accepted offer and closing. The transaction surface where Mantle turns the close into a tracked, voice-profiled, audit-ready workflow.
Users + jobs
Three audiences. Five real jobs.
The listing agent (primary)
Wants to: send the seller strong updates without drafting them from scratch. Wants to never miss a deadline across 3–8 active deals. Wants to never write a compliance file by hand again.
The seller (read-only)
Wants to: know what's happening with their home. Wants to feel the agent is on top of it. Wants to be told bad news in a way that doesn't panic them.
The brokerage compliance officer (audit)
Wants to: review a deal's compliance file in five minutes, not thirty. Wants to know AI-generated content was Fair-Housing-checked. Wants documentation E&O insurers will accept.
The five jobs the dealroom does
- Track 3–8 active deals across stages, with deadlines visible at a glance
- Draft voice-profiled seller updates triggered by deal events (inspection results in, appraisal back, contingency removed)
- Pre-flight inspection-disclosure addenda and other transaction documents for required language and Fair-Housing compliance
- Capture every communication, document touch, and AI transformation into a single audit log
- Export a one-page broker-compliance file at close that the brokerage's compliance officer signs off on in five minutes
Screen 01
The deal dashboard.
The agent's first screen. Every active transaction visible, sorted by urgency and closing date. A glance answers what do I owe this week?
Five deals. One scan. Done.
Active deals listed with the next action surfaced inline. Urgent items (a deadline today, a missed contingency, an appraisal coming back low) get a red treatment that pulls the eye. Calm deals stay calm.
- Stage chip shows where each deal is
- Days-to-close pill turns red inside a week
- Inline action ("Draft seller update - appraisal results") is one click to dispatch
- Filter row toggles active / pending / closed (default: active only)
Screen 02
The single-deal view.
Click into a deal. The full timeline becomes a horizontal stage progression. Three columns underneath show the only three things the agent looks at during a transaction: communications drafted and sent, documents linked from dotloop, and the compliance state.
The whole transaction, on one screen.
The horizontal timeline shows the ten canonical stages of a residential transaction in this geography. Past stages collapse to a thin progress bar. The current stage gets a marker. The next stage previews what's about to need attention.
- Timeline is the same across every deal - agents memorize it once
- Three-panel layout below: Updates · Documents · Compliance
- Documents pane links directly to dotloop / Skyslope (deep links)
- Compliance pane previews the broker file as it's accumulating
Screen 03
Drafting a seller update, in your voice.
An event happens (the appraisal came in low). Mantle detects it from the document parse, drafts a voice-profiled update, hands it to the agent. The agent reads it, edits if needed, sends. The draft was written by the agent's own writing fingerprint.
The draft is already in your voice. The agent is the editor, not the writer.
Triggered by a deal event, manually, or scheduled (e.g., weekly check-in). The draft is shown alongside the event context so the agent knows why it was triggered.
- Italic preview reads as the agent's natural voice
- Regenerate button uses the same voice profile, different framing
- Send / save draft / send later (calendar)
- Sent updates land in the dealroom communication log automatically
Screen 04
Pre-flight on every transaction document.
When a document lands in dotloop - an inspection response, a disclosure addendum, a price-reduction amendment - Mantle pulls it (read-only), runs a compliance check, surfaces any issues. The agent fixes them in dotloop before signing. The dealroom logs the pass for the compliance file.
The document the brokerage compliance officer would have flagged later, flagged now.
The pre-flight runs against a state-and-MLS-specific rule set. NY, CT, and the OneKey + Smart MLS overlays are encoded. New rules ship as data, not code.
- Greens: required disclosures present and correctly worded
- Yellows: ambiguous language; recommend clarification
- Reds: missing required clauses; transaction-blocking
- One-click to draft revision text in dotloop - the agent doesn't re-type
Screen 05
The broker-compliance file, generated.
At close, one click. The brokerage's compliance officer gets a one-page PDF with every AI transformation, every Fair-Housing pass, every disclosure pre-flight, every voice-profiled communication, every document touch - all timestamped. Five-minute review instead of thirty.
What the brokerage actually needs at close.
Single-page summary by default. Drill-down PDF available for any flagged item. The compliance officer reviews and signs off. The agent never assembles this manually again.
- One-page default; expandable per-section detail
- Hashed document references - tampering would be detectable
- Signature lines: agent + compliance officer
- Exportable to E&O carrier format if required
Anti-design
What the dealroom is not.
The boundaries are firm. Integrations are open.
Not a documents-and-signatures platform
dotloop, Skyslope, and Authentisign keep the legal paper-of-record. They handle storage, signature workflow, broker review queues, and archival. The dealroom integrates via OAuth and deep links; we do not duplicate their work.
Not a CRM
Lead capture, contact pipelines, sphere-of-influence touch automation lives in Follow Up Boss, kvCORE, Top Producer. The dealroom integrates with the agent's CRM for party contact info; we do not run their pipeline.
Not a brokerage admin platform
Commission splits, transaction-coordinator queues, multi-agent dashboards are Lone Wolf and BrokerKit. The dealroom shares its compliance file with the brokerage; it does not run their back office.
Not the seller's portal
The seller gets a read-only shareable link to deal status - not an account, not a login, not a notification system. The agent owns the relationship. The dealroom amplifies the agent's voice; it does not replace it.
Sprint mapping
What ships when.
The dealroom is the v3 surface. It does not ship until v1 has 25+ paying agents and v2 (the listing-pitch deck) has 50+. Until then it is documented, not built.
| Sprint | Feature | Effort | Dependencies |
|---|---|---|---|
| Foundations v3 prep · weeks 1–3 |
Deal entity model + dotloop / Skyslope OAuth integration | Medium | Postgres + Vercel API · OAuth from each vendor |
| v3.0 weeks 4–6 |
Deal dashboard (Screen 01) + single-deal view (Screen 02) · timeline, document linking, parties | Medium | Foundations |
| v3.1 weeks 7–9 |
Voice-profiled seller updates (Screen 03) · event detection + draft + send | High | v3.0 · voice profile from v1 |
| v3.2 weeks 10–12 |
Compliance pre-flight (Screen 04) · NY + CT + OneKey/Smart MLS rules | High | v3.0 · rule encoding · counsel review |
| v3.3 weeks 13–14 |
Broker-compliance file export (Screen 05) · PDF generator from audit log | Low | v3.1 + v3.2 |
| v3.4 weeks 15–16 |
Brokerage tier · multi-agent admin · compliance officer review queue | Medium | v3.3 · first brokerage pilot signed |
Open questions for v3 build
- Document parsing. dotloop / Skyslope expose downloadable PDFs. Compliance pre-flight requires text extraction - pdf-parse for searchable PDFs, OCR fallback for scanned. Cost-per-doc and accuracy on scanned docs need real testing in Sprint v3.0.
- Rule encoding. NY § 462, CT realtor disclosures, OneKey 2025A, Smart MLS rules. Encoded as JSON rule sets; counsel reviews quarterly. Question: how much of this is buy-vs-build (CompliancePilot, Real Estate Disclosure Source) vs in-house?
- Event detection. "Appraisal received" can come from dotloop document upload, an email parse, or manual entry. Multi-source detection with deduplication needed; reliability is the make-or-break for the seller-update flow.
- Voice profile bootstrap. The dealroom relies on a voice profile trained in v1's studio. What happens if an agent uses the dealroom for a transaction that wasn't listed via Mantle? Cold-start handling: invite agent to record 5 minutes of "how I'd write this" on first dealroom use.