Can I mix inbound and outbound sources in one project?

Yes, if they share the same ICP and scoring rules. Use separate projects when disqualifiers or offer context differ.

How does Eryx handle duplicate companies from two sources?

Candidates consolidate inside the project run history. Enrichment and scoring apply once per account so exports do not double-count.

When should I still use a spreadsheet?

For client-supplied static lists or conference badges with no discovery step. Import is a bridge; recurring prospecting should stay in projects.

Eryx

Guides

Multi-source B2B prospecting (without spreadsheet chaos)

Combine web, social, and directory discovery into one Eryx project instead of merging CSVs—so every run stays scoped, scored, and exportable.

Start free All guides

Short answer

Multi-source prospecting means pulling candidates from several discovery channels into a single project workflow—discover, enrich, score, review, export—without hand-merging spreadsheets.

Why teams end up with five spreadsheets

A typical outbound week starts with a LinkedIn export, a Google Maps scrape, a directory download, and maybe a conference attendee list. Each source uses different columns, company names, and dedupe rules. RevOps spends Friday merging VLOOKUPs instead of reviewing fit.

The problem is not the number of sources—it is the lack of a shared project boundary. Without one, every new channel creates another orphan file that never connects to scoring or review history.

One project, multiple discovery inputs

In Eryx, a project stores ICP instructions that apply to every discovery run—whether you start from web search, social profiles, or structured directories. Runs accumulate inside the project, so enrichment and scoring treat all candidates with the same disqualifiers and weights.

Teams can run separate discovery passes per source but review one ranked cohort. Exports include fit reasons regardless of where the account first appeared.

Operational habits that keep lists clean

Tag or note the discovery channel in project instructions so strategists can compare source quality over time. Clone the project when you change ICP—not when you add a source.

Reserve spreadsheet merges for one-off event lists; recurring outbound should live in projects where dedupe, enrichment status, and review gates are automatic.

Related resources

lead search blog guides

Frequently asked questions

Build your next qualified pipeline in Eryx

Discover, enrich, score, and export B2B leads in one workspace—so outreach starts after qualification, not before.

Get started View pricing