You're launching. Check the list first.
Send us the file you're about to rely on. Every row comes back cleared for use or kept out. This is what a kept-out row looks like:
left the organisation
An example pass. The organisations, people, findings and dates in it are invented.
We sell no contact data. When we remove a row, we are not the ones selling you its replacement.
From the list you were handed to the list you can work.
Every new client arrives with a spreadsheet nobody trusts. It came out of somebody else's system, nobody has checked which addresses still accept mail or which numbers are still live, some of those people have moved on, and there are duplicates in it that nobody has counted.
When it goes wrong, it goes wrong in front of your client.
What a pass does
the same six rows, before and afterA pass is one run of every check across one file.
The list you were handed
Every check runs across the file
The list you can work
Below, six rows as they arrived and the same six after a pass, in the same order. We chose these six so each of the four outcomes appears, which is why almost every one carries a finding.
Where we wrote something into a cleared row, the changelog records what the cell held before and what it holds now.
An example pass. The organisations and people above are invented and the findings are illustrative, not measured.
The four outcomes
This is the shape every row lands in. It is the structure of the work, not a reading of your list. Nothing has run for you yet.
In the returned file, in the shape it arrived. Same columns, in your column order, same headings.
In the stopped rows, with one line of reasoning against it and the date we checked it. Nothing leaves your list silently.
In the Decision Brief, with what we found, the date, and our recommendation. You confirm or override.
Out of the cleared file by default, with the safe default stated. Do nothing and it stays out.
One file to work from, and the record behind it
One file is the deliverable. One asks something of you. The rest are the record behind them, and you may never need to open one.
The list, in the shape it arrived
Your columns, in your column order, carrying the rows that passed every check we could complete.
It is the file you send from.
You do not have to open any of these. They are there when someone asks you why a row is or is not in the list.
The channel verdict, on every contact
What the checks returned, contact by contact, each with the evidence and the date it was checked.
The stopped rows
Every row we removed, with the reason and the date. Put any of them back if you disagree. It is your list.
The Decision Brief
The rows we could not settle on our own. Each carries the evidence we read, the position we recommend and a safe default that holds if you do nothing.
Two rows in your file are the same person. We found them and we say so. We will not tell you which of the two to keep, because that is a call about your list, not about the evidence.
If you do nothing at all, every row in the brief stays out of your cleared file.
The changelog: what we changed, what we found and left in place, with the reason and the date
Every change, every removal, and every difference we found and left in place. The reason and the date checked.
The withheld addresses, in the shape of the destination you name
The addresses kept out of the send, in the shape your sending tool loads.
The row passports
One card per row: the verdict it carries, the evidence behind it, and the date we checked. Rows that arrived with neither an email address nor a profile URL carry no card, and the document says how many.
The link: one private page carrying the counts, the categories, the dates and every file by name, with no contact rows on it.
Outside the seven, and never counted into them: the Client Note, a one-page note you forward to your own client, under your own name.
It says the list was checked before anyone worked it, what cleared, what was held rather than guessed at, and what could not be checked. Our name is not on it.
Your files are yours to keep. What we hold on our side, and for how long, is set out in our retention statement.
What is in this download: the cleared file in the shape it arrived, the channel verdict, the stopped rows with the reason beside each, the Decision Brief, the changelog, and the one page note. A real pass adds the withheld addresses and a private link to its own pass page, neither of which can travel in a public download. The note that it is invented travels inside every file.
Who it is for
Agencies and consultancies first. Marketing, recruitment, and any team handed a list to work, in-house or for clients.
If someone else built the list you are about to send or call, this is for you.
WHEN IT COMES UP+
It tends to come up when a bought or supplied list arrives, when a big send is going out, when work is handed back to a client, when a new client is onboarded, when a system is migrated, or on a call day.
Who it is not for
If you need a list built, we are not the fit. We sell no contact data; we clean the list you already hold.
Consumer lists are not a fit. Our checks read roles, organisations and work mailboxes; a consumer list gives them nothing to read.
There is nothing to log into. We hand back files.
We stop before the send. Nobody here runs your campaign.
Why us
Deduplication tools never check a mailbox. Enrichment platforms never read your file as a file. We do both in one pass and hand back a finished list.
A dated finding for every contact we could check, with the evidence behind it. Where the evidence is not strong enough to stand on its own, a person looks at it before anything is written into your file, and if it still will not stand up the cell is left empty.
Tell us which organisations are your clients and which are competitors, and those rows are kept aside on your instruction, with the reason, out of the list you work. Where we find a current employer, somebody who has moved into one of your clients is caught by where they work now, not by what your row said.
You send one file and get one back, finished: the cleared list in your own columns, the stopped rows with a reason and a date against each, and our position on every row we could not settle.
Every other row is accounted for, with what we found and the date we found it.
You work the cleared file without second-guessing it: what was removed carries the reason, what was uncertain was held, and nothing left silently.
The list you did not build goes out as yours.
An example pass. The organisations and people in it are invented and the figures are illustrative, not measured.
MEASURED, NOT ILLUSTRATIVE
Between 9 June and 9 July 2026, of 311 addresses checked, 80 should not have been sent to.
The only measured figures on this page. Everything above that looks like a pass is an example.
No one should launch on an unchecked list.
That's the whole idea. Everything on this page is the mechanics of making it true.
The way in
Send us the client list you trust least and pick a call slot.
READ MORE+
We run it the day before, email and phone across the whole file and the identity check on up to one thousand rows, and show you three numbers, cleared, removed or held, could not check, with your own rows on the screen while we talk it through. No cost, and if nothing in there surprises you we stop.
One flat price per pass, quoted from your file's size before we start.
READ MORE+
No minimums. No balance to run down, no credits, no surprise charges. A first pass is invoiced when the work is in your hands.
Your column mapping, the keys we use to recognise a row again, and your output answers. It is yours.
READ MORE+
The list you send next is read the same way, and a contact you have already sent us is recognised as one you already had. If you ever stop we hand the baseline over.
The first check is free. After that, one flat price per pass, quoted from your file's size before we start. No per-row credits, no subscription.
What it costs →The free check takes one whole file, roughly 500 to 5,000 rows, and the more rows you send the more it will show you.
You get the counts and your own rows on a call, not a file back, once per organisation.