Lead Score Decay: Let Research Signals Expire at the Right Speed

November 08, 2026•11 min read

Research does not remain equally useful forever. A request related to an urgent replacement can become irrelevant quickly, while a complex capital project may develop over months. Intent data recency should reflect the business decision being made. Score decay is the rule that reduces the influence of aging observations. A clear decay policy helps prevent old research from crowding out current opportunities.

A useful starting point for revenue operations managers is to name the desired result: a timely qualified conversation. Evaluate one account and offer pair at a time using a documented entry rule. This prevents a dashboard from mixing activity, people, accounts, and opportunities in a single success total. The practical approach is to make each transition explainable before increasing volume.

A worked business example

Consider a commercial equipment distributor serving both emergency repairs and planned upgrades. A buyer researching a failed component may need help today. A facilities team evaluating an automation upgrade may still be gathering requirements next quarter. Applying one expiration period to both mixes very different buying windows. Separate the offers, track project status when known, and let confirmed customer information override a stale behavioral assumption.

Treat this as an operating example rather than a customer case study. The intended action is to move the account into the appropriate follow-up queue, with the buyer free to confirm or correct the premise. A representative should be able to explain why the resource or conversation is relevant without referring to an unsupported personal browsing history.

That keeps the next step grounded in the business problem.

Define the evidence before you score it

Measure time from the underlying event, not merely from delivery into the CRM. A signal delivered today may describe last month. Retain both timestamps and inspect the delay distribution. Repeated observations can renew relevance, but identical events from duplicated feeds should not repeatedly refresh the clock.

The decay explanation should tell a representative why an account moved down the queue without suggesting that the buyer has stopped needing the product.

Use recent research that remains relevant to the current buying window as the proposed evidence, then test whether it is available at the level the workflow requires. Establish explicit exclusions for expired projects, completed purchases, and unresolved customer support activity. Do not let a broad topic name stand in for a precise definition. Record the version of the rule and the date it becomes effective.

When the rule changes, retain enough history to distinguish a different observation process from a real shift in demand.

Build a record that supports the decision

A practical starting record includes

  • event time,
  • ingestion time,
  • offer,
  • last confirmation,
  • expiry rule.

These fields are a proposed minimum for this workflow, not a claim about a specific software integration. Keep source information and observed dates separate from later sales judgments. When a field is unknown, retain the unknown value and identify whether it blocks the next action. Avoid asking the sales team to maintain fields that have no clear use in routing, qualification, or evaluation.

The record should tell a coherent story for each account and offer pair: what was known, what was proposed, who acted, and what was learned. Use identifiers that remain stable when names or owners change. A spreadsheet export can be useful for review, but it should not become an untracked parallel source of truth.

Decide where corrections are made and how the corrected status reaches downstream queues.

Choose a useful response and a stopping point

The proposed action is to move the account into the appropriate follow-up queue. Define what must be true before that happens: relevant evidence, business fit, clear ownership, a supported contact route, and no unresolved restriction. The action should answer a practical buyer question.

A generic request for a long demonstration may be premature when the available evidence supports only a short resource or an initial qualification question.

Decide what the team should do when the premise is wrong. If the account confirms a different need, update the record and route it appropriately. If it asks for a later conversation, preserve the date. If it declines further contact, follow the applicable suppression process.

A thoughtful exit is part of a useful workflow, because continued activity without relevance consumes capacity and damages the next conversation.

Make customer feedback specific enough to learn from

Cortex’s customer-specific approach centers on learning from the business’s own feedback and outcomes. In this workflow, the useful feedback concerns a timely qualified conversation and the reasons a record does or does not progress. Keep those reasons tied to the actual offer. A broad research topic does not become proprietary simply because it appears in a CRM.

The distinctive learning comes from the customer’s operating context and documented outcomes.

Separate a fit problem from a contact problem and an operational constraint. If sales could not act, the record does not teach the same lesson as a buyer who confirmed the offer was unsuitable. Give the team a small number of usable reason codes with examples. Keep dated outcomes so that later success does not rewrite what was known earlier.

Review disagreements in labeling before increasing the influence of the feedback.

Design the comparison before reviewing the winners

Review historical qualified conversations by elapsed time since the relevant observation. Keep product and urgency segments separate. Use a provisional rule when history is limited, label it as a policy assumption, and test it prospectively. Preserve the original score and event history so later analysts can reconstruct what the team knew.

Compare the current queue with one that applies offer-specific expiration rules. Keep staffing and eligibility consistent. Evaluate accepted conversations, stale-project complaints, and the number of productive follow-ups lost through overly aggressive decay.

A comparison needs a consistent entry date, enough time to observe progress, and an explanation of who received attention. Preserve records that did not respond or did not qualify. Removing them after the fact makes the process look more selective than it was. Where a controlled experiment is impractical, use a transparent comparison and state the likely sources of bias.

A useful directional result should still be labeled with its limits.

Measure commercial usefulness and the work required

Report the number of eligible records, the number receiving the intended action, and the number reaching a timely qualified conversation. Use one account and offer pair consistently when calculating rates. Show the underlying counts with the percentages. Keep open outcomes separate from completed losses when the buying cycle is still developing.

A higher rate among a much smaller, heavily selected subset does not necessarily mean the overall policy creates more value.

Evaluate efficiency as well as volume. The time required to establish a timely qualified conversation is part of the economics. Include implementation, data preparation, and specialist review where they are material. Avoid calling pipeline value realized revenue. If commercial outcomes remain immature, report them as open and schedule follow-up. The business can make a bounded decision without pretending the final return is already known.

Watch for the errors that make the result look better than it is

Check for duplicated accounts, inconsistent timing, and selectively missing outcomes. A single opportunity linked to several contacts should not become several independent wins. A newer cohort should not be penalized for having less time to convert. Missing feedback should remain visible, especially when busy representatives report successes more reliably than unsuccessful attempts.

These checks are essential for interpreting a timely qualified conversation rather than rewarding the reporting process.

For intent data recency, revisit the exclusions explicitly: expired projects, completed purchases, and unresolved customer support activity. Check a sample of excluded and unresolved records as well as apparent successes. An exclusion that is too broad can hide useful demand. One that is too narrow can flood the queue with irrelevant activity.

Record the reason for the adjustment and verify it on subsequent records rather than judging it only on examples that motivated the change.

Put the workflow into operation in a manageable sequence

Start with a narrow scope that the team can explain. Confirm who owns the record, who performs the action, and who checks the result. Test how a correction reaches the queue before increasing volume. Let actual feedback about a timely qualified conversation guide the next version, while preserving the earlier rule.

A manageable implementation produces clearer evidence than a broad launch with inconsistent execution across teams.

Keep an operating note with the current definition, required fields, assigned owner, review date, and unresolved questions. That note can be short. Its value is continuity when a representative changes roles or a system is updated. A correction process should be as visible as the score itself.

The workflow needs to recover from normal errors without silently rebuilding the cohort or losing the history needed for evaluation.

A practical review exercise

Make a buying-window map for the offer. Ask sales how long research remains relevant for an urgent problem, a planned project, and a longer-term evaluation. Treat those answers as initial operating assumptions rather than measured decay curves. Review actual event dates and delivery dates to see whether source latency already consumes part of the useful window.

Then test a few account histories against the proposed expiration rule. Check a new observation, a duplicated observation, a confirmed delay, and a completed purchase. The output is an understandable recency policy showing when relevance decreases, what can renew it, and what verified information overrides it. Keep the original score history available for the authorized evaluation.

A representative should understand why an account moved down the queue and what evidence would justify another review. The policy should help the team spend effort at a useful time without suggesting that an expired observation means the buyer has no future need.

Review the result before changing the policy

Set aside a short review with the person who owns the action and the person who maintains the records. For intent data recency, ask them to explain one successful case, one unsuitable case, and one unresolved case using the same definitions. Compare their explanations with the stored fields.

If an important reason appears only in someone’s memory, decide whether it needs a structured place in the workflow. If a stored field is never used to explain a decision, question whether collecting it is worth the effort.

Distinguish three possible next steps.

  • Continue when the process works and the evidence needs time to mature.
  • Revise when a specific problem has a plausible correction that can be tested.
  • Pause when the available evidence cannot support the proposed action or the workflow lacks an accountable owner.

Record the decision, its reason, and the date of the next review. This keeps normal implementation learning separate from a claim of proven commercial improvement.

When the policy changes, identify which later records will evaluate the new version. Preserve earlier results under the rule that generated them. Do not combine the most favorable parts of several versions into a single apparent success. A useful learning process can acknowledge a correction and still show progress.

What matters is that the next decision rests on evidence the team can trace and a response the business can actually deliver.

Turn the learning into substantiated original research

An expiring signal is not permission to delete every related record. Retention and operational prioritization answer different questions. Keep only the history that the business is authorized to retain, with the detail needed to explain decisions and respect suppression rules.

This article proposes a practical method and uses illustrative reasoning. It does not report a measured Cortex conversion benchmark. To publish a numerical finding about intent data recency, retain anonymized eligible counts, event and outcome dates, definitions, comparison logic, and the material limitations. Publish the period and sample size beside the result. If the evidence shows an association, describe it as an association.

Reserve stronger causal language for an evaluation that supports it.

Questions to resolve before expanding

What should the team regard as success?

For this workflow, use a timely qualified conversation as the working outcome and define its acceptance criteria with the responsible team. Track volume, rate, cost, and incomplete follow-up separately. The definition should remain stable long enough to support a useful comparison.

What if the available evidence is incomplete?

Keep the uncertainty visible for each account and offer pair. Decide whether the missing information blocks action or can be resolved in a normal qualification conversation. Do not invent a source, an identity, or a buying deadline to complete the record.

What is the most important topic-specific question?

Should a score fall to zero after a fixed period? Sometimes a hard expiration is appropriate, but a gradual reduction or a request for reconfirmation may fit better. The right policy depends on the buying window and evidence quality.

Map the method to your own offer

To evaluate intent data recency for your business, bring one real decision, a sanitized example record, and your current definition of a timely qualified conversation. Discuss which topics, sources, exclusions, and feedback are available for your scope. Contact Cortex Marketing AI to review a customer-specific two-way intent workflow.

Begin with an approach your team can explain, then measure whether it improves the decisions you actually need to make.

Back to Blog