What a CDP is, and why CRMs and CDPs overlap
A CRM holds relationship data that people enter: contacts, deals, notes, tasks, call summaries. A customer data platform collects data that systems generate, such as website visits, email opens, billing events and support history, and merges it into one profile per customer that other tools can read. For years these were two boxes on the architecture diagram, joined by a sync that ran hourly, daily or sometimes in real time.
In 2026, vendors increasingly build CDP-style features into the CRM itself. That is a sensible direction, but the useful idea underneath it is older and simpler: the fewer places a customer’s facts live, the fewer places they can disagree.
Why the gap hurts
When the customer profile lives in one system and the job record in another, every event has to travel through a sync. Syncs lag, they fail, they hit limits at busy times. The result is a customer who is correct in some systems and out of date in others: the office sees one version, the technician another, the invoice a third.
For a trades or trucking business the same thing happens with ordinary tools, no CDP needed. A CRM here, a scheduling tool there, accounting somewhere else, a portal somewhere else again. Each hand-off is a place where records can drift apart, and somebody in the office ends up reconciling them with a spreadsheet.
What “one record” means in Operations Link
In Operations Link the client record, the quote, the job, the invoice, the payment and the messages in the client portal belong to one record from lead to payment. With Payroll, a service, approved hours become the next pay run, and pay runs calculate for Ontario, Canada today. A request is checked for who is asking, what their role may do and which company’s records they may see, and the last of those checks is made by the database itself.
That matters most for the two AI services, because both answer from your records. Vera answers your existing customers on your phone line and in your client portal, after checking who is calling, about their own jobs, invoices, quotes and payments. Nova is the assistant you talk to inside the app. An assistant that works from a copy repeats the copy’s mistakes with complete confidence, so what it reads from matters more than how clever it is.
There are seams, and we would rather name them. The books live in your own QuickBooks Online, which Bookkeeping (a service) feeds and reads back from. Payroll, whose pay runs calculate for Ontario, Canada today, produces a payment file for your bank. Operations Link has no public API today, so it is not a source you can pipe into a CDP or a data warehouse.
Four ways to arrange the same data
| Arrangement | Where the customer’s facts live | Hand-offs to maintain | When it fits |
|---|---|---|---|
| CRM plus a separate CDP | The CDP holds the profile; the CRM holds the relationship | A sync in each direction, plus the connectors feeding the CDP | Large marketing teams with many channels and a data team |
| CRM with CDP features built in | In the CRM, with web and campaign data brought in | Fewer, but the other business tools still sit outside | Sales and marketing organisations that live in the CRM |
| Several single-purpose tools | Spread across each tool | One for every pair of tools | Very small teams that use each tool lightly |
| One system for the work | In one record from lead to payment | Only the edges, such as your own QuickBooks Online and your bank | Operations businesses whose customers are also jobs and invoices |
When you do need a CDP
A CDP earns its place when you have many channels producing data about the same people: advertising, a busy website, several email platforms, a store, an app. It also fits a company with a data team that wants customer data in a warehouse. If that is you, a CDP is a reasonable purchase, and Operations Link is not a replacement for one. The case for the single-system approach is narrower: a business that sells jobs, not clicks, gains little from a profile of website behaviour and a lot from a client record that is correct when a customer asks about an invoice.
Three questions to ask a vendor about “embedded” data
- Does the AI read the same records the screens show, or a copy? If a copy, ask how often it is refreshed.
- What happens when a sync fails? Silent drift is worse than a visible error.
- Who may see which rows? Ask where the check is made. A check in the database itself is harder to bypass than one in each screen.
Frequently asked questions
What is a CDP and how is it different from a CRM?
A CDP gathers customer data from many systems into one profile that other tools can use. A CRM is where people manage relationships, deals and tasks. They overlap, which is why vendors keep merging them.
Does a small operations business need a CDP?
Usually not. A CDP pays off when many channels feed data about the same people. A business whose customers are mostly jobs, quotes and invoices gets more from one correct client record.
Why does the gap between systems matter for AI?
An AI that answers from a stale copy gives a wrong answer with full confidence. Where the data comes from, and how fresh it is, decides whether the answers can be trusted.
How does Operations Link keep a customer's facts in one place?
The client record, quotes, jobs, invoices, payments and portal messages belong to one record from lead to payment, and each request is checked for who is asking and which company's records they may see. The books live in your own QuickBooks Online.
Does Operations Link replace tools like Segment or RudderStack?
No. Operations Link is not a CDP and has no public API today, so it is not a source for a CDP pipeline. It suits a business that wants its customers, jobs and invoices in one system.
Related reading: one database or a tool stack · ERP and CRM convergence · consolidating SaaS tool sprawl · the platform · Operations Link and HubSpot · Operations Link and Salesforce