HeatCheck
Feature

A score built from what buyers actually do.

One cumulative score per contact, built from real behavior across every signal source, on a rolling 90-day window, bucketed into Cold, MQL and SQL.

Get early accessWatch a walkthrough
01

The problem

Most lead scores reward the wrong things. A student downloading whitepapers outranks the VP who went straight to a demo, because the model counts form-fills, not intent. Reps stop trusting the number and ignore it.

02

What it does

Per-occurrence

Every action scores every time it happens. Engaging across ten posts counts as ten signals, not one flag.

Configurable weights

You set the points per signal type, so a demo-page visit can outweigh a newsletter open.

Three clear tiers

Cold, MQL and SQL, with thresholds you control, so reps know exactly what a number means.

03

How it works

Step 1

Stack

Signals accumulate per contact across LinkedIn, webinars, gated content and page visits.

Step 2

Decay

Old signals age out of the 90-day window, so heat reflects recent behavior, not history.

Step 3

Tier

The running total maps to a tier and writes to the contact for routing.

The score is never a black box. Every point is traceable to a specific signal, so a rep can see exactly why a contact is a 7.

A lead score you do not trust is just a random number in the CRM.
Questions

The short version.

Is scoring cumulative or a one-time flag?

Cumulative. Each occurrence of a signal adds points, so a highly active contact rises above one-off engagers automatically.

Can I set the weights?

Yes. Points per signal type and the Cold/MQL/SQL thresholds are all configurable.

Does the score ever go down?

Yes. Signals decay out of the 90-day window, so a contact that goes quiet cools off.

See who’s hot right now.

Early access is open for a small design-partner group.

Get early accessSee how it works