Unified Client Data Platform
A customer relationship doesn't start on the showroom floor. Roots takes the records that already describe it — DMS, CRM, the service drive, survey responses — and resolves them into one governed profile per household, across every rooftop in the group.
30 minutes, against your own data model. No deck.
Three problems, solved in the core rather than in each integration.
01 / Ingest
A documented canonical event model and a keyed ingestion endpoint. A test drive, a closed repair order, a parts sale and a survey response all land as the same row shape — so a new source is a field map, not a new pipeline.
02 / Resolve
Identity resolution runs on a configurable key precedence, collapsing the duplicate records that multi-rooftop groups accumulate. Household members, owned vehicles and service history hang off a single profile the whole group can see.
03 / Govern
Role, tier and org-unit scope are applied as row-level security and column masking in Postgres, and consent suppression runs on every activation. Not a convention in the UI that a query can route around.
The unified profile, assembled per viewer — filtered to the role and rooftop asking.
3 vehicles owned • Open repair order, bay 02 • High trade equity
Sample data. Every field above is derived by the engine from ingested events — none of it is hand-entered, and each one is withheld from any viewer whose tier doesn't reach it.
We'll walk the event model, the permission rules and what your systems would map to — then you can decide whether any of it is worth building.