Outreacher is a French outbound agency run by Corentin Robert. It handles email, LinkedIn, and WhatsApp outreach, plus senior marketing, for SMB founders and sales teams who want structured outbound but don't want to become ops people overnight. It also takes bigger mandates. A recent one was a large, publicly listed French events group with plenty of salespeople, and CRM and outreach tooling that hadn't kept up.
Corentin stays on each mandate from start to finish. He writes the copy, builds the lists, sets up domains and deliverability, then runs regular reviews of what gets replies. Sending goes through lemlist, where Outreacher has been a partner for two years. Apify Actors sit upstream. They feed those campaigns with LinkedIn URLs, hiring signals, and local company lists, and they handle the sync between a client's CRM and lemlist.
That upstream part is where Corentin says most of the trouble starts. "Most of the pain was bad or stale data, not weak messaging," he says.
I used to lose half a day every week just choosing and patching Puppeteer scripts on my Mac.
-- Corentin Robert, Founder, Outreacher
The challenge: five hours a week lost to scripts on one Mac
Before Apify, Outreacher's data work ran on Node.js and Puppeteer scripts that only worked on Corentin's own machine. They held up until a login wall, a change to a page's layout, or an IP block broke them. He lost about five hours a week deciding which script to run, patching it, and rerunning jobs that failed halfway. Clients saw delays, and the scripts sat in folders on his Mac with no clear owner.
Connecting a client's custom CRM to lemlist meant Zapier or Make. That works for a demo, but it gets expensive and hard to follow once volume picks up. On the events group account, the sales team could sell. What was missing was a pipe that carried fresh market data into the CRM and from there into lemlist.
The solution: client file in, lemlist-ready contacts out
Outreacher's LinkedIn pipeline runs at least once a week for each active client, and more often for some. It runs on the Apify platform, sends through lemlist, and Corentin builds and operates it from Cursor through MCP.
- Client file. A CSV or CRM export with first name, last name, and company.
- Apify enrichment. Actors run in the client's own Apify organization, or in Outreacher's during setup. Profile detail comes from LinkedIn Profile Scraper. When a use case is unusual or comes up a lot, Corentin publishes or extends an Actor on his Apify developer profile, so clients aren't left with a script only he can run.
- Fields kept. LinkedIn profile URL, current role, experience history, time in role, location, and profile summary. These feed lemlist custom variables and shape the copy: icebreakers, a senior or junior tone, and geography.
- Second enrichment pass. Missing emails or phone numbers go through FullEnrich or Enrow after the Actor run, not before. If the bounce rate on a send goes above about 2%, the list counts as failed, and the targeting or enrichment gets fixed before anything scales.
- lemlist import. Contacts go into lemlist through lemlist MCP or the API, from Cursor. Duplicates and variable mapping get checked before a sequence goes live.
The Apify MCP server sped up how quickly Corentin creates and runs Actors, including setting inputs, scheduling runs, and checking datasets. The last step into campaigns runs through lemlist MCP. Apify Store Actors and his own published Actors sit in one organized library, so he doesn't have to dig through one-off repos every Monday.
A typical LinkedIn mandate starts with 1k to 10k+ input rows. Launching the run and preparing the file for lemlist takes about two hours of active work. On the biggest lists, the Actor runs can stretch over several days while he works on other clients. The target is at least 50% enrichment, depending on the ideal customer profile, so a 1,000-row file often yields 500+ lemlist-ready contacts.
Hiring signals and recent posts go into the copy
Title and company alone don't get the replies Outreacher wants. From profile and activity data, the pipeline pulls hiring signals, where someone sits in the org, how long they've been in the role, their recent posts, and the topics they talk about. All of it lands in lemlist variables, so a founder sequence doesn't read like a mail merge.
When LinkedIn isn't the lead source
Local B2B lists come from Google Maps Scraper plus parsing company websites. Travel clients use Corentin's own Airbnb Pro Host · Business Emails by City Actor on Apify Store. Every source follows the same pattern: dataset, enrichment, lemlist.
That Airbnb Actor is one of more than 200 that Corentin has published on Apify Store, most of them built for a client first: French company registries, real estate agent directories, Booking.com hotel contacts, and a tool that checks whether a company uses lemlist.
The events group mandate
For the events group, the job was never "send more cold email." Outreacher lined up CRM data, Apify-backed enrichment, and lemlist so regional reps worked from lists that matched what they already knew about their accounts. Apify automations between CRM fields and lemlist replaced several Zapier bridges.
Now I have a proper Apify library, clients rerun the same Actors, and I stay on copy and deliverability. That is the job I actually sell.
-- Corentin Robert, Founder, Outreacher
The results
- 1k to 10k+ rows per LinkedIn run, with about 50% enrichment as the floor. That often means 500+ lemlist-ready contacts from a 1,000-row file.
- About two hours of active prep per batch. Long Actor runs on large lists keep going in the background for days.
- About 10 hours a week saved across the workflow, from no more patching Puppeteer scripts and from connecting Cursor and lemlist through MCP.
- Bounce rate at or below about 2%. If it goes higher, the list gets fixed before the subject line does.
- About 20 companies onboarded onto Apify, and most still run the Actor setups Corentin built for them.
- Weekly reruns at minimum on most active accounts.
- Listed events group: sales tooling and enrichment aligned without hiring an internal scraping team.
Why Apify stays in Outreacher's stack
Puppeteer on one laptop was fragile, and Zapier-only stacks were expensive and hard to explain. Apify brought scheduling, monitoring, and an API, and clients can rerun Actor configurations that were set up once.
The setup stays the same: client file, Apify Actors (from Apify Store and Corentin's own), FullEnrich or Enrow, and lemlist through MCP or the API, with Cursor and Apify MCP as the way runs get built and operated. New client requests keep shipping as published Actors on Corentin's Apify profile instead of ending up as scripts on one laptop.
As an Apify affiliate partner, Corentin points clients to their own Apify organizations, so their usage stays visible to them.
When I recommend Apify to a client, it is because the data has to hold up in production, not because a demo looked nice once.
-- Corentin Robert, Founder, Outreacher