What a thin record leaves out
A customer record often holds a name, a transaction and an address, and little else. It does not say what the business does, who owns the decision to buy or whether there is an honest reason to get in touch now. A large database can look like a large opportunity while most of it cannot be used.
Enrichment is the work between the record you hold and a lead a person can act on.
What we do with the records
We agree one record group with you: where it comes from, which fields matter and who will follow it up. We then set aside what should not be touched: duplicates, contacts who have opted out, records of unclear source and anyone outside the segment you serve.
For what remains, we fill the gaps we can support. That can mean details from other systems you authorise and, for business customers, the company’s own public information, matched to the right legal entity. Each added detail keeps its source and capture date. The records are then scored, so your team sees where to look first, and each entry says why it surfaced.
One record, worked through
Take a record that holds a business name, a delivery address and an order date. The name is matched to a company on the public register, and the company’s own website says what it does. Both appear as sources, beside what your record said.
The record is checked against your opt-out list and for duplicates, then scored. It reaches your team with the source facts, what was added, what was checked and who owns it. Anything we inferred is marked as a reading. Your team accepts, defers or rejects the entry, and the outcome is written back to your system.
Why we check before we fill
A stored record is not the same as a record you may contact. The ICO says business-contact data can still be personal data and that the rules differ by channel and by type of subscriber. That is why the audit comes first, and why records are sorted green, amber or red before any is used.
The sorting is an operating starting point, not legal advice. The work does not decide whom you may lawfully contact; the basis for each record group is recorded with you before anything is sent.
What stays with your team
Your named person decides who is contacted, and keeps pricing, objections, complaints and anything sensitive. You approve the record group, the sources, the channel, the message, how often it goes and when it stops. A score only sets the order of the list. It is not a judgement about the people on it.
How we start
We start with the audit on one set of records. You export the fields you can authorise, and we map them, count what is usable and look at what your current tools already do before proposing anything on top.
You then receive a recommendation, and it will be one of three: run a small pilot, repair the data first, or stop. If your existing tools already fill the gaps and score the records, we say so. If you hold only an old, finite database, the honest product is a one-off pilot, not a subscription.
A pilot is a finite queue worked by a person, with an outcome log, so the result is measured in your own system.