Banking CDP: build или buy

Когда возникает развилка

Customer 360 инициатива созрела. CMO want быстрее. CTO want ownership. Vendors (Salesforce, Tealium, Treasure Data, Bloomreach) presентуют 6-month pilot. Internal data engineering claims «9 months и наш».

Banking-specific criteria

Data residency. ПДн в УЗ — мост vendors не имеют local region. Disqualifier для cloud CDP без on-prem option.

Regulatory requirements. CDP touches sensitive financial data — vendor должен быть compliant per cbu.uz expectations.

Cross-product complexity. Banking customer имеет 10-15 продуктов в multiple systems. Identity resolution не trivial — corporate hierarchies, joint accounts, UBO.

Consent granularity. cbu.uz biometric requirements + general data protection — granular per-purpose consent обязательно.

Integration depth с АБС. Tighter чем typical CDP integration с marketing systems.

Когда buy

Mid-size bank с standard data complexity.

Limited data engineering team.

Need for speed (6-month launch).

Vendor offers on-prem или local cloud.

Use cases standard (marketing automation, basic personalization).

Когда build

Large bank (multi-million customers).

Banking-specific identity requirements (UBO, hierarchies).

Strict data residency без vendor local region.

Strong existing data engineering team.

5+ year strategic horizon.

Когда hybrid

Buy для quick-win frontend (audience builder, segment activation), build для long-term backend (identity resolution, profile store).

Где обычно ошибаются

Buy под лозунгом «у нас нет команды». Через год команды нет, vendor поднимает цены.

Build под лозунгом «всё уникальное». Через 18 месяцев — generic CDP с retro design.

Vendor selection by feature list, не по реальному banking job to be done.

Связанное

• /architecture/banking-cdp-architecture/ — CDP architecture
• /solutions/banking-customer-360-platform/ — customer 360
• /insights/banking-vendor-management/ — vendor management
• /decisions/banking-abs-modernization-timing/ — ABS decision