What problem does it solve?
Lead databases store company names the way registrars and scrapers found them — with legal suffixes, taglines, dba entities, parenthetical descriptors, and shouting capitals — and pasting those strings into cold email copy reads like an obvious mail merge that kills reply rates.
Core Features & Use Cases
- Default free normalization: Uses Clay's built-in Normalize Company Name action as the default, with a three-condition test for when to switch on the AI toggle.
- Locked AI prompt with deterministic guards: A benchmarked gpt-4o-mini prompt (98/100 on a 100-row sample) that strips suffixes, taglines, and second-language duplicates, plus a placeholder blocklist and a substring guard that catches invented words for free.
- Abstain and downstream gating: Junk strings like "Self-employed" or "N/A" return an empty value that excludes the row from campaigns naming the company, instead of substituting generic copy.
- Use Case: A list of 5,000 leads contains strings like "AMTC TECH GROUP LLC" and "318, Inc dba Hamiltons Bud and Bloom"; run this playbook to produce "AMTC Tech Group" and "Hamiltons Bud and Bloom" as a sendable {{company_clean}} variable.
Quick Start
Ask Claude to clean the company names in your lead list using the company name cleaning playbook and output a company_clean variable for each row.