Anti-Fragile take
Every company should have exactly one ID in your system, regardless of how many domains, subsidiaries, or name spellings exist. Without it, enrichment writes to the wrong record and routing sends leads to the wrong rep.
We generate canonical IDs in the warehouse and map every domain, alias, and subsidiary to them.
Why it matters
Canonical IDs are the foreign key that makes dedupe, enrichment, scoring, and routing composable.
How we build it
UUID per resolved company, domain-to-ID map table, and subsidiary parent-child links maintained by scheduled jobs.