The collection of platforms a marketing team uses to acquire, engage, retain and measure customers, typically CRM, engagement platform, CDP or data layer, automation, and analytics. It matters because it's the infrastructure that decides whether customer data drives revenue decisions or sits unused in disconnected systems.

Strategy defines what the stack should do: which journeys to automate, which data to collect, which outcomes to measure. Implementation is the technical execution. Most enterprises have one without the other, a strategy never executed, or configured tools with no revenue logic connecting them. ONE CX owns both. That is the difference between a tool deployment and a revenue system.

Phased remediation running parallel to live operations: full stack audit first, consolidation sequenced by revenue risk, lowest-disruption changes first. Significant simplification is achievable within 60 days without pausing a single campaign.

The DPDP Act requires every piece of customer data used for personalisation to be collected with explicit consent, processed for a defined purpose, and auditable. Built into the architecture correctly, it structures personalisation rather than restricting it: consented first-party data is more reliable and more actionable than third-party data collected without it.

Three things, built in from the start: server-side tracking that survives cookie loss and ad-blockers, a data model connecting individual customer actions to downstream revenue events, and reporting in the language of P&L rather than marketing dashboards. So the CMO shows the CFO which campaign, which journey, which channel moved the number.

A CRM holds what your team knows about a customer: records, pipeline, service history. A CDP holds what your customer is doing right now: real-time behavioural signals from every digital touchpoint. Most Indian enterprises need both, the CRM as the record of relationship, the CDP as the engine of real-time personalisation. We assess which to prioritise in the first two weeks, before recommending any platform spend.

Building it is. Making it earn is ours. Data Engineering owns the foundation: pipelines, identity resolution, the CDP implementation itself, and data quality. Martech Solutions owns what that foundation is for: the journeys, campaigns, consent-governed activation and attribution that run on top of it. If your CDP doesn't exist yet or can't be trusted, the engagement starts with our Data Engineering practice. If the CDP you already run isn't producing revenue, it starts here. On most engagements the two work as one pod the fence is accountability, not a handoff.

A: Martech is the delivery system: unified data in, governed campaigns and journeys out, every send measured. Personalisation is the decisioning layer that makes each interaction individual, recommendations, adaptive content, next-best-action for one customer at a time. Martech decides that a message goes, to whom, and proves what it earned. Personalisation decides what that one customer sees when it arrives. Martech can run without deep personalisation; Personalisation cannot run without the connected foundation this page describes, which is why the two practices are fenced, and frequently deployed together.

Three criteria most vendor pitches avoid: 1. Outcome accountability (are they measured on your revenue KPIs or on deployment milestones?) 2. Platform independence (do they recommend what's right, or what they're incentivised to sell?) 3. DPDP competence (is compliance in the architecture from day one, or legal's problem later?) ONE CX is platform-agnostic, scoped against agreed revenue KPIs before day one, and builds DPDP defensibility structurally. Red flags to watch for: pricing tied to a platform they resell, success defined as go-live rather than lift, and DPDP positioned as legal's problem to solve later