Every record complete, before anyone has to look it up.
Most CRMs are full of half-records. A name and a company, no role. An email that bounced eighteen months ago. Someone has to look the rest up, and because it is nobody's actual job, it happens the morning of the call or not at all.
This fills the gaps from sources you approve, verifies what it finds, and writes it back. The part that matters is what happens when it can't find something: the field stays visibly empty rather than being filled with a plausible guess.
How a half-empty record gets filled without anything being invented.
A name, a domain or a form submission goes in. Records are pulled, the missing fields filled from your sources, and each one verified. Complete records are written to your CRM. Incomplete ones are still written, but with the gaps left visibly empty rather than filled with a plausible guess.
Good fit, and not.
The second list is the useful one. If you recognise yourself in it, say so on the call and we’ll tell you that rather than sell you something.
Good fit if
- Your records are inconsistent enough that people don't trust them
- Someone on your team researches contacts by hand before reaching out
- You can say which sources you're comfortable using
Not a fit if
- You need personal data your jurisdiction doesn't allow you to collect. We won't build that
- The gaps aren't costing you anything — plenty of teams work fine without them
- You want the fields filled regardless of whether the values are right
What a build usually looks like.
Descriptions of what we build, not case studies. We have no clients yet, and these are illustrations rather than work delivered for anyone.
A backfill build
Works through the records you already have, fills what it can, and hands you a list of what it couldn't.
An on-entry build
Enriches each record the moment it's created, so nobody ever opens a half-empty one.
A hygiene build
Re-checks addresses on a schedule and flags the ones that have gone stale, before a campaign finds out for you.
For whoever asks the hard question.
Every filled field is stored with its source and the date it was found, so a value can always be traced back and re-checked. Verification is a separate step from retrieval on purpose: finding a plausible address and confirming it resolves are different claims, and conflating them is how bad data gets confident.
- Gaps stay gaps
- A field it can't confirm is left empty and marked, never guessed.
- Provenance
- Every value carries where it came from and when.
- Idempotency
- Running it twice over the same record doesn't create a second one.
Thirty minutes to find out whether this is worth building.
Usually one to two weeks. You’ll get a written scope and a fixed price before anything is built, and if it isn’t a fit we’ll say so on the call.
Explore related work