// PIPELINE HYGIENE · REVOPS CONTROL

Lead-Scoring Agents Need Decay Rules Before They Fossilize Demand

Operator thesis: if a machine worker can keep inflating a score after the buyer stopped caring, the system stops measuring intent and starts preserving fiction.

Fresh intent beats stale certainty

01 PatternScores only go up

Agents add points for visits, opens, meeting clicks, and enrichment events, then never remove them.

02 FailureOld interest still routes hot

Sales sees “high intent” records that have not done anything real for weeks.

03 ControlDecay by time and evidence

Points expire unless the buyer creates a fresh, durable signal with context.

04 DecisionNo fresh proof, no priority

The agent can nurture cold demand. It cannot keep calling it hot.

// WHERE THIS GOES SIDEWAYS

Scoring without decay turns your CRM into a museum of old enthusiasm.

Lead-scoring agents are usually sold as focus tools. They decide who gets routed first, who receives faster follow-up, and which accounts look “sales-ready.”

That only works if the score reflects current reality. When points stack forever, the machine starts protecting yesterday’s intent. Pipeline stays busy, but it is busy with ghosts.

Grounded example

A buyer downloads a pricing sheet, attends one webinar, and visits the careers page twice during a vendor evaluation sprint. The agent pushes the score above the routing threshold.

Three weeks later procurement froze the project. The account is quiet. No reply. No return visit. No meeting booked. The score still says “hot,” so SDRs keep spending prime time on an account that already went cold.

A lead score that cannot cool down is not intelligence. It is trapped momentum.

// DECAY RULES THAT HOLD UP

Every scoring write needs an expiration policy.

Intent should age differently based on the evidence. A pricing-page view should decay fast. A live buying signal with named stakeholders can live longer. The point is not mathematical purity. The point is operational honesty.

Signal class

Decay rule

Soft activityEmail opens, anonymous site visits, recycled enrichment, light content clicks.

Expire in days, not weeks. Never route alone.

Buyer actionDemo request, pricing reply, booked meeting, multi-stakeholder thread.

Hold longer, but force a freshness check before routing priority.

Negative evidenceNo reply, unsubscribe, project freeze note, disqualification, bounced owner.

Subtract immediately and override stale positive history.

Operator overrideRep confirms active deal motion with current notes.

Temporary extension with owner name and timestamp attached.

// CONTROL PLANE CLOCK

Make the agent prove recency before it decides priority.

1 Collect

Capture the event with timestamp, source, and account identity.

2 Classify

Mark whether the signal is soft activity, buyer action, or negative evidence.

3 Decay

Run the expiration window automatically instead of preserving points forever.

4 Route

Only priority-route accounts with fresh evidence above threshold.

// OPERATOR TAKEAWAY

Use this rule before scoring agents touch your queue.

Attach a half-life to every scoring signal before the agent can write priority.
Separate vanity engagement from durable buying evidence.
Let negative evidence subtract faster than positive history accumulates.
Require a named owner for any manual extension of a “hot” score.
Audit routed accounts weekly for age of last meaningful signal.

Decision rule: if the score cannot explain why the account is hot right now, the machine worker should not be allowed to treat it as hot.

What A Head Of Growth Should Do Next

Open your top-scored queue and check the age of the last meaningful buying signal on the first 25 accounts. If too many are living on inherited points, your routing logic is flattering itself.

The fix is simple: put expiration policy next to every scoring signal, then let fresh evidence outrank historical noise.