A single customer view is one record for each customer that pulls together what your business knows about them from every system you use: CRM, invoicing, scheduling, support inbox, website and email. Instead of five partial pictures, your team sees one current, trustworthy profile. It is mostly an organizational habit backed by clean data, and it is not necessarily a big new product. For a small or mid-sized business, it can be built without a six-figure data platform if you are clear about what you want it to do.
Below, we cover what it is, the other names you will see for it, how profiles get unified, what can go wrong, what Canadian privacy law expects, and how to decide whether your business is ready.
Table of Contents
- What is a single customer view?
- Is it the same as a 360 customer view or a unified customer profile?
- How is it different from a CRM, a CDP and a data warehouse?
- Why would a small business bother?
- How do systems combine records into one reliable profile?
- What goes wrong, and how do you plan for it?
- What do Canadian privacy rules require?
- How do you build one, step by step?
- Is your business ready? A quick check
- Our perspective: unify the tools before you buy a platform
- Where can we help?
- FAQ
- Sources
What is a single customer view?
It is a consolidated record of everything you know about one customer or prospect. That includes contact details, purchases, invoices, appointments, support conversations, marketing interactions and preferences. The goal is simple: when someone calls, emails or books, whoever is helping them can see the full picture without opening four tabs.
Some practical points that get lost in vendor pages:
- It is a view of the data, not a single piece of software. You can build it inside one custom application, in a data warehouse, or in a dedicated platform.
- It only works if the underlying records are matched correctly. Two "Jas Dhillon" entries that are really one person, or one entry that merges two different people, defeat the purpose.
- It needs an owner. Someone has to decide which system wins when two systems disagree.
If you run a plumbing company, a dental clinic, a property manager or a wholesale distributor in Surrey, the version you need looks like this: open a customer's name and see their open quotes, unpaid invoices, upcoming appointments, past tickets and the last email, all in one place.
Is it the same as a 360 customer view or a unified customer profile?
Mostly, yes. Single customer view, 360-degree customer view, unified customer profile and single view of customer are used interchangeably in most conversations. Some practitioners draw a fine line: the single customer view is the cleaned, deduplicated data foundation, and the "360" is how the business uses it day to day (dashboards, service screens, campaigns). That distinction is useful when you plan the work, because the foundation comes first. For buying decisions, treat the terms as the same goal.
The terms that genuinely differ are the tools people use to get there, which is the next question.
How is it different from a CRM, a CDP and a data warehouse?
This is where most small business owners get stuck, so here is the short version.
| Tool | What it is mainly for | Where it falls short for a single customer view |
|---|---|---|
| CRM | Managing sales and relationships: contacts, deals, follow-ups | Usually does not hold invoices, job scheduling or support history unless you connect them |
| Data warehouse | Storing data from many systems for reporting and analysis | Stores data but does not by itself match people or push profiles back into daily tools |
| Customer data platform (CDP) | Building persistent customer profiles and making them usable for marketing, sales and service | Heavier and more costly than most small businesses need; marketing-centred |
| Custom unified system | One application with CRM, invoicing, scheduling and reporting sharing the same customer record | Needs to be scoped and built around your processes |
The Interactive Advertising Bureau of Canada's CDP guide describes a CDP as software with a persistent unified customer database and API access to other systems, and notes that a data warehouse stores data, is typically managed by IT, and a CDP processes stored data to make it actionable for marketing. It also describes CDPs as complementary to existing systems rather than replacements. Boston Consulting Group makes the same point: companies adopting CDPs often already have warehouses, data lakes or master-data systems, and the CDP sits alongside them.
So "CDP versus data warehouse" is rarely an either/or. The warehouse holds the history, the CDP-style layer prepares and activates it. If you are weighing storage options before anything else, our MVP-first comparison of a data lake and a warehouse for SMBs is a good place to start.
And "customer 360 versus CRM"? A CRM can be the home of your customer 360 if it holds, or is connected to, the other data. On its own, a CRM is one source feeding the view. If your CRM is the system everyone argues about, see when a custom CRM pays off for a small business.
Why would a small business bother?
Because the cost of scattered customer data is paid every day in small pieces. A few examples we see in Surrey and Metro Vancouver businesses:
- Double entry. Someone types a new client into the CRM, then again into the invoicing tool, then again into the scheduler.
- Embarrassing service moments. A customer calls about an invoice and the person answering cannot see that a technician visited yesterday.
- Reports nobody trusts. Revenue by customer differs depending on which system you ask.
- Missed follow-ups. A quote sits unanswered because the sales tool does not know the customer already paid a deposit elsewhere.
The IAB Canada guide lists single-sourced profiles, segmentation, attribution and consistent messaging across channels among the benefits of centralized customer data. In a small firm, the gains are usually more down to earth: fewer repeat tasks and fewer "let me check and call you back" moments. Our clients typically report saving 5 to 15 hours of administrative work per week after their systems are unified. Your result depends on how fragmented things are today, so treat that as a range clients report, not a promise.
How do systems combine records into one reliable profile?
The mechanics are the same whether you use a platform or a custom build. Oracle's documentation on profile unification lays out three stages:
- Identity resolution and deduplication. Records from different source systems are compared using matching rules based on identifiers such as email, customer ID, phone number or name.
- Consolidation. Matched records are grouped under a master customer or account that stays linked to the original source records.
- Promotion and enrichment. Rules decide which value wins when sources conflict (for example, two different phone numbers), and the profile is enriched with derived attributes such as lifetime spend or last contact.
Keeping the link back to the originals matters. If a match turns out to be wrong, you can undo it instead of losing data.
What are "matching rules" in plain terms?
They are the instructions that say two records are the same person. A strict rule might require an identical email address. A looser one might accept the same last name plus phone number plus postal code. Strict rules miss real duplicates, loose rules merge strangers. Start strict, review what is left over by hand, then loosen carefully. If you are cleaning an existing CRM first, read our guide to merging duplicate contacts safely.
Who decides which value wins?
You do, in writing. A simple convention works for most small businesses: the invoicing system is the authority for billing address and legal name, the scheduler for service address, and the CRM for communication preferences. When a rule is not written down, the newest edit tends to win, and that is how good data gets overwritten by bad.
What goes wrong, and how do you plan for it?
Most failed projects fail on the data, not the technology.
- Inconsistent formats. "604-555-0142", "(604) 555 0142" and "6045550142" are one number to a person and three to a computer.
- Incomplete and stale records. Old emails, missing phone numbers, customers who moved.
- No shared identifier. If your scheduler never captured an email, there is nothing reliable to match on.
- Scope creep. Trying to unify every field from every tool in one go.
Experian's documentation on building a single customer view recommends profiling your data first for incompleteness, incorrect values, inconsistent formats and duplicates. We agree with that order: look before you merge. A one-afternoon audit of a sample of 200 records tells you more than a month of planning.
It also helps to treat the result as a living thing. Matching rules need reviewing, new tools get added, and people keep typing things in wrong. A single customer view is closer to a process you maintain than a project you finish.
If the data is moving between systems as part of the project, the six-phase data migration plan and our guide to profiling before a CRM migration cover the sequencing.
What do Canadian privacy rules require?
Bringing customer data together changes how much personal information sits in one place, so privacy law deserves attention at the design stage, not after launch. This is general information, not legal advice. For your specific situation, speak with a privacy lawyer or the privacy regulator.
Which law applies in BC? Transport Canada's privacy guidance explains that the federal PIPEDA does not apply to organizations operating entirely within Alberta, British Columbia or Quebec where substantially similar provincial private-sector laws apply. The exceptions are federally regulated organizations and cross-border collection, use or disclosure. For many BC businesses that means the provincial Personal Information Protection Act is the main law, while a business that sells or shares data across provincial or national borders may fall under PIPEDA as well. Confirm which applies to you before you design anything.
The principles are similar in both, and the Office of the Privacy Commissioner's summary of PIPEDA's fair information principles is a clear way to see them. In practice for a unified profile:
- Purpose. Under PIPEDA, personal information generally may only be used for the purposes it was collected for unless the person consents or the law requires otherwise. A customer who gave you their email for invoices has not necessarily agreed to marketing.
- Limit collection. Collect only what you need for the stated purposes. A unified profile is not a reason to add fields "just in case".
- Access and accuracy. People can ask what you hold, challenge accuracy and have errors corrected. The OPC's self-assessment tool notes organizations generally must respond within 30 days, subject to permitted extensions. One consolidated record makes that much easier than searching five systems.
- Accountability for vendors. Under the same tool, you remain accountable for information handled by third parties and should use contracts or other means to ensure comparable protection.
One upside: a good single customer view makes compliance easier, because you know where each person's data lives. Our guide to data mapping that stands up to PIPEDA audits shows how to document it.
How do you build one, step by step?
For a business with 5 to 100 staff, this sequence works and keeps the first result small enough to finish.
- Pick one use case. For example: "Our front desk can see unpaid invoices and upcoming appointments when a customer calls." A measurable, fairly simple first goal builds momentum.
- Map your systems. List every tool that holds customer data, who owns it, and which identifier it uses (email, phone, customer number).
- Audit quality. Sample records, then count duplicates, blanks and format problems.
- Write the rules. Matching rules, plus which system is the authority for which field.
- Clean and merge. Deduplicate, standardize formats and keep links to the original records.
- Connect the sources. Either sync them into one place or, better for small teams, consolidate into a single application where new data lands in the right record from the start.
- Put it in front of people. A profile nobody opens is not a single customer view. Put it on the screen your team already uses.
- Set privacy and maintenance routines. Consent flags, retention periods, deletion requests, a monthly check of duplicate counts.
For timing, our CRM implementation timeline compares 8-week and 16-week paths with project gates. Once the profile exists, customer journey analytics starting with timeline and identity is the natural next step, and self-service analytics built around ten questions helps your team use what you built.
Is your business ready? A quick check
Answer yes or no:
- Can you name every system that stores customer information?
- Do most records share at least one reliable identifier, such as an email?
- Does one person own customer data quality?
- Do you know the first workflow you want to improve?
- Have you documented why you collect each piece of personal information?
Four or five yeses: you can start building. Two or three: spend a few weeks on audit and ownership first. Zero or one: you are not behind, you are just at the stage where a short assessment saves money. Our AdaptAI Readiness Stack covers five dimensions of readiness and is a good frame for that conversation.
Our perspective: unify the tools before you buy a platform
We build custom software for small and medium-sized businesses, so we see this problem from the inside. Most owners who ask us about a "single customer view" do not have a data problem in the abstract. They have a CRM, a separate invoicing tool, a scheduling app and a pile of spreadsheets, and nobody trusts the totals.
Our view is that for a company of this size, the cleanest single customer view is usually not a new layer on top of those tools. It is fewer tools. When CRM, invoicing, scheduling, reporting and workflow automation live in one application behind one login, every record is created once, the customer ID is shared by default, and the matching problem mostly disappears instead of being solved repeatedly. That is why we build fully custom around each business's own processes and data, and why our clients own the code with no lock-in.
That is not the right answer for everyone. If you have a large marketing operation with many online channels, a dedicated platform may fit better, and we will say so. And no tool fixes unclear ownership. We have seen a beautifully unified system fill up with bad data in six months because no one was responsible for it. Pick an owner, write the rules, train the team, and keep the first scope small.
— Harry Gill
Where can we help?
If you want one record per customer and one login for your team, our custom software work consolidates CRM, invoicing, scheduling and reporting into a single system, built to a fixed price with regular milestones and local support in Surrey and Metro Vancouver. If you are not sure where to start, AI strategy consulting and a discovery sprint are a lower-commitment way to map your systems first, and our data analysis and reporting service turns the unified data into dashboards your team will actually read. See what custom software costs a small business before you talk to anyone.
FAQ
What does SCV stand for?
SCV stands for single customer view. You will also see it written as single view of customer, 360-degree customer view or unified customer profile. In everyday use they all mean one consolidated record of what you know about a customer.
Do I need a CDP to get a single customer view?
Not necessarily. A CDP is one way to build it and suits businesses with heavy marketing across many channels. A small business with a handful of operational tools can often get the same result by consolidating them into one system or by cleaning and connecting what it already has.
How long does it take to build?
It depends on how many systems you have and how clean the data is. A focused first use case can be finished in weeks, while a full consolidation takes longer. Our implementation timeline guide shows how gates keep the work on track.
Is a single customer view legal under Canadian privacy law?
Yes, provided you collect and use personal information for identified purposes, get consent where required, limit collection, protect the data and can respond to access requests. BC businesses operating only within the province are generally covered by the provincial private-sector law, but cross-border activity can bring PIPEDA in. Check with a privacy lawyer for your case.
Sources
- Customer Data Platforms, IAB Canada
- Customer Data Platforms for One-to-One Personalization, BCG
- About Profile Unification, Oracle documentation
- Single Customer View data quality documentation, Experian Aperture
- PIPEDA fair information principles, Office of the Privacy Commissioner of Canada
- PIPEDA Self-Assessment Tool, Office of the Privacy Commissioner of Canada
- Privacy guidelines, Transport Canada