The customer list nobody can call
Thousands of contacts, and no working numbers against most of them. A pass over the part of it the business would actually work turns an archive into something the team can pick up and use.
Enrichment · Append and check
Data enrichment for a small business is a pass that fills in what is missing from trusted data sources, checks what is already there, collapses the duplicates and marks every new value with where it came from and when. The customer list has a first name and an email for one person, a phone that stopped working for another, and the same customer three times. What came back is never mixed silently into what the business already knew.
A first name and an email, from a sign-up sheet
filledA service address with no contact behind it
partialA customer whose number the business already had
needs a decisionAn illustration rather than a real record. No customer, no address and no telephone number here belongs to anybody. What it is showing is the third row: when an outside file disagrees with something the business already knew, the honest behaviour is to keep both and ask. The common default is to overwrite without telling anybody.
Data enrichment matters because a customer nobody can reach is a customer nobody can serve. Enrichment fills the gaps in records the business already owns, and writes down where each value came from and when, so every row says how much to trust it.
What it is
Data enrichment is the pass that makes the records a business already owns usable. Most customer lists are full of half-records: a first name and an email, an address with no phone, a duplicate of a contact that already exists, a number that stopped working two years ago.
Enrichment resolves them through trusted data sources and public records into a phone number, an email and, for a business that works on homes, the property detail behind the address. Then it collapses duplicates and checks each value, so the list handed to the team is one it can actually work. What a check establishes is that a number is well formed, in service and not a duplicate. That is useful, and it is not the same as establishing that it reaches that person.
It fits any business with an old or messy customer list: a contractor or landscaper with years of job addresses, an accounting office with client emails from three systems, a salon or gym with members who changed numbers, a real estate office with open-house sign-ins. Before anything is appended, we agree with the owner which part of the list is worth working at all.
How it works
Which records are worth a pass, which fields may be filled, and what happens when an outside file disagrees with something the business already holds. The owner approves those rules, and they go on the job before a single record changes.
A phone number for the email-only contact, an email for the phone-only one, and the property detail behind the address where the business needs it.
Numbers and emails are checked rather than assumed. Time spent dialling numbers that no longer connect is a real cost, and one almost nobody counts, which is why the checking happens before the list is handed over rather than after.
Duplicates merge with their history intact. Records that came back thin are flagged as thin, rather than padded out to look complete.
Every enriched value records where it came from and when it was written. Where an outside file disagrees with what the record already held, both values can be kept, so a person settles it rather than a default.
Use cases
Thousands of contacts, and no working numbers against most of them. A pass over the part of it the business would actually work turns an archive into something the team can pick up and use.
Years of addresses from past jobs, many with an old phone or none. The pass fills in what it can, marks where each value came from, and leaves the rest flagged rather than guessed.
The same client appears with three emails. The duplicates collapse into one record with the history kept, and the disagreement over which email is current goes to the person who knows the client.
A first name and a scrawled email become a fuller record, with the property they already own attached and a note saying where the rest of it came from.
Checking first means a campaign is not spending on rows that were never going to reach anybody. And it is cheap to do on a sample before it is done on everything.
Limits
Every other section on this page is selling you something. This is the one that says where it stops. If a vendor cannot tell you this about their own product, you have learned something anyway.
See it live
Everything on this page is a node on the home page. That page is a galaxy that reshapes into a brain, with every service hanging off the core. Open the Data Enrichment node to read the same thing in its own habitat.
Questions
The questions people actually ask about Data Enrichment, answered the way we would answer them on the phone. If yours is not here, ask us and we will add it.
Data enrichment is filling in what a contact record is missing, and checking what it already has: appending a phone number or an email, adding the property detail behind an address where it matters, confirming that a number is in service, and collapsing duplicates. What arrives is an assertion from an outside file rather than something the business observed, which is why the source and the date matter as much as the value.
Skip tracing starts from a property or an address and finds the owner. Enrichment starts from a contact the business already has and completes it. They use similar underlying sources. The legal weight sits with skip tracing, because there is no prior relationship behind it.
Enrichment overwrites the data a business already has only if the pass is set up that way, so settle which way rather than assuming. Decide it deliberately: fill blanks only, keep both values in separate fields, or send disagreements to a person. Whichever is chosen, the previous value, the source and the date should be written to the record. Without them there is no way back from a bad pass.
Contact data has no published rate of going stale worth quoting: the figures that circulate trace back to press releases and vendor pages rather than to a study with a stated sample. What is knowable is the mechanism. A field stops being true when something happens to a person: a move, a new job, a new number. So the rate belongs to the people on a particular list rather than to the data, and it is different for a gym's members than for an accounting office's long-time clients.
Records that cannot be enriched come back flagged as thin or unreachable rather than padded out with a guess. A dead number that looks like a live one is worse than a blank field, and it is paid for in dialling time.
To clean up CRM data, start with the part of the list worth working, not all of it. Collapse the duplicates first, then check the numbers and emails, then fill what is missing, keeping the source and date on every new value. Send every disagreement with an existing value to a person. Then keep it clean going forward with one identity field that every app matches on.
We are based in New York, and the call works for an owner anywhere. Tell us about the business in the form on this page, and we reply.
Read more

August 25, 2026
One invented insurance office runs a data enrichment pass, and the blanks get filled, and so does a field that was already right. How to clean stale contact records in a CRM in an order that protects what you know. What the FTC found when it ordered nine data sellers to explain themselves. Why no honest decay rate exists, and how to measure your own. And the two columns that make every later step possible.

August 25, 2026
One invented roofing company has a duration read perfectly off a signed proposal and still lands on the wrong deadline. Which half of document automation is hard, what research measured on noisy scanned forms and on people, why a deadline is not printed on the page, what the mortgage rules mean by a business day, and what to keep after the fields are filled.
Five free assessments and five free websites, by application.
To apply, tell us about the business in the form, and we reply.
Also built
Website chat · Answers and bookings
An AI chatbot for small business websites that answers and books
Voice · Answering and call-backs
An AI receptionist for small business that answers the calls an owner misses
Prospecting · Lists and skip tracing
Lead generation services for small business: lead lists built fresh for the area
The Singularity · the tipping point
The Singularity: the AI system for small business that starts improving itself
AI assistants · One per repeated job
AI agents for small business: one for each job the team repeats
AI clone · Video and voice of the owner
An AI video avatar and voice clone of the owner