Every report, routing rule and AI feature downstream inherits whatever the CRM gets wrong. This is the work that made it right, and the guards that keep it that way.
Salesforce
Apex
Flows
HubSpot
Postgres
SQL
Python
Why this had to be built
When the work started, 106 of about 16,000 leads had ever converted, 11,579 sat in “New” indefinitely, and Salesforce and HubSpot agreed on lead status only about 45% of the time.
Five automations that keep leads and accounts clean as they arrive: match every lead to the right account, name accounts properly, keep lead source meaningful, verify every email before anyone sends to it, and label every contact by seniority and function.
What it did
Lead-to-account matcher: a 200-lead trial, then 7,175 leads in 72 of 72 batches. Accounts went from 1,192 to 4,136, of which 2,944 were created automatically, with 0 duplicate domains. A check at conversion now stops reps creating duplicate accounts.
Account naming: auto-created accounts start out named after their domain. A 479-account backfill read each homepage and wrote 397 real names, all correct on a hand check; 83% needed no human touch.
Lead source: 32 legacy values consolidated to 7, set automatically on new records by flows and custom metadata.
Email verification: form fills were hard-bouncing at 2.7%. Every address now gets a SEND / DO NOT SEND / UNSURE verdict in both CRMs, cached for 90 days; a backlog of 8,597 was scoped down to the 2,942 that needed checking.