Builder spotlight: How Goldmine turned a LinkedIn scraper into an Apify-winning portfolio

# The problem he solved

Daniel Mesfin was leading development at a US startup when marketing hit a hard limit: every lead required manually opening a LinkedIn profile, reading it, and crafting a personalized outreach email. That process capped the team at about five to ten emails per day.

He built a LinkedIn scraper to extract profile data and fed outputs to a language model to draft outreach. That workflow boosted their daily personalized emails to about 30–40.

# Why he moved to Apify

Self-hosting the scraper introduced new problems: proxies, session rotation, anti-bot management, and operational overhead. He describes the management side as a headache and looked for a platform that would absorb that complexity.

Apify handled the hosting and API layer. He picked up a public Actor to do the scraping, wired it into his pipeline, and infrastructure concerns largely vanished. The platform's publishing flow made it simple to turn local scrapers into live products.

# What he builds and how

Publishing identity: Goldmine (logical_scrapers). He joined Apify in June 2024 and now lists about 40 public Actors, roughly 15,000 users, and reports a success rate above 99%.

• Crawlee: used on about 90% of his Actors to avoid wiring headless browsers, proxies, session management, and anti-bot handling by hand.
• Apify Proxy: paired with Crawlee for network handling.

Notable Actors include a LinkedIn Jobs Scraper and a bulk company scraper that runs without cookies.

# How he scaled productivity

He stopped reinventing the stack for each scraper and created a reusable Actor structure — a scaffold he applies to new projects. He estimates that system makes him 70–80% more efficient compared with when he started.

He treats the Actor quality score as a diagnostic: he reads the criteria breakdown to decide what to improve or remove. When earlier Actors scored poorly, he revisited and reworked them.

With a small team he now builds alongside, he has published 60-plus Actors with the team and estimates a total of 90–100 published Actors overall.

# Community and platform practices

He also followed the Apify publishing guide to prepare input schema, README, and monetization choices before releasing tools. Apify's Actor templates serve a similar onboarding purpose for new developers.

# The contest and recognition

He discovered the Apify $1 Million Challenge on Discord. Less than two years after joining, he won the Europe, Middle East, and Africa (EMEA) regional prize.

# Practical takeaways for a reader

If you have scrapers sitting idle locally, consider publishing them: Apify's hosting and API layer reduce devops work. Use Crawlee and Apify Proxy to handle common scraping elements. Build a reusable Actor scaffold to cut development time, track Actor quality scores as a practical metric, and use community channels for product updates and bug reporting.