The questions people ask about LeadGrade, answered in full, read out of this product's own register.
It works your inbound overnight. Every lead that came in — from HubSpot and from your own forms — is scored against your ICP, enriched from the company record HubSpot already holds, and handed to you in the morning as a ranked queue. You open one screen and work it top down instead of reading a form dump.
Because you can disagree with it. Every score carries the rules that produced it — 12 of them — each with the value it read and what that value was worth. "82, VP title +16, 180 employees +14, asked for a demo +20" is a number you can act on. "82" on its own is a number you learn to ignore.
Only what you approve, and only into a field that is empty. LeadGrade writes its own four properties — score, band, top reason, date — and it will fill jobtitle, company, phone, employee count or industry when HubSpot has none. If a rep has typed into one of those, the write is refused, and the refusal is written down with the value it protected.
One OAuth connect and, if you want form leads too, one URL pasted into your form tool. There is no field mapping to configure: the scoring rules ship with a default ICP you can edit, and the write-back only ever touches properties the settings page lists.
Change the rule, not the lead. The settings page lists every rule, the ICP band it measures against, and the band floors. A score is the sum of rules you can read, so a disagreement is always about one specific line rather than about the model.
$9 a month, flat. That is the whole product: your own forms and HubSpot both read overnight, every lead scored with its reasons, enrichment from the company record your CRM already holds, and a write-back you approve and can undo. That is the only plan; there is no seat ladder to work out. The subscription starts when you pay, and cancelling is one control in Settings. No credit meter, no seat bands and no free tier; the demo runs the real scoring engine on a sample book if you want to look first.
Your own CRM. LeadGrade resolves the company record HubSpot already holds against the lead's domain, plus what the address itself tells you — company domain or free mailbox, a person or a shared inbox, a real provider or a throwaway. It does not buy a third-party data set, and it never invents a company size: a lead it could not resolve is scored on its form alone and says so on its own card.
12 rules, run in order, each returning the value it read: seniority of the title, company domain versus free mailbox, shared mailbox, which form it came through, buying language in the message, company size and industry against your ICP, whether HubSpot already knew them, your exclusion list, how much of the form was filled, and whether it could be enriched at all. Hot starts at 70.
No. The scoring pass is deterministic: the same lead and the same CRM record produce the same score and the same reasons every time, months later, without re-running anything. That is what makes the queue re-explainable and the rules arguable.
Kill it in the queue and nothing was written. If you already approved it, an approved write waits 60 seconds before it goes, and after it has gone the value it replaced is still stored — putting it back is one tap and the same window again.
Only if you switch it on. Copilot is the default and writes nothing without a tap. Autopilot queues a write-back for leads at or above a score you set, and every one of those still sits out the 60-second window and still refuses an occupied field.
It keeps scoring. Past 250 lookups a day the pass stops enriching and ranks the rest on what their own form carried, with "scored on the form alone" as a reason line on each card. A cap that dropped leads would be a data-loss bug wearing a cap's name.
HubSpot, through its own OAuth — LeadGrade reads contacts created since the last watermark and writes back to them. Your forms need nothing but a URL: point any form tool that can POST JSON at your endpoint and those submissions join the same queue.
Any that can POST JSON: HubSpot forms, Webflow, Framer, Typeform, or your own site. The webhook reads the field names your form already posts — email, first_name, company, job_title, message and the usual aliases — and answers 422 naming the keys it saw when it cannot find an email, so a misconfigured form is visible immediately rather than dropping leads quietly.
Read and write on contacts, plus company read as an OPTIONAL scope. A portal that declines the optional scope still connects — enrichment then resolves nothing and every lead says it was scored on the form alone, rather than the connection failing or a company size being invented.
Four of its own (score, band, top reason, scored date) and five of yours (job title, company, phone, employee count, industry) — and yours only when they are empty. The integrations page lists all nine before you connect anything.
Reading and writing stop immediately. Everything already scored stays in your queue and your ledger, and the properties already written stay in HubSpot exactly as they are — nothing is retracted behind your back.
In this product's own tables, scoped to your account, and in your HubSpot. Leads are not pooled, not resold, and not used to score anybody else's inbound.
Every answer above is already published on LeadGrade itself, at https://leadgrade.thecompound.tech/. Nothing on this page is written for it: the answers are read out of this product's own question register by a script, and a build gate re-runs that script and fails the deploy if a word here has drifted from it. The register was last re-checked against its sources on 14 August 2026.
WHEN A RULE CHANGES
LeadGrade scores every inbound lead overnight and ranks the queue highest first. The scoring rules and the rails it will write back to both change. Leave an address and LeadGrade writes when one does.
