ARCHITECTURE

Who owns the customer?

Identity is the first architectural decision in any connected system, and the one most often made by accident.

7 MIN READRATTLECODER

A single person can exist as a contact in the CRM, a customer in the payment platform, a user in the application and a subscriber on an external distribution platform. Four records, four identifiers, one human.

Choose a reference, not a winner

Ownership doesn't mean one system holds everything. It means each fact has one authoritative source, and every other system stores a reference to it rather than a copy of the logic.

  1. EXPERIENCE LAYERApplication user
  2. COMMERCE LAYERBilling customer
  3. INTEGRATION LAYERIdentity resolution
  4. REVENUE CORECRM contact — canonical
ONE HUMAN, RESOLVED ACROSS LAYERS

Practical rules

  • Persist external identifiers on the canonical record from day one.
  • Never match on email alone in a system where email can change.
  • Decide what happens on conflict before conflict happens.

WORKING THROUGH SOMETHING SIMILAR?

Turn the thinking into architecture.

If you're dealing with a complex CRM, integration or digital system, we can help you map the architecture before deciding what to build.