VANDAMSource Cleanup
Give your agents one versionof every customer.
Three weeks to merge duplicate records, archive dead sources and agree what your key terms mean. Your agents read one customer, one product list and one definition of churn, and every merged field shows the rule that decided it.
$12,800 three weeks
acct 88412ERPC-20417Inbox214 threadsKey accounts.xlsxrow 37Contract 2022.pdfscan, p. 1One recordcust:NW-0001Stale sources
- #northwind-2019
Slack · last message March 2021Archived - Key accounts.xlsxShared drive · last edited 2023Folded in, archived
- /Sales/Old CRM export1,240 files · last opened 2022Archived
- Contract 2022.pdfScanned, no text layerMade searchable
Glossary
Active customer
- Salesplaced an order or took a call this quarter
- Financeinvoiced in the last 12 months
- Supporthas an open service contract
Agreed by Sales, Finance and Support · owner Finance
Company data holds several answers.
Agents pick one.
- 26%
- of their organization’s data is untrustworthy, data and analytics leaders estimate.
Salesforce State of Data and Analytics, November 2025. - 19%
- of company data is siloed, inaccessible or otherwise unusable, by the same leaders’ estimate. 70% of them think their most valuable insights sit in that 19%. Salesforce, 2025.
- 60%
- of AI projects without AI-ready data will be abandoned through 2026,
Gartner predicts.
Marie Kondo for your company’s data (clean it up so agents can use it)
Late CheckoutOctober 2026Source Agents repeat whatever they find.
Most companies keep several answers to the same question.
Point an agent at your systems and it reads every version of a customer with the same confidence. The CRM has one address, the ERP another, a spreadsheet from 2023 a third. The agent picks one, and the answer sounds right whichever it picked. Data and analytics leaders estimate that 26% of their organization’s data is untrustworthy, according to Salesforce.
The Agent-Ready Audit shows where this blocks the first agent. Source Cleanup fixes it. We match the duplicates for the two or three entities your agents need most, settle each conflicting field with a rule the field’s owner signs off, archive what nobody maintains and write down what words like active customer, ARR and churn mean at your company. Company Brain and every agent after it builds on the result.
How do you deal with fragmented data? What is your process to unify without a massive overhaul of our orgs data architecture?
TenexJuly 2026Source Your systems stay where they are. We clean the records inside them, keep a match table that links every source ID to its one record and give agents a read-only connection to the result. A company of 40 needs the same work at a smaller scale, which is why the scope is two or three entities and three weeks.
What your team works from after the cleanup.
Each record shows every source it came from and, field by field, the rule that chose the value. Anyone can see why the address is the ERP address and which spreadsheet row was folded in, and owners settle the matches the rules could not decide.
The glossary sits next to it. When a dashboard, a colleague or an agent says active customer, it means the definition Finance, Sales and Support agreed, with the date and the owner written beside it.
What every cleanup delivers.
Your systems differ. The cleanup is built the same way each time.
Entity scope
The two or three entities your agents need first, agreed at the start.
Match table
Every source ID linked to the one record it belongs to.
Field rules
For each field, which source wins and why, signed off by its owner.
Golden records
One record per customer, product or supplier, written back where you choose.
Source register
Every source reviewed, with an owner and a verdict: keep, archive or make searchable.
Archive
Retired channels, folders and files moved out of reach, with a pointer to what replaced them.
Glossary
Shared definitions for terms like active customer, ARR and churn, each with an owner.
Agent connection
A read-only MCP connection to the clean records and the glossary.
How the three weeks run.
Match the records
We pull customers, products or suppliers from every system that holds them and match duplicates on VAT number, address, email domain and name. Your team confirms the matches we are unsure of.
Settle the conflicts
For each field we agree a rule with its owner: legal name from the ERP, contact from the most recent email, status from the last invoice. The rules run on every record and stay written down next to it.
Retire, define, connect
Sources nobody maintains are archived with a pointer to what replaced them. Definitions are agreed with the teams that use them. The clean records and the glossary are exposed to your agents through a read-only MCP connection.
Cleaned once.
Kept clean every month.
New records arrive with the old habits. After the cleanup we can run the matching and the field rules every month, send new duplicates to their owners and keep the glossary current.
Duplicate sweep
New duplicates matched with the same rules, uncertain ones sent to their owner.
Rule review
Field rules adjusted when a system or a process changes.
Source check
New channels, folders and files reviewed before agents read them.
Glossary session
A monthly check with the owners on definitions that need to change.
What you
receive.
Golden records
One record per customer, product or supplier, with the rule behind every field.
Source register
What stays, what is archived and who owns each source.
Shared definitions
A glossary your teams and agents read from.
Where the cleanup leads.
Each next step has its own service.
Agent-Ready Audit
Comes before: finds which sources need cleaning for the agents you plan.
$9,600
Company Brain
Reads the clean sources and keeps them current.
$19,200
Agent Onboarding
Connects agents to one clean version of the data.
$9,600 + $1,600/mo
Invoice to ERP
Matches invoices against supplier and article data that now agrees.
$24,000
Before you ask.
Which entities do you clean?
Two or three, chosen with you at the start. Usually customers plus products or suppliers, because those are the records your first agents read most.
Do we need to replace our CRM or ERP?
No. Records are cleaned where they live, and a match table links every source ID to its one record, so your systems keep working as they do today.
What happens to the sources you archive?
They move to an archive with a pointer to what replaced them, and agents stop reading them. Nothing is deleted without the owner’s approval.
Who decides which value wins?
The owner of each field. We propose a rule, show the records it would change and run it once they agree.
Claude