If your customer data lives in five different systems, you already know the cost. The CRM says one thing, the email platform another, and the e-commerce store a third. Someone spends part of every week exporting spreadsheets and reconciling them by hand, and the numbers still do not agree. Campaigns go out to people who unsubscribed last month. Reports get questioned in meetings. A customer data platform fixes that by pulling email, CRM, web, mobile and transaction data into one unified profile you can actually trust, then activating it back out to the tools your team already uses.
Most CDPs on the market expect you to bend your process to fit theirs. We do it the other way round. ByteGears is a UK consultancy that builds business automation software, and we build CDPs around how your team already works, on infrastructure you control. The result connects to the systems you have, keeps your data inside the UK, meets UK data rules, and does not leave you fighting the software to get a simple answer.
Where off-the-shelf CDPs fall short
Packaged CDPs are good products, and for plenty of companies they are the right choice. But for a lot of UK businesses they trade one set of problems for another:
- Pricing that climbs with success. Most platforms charge by monthly tracked users, stored profiles, ingested events or consumption credits. Your bill grows as you do, and overage rates often run 30-50% above your contracted rate. A busy quarter becomes a budget overrun.
- Hidden costs on top of the headline. Implementation, data migration, custom integrations and premium support are usually quoted separately. The real first-year figure can land two to three times above the platform fee you were shown.
- A fixed identity model. Their matching logic is built for an average company. If your customers do not behave like the average, you either accept fragmented profiles and false merges, or pay for custom development to fix it.
- Connector gaps. Pre-built connectors cover the popular tools. The legacy system or in-house service that actually runs your business often has none, so a “quick” integration becomes weeks of custom API work anyway.
- Workflow rigidity. Standard email, SMS and retargeting flows cover most cases. The approval chains, commission rules or sector-specific logic that make your operation yours usually do not fit.
- Vendor lock-in. Six months in, the switching cost — data export, re-implementation, retraining — is high enough that a price rise meets little resistance. Vendors get acquired, sunset features, and change pricing direction.
- Data residency you have to argue for. UK-hosted options are limited or sit behind expensive enterprise agreements, which makes the compliance story harder than it needs to be.
So you end up with workarounds, manual steps and a tool that quietly costs more every year than the one it replaced.
What we build instead
Our UK team builds CDPs that fit the business rather than the other way round. Depending on what you need, that might be a fully bespoke platform, a build on a warehouse like Snowflake or BigQuery, or an extension of a sound open-source foundation such as RudderStack — we will recommend the approach that gives you the best result, not the biggest project.
- We map how your team works and audit your source data before we write any code, so people adopt the platform and it is not fed from messy records.
- You pay once and own the software, with no licence renewals and no per-user or per-event meter running in the background.
- An API-first build connects to your CRM, e-commerce, email tools, analytics and operational systems, including the legacy ones with no off-the-shelf connector.
- Identity resolution is built around your data and your matching rules, and tested before go-live so you can see how accurate it is.
- UK GDPR, the Data Protection Act and your sector’s rules are designed in from the start, on UK-hosted infrastructure.
- A modular design means you can add real-time segmentation, journey orchestration or predictive scoring later without a rebuild.
We take on a small number of clients at a time. That is deliberate, and it means your project gets real attention rather than a queue.
What’s in the build
Every CDP we build covers the core a CDP needs to be worth having:
- Data collection and ingestion from web, mobile and server-side events, plus API and batch imports from your existing systems
- Identity resolution that merges records into one profile per customer, using deterministic matching on email, phone and customer ID, with probabilistic matching where it earns its place
- Unified customer profiles holding identifiers, descriptive and behavioural attributes, consent and preferences, engagement history, and qualitative data like support tickets and survey responses
- A segment builder for both visual rules and SQL, so “purchased in the last 30 days, opted in to email, cart abandoned over £50” is a few minutes’ work
- Activation that syncs segments and attributes out to email, SMS, CRM, ad platforms and your data warehouse
- Dashboards and reporting shaped around the numbers your team actually reviews, not generic vendor templates
- Consent and compliance tooling — lawful-basis tracking, automated data subject access requests and deletion, retention rules that run on schedule
- Encryption, role-based access and immutable audit logs so access is controlled and every change is traceable
- Event-triggered automations that send a message or update a system the moment a customer does something
On top of that, we build modules for the parts that are specific to your operation and your industry — journey orchestration, churn and propensity scoring, real-time decisioning — usually in a later phase once the core is proven.
How the project runs
We work in phases, and we start small on purpose. Trying to solve every use case in one go is the most reliable way to delay go-live.
- Discovery and planning (2-4 weeks): we go through your systems, your use cases and your data model, assess the quality of the records you will be feeding in, and pin down requirements with the people who will use the platform
- MVP build (roughly 4-8 weeks): event collection, profile unification, a segment builder and activation to two or three key destinations, with identity logic tested against a held-out sample so match rates are visible before go-live
- Expansion (8-12 weeks): more data sources, additional workflows, real-time segmentation, predictive scoring and full compliance automation, rolled out to a second team or channel
- Migration, training and support (ongoing): we move and reconcile your historical data, retire legacy steps in stages, train your team, hand over documentation, and stay reachable when something comes up
Most projects run 3-6 months from the first conversation to a working platform. Enterprise-scale builds with many integrations and a formal compliance review take longer, and we will say so before you commit.
What it costs
Custom development costs more upfront than a subscription. The trade-off is what happens afterwards.
- A fixed build cost instead of a meter that runs on tracked users, profiles or events
- No overage charges when a busy quarter pushes your volumes up
- No vendor lock-in, and no forced migration when a provider is acquired or changes direction
- No per-user fees as the team grows
- Predictable running costs — hosting and maintenance — that you can actually budget
This works best as a build-versus-buy decision, and the honest answer depends on scale. If you are a smaller operation with standard email and retargeting needs, an off-the-shelf CDP is often the sensible choice, and we are happy to help you set one up well rather than oversell a bespoke project. If you are already spending into six figures a year on a CDP, hitting overage charges, or held back by a fixed identity model, custom tends to win on both economics and control. We give you a clear price during your free consultation, once we understand which side of that line you are on.
Where custom CDPs make sense
A custom or composable CDP earns its keep when the off-the-shelf model gets in the way:
- Retail and e-commerce: one profile across online and in-store, powering abandoned-cart recovery, loyalty segmentation and product recommendations without paying for bundled features you do not need
- Professional services and B2B: account-level profiles for ABM, customer health scoring from usage and support data, and expansion campaigns to customers using only part of your offering
- Financial services: customer segmentation by risk and value, churn signals acted on early, and the granular, tamper-proof audit trail the FCA expects — something generic CDP logging rarely satisfies
- Healthcare: patient retention and follow-up communication with special-category data masked and tightly access-controlled; very few mainstream CDPs are suitable here, so a controlled custom build is often the only realistic route
- Media and publishing: subscription retention and paywall decisions driven by engagement data, plus first-party audiences for onsite advertising
- Membership organisations and nonprofits: engagement tracking, renewal forecasting and donor relationship management on data you fully own
The common thread is a trigger event: outgrowing spreadsheets, a GDPR or audit deadline, a merger that leaves you with two customer databases, multi-channel expansion that manual syncing can no longer keep up with, or a SaaS bill that has quietly become hard to justify. Because the build is custom, your CDP handles the compliance rules and the operational quirks specific to your sector — and stays yours as both change.
Common Questions About Custom Customer Data Platforms (CDP)
How does a custom CDP compare on cost to Segment, Salesforce or Adobe?
A custom build costs more to start and a SaaS CDP costs more to keep. Packaged platforms charge by monthly tracked users, profiles, events or consumption credits, so your bill rises as you grow and overage rates often run 30-50% above your contracted rate. Implementation, data migration and premium support are usually quoted separately and can push the real cost well past the headline figure. A custom CDP, or a build on a warehouse or open-source foundation, gives you predictable running costs. For organisations already spending six figures a year on a CDP, custom tends to make sense; below that, an off-the-shelf tool may be the right call, and we will tell you so.
What's the typical development timeline?
Most builds run 3-6 months from first conversation to a working platform, in line with a typical mid-market CDP rollout. We start with an MVP: event collection, profile unification, a segment builder and activation to two or three destinations such as your email tool and CRM. Real-time segmentation, journey orchestration, predictive scoring and full compliance automation come in later phases once the core is proven. Enterprise-scale projects with many integrations and a compliance review take longer.
Can you integrate with our existing systems?
Yes. CDPs typically connect to email platforms (Klaviyo, HubSpot, Braze), e-commerce (Shopify, WooCommerce, Magento), CRMs (Salesforce, HubSpot, Dynamics, Pipedrive), payments (Stripe, Chargebee), analytics (GA4, Mixpanel), ad platforms (Meta, Google, LinkedIn) and warehouses (Snowflake, BigQuery, Redshift). We also integrate directly with legacy and in-house systems that have no off-the-shelf connector. One-way syncs are straightforward; two-way syncs need conflict resolution and identity matching, and we scope that honestly upfront.
How do you handle identity resolution?
Identity resolution is where most CDP projects succeed or fail. We build matching rules around your data: deterministic matching on email, phone or customer ID, plus probabilistic matching where it is justified. We test the logic against a held-out sample before go-live so you can see the false-merge and false-non-match rates rather than discovering them in a live campaign. Because the logic is yours, you can change it as your data changes.
What about data security and UK compliance?
We can host your CDP entirely on UK infrastructure, which keeps your data residency story simple for the ICO, FCA or CMA. Builds include UK GDPR essentials: consent and lawful-basis tracking, automated data subject access requests and deletion, retention rules that actually run, encryption at rest and in transit, role-based access, and immutable audit logs. Where you handle payment or health data, we keep raw PCI or special-category data out of the CDP and tokenise or mask it instead.
How do you handle messy source data?
Honestly, and early. The most common reason CDP projects slip is assuming source data is cleaner than it is. During discovery we assess the data in your CRM, e-commerce and email systems for duplicates, missing fields and inconsistent formats. If it needs cleansing, we plan that work in rather than letting the new platform amplify the mess. A CDP only unifies data as well as the records feeding it.
Do you provide training and ongoing support?
Yes. Marketers and analysts need a few hours to learn segment building and reporting; marketing ops and data engineers need longer for workflow design and identity tuning. We include training, documentation and handover, and offer support packages for changes and enhancements afterwards. You own the software, so you are never forced into an upgrade or a migration on a vendor's timetable.