HeatCheck
Feature

Three tiers, one hand-raise signal.

Cold, MQL and SQL, with thresholds you set, so a number becomes a decision a rep can act on.

Get early accessWatch a walkthrough
01

The problem

A raw score of 63 tells a rep nothing. Without a tier, everyone invents their own cutoff and the score means something different to each person.

02

What it does

Clear labels

Cold, MQL and SQL replace an ambiguous number.

Your thresholds

You set where each tier begins.

Routing-ready

Tiers drive HubSpot workflows and rep tasks.

03

How it works

Step 1

Score

The cumulative total is computed.

Step 2

Bucket

The total maps to a tier by your thresholds.

Step 3

Write

The tier lands on the contact for routing.

One shared ladder means the whole team reads the same signal the same way.

A raw score is a number. A tier is a decision.
Questions

The short version.

Can I change the thresholds?

Yes, the point at which a contact becomes MQL or SQL is yours to set and change.

Why three tiers?

Cold, MQL and SQL match how most teams already route leads, so it drops into your existing motion.

Do tiers drive automation?

Yes. Tiers can trigger HubSpot workflows and rep tasks.

See who’s hot right now.

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

Get early accessSee how it works