Lead enrichment is one of those workflows that sounds simple until you're actually running it. Build a prospecting list in Apollo, push it through People Data Labs for contact enrichment, get back usable data on maybe 50-60% of contacts, route the gaps to a second data provider, separately verify emails because enrichment sources bounce at 15-20% even when the data looks clean, then manually load everything into HubSpot because none of these tools connect to each other without friction. Five steps. Three paid vendors. Over an hour per campaign.
A practitioner recently documented replacing the whole thing with Claude custom skills - a feature inside Claude that lets you define reusable, specialized instructions the model applies consistently across tasks, turning it into a configured workflow component rather than a general-purpose assistant.
What the Old Stack Actually Cost
The 50-60% usable rate from People Data Labs isn't a knock on that specific tool - it's typical across the category. B2B contact data degrades fast. People change jobs, companies restructure, emails go stale. Any single enrichment source will have meaningful gaps, which is why the multi-vendor fallback chain exists in the first place. The problem isn't any one tool. It's that stringing five tools together creates five points of failure and a lot of manual handoff work.
Email verification as a separate step is also more common than people admit. Enrichment providers sell contact records; they don't guarantee deliverability. A bounce rate of 15-20% on enriched lists is normal, and sending to those addresses damages your domain reputation over time.
Where Claude Fits In
The approach here uses Claude's custom skills to handle the orchestration and gap-filling logic that previously required switching between tools. Custom skills let you encode specific instructions - how to prioritize data sources, what to do when a field is missing, how to format output for a CRM import - and reuse them consistently without re-explaining the context each time.
This isn't magic. Claude doesn't have access to PDL's database or Apollo's contact graph. What it can do is process and reconcile data you already have, apply consistent rules for filling gaps or flagging records, and format output in whatever structure your CRM expects - cutting out the manual steps between tools.
For solo operators or small sales teams doing this work manually today, the time math is straightforward. An hour-plus workflow that collapses into one step is worth testing regardless of whether the output is identical. The enrichment accuracy question is real and worth tracking, but the process overhead alone justifies the experiment.