Forty-four percent of revenue teams say their AI data isn't ready. That's the headline finding from MarketScale, and it sits on top of a quieter shift: fragmented buyer identity has stopped being a CRM housekeeping issue and started showing up as a revenue ops problem.

What does "fragmented buyer identity" mean at the deal level?

It means the same procurement director at the same Fortune 500 account exists as three records in your CRM (the database salespeople work out of), one enriched contact in your marketing automation tool, and a separate company hierarchy in your sales intelligence vendor. When your account executive opens the account, they see contradictory titles, conflicting email domains, and stale firmographics (company-level attributes like revenue, headcount, and industry).

Why does AI readiness collapse under fragmented identity?

The 44% points to an upstream constraint. Before a team can ask a model to score an account, draft a follow-up, or summarize a call, the data feeding that model has to resolve to a single buyer. MarketScale's framing treats identity as table stakes — a foundational prerequisite — for revenue AI, not a feature you unlock at the vendor layer.

What changes for the frontline rep?

The rep stops trusting the system. When the CRM shows two titles for the same stakeholder, sellers revert to manual research. That cuts active selling time and lengthens cycle.

Outbound teams feel it in deliverability and reply rates. Enterprise teams feel it in account mapping and stakeholder coverage. A duplicated champion record (the internal buyer who advocates for your solution) can stall a six-figure deal because nobody owned the follow-up.

Where the problem actually lives

Identity fragmentation sits inside revenue operations, not sales enablement. RevOps owns the systems of record. When those systems disagree about who the buyer is, every downstream tool — conversation intelligence, forecasting, lead scoring — inherits the disagreement. That's why MarketScale frames this as a RevOps problem rather than a sales problem.

The 44% gap is the symptom. The cause is years of point-tool procurement (buying individual software pieces without unifying the data underneath) without an identity layer. Each vendor added its own record schema, and nobody consolidated.

What does a RevOps-led fix actually change?

For a 50-rep team, the standard move is consolidation onto a single source of truth — usually the CRM, with a reverse-ETL layer (pushing cleaned data from a warehouse back into operational tools) feeding the enrichment stack. For a 500-rep enterprise, the move is a dedicated data engineering pod owning identity resolution.

Either way, the first decision is governance, not tooling. Who owns the canonical buyer record? Who reconciles conflicts? Without an owner, no AI vendor will fix it.

What to watch next

The next reporting cycle from MarketScale will likely track whether the 44% moves. If AI-vendor adoption keeps outrunning data readiness, the gap widens. If RevOps budgets reallocate toward identity resolution, the number compresses. Either direction reshapes how sellers experience their stack, because every workflow change in the tooling layer lands on the rep's daily screen.

For now, the buying signal is straightforward. Ask your RevOps leader this quarter who owns buyer identity. If the answer is "everybody," you're in the 44%.