SimplifiedDashboards
Wellness CoachingIdentity mismatches · 90% split

90% of Sales Reps Had Split Performance Data. Nobody Knew It.

When the same rep's numbers live in two systems, you're managing a fiction. Here's what it looked like — and what changed.

Identity mismatches

90% split

Fig. A.04 — Split identity
90%

of 50 reps had performance data split across systems

one query resolved 90% of the mismatches

Split identity. The same rep held as two half-profiles: a setter profile spelled “John S.” in the CRM, carrying 142 leads and $0, and a closer profile spelled “John Smith” in the payment processor, carrying 1 lead and $17,602. The two are drawn apart with no join between them, then passed through the name-unification layer, where one query resolves them into a single record holding both spellings. The halves are never added together.PROFILE 01SETTER"John S."IN CRMLEADS142REVENUE$0NO JOINPROFILE 02CLOSER"John Smith"IN PAYMENT PROCESSORLEAD1REVENUE$17,602UNIFICATION LAYERONE REP · ONE RECORD"John S.""John Smith"ONE QUERY3 SOURCE SYSTEMS · 50 REPSBUILD 2 WEEKS · CLIENT TIME 10 MINUTES
Two profiles, one person. Neither was complete, and no report joined them.

The Setup

The same 50-rep wellness coaching company. We audited the identity layer underneath the reporting in detail.

The Problem

The reporting looked clean on the surface. Every rep had numbers. The numbers seemed plausible. But when we walked every rep's data back through the systems, we kept finding the same thing: their performance was split.

One rep showed up in the CRM as "John S." and in the payment processor as "John Smith." Same person, two profiles, and no system knew to combine them.

The data didn't lie. But it was telling two stories about nine reps in ten.

What We Found

Of the 50 reps, 90% had performance data split across systems.

One rep existed in the data as two profiles: a setter with 142 leads and zero revenue, and a closer with one lead and $17,602. Same person. Neither profile was complete, and no report joined them.

What We Built

A name-unification layer that sits between the source systems and the reporting views. One query resolved 90% of the mismatches. From then on, every report reads one rep as one person.

Two weeks of work on our side. Ten minutes on theirs. That was the client's entire time cost.

The After

When it shipped, every report described one rep as one person for the first time — including the rep whose leads and revenue had been sitting in two different profiles.

The Marketing Director at this client told us:

"Now that we have better insight into next day appointments, I'm starting to work in 2x per day promos"

Closing

This kind of work isn't glamorous. It's the layer underneath the dashboard that the CEO never sees. But every real reporting system depends on it. It's the first layer we audit on every engagement.

Want this for your business?

Want this for your own numbers?

No pitch and no deck. Thirty minutes that ends with a clear picture of what we would build for you and what it involves.