Your website says one price. Your app shows another. A support agent quotes a third. Nobody decided this split should exist — it’s just what three teams updating three channels, on three schedules, produce.
For years that didn’t matter, because a human sat in the gap. Someone reading the outdated page would think “let me just check by calling” and quietly correct for the drift, entirely in their own head. That correction never touched a dashboard, never got logged anywhere. It happened before they acted, and nobody had to ask them to make it.
That’s the part worth naming precisely. Every channel your company runs is effectively its own database, replicated from a shared truth that was never written down anywhere a machine can read. N replicas, no consensus protocol running between them. The system held together for years because the reader resolved the conflict at read time, silently, for free, before acting on whatever they found.
Remove that reader and you don’t get a system that’s slightly less accurate. You get split-brain: every reader acting on a different truth, with full confidence, and no signal anywhere that another version exists. An agent that reads your site gets one answer. One that reads a listing on someone else’s platform gets a different one. Neither doubts what it found, because doubting requires already knowing there’s something to doubt it against.
This is also why fixing the one outdated channel doesn’t fix the failure mode. The problem was never which channel happened to be wrong that week. It’s that nothing in the system has ever compared them against each other, so nothing knows they disagree — and nothing will, until the day a reader who can’t self-correct acts on the wrong one.
Before you touch any single channel, find out how many of yours currently answer the same question right now — and whether they agree with each other.