How Leadkaun scores, ranks and verifies.
Every threshold on this page is the one the product applies. We publish the mechanism because a grade nobody can interrogate is a grade nobody trusts.
Quick answer
How does Leadkaun decide a lead's grade?
Leadkaun computes three independent 0–100 scores for every lead, Fit (how well it matches the customer profile you configured), Intent (live engagement from signal events, which decays as the lead goes quiet), and Quality (whether the record can be trusted). Those combine into an A–F grade on fixed thresholds: Grade A requires Fit of at least 65, Intent at least 60 and Quality at least 60. A Quality score below 20 forces Grade F regardless of the other two. The weights are identical for every account and are not customer-tunable.
01The three scores
What each score actually measures.
They are kept separate on purpose. One blended number tells a rep a lead is a 62, which is not an instruction. Three tell them it is a strong-fit lead that has gone quiet, which is.
Fit
0–100
How closely a lead matches the customer profile you configure.
Industry, state, business type, decision-maker role and budget band, all set once per account in the onboarding wizard.
This is the part you shape. You define who a good customer is; the arithmetic on top is fixed.
Intent
0–100
Live engagement, measured from signal events rather than assumed.
Source strength plus events, a logged WhatsApp reply, an answered call, a pricing question, a negotiation. Each carries a published weight.
Intent decays as a lead goes silent and is floored at the source baseline, so a lead never drops below where it started.
Quality
0–100
Whether the record can be trusted at all.
Phone validity, email presence, company and enquiry completeness, source reliability, plus duplicate and junk detection on insert.
Quality acts as a cap, not an average. Below 20 the lead is Grade F regardless of Fit and Intent.
02The thresholds
The exact cut-offs.
- Grade A (post-contact)Fit ≥ 65 · Intent ≥ 60 · Quality ≥ 60
- F guardQuality < 20 forces Grade F, always
- Intent decay−3 points/day after the engagement threshold (default 28 days)
- Decay floorIntent never falls below the lead's source baseline
- WeightsFixed and identical for every account, not customer-tunable
03How claims are checked
Marketing copy is checked against the product, by machine.
Marketing sites drift from products. Ours did: for a period this site described rules-based lead routing, round-robin distribution and an unassigned-lead queue. None of those exist. They were not invented maliciously, a page cited another page, which cited a third, and nothing ever checked the chain against code.
So the repository now holds a ledger of every capability, what may honestly be said about it, and the product file paths that prove it. The build fails if a page claims more than the ledger allows, and it also fails if one of those evidence paths disappears, which forces a fresh audit instead of letting a stale claim quietly survive.
The same check runs in reverse. It reports capabilities the product ships that the site never mentions, because under-claiming is a cost too.
Where we do not fit, we say so. Our guide to lead routing software ranks other tools and excludes Leadkaun entirely.
04FAQ
Questions about the model.
Your reps open their queue tomorrow.
Setup the same day. 14-day free trial. No credit card required.