Who Are Your Customers? If Your CRM Can't Answer, Start Here
The most foundational question your CRM should answer is the one many CRMs can’t.
Try a quick exercise. Log into your CRM and pull an account report. Can you tell, with confidence, which of those accounts are current customers?
Not "which ones do you personally remember closing." Not "let me check with the rep." Can the system tell you?
For a surprising number of organizations, the answer is no. Setting aside fresh implementations, the majority of orgs we work with have had no reliable way to answer "who are our customers" straight from the platform. They have the C in CRM, but the system can't point to a single customer with certainty.
It sounds like it couldn't possibly be true. These are companies that invested real money in the platform. And yet "who are our clients" is a question their CRM simply cannot answer.
It's a Definition Problem, Not a System Problem
Here's the part that's easy to miss: this is rarely a technical gap. It's a definition gap. Before the system can tell you who a client is, you have to decide what a client is, and most organizations never actually did.
Consider how slippery it gets:
Is a client someone who placed an order in the last calendar year? The last two years?
Is it someone you're actively engaged with right now?
Once a client, always a client?
In a subscription business, it's fairly clean: a client is a client as long as they renew. In a transactional business, you're only as good as the last order, so a company that hasn't needed to buy in eight months is a genuine judgment call. There's no universally correct answer. There's only the answer your organization agrees on and writes down. Until you do that, every report and every "how many customers do we have" conversation is built on sand.
Where the Missing Definition Quietly Costs You
The cost of skipping this shows up in places you wouldn't immediately connect to it.
Numbers that don't reconcile. We're often pulled into a standoff between Salesforce and the accounting system: two lists of "clients" that don't match, and two people each certain theirs is right. It's almost never a data error. Salesforce was counting anyone with a closed-won opportunity in the last 24 months. Accounting was counting anyone who paid an invoice in the last 18. Both are reasonable. They're just answering different questions, and no one noticed until the two numbers had to agree in a board deck.
Everything downstream stalls. You can't segment customers you can't identify. You can't measure retention against a population you haven't defined. Marketing can't run targeted campaigns when there's no clean way to separate active clients from past clients and prospects.
AI inherits the confusion. This is the one everyone cares about now. You cannot point an AI tool at your data and expect a sensible answer about your customers if you never told the system what a customer is. AI doesn't fix a missing definition. It just confidently scales the ambiguity.
How to Fix It
The good news is that the fix is far smaller than the problem feels. You don't need a re-implementation. You need a decision and a place to put it.
Define it together. Get sales, marketing, finance, and customer success in a room. Each likely carries a different working definition, and surfacing that mismatch is the point. Give them a concrete draft to react to ("a client is any account with a closed-won opportunity in the trailing 24 months") rather than an open-ended question. The debate is the work.
Decide where it lives. Too often the definition lives nowhere. The Type field exists but no one maintains it, and no one is accountable for keeping it current. You have two paths: make it a maintained field someone genuinely owns, or let the system derive it through a formula or automation that flips an account to "client" the moment it meets your criteria. We usually prefer the system doing the work, because anything dependent on people remembering will eventually drift.
Make it visible. If the definition lives in the system but can't be seen on the record, it won't be trusted. Surface it where people work.
Reconcile it. Hold your new definition up against accounting, against marketing's list, against whatever shadow spreadsheet has quietly been the real source of truth. That reconciliation is where you'll settle the last disagreements worth settling.
The Bottom Line
"Who is our customer" is the most foundational question your CRM can answer. An organization that can answer it cleanly is miles ahead of one that can't, for reporting, for retention, and for everything AI is about to ask of your data.
If you want a structured starting point, our Data Audit Scorecard helps you turn vague "the data feels off" frustration into evidence you can act on, no form required.
