Lead Signal Radar

Reads the same cdp_events rows the first-party collector writes. Each signal decays on its own half-life — a pricing visit is stale in a fortnight, a project reaching production still counts a quarter later — so an account that exported a quote package this morning does not look like one that did it in March. Scores show their own arithmetic, because an intent score a salesperson cannot argue with is one they ignore. The public-signal half (hiring, funding, technographics) needs a vendor and none is connected, so those rows say unavailable rather than quietly scoring zero.

Lead Signal Radar

Intent Signals

Recency Decay

Explainability

Reading the event store…

How it works

Reads the first-party event store — the same cdp_events rows the collector writes.
Each signal decays on its own half-life: a pricing visit goes stale in days, a project reaching production is still worth something a quarter later.
Every score shows its arithmetic. An intent score a salesperson cannot argue with is one they will ignore.
Signals that need a vendor are listed as unavailable rather than silently scored zero.

Where the signals come from

Built on the event layer in these same Labs, so the signals are ours rather than rented. The public-signal half is deliberately unbuilt — see the panel below.

First-Party Event Layer