Supabase Lead Scoring

HubSpot is fine as the shared record for contacts, deals, and ownership. It is a bad place to park every intent, firmographic, and engagement signal you might want to weight later — custom properties multiply, workflows get brittle, and joining three signals turns into a maze of lists nobody trusts as a single priority queue. Clay is the other trap: great at enrichment and enrollment, a terrible control panel for a living score. Every rescoring becomes spreadsheet archaeology.

So the shape is: keep HubSpot as the operational CRM, use Clay for the actions, and put a simple scoring model in a mirrored database you control. Engagement signals and firmographic change signals — headcount growth, funding rounds, hiring — land in Supabase against the same account keys, and a scoring pass produces a living shortlist. Not “who clicked an ad,” but “who should the team be working right now, given everything we know.”

The real problem with account scoring is that it happens once a year while the product and the persona keep moving. When the data lives in a database you control, the interesting interface is a weight dashboard: persona drifts from marketing leaders toward RevOps, you de-weight one, bump the other, and the shortlist reshuffles against the same underlying accounts. No six-week scoring project, no annual ICP refresh, no opening twelve Clay tables to change one assumption.