This page as Markdownllms.txtllms-full.txtservices.jsonsitemap.xml
# Source Cleanup by VANDAM: Clean the data your agents will read > 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. URL: https://vandam.ai/source-cleanup Contact: hendrik@vibelab.be # Give your agents one version of 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. [Discuss the project](mailto:hendrik@vibelab.be?subject=VANDAM%20/%20Source%20Cleanup) **$12,800** three weeks ## Company data holds several answers. Agents pick one. - **26%** of their organization’s data is untrustworthy, data and analytics leaders estimate. [Salesforce](https://www.salesforce.com/news/stories/data-analytics-trends-2026/) 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](https://www.salesforce.com/news/stories/data-analytics-trends-2026/), 2025. - **60%** of AI projects without AI-ready data will be abandoned through 2026, [Gartner](https://www.gartner.com/en/newsroom/press-releases/2025-02-26-lack-of-ai-ready-data-puts-ai-projects-at-risk) predicts. > Marie Kondo for your company’s data (clean it up so agents can use it) > > Greg Isenberg, CEO, Late Checkout, October 2026, [Source](https://x.com/gregisenberg/status/2113721373482987970) ## 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](https://www.salesforce.com/news/stories/data-analytics-trends-2026/). The [Agent-Ready Audit](https://vandam.ai/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](https://vandam.ai/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? > > Alex Lieberman, Co-founder, Tenex, July 2026, [Source](https://x.com/businessbarista/status/2077143133049995619) 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. ## How the three weeks run. 1. 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. 2. 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. 3. 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. [Ask about monthly upkeep](mailto:hendrik@vibelab.be?subject=VANDAM%20/%20Source%20Cleanup%20care) ## 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. $12,800 three weeks An indication from past projects. The final price can move a little with the size and complexity of your company, and we agree it in writing before we start. For operations, finance and IT leads at 20–500 person companies about to connect agents to company data. Useful after an Agent-Ready Audit, or when a pilot keeps answering from the wrong record. [hendrik@vibelab.be](mailto:hendrik@vibelab.be?subject=VANDAM%20/%20Source%20Cleanup) ## 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.