Data Enrichment for RevOps and Data Teams
You do not have a list. You have a database, a decay rate, and everyone downstream complaining about both.
From signing up to your first export
- Minute 0–2. Sign up. No card.
- Minute 2–5. Install the Google Sheets add-on, or copy your API key.
- Minute 5–8. Paste ten LinkedIn URLs, or drop in your CSV.
- Minute 8. Export verified emails and direct dials.
The problem is the decay rate, not the backlog
Contact data decays at roughly two to three percent a month. A one-off cleanup fixes the backlog and then starts rotting the day it finishes, which is why the same project gets re-run every eighteen months by whoever inherited it.
What actually holds is enrichment wired into the system: on record creation, on a schedule for anything older than a threshold you set, and on demand for a segment before a campaign. That is an API problem rather than a CSV problem, which is why this page leads with the docs.
What RevOps teams wire up
- On create. A new record arrives with an email or a LinkedIn URL and comes out with title, company, domain and headcount, so routing and scoring have something to work with immediately.
- On a schedule. Re-check anything untouched for ninety days. The output is both corrected fields and a job-change list, which is the single most useful thing a stale database can produce.
- Before a send. Verify a segment ahead of a campaign so bounce rate never teaches the mailbox providers something you cannot unteach.
- As a dedupe key. Resolving names and companies to a canonical domain and profile URL is what makes duplicates actually collapse.
How it plugs in
| Route | Use when |
|---|---|
| REST API | You are writing the integration yourself. One endpoint, an OpenAPI spec, credits charged on results rather than calls. |
| n8n or Make | You want the pipeline visible and editable without shipping code. |
| HubSpot sync | The records live in HubSpot and should stay there. |
| Google Sheets | The team works in sheets and a migration is not happening this quarter. |
Designing the recurring job itself is covered on the enrichment pipeline page. Migrating off a provider that shut down? See the Proxycurl migration guide.
What we will not claim
Match rates vary by market, seniority and how good your input field is. A LinkedIn URL resolves far better than a name and a company, and phone coverage is materially thinner than email everywhere. Benchmark it against a sample of your own database rather than a published figure, including ours.
Wire it in once instead of cleaning up every eighteen months
Free credits and a documented endpoint. Enough to prototype the job before you put it in front of anyone.
Start free — no card required