Readiness path
CSV-first- InventoryIdentify exports you can obtain lawfully.
- AssembleImport files with source provenance.
- ResolveReview duplicates and consent fields.
- ExportDownload CSV, manifest, and exceptions.
Assemble export files, clean fields, make human merge decisions, classify relationships, and create a deterministic, mapping-ready CSV package for major residential real estate CRM import workflows.
See how SphereReady helps a residential agent turn scattered relationships into a clean, reviewable CRM import while keeping every decision under human control.
Being in an address book is not marketing consent. Newsletter eligibility, SMS consent, and call consent are separate fields. Suppression overrides all outreach.
Choose what you have. Every path below states its real setup boundary.
The official Mesh MCP supports contact search, contact details, statistics, groups, notes, events, and write tools. This demo does not connect to Brad's or anyone else's account. Use an authorized export or separately configured MCP in a production tenant.
Operational fields stay visible and auditable.
| Contact | Source | Quality | Classification | Relationship | Permissions | Status |
|---|
Exact rules are deterministic. Likely matches always require review.
SphereReady standardizes supported CSV and tabular export data, preserves provenance and permission decisions, and produces a clean mapping package for the import workflow used by the selected CRM. Platform requirements change, so every production import remains a human-reviewed handoff.
Checks reflect a mapping-ready CSV preparation path—not an authenticated vendor template, endorsement, or direct API connection.
Files are deterministic, UTF-8, CRLF, and formula-injection protected. ZIP values remain text. Relationship is preserved in the workspace but is not asserted as a native vendor field until the target CRM mapping is verified.
This Sandbox demo uses browser-local storage for its preview data and static assets for delivery. Production architecture remains Worker + Static Assets, D1, private R2, Queues, Workflows, Turnstile, and managed authentication.
Subpath-safe files plus a browser-local API adapter.
Contacts, provenance, imports, and reversible merge records remain on this device.
Original uploads and generated exports with signed, short-lived access.
Resumable OCR, parsing, deletion, and audit jobs.
Abuse controls, tenant-scoped RBAC, session management.
Future read-only Google/Microsoft connectors with envelope-encrypted tokens.
This screen is non-functional. Authentication is intentionally not implemented in the Sandbox demo.