Coverage, not a vanity leaderboard.
See which hot leads are being worked and which are sitting untouched, so no SQL falls through the cracks.
The problem
The failure mode of scoring is a hot lead nobody worked. Teams need coverage visibility, not another activity vanity metric.
What it does
Coverage view
Which SQLs have an open task and which do not.
By owner
Where hot leads are piling up unworked.
Actionable
Reassign or nudge before a hot lead cools.
How it works
Match
Hot leads are checked against open tasks.
Surface
Uncovered SQLs are flagged.
Route
Coverage gaps go to the manager.
Framed as coverage, not gamification, so it protects revenue instead of rewarding busywork.
The failure mode of scoring is a hot lead nobody worked.
The short version.
Is this a gamification leaderboard?
No. It is a coverage view: which hot leads are worked and which are sitting untouched.
Who sees it?
Managers, so they can spot and close coverage gaps before hot leads cool.
What action does it drive?
Reassigning or nudging on uncovered SQLs before the window closes.
See who’s hot right now.
Early access is open for a small design-partner group.