KNOWLEDGE 4 min READ

PART OF TECHNOLOGY MARKETING

Ask sales and marketing how many qualified leads came in last month and you may get two numbers, each with a screenshot to defend it. It gets reported as a data problem or a tooling problem. It is usually a definition problem: nobody decided what counts, or which system holds the truth, so both do, and they drift.

Why it matters

The customer record is where marketing, sales, service and finance meet. When it is coherent, a business can answer simple questions: who are our best customers, what did they buy before, who has gone quiet. When it is not, those questions require a spreadsheet, an argument, and someone's memory. The operating model of the whole company runs through this record.

What the strategy decides

• Definitions: what is a lead, a qualified lead, an opportunity, a customer, a lapsed customer. Written down, agreed across teams, with the criteria that move a record from one to the next.
• Source of truth: which system owns which fact. The CRM owns the relationship; the commerce platform owns the order; the support desk owns the ticket. Each connects to the others rather than duplicating them.
• Ownership: who is responsible for a record's accuracy at each stage, and what happens to records nobody owns.
• Triggers: what a change in the record causes. A stage change that creates a task, a lapse that starts a re-engagement sequence. This is where automation attaches.
• Measurement: the pipeline and lifecycle numbers the record must be able to produce without manual assembly.

A sequence that works

1. 01 Map the journey

   The stages a customer actually passes through, from the customer journey map, not the stages the vendor's template suggests.

2. 02 Agree the definitions

   In a room with sales, marketing and whoever answers the phone. Disagreements here are the project; do not paper over them with a field called 'Status'.

3. 03 Decide the fields ruthlessly

   Every field is a tax on the person updating it. Keep the ones that drive a decision or a trigger. Delete the ones kept because someone might want them one day.

4. 04 Choose the tool

   Now, and only now. Fit the tool to the process; the process that fits the tool is the vendor's process.

5. 05 Wire the joins

   Website forms, commerce, email, support: connected so nobody retypes. A CRM updated by hand is a CRM that is out of date.

Why CRM projects fail

• Bought to fix a process problem. The tool arrives; the process is still undefined; the tool is blamed.
• Configured with every field the vendor offers, so updating it is a chore, so nobody does, so the data is wrong, so nobody trusts it, so nobody updates it.
• No source-of-truth decision, so the CRM and the commerce platform both claim the customer and disagree.
• Adopted by marketing and ignored by sales, or the reverse. A record half the company maintains is a record nobody can rely on.

Customer data platforms and where they fit

A customer data platform unifies records from many sources into one profile. It is a solution to the source-of-truth problem for companies with enough sources to justify it. It is not a shortcut around the definitions; a CDP built on undefined stages produces a very expensive unified confusion.

The tool will faithfully store whatever ambiguity you configure.

Which CRM should we choose?

The one that fits the process you have defined, that the team will actually update, and that connects to the systems you already own. Feature comparisons are the wrong lens until the definitions exist.

Can we fix our existing CRM instead of migrating?

Usually, and usually you should. Much CRM pain is definitions and fields, both of which can be fixed in place. Migration costs are real and rarely budgeted honestly.

How do we get sales to use it?

Make it the place their pipeline lives, remove every field that does not help them close, and connect it to the tools they already use so updates happen as a by-product of work rather than as admin.

What does privacy law mean for a CRM?

That the customer record is personal data. Data-protection rules in many countries expect you to collect it for a stated purpose, with consent where the law requires it, keep only what that purpose needs, protect it, and respond when people ask to see, correct or delete what you hold. The details vary by country, so take local advice. The ruthless field list helps here too: data you never collected cannot leak.

GO DEEPER

Reading is free. The diagnosis is a conversation.

Say Hi

NEXT TOPICS TO LEARN