The single customer view has been a strategic objective for nearly three decades. Most organisations do not have it — not because the technology is unavailable, but because the organisational and governance requirements are consistently underestimated and underfunded.
The Single Customer View Promise and the Reality of Implementation
The single customer view has been a strategic objective for Australian organisations since at least the late 1990s, when the first CRM platforms promised to consolidate customer data across touchpoints into a unified record. Nearly three decades later, most large organisations do not have it. They have fragments of it — isolated within business units, constrained by legacy systems, degraded by data quality issues, and limited by the consent architecture that governs what can be connected and used. The persistence of this gap between ambition and achievement is not the result of insufficient technology investment. It is the result of consistently underestimating what building a genuine SCV actually requires.
The term itself contributes to the confusion. “Single customer view” implies a destination — a unified record that, once built, provides comprehensive visibility of each customer’s history and behaviour. In practice, an SCV is not a destination but a continuous process of reconciliation, enrichment, and governance that requires sustained organisational commitment across multiple functions indefinitely. The organisations that have come closest to achieving a genuine SCV treat it as an ongoing operational programme, not a one-time technology implementation. Those that treat it as a project with a completion date typically discover, at completion, that the data landscape they were building to has shifted and the project must begin again.
The strategic importance of the SCV is unambiguous. An organisation that can connect a customer’s acquisition channel, subsequent purchases, service interactions, digital behaviour, and lifetime value into a single coherent record has a fundamentally different capacity for measurement, personalisation, and strategic planning than one that cannot. The lifetime value calculation that informs media channel investment. The propensity model that identifies high-value acquisition segments. The churn prediction model that enables proactive retention investment. All of these depend on the SCV as their data foundation.
The Identity Resolution Challenge That Most Strategies Underestimate
The core technical challenge of building a single customer view is identity resolution: the process of determining that multiple data records across different systems and channels refer to the same individual. This sounds straightforward in principle and is enormously complex in practice. A single customer may exist in an organisation’s data environment as an email address in the marketing platform, a loyalty card number in the point-of-sale system, an account ID in the CRM, a device ID in the analytics platform, and a postal address in the finance system — with none of these identifiers directly linked.
The Organisational Barriers That Technology Cannot Solve
Every SCV implementation programme eventually encounters the same set of organisational barriers that technology investment cannot resolve. The first is data ownership fragmentation. Customer data in large organisations is generated, stored, and governed by multiple business units with different systems, different standards, and different priorities. The marketing team owns the campaign data; customer service owns the interaction records; finance owns the transaction data; IT owns the infrastructure. No function owns the integrated customer record.
The single customer view is not a technology destination. It is a continuous process of reconciliation and governance that most organisations are not structured to sustain.
The second barrier is the absence of a data quality standard that all contributing systems are held to. An SCV is only as good as the weakest data source feeding it. If customer address data in the point-of-sale system is 40 per cent inaccurate because staff enter it manually at the checkout, that inaccuracy propagates into the unified record and degrades every model built on it. Establishing and enforcing a consistent data quality standard across contributing systems requires cross-functional authority that reporting lines rarely support.
The third barrier is the tension between data utility and data minimisation. Privacy best practice — and increasingly, privacy regulation — encourages organisations to collect only the data necessary for a defined purpose. The SCV imperative pushes in the opposite direction, seeking to accumulate as much customer data as possible to enrich the unified record. Resolving this tension requires a clear and documented purpose framework that can justify each data element in the SCV on the basis of a specific, consented use case.
Why Most Organisations Stop Short
The pattern of SCV implementation failure in Australia is consistent: organisations invest significantly in the technology layer, achieve a partial implementation that covers the highest-priority data sources, and then find that the incremental effort required to integrate the remaining sources — typically the more complex, legacy, or politically contested ones — exceeds the available resources or organisational appetite. The resulting implementation is called an SCV but is in practice a partial customer data consolidation that excludes the data sources where the most complex customer journeys occur.
The commercial consequence of this partial implementation is that the measurement and personalisation use cases that depend on complete journey visibility remain unachievable. The lifetime value model is built on incomplete transaction data. The attribution model cannot connect online and offline touchpoints. The churn prediction model misses the service interaction signals that are its most predictive inputs. The SCV exists; the value it was built to deliver does not.
The Governance Structure That Makes the Difference
The organisations that have successfully built and maintained a genuine SCV share one structural characteristic that is more important than any technology choice: executive-level ownership of customer data quality as a strategic asset. In these organisations, there is a designated executive — typically a Chief Data Officer or Chief Customer Officer — with cross-functional authority over data standards, integration requirements, and consent architecture. This role has budget authority, reporting accountability, and the organisational standing to enforce data quality requirements on business units that would otherwise prioritise local operational convenience over enterprise data standards.
For boards considering the investment case for SCV infrastructure, the governance structure deserves as much attention as the technology platform. A well-governed SCV programme that operates on a modest technology budget will consistently outperform a poorly governed programme on an enterprise platform budget. The technology is the easy part. The sustained organisational commitment to data quality, consent management, and cross-functional integration is the hard part — and it is the part that most investment cases underestimate.