Free tool
How many places does one customer record live?
Pick the systems you run. See the map of where the same record is scattered, and how many hand-offs keep it almost in sync. Then see the same thing on one owned database that every system reads from. No email needed to see the result.
Which systems do you run?
Your industry (optional, narrows the list)
Tap the systems you run. Pick the ones that hold a customer, client, or job record.
Select two or more systems to see the map.
How we worked this out
Every system that holds the record is a pair with every other one, and n systems make n times n minus one, divided by two, distinct pairs. It is a plain fact about the shape of your stack, not a guess at how often you re-key.
Send this to whoever signs off
Or save the card to paste into a deck or an email
Nothing you enter leaves your browser unless you ask us to email your map. The map is drawn on your device, and the share link only carries the systems you picked.
How many places does your data live?
Your customer record usually lives in more places than you think. The accounting system has a version. The practice or job system has another. The CRM has a third, and a spreadsheet and an inbox hold the rest. Every system that holds the same record becomes its own source of truth. The moment there is more than one, they begin to disagree. The map above counts those places based on the systems you pick, then counts the pairs that must be kept in sync by hand. Five systems is not five problems. It's ten pairs that can drift out of sync.
That pair count is a plain fact about the shape of your stack, not a guess at how often you re-key. The more systems hold the record, the more hand-offs there are, and a hand-off is simply a place where a figure can fall out of step. It is why the totals never quite match, why a change in one place does not show up in another, and why someone spends Friday afternoon working out which version is right.
What one source of truth actually means
One source of truth means the record lives in a database you own, and every system reads from and writes to that, instead of holding its own copy. Update an address once, and it's right everywhere, because there is only one place it is stored. That is the database-first idea, and it is the whole point of the fix view in the map above: the same systems, the same record, one place where it lives, and zero pairs to reconcile.
Getting there is the work we do. We put the record in one owned database, then connect the systems you already run onto it so the data flows once instead of by hand. See how we connect systems, or read how we rebuilt a wealth firm onto one client record drawn from Xplan, HUB24 and Netwealth.