Case Study 14
AI Integration / HubSpot CRM

AI Lead Validator:
For HubSpot CRM.

A custom integration that checks every new HubSpot lead with AI before it reaches sales. Each contact gets a verdict and a plain-language reason on the record, and HubSpot workflows route it from there.

Role

AI & Integration Engineer

Stack

TypeScript, Node.js, HubSpot API, LLM

Platform

HubSpot CRM

Scope

Validation, Reasons, Routing

New HubSpot contacts labelled valid, review or reject by an AI lead validator, with the verdict and reason stored as contact properties and used by a workflow

Fig 0.1 – New contacts with an AI verdict and the reason written to the CRM record.

01 // The Problem

Sales Reading
Spam.

Every form on the website created a contact in HubSpot, and every contact landed in front of sales. That included test entries, personal email addresses with no company behind them, students, job seekers and competitors. Reps spent the first part of each day deciding which leads were real, and the good ones waited behind the noise.

02 // What I Built

A Check on
Every New Lead.

When a contact is created, the integration picks it up and looks at what is known about it: the email domain, the company website and what the person wrote in the form. The AI compares that against the client's ideal customer profile and writes two things back to HubSpot: a verdict and the reason for it. From there, ordinary HubSpot workflows take over, sending good leads to sales and questionable ones to a review queue.

03 // The Hard Part

Verdicts You
Can Disagree With.

A label without a reason gets ignored the first time it is wrong. Writing the reason onto the contact record means a rep can see why a lead was marked and overrule it in one click, which keeps sales in charge of the decision. Cheap, certain checks such as obviously fake emails and disposable domains run as code before the AI is called, so the model only handles the cases that need judgement and the cost per lead stays low.

04 // Built to Last

Outlives the
Model.

The ideal customer profile and the prompts live in configuration, not in code, so marketing can adjust what a good lead means without a developer. The model can be swapped without touching the HubSpot side, and the integration is built on HubSpot's current API rather than the legacy versions being retired in 2027.

The Build.

What the integration adds to the CRM, counted from the build rather than from a sales report.

Every
New Lead Checked
1
Reason Written to Each Record
Code
Checks Before the AI Is Called
Config
ICP Editable Without a Developer
Next Project

AI Document Analyzer for the Energy Industry

→