CDP Onboarding Build Estimator
Estimate the build effort for a Lexer CDP onboarding
1Business & Sources
2Data
✓Results
Business
Hub structure questions — separate hubs = datasets onboarded independently into each.
Business name is required.
Each hub = a separate Lexer environment. Most clients use 1 hub.
Separate hubs per region = each region's datasets onboarded independently.
Multi-currency with separate hubs increases scope significantly.
Separate hubs per brand = each brand's datasets onboarded independently.
Sources
What data will feed into the CDP, and how is it structured?
Select all source platforms.
Accounts per Source
Each account / store instance = one group of datasets. E.g. 3 Shopify stores → enter 3.
Additional Datasets (optional)
For data sources not in the list above.
Lexer API — standard API integration.
Lexer Custom Transform — new transform pipeline build required (higher effort).
Lexer Custom Transform — new transform pipeline build required (higher effort).
Every source instance = its own siloed dataset. E.g. Shopify split into 3 regional stores = 3 accounts.
✅ QA & UAT hours are always included in every dataset estimate
Data
Customer identifiers, data quality, and custom requirements.
Drives the customer merge / identity resolution strategy.
E.g. if AP21 has all transaction data, it can supply Transactions + Store Records.
Custom metafields require DI + Custom Fields integration tier.
How many custom metafields?
Selecting any event type automatically adds 1 Custom Events dataset to the estimate (Solution 3h + Build 16h + QA 4h). Schema discussion needed on a separate technical call.
Includes a curated post-onboarding data quality and insights report.
A weekly sync adds 6h to the total engagement hours.
✅ QA & UAT hours are always included in every dataset estimate