The story in 30 seconds
Today a real-estate deal is scattered across a dozen logins — MLS here, forms there, signatures somewhere else,
the association's spreadsheet, the broker's filing cabinet, the client's email. PURE collapses all of it into one system
where the listing, the contract, the people, the money, and the proof live on a single record. Everyone sees their slice;
nobody re-types; everything is auditable. And it's owned by the industry it serves — associations and MLSs run it,
agents and members fund it through fair per-use pricing (PD), and the data stays theirs.
1login · many hats
33working surfaces
10store products
35live data tables
22connected services
50Kusers · design target
The PD economy — how the money works
PD is PURE's unit of value. Instead of every agent buying five subscriptions they barely use,
PURE prices per use, per deal, per listing — small numbers that follow real activity. The association and MLS run
the platform; the store routes a share of every product back to them, so the system funds the industry that owns it.
WHO PAYSWhoever benefitsAgent, buyer, or seller can hold a product — the deal doesn't care who pays, only that the work gets documented
HOW MUCHSmall + honest5 PD a listing for disclosure help · 25 PD a transaction for move-in proof · 100 PD/user/mo for full professional workbenches
WHO EARNSThe industryStore revenue shares to the association/MLS; vendors get paid through the platform — no invoicing chaos
WHAT IT REPLACESThe subscription stackForms tool + e-sign + showing tool + CRM glue + inspection app + status calls — collapsed into one record
ONE LOGIN · MANY HATS — the access model in one row
Agent their deals + market
Broker every office file
Association members · dues · governance
MLS listings · feeds · compliance
Vendor their jobs only
Client their deal only
Switching hats re-renders the whole product to that role's scope.
A hat is never a second account — it's the same person, seen correctly. Cross-boundary access happens only through explicit,
expiring grants, every one logged.
How it all connects
One database in the middle. Lead sources and field capture flow in; deals, documents, money,
and proof flow out. The lanes (your AI workforce) build and run it; you steer from one window.
Lead sourceswebsite · Zillow · StreetText · referrals
Field capturephones: photos · dictation · identity checks
SmartformsTREC contracts → database, once
Members & staffhats: agent · broker · assoc · vendor · client
→
THE PURE RECORDone live database · 35 tables
deals · listings · people · money
board · memory · audit
→
The dealspine · signatures · tasks · closing
The marketfeeds · syndication · alerts
The moneydues · fines · store · commissions
The proofstatus page · banners · audit · backups
Around the core: 22 connected services (CRM, maps, analytics, design, monitoring, video) managed
with on/off switches in the Integrations Hub — and the AI lanes,
which claim tickets from a live board you dispatch from one window.
Roadmap — what's next, in order
NOWacquisto.live/status + phone installDNS + PWA — your 2-second glance on the home screen (approved, Phase 2)
NOWOne-click real deploysFull batch → GitHub → Netlify; the Releases tab stops queuing tickets and just ships
NEXTLeads phase 1–3Live FUB ingestion → auto action plans → partner status updates (plan approved by probe, awaiting APR-5/6)
NEXTThe PURE MCP serverNamed, scoped, audited tools — retires raw keys, meters real AI spend (APR-2/3)
THENReal data everywhereMatterport tours, geocoded search, analytics BI, Zoho reconciliation — all connections already live, waiting to be wired
THENHardening for scaleRLS tightening, auth principals, realtime, storage buckets (infra brief delivered to Shattique)
Your actions — everything waiting on a person
YOUUpload the TXR forms (1101 · 1406 · 1405 · 1414 · OP-H)Unblocks promulgated-form output across forms + disclosure (ND-1)
YOUUpload the 4.8 b-mlsops rules engineLocal-MLS deltas for listing gates (ND-2)
YOUReconnect UptimeRobot with the main API keyCompletes the site-uptime tile on the status page (ND-6)
YOUConfirm acquisto.live DNS access + name Leads & Money section ownersPhase 2 of the status page (APR-7 b/c)
YOUAnswer APR-1..6 in the Command Center ▸ Approvals tabVerified Capture price · MCP hosting · Netlify token · spend caps · FUB registration · lead routing
YOUGet Lane A's close-out batch into the workspaceTheir 7 cleared tickets union at the next Combine (ND-4)
RUNS ITSELFBackups · QA logging · lane coordination · needed-docs registry · auditProtocol-driven, in the database, every session
Quick answers
QIs this live or a demo?The surfaces are live against a real database; client-facing money/PDF moments are clearly marked demo until their gates (forms uploads, pricing approvals) clear.
QWhat happens if something breaks?The status glance goes amber/red, a banner posts everywhere, staff get messaged, and any release can be reverted to the previous batch in one action.
QWho can see my data?Your hat decides. Cross-boundary viewing requires a logged, expiring grant. Identity checks can be required on any sensitive capture.
QWhat does it cost to run?Static hosting + one database + per-use AI work metered by tier — the ops report tracks spend per ticket; the store funds the platform.
QCan it really replace our current tools?The deal record already carries forms, signatures, tasks, money, search, disclosure, inspection, and appraisal natively — the integrations layer covers the rest while it migrates.
