Development of a contact parser for cryptocurrency projects to launch sales campaigns

It is necessary to develop a solution (script/service/make.com scenario) that automatically finds new token projects that meet our criteria and collects contact information of key team members (Founders / C-level / Head of Trading / Head of Listings, etc.) for further launching outbound/sales campaigns.

Expected Result

A ready solution that stores the contacts of found profiles in the structure:

• Project website

• Email

• LinkedIn profile link

• Job title

• Twitter/X profile link

• Phone number

• Telegram handle or Telegram link

Main Logic (2 Parsing Streams)

1) Parsing DEX Screener (new pools)

The solution must:

1. Parse pools for a certain period, periodically check DEX Screener pools, and identify new pools.

2. Identify tokens that:

   • are not in our internal list (we will provide a list in CSV/Google Sheet/JSON format),

   • have newly created pools on DEX Screener,

   • and have listings on at least one centralized exchange (CEX).

3. For each relevant token:

   • find the official project website,

   • extract/find information about Founders / C-Level / Head of Trading / Head of Listings or related roles that are relevant for communication (e.g., BD/Partnerships, Growth, Listing, Liquidity, Market Making).

2) Parsing Token Aggregators (CMC / CoinGecko / etc.)

The solution must:

1. Parse/get data from:

   • CoinMarketCap

   • CoinGecko

   • LiveCoinWatch

   • CryptoCompare

   • + suggest additional relevant sources (e.g., CoinPaprika, Messari, DefiLlama, TokenTerminal — the executor suggests, we approve).

2. Identify token projects that:

   • are not in our internal list,

   • meet the filtering parameters that we will apply (criteria will be discussed, but it needs to be implemented in a way that they are configurable: through a config file / admin panel / launch parameters).

3. After obtaining the filtered list of projects:

   • find the project website,

   • extract the contacts of the required roles and save them to the database.

3) parsing data from centralized exchanges and comparing listings of token projects.
1. Parse data from: MEXC, XT, DEX (Pancakeswap, uniswap, aerodrome)
2. Identify token projects that:

• are not in our internal list,

• meet the filtering parameters that we will apply (criteria will be discussed, but it needs to be implemented in a way that they are configurable: through a config file / admin panel / launch parameters).

3. After obtaining the filtered list of projects:

• find the project website,

• extract the contacts of the required roles and save them to the database.

Requirements for Data Storage and Quality

• Storage in DB (PostgreSQL/SQLite - suggest the optimal option) or in a storage with the ability to export to Google Sheets.

• Deduplication of contacts (to avoid duplicating the same profiles/emails/links).

• Ability to export results to CSV/Google Sheets/Airtable (any 1 option is sufficient, better — 2).

• Logs of operation, error handling, retry/backoff, rate limiting.

• Preferably: a simple mechanism “mark as processed / already contacted”.

Technology Preferences (alternatives can be suggested)

• Python (Scrapy + Playwright / Requests) or Node.js (Puppeteer/Playwright) or Make.com scenarios.

• Preference for official APIs, if available (considering limits); if APIs are not available — careful scraping.

• Docker container for reproducible deployment.

• Scheduler: cron / Celery / another simple scheduler.

• Ability to run on VPS.

What We Will Provide

• An internal list of tokens/projects that need to be excluded (format to be agreed upon).

• Initial filtering criteria and a list of relevant roles.

• If necessary — API keys (if the sources have keys/paid plans).

What the Executor Must Provide

• A repository with code/account with scripts + launch instruction (README).

• Configuration of filters (so we can change rules without rewriting code).

• An example of a test run (demo data/screenshot/log) and a brief description of the architecture.

Criteria for Selecting the Executor

• Experience in web scraping / parsing / automation of lead collection.

• Understanding of limitations (rate limits, anti-bot, stability, dedup).

• Examples of similar projects (links/screens/descriptions).