Bulk & CSV enrichment
Enrich the whole list in one run
Upload a CSV of prospects, start the run, and come back to a file with the contact columns filled in. Progress is tracked row by row, and anything that did not resolve can be retried on its own.
5 free credits on signup · No card required
q3-prospects.csv
68 / 100- 54
- Enriched
- 9
- From cache
- 5
- No result
- 32
- Remaining
Cached rows reuse verification already done for that company domain. Rows with no result cost nothing and can be retried on their own.
Enriching a list one row at a time does not scale
- A list of three hundred prospects is a full day of copying, pasting and waiting if it is done by hand.
- It is the kind of work that gets started and abandoned halfway, leaving a file that is partly enriched and impossible to trust.
- When something fails silently, you find out at send time — from the bounce, not from the tool.
- Restarting a batch usually means paying again for the rows that already worked.
- Nobody wants to leave a browser tab open for an hour supervising a job.
Bulk work needs three things a manual process cannot give you: it must run without supervision, it must tell you honestly what did and did not resolve, and it must let you retry the failures without paying twice for the successes.
Upload, start, come back to it
Upload a CSV containing prospect profile URLs — up to 100 rows per file, with up to 3 files held at a time. Uploading stores the file; nothing runs and nothing is charged until you start the job yourself.
While it runs you get live counters: how many rows are enriched, how many resolved from cache, how many produced no result and how many are still to go. You can close the tab — the job continues, and the state is there when you return.
Rows whose company has already been verified for another prospect resolve from cache, which is faster and avoids spending a second credit on work already done. When the run finishes, download the file with the enriched columns appended.
- Up to 100 prospects per file, 3 files stored at once
- Live per-row status, with a recorded reason against anything that did not resolve
- Retry only the incomplete rows — successful rows are not re-charged
- Cancel a job that has not started processing
- Cached rows reuse verification already done for that company domain
Process
How a bulk run works
STEP 01
Upload the file
A CSV containing your prospects' profile URLs. Row count and URL format are checked on upload, so a malformed file is rejected immediately rather than halfway through a run. Uploading is free.
STEP 02
Start the job when you are ready
Stored files sit in your dashboard until you choose to run them. Your credit balance is checked at this point, not at upload, so you can prepare files ahead of buying credits.
STEP 03
Watch it, or do not
Live counters show enriched, cached, no-result and remaining rows. The job runs server-side, so closing the tab or shutting the laptop does not affect it.
1 credit per enriched row · no-result rows cost nothing
STEP 04
Retry what did not resolve
Rows that failed or were skipped can be retried as a new job covering only those rows. Rows that already succeeded are untouched and not charged again.
STEP 05
Download the enriched file
Export as a full CSV, or in a column layout that maps onto a standard Salesforce or HubSpot import. Downloading is free and repeatable.
Benefits
What bulk enrichment gives you
Unattended runs
Jobs run server-side. Start one and close the tab — progress and results are there when you come back.
Cached rows cost less time
Prospects at a company already verified in a previous run resolve from cache instead of repeating the work.
Targeted retries
Retry only the rows that did not resolve. Successful rows are never re-run and never re-charged.
Scheduled runs
Run enrichment daily or weekly without touching it, with a credit ceiling per run so a schedule cannot overspend.
Failures are free
Rows that produce no verified address cost nothing, so a difficult list does not quietly drain your balance.
Same shape every time
Every export has the same column set, so a downstream import or script does not need adjusting per file.
Who uses this
Export formats
Full export
Every field ReachNow resolved: LinkedIn ID, first and last name, title, company, company domain, verified emails, invalid emails, profile URL.
Salesforce column layout
A CSV whose column headers match a standard Salesforce Lead import, so the file maps cleanly in the import wizard.
HubSpot column layout
A CSV whose column headers match a standard HubSpot contact import.
Limits worth knowing before you upload
- A file may contain at most 100 rows. Larger lists need splitting into several files.
- At most 3 uploaded files are stored at a time — delete one to make room for another.
- Rows must contain a profile URL. A CSV of names and companies alone cannot be enriched.
- Very large runs may have rows deferred by daily capacity limits. Deferred rows are shown as skipped with the reason, and can be retried.
- The Salesforce and HubSpot options are CSV column layouts for import, not live integrations. Nothing is written into your CRM automatically.
That last point is worth repeating because the industry uses "integration" loosely: ReachNow produces a file that imports cleanly. It does not connect to your CRM.
Try it against a list of your own
The fastest way to judge enrichment quality is to run it on prospects you already know something about. Sign up, enrich a handful, and check the results yourself.
5 free credits on signup · No card required · Credits are only spent on enriched profiles