RULE: Own a single customer_id primary key that joins across your vertical SaaS + QuickBooks + email + ads.
Created 2026-05-22
Rule: Every Candid Creative client data layer is anchored on a single canonical customer_id that joins records across the vertical SaaS, QuickBooks, email/marketing automation, ad platforms, and any other system holding customer records.
Why:
- MuleSoft 2025: average org has 897 apps, only 29% integrated (MuleSoft 2025 Connectivity Benchmark: organizations use 897 applications on average; only 29% are integrated)
- The single biggest blocker to Stage 3 → Stage 4 on the Reference: the 5-stage Data Maturity Curve — from stranded data to data as product is entity-resolution across silos
- IDC: data silos extract 20-30% operational efficiency annually
- The Zillow / ATTOM / Cherre playbook is, fundamentally, "own the primary key" — that's what their normalization engines deliver
How to apply:
- During the data-infrastructure scoping (Reference: minimum viable data stack for a $1M-$10M Canadian service business (2026, C$100-C$500/month)), the FIRST table to design is the canonical customers table
- Pick the source-of-truth for new customer creation (often the vertical SaaS) and ALL other systems get mapped to its customer_id
- For legacy data: fuzzy-match + manual reconciliation to create historical customer_ids; one-time cost worth the recurring queryability
- Privacy bonus: SARs and Law 25 portability requests become a single SQL query (
SELECT * FROM all_tables WHERE customer_id = $1) rather than a five-tool scavenger hunt
Depends on
- reference MuleSoft 2025 Connectivity Benchmark: organizations use 897 applications on average; only 29% are integrated
- reference Reference: the 5-stage Data Maturity Curve — from stranded data to data as product
- reference Reference: minimum viable data stack for a $1M-$10M Canadian service business (2026, C$100-C$500/month)