Your Lead Score Needs an Expiry Date

A lead can be a strong fit and still be the wrong lead to work today.

That is where many scoring models break. They add points when something happens, but rarely remove those points when the reason to reach out has gone stale. The result is a queue full of accounts that look urgent on paper and feel irrelevant in the inbox.

A useful lead score should answer two different questions:

Is this account a good fit for us?
Is there a good reason to contact them now?

Those are not the same thing. If your model treats them as one score, old activity can keep weak opportunities near the top of the list long after the buying window has closed.

Fit lasts longer than timing

Company size, industry, location, business model, and technology requirements tend to change slowly. These inputs tell you whether an account belongs in your market.

Timing inputs behave differently. A new executive hire, a funding announcement, a job posting, a website visit, or a product launch can make an account more relevant today. But the value of that information declines with time.

A leadership change from last week may justify a timely message. The same change from six months ago probably does not. A company that visited a pricing page yesterday deserves different treatment from one that downloaded a guide last year.

If both events keep their original points forever, the score becomes a record of everything that has ever happened. It stops being a useful work queue.

The fix is to separate durable fit from temporary priority.

Use three parts instead of one permanent score

A practical scoring model can be built around three parts:

Fit score: How closely the account matches the customers you can serve well.
Timing score: Whether something recent creates a credible reason to start a conversation.
Suppression rules: Whether the account should not be worked right now, regardless of its score.

Fit should be relatively stable. Timing should decay. Suppression should override both.

For example, an account might receive a strong fit score because it is in the right industry, has the right team size, and uses a compatible system. It may then move up the queue after posting several relevant roles.

If those roles are filled and no other relevant activity appears, the account should move back down. It remains a fit, but it is no longer timely.

If the account is already an active customer, has an open opportunity, recently opted out, or sits inside a contractually excluded territory, it should be suppressed instead of ranked.

This structure gives reps a much clearer answer. They are not just seeing who looks good. They are seeing who is worth working now and who should be left alone.

Set an expiry rule for every timing input

Do not let temporary inputs live forever.

For each one, define four things:

What happened? Name the exact event or behaviour.
Why does it matter? Connect it to a likely business problem or buying window.
How long is it useful? Set the period during which it should affect priority.
What happens next? Reduce the points, remove them, or suppress the account if the context changes.

The expiry period depends on what you sell and how buyers make decisions. There is no universal number.

A pricing-page visit may lose value quickly. A leadership hire could remain useful for several weeks. A major expansion project may matter for months. The point is not to choose perfect time periods on day one. The point is to stop pretending every event has equal value forever.

Start with simple bands such as recent, ageing, and expired. Then adjust them using real outcomes.

If accounts contacted within the first band create qualified conversations and those contacted later do not, tighten the window. If good opportunities continue to appear after the current cutoff, extend it.

Do not confuse recency with relevance

A recent event is not automatically a reason to contact someone.

A company anniversary is recent. So is a generic social post. Neither necessarily points to a problem your offer can solve.

Before adding a timing input to your model, ask:

Does this change the account's likely need?
Can a rep explain the connection in one plain sentence?
Would the message still make sense if the prospect asked, “Why are you contacting me now?”

If the answer is no, the event should not increase priority.

This matters because weak triggers create bad personalization. Reps end up mentioning a piece of news without connecting it to the buyer's work. The message looks researched, but it does not feel relevant.

Good timing data gives the rep a reasonable hypothesis. It does not give them permission to force a connection.

Show reps why the score changed

Decay rules will not help if the final score is still a black box.

A rep should be able to see:

why the account fits
which recent event raised its priority
when that event will expire
whether any rule blocks outreach
what changed since the last review

That explanation improves both execution and feedback.

The rep can use the actual reason in their account research rather than inventing one. They can also flag cases where the model is wrong. Maybe a hiring event has no connection to the offer. Maybe a trigger expired too early. Maybe an account should have been suppressed because another team is already in contact.

Without that context, reps either trust the number blindly or ignore it completely. Neither outcome improves pipeline.

Audit the queue, not just the formula

You do not need to rebuild your whole scoring system to find this problem.

Take the top accounts in the current queue and review them manually. For each account, ask:

Is the fit still valid?
What put this account near the top?
When did that happen?
Is the reason still useful today?
Is there any reason not to contact them?
Could a rep explain the priority without seeing the final number?

You will usually find a mix of strong accounts, stale events, duplicated points, and missing suppression rules.

Fix the obvious cases first. Remove permanent points from temporary events. Add expiry periods. Separate fit from timing. Create overrides for accounts that should not enter outreach.

Then review the queue again after a full sales cycle. The goal is not a more complicated score. It is a list that helps reps make better decisions with less digging.

A score should lose confidence over time

Lead scoring often focuses on adding evidence. Good prioritization also removes confidence when the evidence gets old.

An account does not become a bad fit because its timing input expired. It simply returns to the pool until there is a better reason to act.

That distinction protects rep time, improves the quality of personalization, and keeps yesterday's activity from controlling today's queue.

If your highest-ranked accounts cannot explain why they are worth contacting now, your score is not prioritizing work. It is storing history.

FAQ

Should every scoring input expire?

No. Stable fit criteria such as industry or business model can remain until the underlying account data changes. Behavioural and event-based inputs should usually have an expiry or review rule.

How often should timing scores be recalculated?

Recalculate them often enough that the queue reflects how quickly your chosen events lose value. For some outbound teams that means daily. Slower sales cycles may support less frequent updates. The important part is that expiry happens automatically and predictably.

What should happen when a timing input expires?

Usually, remove or reduce the temporary points while keeping the fit score. The account can remain eligible for future outreach without staying at the top of today's queue.

Can several recent events extend the window?

Yes, if each event is relevant and independently verified. A new event can renew priority, but avoid counting several versions of the same underlying change as separate proof.