On 14 March 2025, Apollo.io sent an email to its free-tier users that landed like a quiet grenade. The monthly free credit allowance, which had sat at 10,000 for years and attracted hundreds of thousands of individual salespeople and founders to the platform, was being reduced to 720.
That is a 93% cut.
I remember reading it twice, assuming I had misunderstood. I had not. 720 credits. For a solo founder doing targeted outbound, 720 verified contacts per month is the difference between having a pipeline and not having one.
The forums erupted. r/sales, r/coldemail, LinkedIn posts, Slack communities — everywhere I looked, salespeople and founders were asking the same question: what do we use now? Clay was popular but expensive for solo operators. Clearbit had been acquired and repriced toward enterprise. ZoomInfo was always enterprise. Hunter.io was strong for email finding but not LinkedIn profile enrichment. Lusha had capped its free tier even harder than Apollo.
Every tool in the stack seemed to be moving up-market simultaneously, leaving a gap at the bottom where individual founders and small teams live.
I did not want to spend £150/month on a tool I used for fifteen minutes a week. What I wanted was to pay for what I actually used — verified contacts, on demand, at a price that made unit economics work for a consultancy my size.
So I built the LinkedIn Contact Enricher.
The actor takes either LinkedIn profile URLs or company domains as input. For each input, it does two things. First, it uses Hunter.io's API to identify the most likely email address pattern for that company and the most likely contact at the seniority level you specify. Second — and this is the part that matters — it passes that email address through Reacher for SMTP verification. Not a probabilistic confidence score. An actual server-level handshake that confirms the inbox exists and will accept mail.
The distinction matters enormously if you care about sender reputation. Bounce rates above 5% start damaging your email deliverability. Above 10%, you are putting your entire domain at risk. Apollo's EU bounce rates, reported anecdotally across multiple SDR forums, run between 15% and 35% for European contacts. That is not a tool problem — it is a database freshness problem. A static database that is not continuously re-verified goes stale fast, especially for mid-market European companies where employee tenure and contact details change frequently.
The difference with building my own enrichment layer is control. I am not drawing from a static database of stored emails. I am finding the pattern, generating the most likely address, and verifying it at runtime. The data is as fresh as the moment the actor runs.
You bring your own Hunter.io key and your own Reacher key. Both have free tiers that cover the volume most founders need. Hunter.io gives 25 free searches per month on free tier, 500 on Starter. Reacher gives 50 free SMTP checks per month. For a founder doing targeted outbound — fifty to a hundred enrichments per week rather than industrial-scale blasting — this combination costs almost nothing.
The actor charges £0.004 per contact enriched with a verified email, and £0.002 for contacts where we found a pattern but could not verify. You only pay full price for results that passed the SMTP check. That felt like the right incentive structure to build: you should not pay the same for data that might bounce as for data that will not.
What surprised me building this was how many people had already tried to solve the problem manually. I spoke to a recruitment consultant in Cambridge who was spending two hours every morning on LinkedIn, copying profile URLs into Hunter.io one at a time, then manually running each resulting email through Email Verifier tools in another tab, then pasting results into a spreadsheet. That workflow — copy, paste, check, copy, paste, check — was eating twelve hours of her working week.
The actor collapses that workflow into a single API call. Give it a list of LinkedIn URLs or domains. Get back a list of verified contacts. The entire thing runs unattended while you do something else.
Apollo's pricing decision was frustrating in the moment. In retrospect it was an instruction: do not build your workflow on top of a vendor who can change the terms unilaterally. Build on data sources you control, enrich through APIs you own the relationship with, and verify at the point of use.
That is what this actor does. And it costs a fraction of what I was paying before.