Cleaning Your Data: Who owns it, and can you trust it?

The second step of the build — one named owner per domain, and a source of truth worth trusting.

Part three of the Company Brain series. How naming one owner turns a map into something you can actually rely on — and the two ways ownership quietly fails. About five minutes to read.

01 From a list to one trusted answer

Part two left you with a map: for the accounts domain, a CRM record partly filled in, an agreements folder with three versions and no marker for which is current, and an account owner who holds the rest in their head. The map didn't fix any of that — it doesn't clean anything up and it doesn't pick a winner between three folders. It's a list, not a source of truth.

Clean is the step that turns the list into something you can actually rely on. It starts with one decision: who's accountable for this domain now.

02 Name one owner, not a team

Give the domain one named person, not a team and not a pair splitting it between them. This is a different role than the "account owner" from part two — that's the rep who owns one customer relationship. The domain owner has authority over the whole domain: every account, every agreement, every gap the map found. For accounts, that's usually a head of sales or a senior revenue lead, not necessarily someone who's personally touched every record.

Their job is to be able to say, with confidence, what's correct, what's outdated, where there's conflict, and what should be removed. Not to have written every entry — to be the one person whose call is final when two things disagree.

We're doing the same for our own domains right now: naming one owner per domain, not spreading it across the team.

03 Check four things, not everything

For the domain the owner now runs, four checks — the same four for every domain, every time:

— What's correct — which records match reality right now.

— What's outdated — a value that was true once and isn't anymore.

— Where there's conflict — two things claiming to be true that can't both be.

— What should be removed — entries nobody's using and nobody can vouch for.

For accounts, that's the head of sales going through the CRM record by record: which customers and leads haven't been touched in months, which of the three agreement versions actually has the signature, what's genuinely stale versus just quiet. None of this requires new information — it requires one person with the standing to make the call.

04 Pull what's only in someone's head into the record

Part two named the carrier problem: knowledge that exists only in someone's head is invisible until it costs you something. Clean is where that stops being acceptable. If an account owner knows a deal renewed on different terms than the CRM shows, the domain owner's job is to get that into the record — not to let it stay a fact only one person can produce on demand.

This is the same extraction problem mapping raised, and the same fix applies: ask for the specific missing piece, not "tell me everything you know."

05 What usually goes wrong

Two patterns account for almost every failed attempt at this step.

A whole team owns the domain. Sounds safer than one person — it isn't. When three people could plausibly answer a question, none of them feels obligated to. The ambiguity mapping found doesn't disappear; it just moves up a level, from "which record is right" to "whose job was this."

Two people split it. One owns customer data, the other owns lead data, say. This fails the same way, just with a boundary instead of a gap — the line between the two halves becomes its own permanent argument, and neither owner has standing to resolve it.

Both fail for the same reason: one name attached to the source of truth is what makes Clean work. Anything less and the domain is still, in practice, unowned.

06 Three questions this raises in practice

What if there's no obvious person to own it?

Pick anyway. An imperfect but named owner beats a perfect but undecided one — the point is having someone whose call is final, not finding the ideal candidate. The role can change hands later; the domain can't stay unowned in the meantime.

Does the owner personally fix every record?

No. Their job is the call, not the labor — resolving which version wins, deciding what's stale enough to retire, saying yes when a gap gets filled. The actual data entry can come from anyone; the accountability can't.

What if two versions look equally valid?

Then the owner's judgment is the tiebreaker, and that's the entire point of naming one. A domain with no owner has no way to resolve a genuine tie. A domain with one does — even when the answer is a judgment call rather than an obvious fact.

Part 4 covers wiring a now-trustworthy domain to AI through a connector — and why that stays tool-agnostic by design.

Read Part 4: Connect