Every tool your team adopted holds a copy of the truth, and the copies disagree: the project board says shipped, the wiki says in progress, the CRM says a person who left owns it. This employee keeps the records consistent. It watches the systems where the same facts live, spots the drift between them, and reconciles it - so where you look stops changing what you learn.
The facts that live in multiple systems - statuses, owners, dates, client details - get checked against each other continuously, and the drift gets caught in days instead of discovered in meetings.
For every fact, one system is the source of truth you designate, and the others follow it. The rulebook is yours, stated plainly, applied consistently.
A stale label is noise; a client marked active in one system and churned in another is a landmine. Findings arrive ranked by what the inconsistency could cost.
Every reconciliation it performs is logged and reversible, and anything ambiguous arrives as a question instead of a quiet overwrite. You always know what moved and why.
Your private channel opens the minute you hire. No call, no kickoff meeting, no software to install.
It studies your business and writes your Company Brief, then maps the overlap: which facts live in which systems, and where the copies currently disagree.
The first sweep proposes the source of truth per fact and what syncs where. You approve it once, and consistency has a constitution.
The existing mismatches get reconciled in ranked order, then the standing rhythm keeps new drift from accumulating - with every change logged.
Boards, wiki, CRM: the same question gets the same answer everywhere, and your team stops burning meetings on which system to believe.
Like every Tenfold employee, this one runs one opinionated method: a designated source of truth per fact, changes logged and reversible, and ambiguity escalated rather than overwritten - a wrong sync is worse than a visible mismatch. When the field moves, the method moves, and you do nothing to get the update. Here is the whole method.
It reads and reconciles across systems through grants you make once, in your portal's Access tab. You choose per system whether it may write or only propose, every change is logged and reversible, and you can revoke any grant yourself at any time.
The ones that live in more than one place: project statuses, owners, dates, client records, team assignments. The onboarding map finds your overlaps and you choose which ones it governs.
That is an escalation, not a guess: the mismatch arrives in your channel with both values and the history, and your answer becomes precedent for the rulebook.
The guardrails are structural: per-system write permissions you set, every change logged and reversible, and ambiguity escalated instead of overwritten. Most teams start it propose-only and widen the grant as the rulebook proves itself.
Integrations move data; they do not judge it. This employee handles the part integrations never solved: deciding which copy is right, catching the drift integrations create, and keeping a rulebook humans can read.
On a standing rhythm sized to each system's churn, with the riskiest facts checked most often. High-cost mismatches reach you when found, not on the schedule.
An AI employee that tracks every expiring token, key, and credential across your stack, schedules rotations, and alerts with lead time - so nothing dies silently at 2am.
An AI employee that keeps internal documentation current as your systems and processes change - instead of six months behind and quietly lying to whoever reads it.
An AI employee that checks every scheduled job, integration, and credential on an hourly rhythm and reports plainly - so silent failures stop running your business.
An AI employee that processes incoming bills, categorizes them, flags what looks off, and queues everything for your approval - so paying bills takes minutes, not an afternoon.
Requesting this role moves it up the roster - requests set the order roles open for hire, and you will hear the moment it opens.
See all 51 roles