Lead Aging
Lead aging is the measure of how much time has passed since a lead was captured and last engaged. It tracks the elapsed lifespan of a lead in your pipeline.
Key takeaways
- Age is the interval since creation or the last meaningful touch, nothing more.
- Rising average age usually signals capacity or routing failure, not lead quality.
- Buckets make the distribution readable; averages hide a growing oldest group.
- Age combined with score tier turns a flat queue into a priority order.
- Automated emails can reset the clock without any human contact occurring.
In depth
Lead aging is a clock, not a judgement. A timestamp is written when the record is created, a second timestamp updates on each meaningful interaction, and the age is the difference between the later of those and now. Records are then sorted into buckets, commonly same-day, two to seven days, and older, so the distribution can be read at a glance. Age says nothing about quality on its own; it says how long the record has been waiting for someone to act.
Average age rises when inflow exceeds the team's capacity to work it, when routing rules leave records unassigned, and when reps cherry-pick the easiest names and leave the rest. It falls with capacity, tighter routing and automated first touch. The trade-off is that age can be reduced by contacting everyone quickly and badly, which looks good on the report and burns the list. Age is therefore only useful next to a quality measure, never as a target on its own.
Operationally, age works best as a trigger rather than a column. Rules watch the clock and escalate: unassigned after thirty minutes, unworked after two hours, no reply after three attempts. Combining age with the score tier from a quiz makes the queue meaningful, since a fresh high-tier respondent and a week-old low-tier one are not the same job. Aging buckets also expose capacity problems early, because the oldest bucket grows before anyone notices the team is behind.
The clock misleads whenever the buying timeline is set by something outside the funnel. A contact who downloaded a guide while their contract has eleven months to run is not stale at six months old; the age simply does not describe their readiness. Long-cycle enterprise pipelines break aging rules routinely. Age is also distorted by data hygiene: a record touched by an automated email shows as fresh without a human ever having engaged, which hides exactly the problem the metric was built to expose.
Example in practice
How to measure it
Two numbers do most of the work: median time to first human touch, and the share of leads still untouched beyond the agreed threshold. The median resists the distortion a few forgotten records cause. Track both by score tier, since a slow first touch on the top tier costs far more than the same delay lower down. Watch the trend weekly rather than the absolute value.
To prove the thresholds are set correctly, plot reply or meeting rate against age bucket for a few months of history. The curve shows where response actually falls off for this audience, which is the only defensible basis for an escalation rule. If the curve is flat across buckets, speed is not the constraint and the effort belongs somewhere else in the funnel.
Common mistakes
A frequent error is letting automated touches reset the aging clock. A nurture email counts as activity in most systems, so a record that no human has ever spoken to reads as freshly engaged, and the queue looks healthy while nothing is being worked. Define the clock against human or inbound activity only, and keep automated sends on a separate field so both can be seen.
The other is reporting a single average age across the whole database. One average blends a fast-moving inbound queue with a dormant list of old form fills, and both look mediocre. Report by source and score tier instead, and use a percentile rather than a mean, because a handful of very old records drags the average and hides whether the recent intake is being handled.
Frequently asked questions
What is considered a 'fresh' lead?
A fresh lead is one captured within the last 24 to 48 hours that has not yet gone stale. In quiz funnels, the freshest leads are those who just submitted their score, since their buying intent is at its peak.
How does lead aging differ from lead decay?
Lead aging simply measures elapsed time since capture, while lead decay measures the resulting drop in conversion probability. Aging is the cause and decay is the effect you want to prevent.
How can I reduce lead aging?
Automate routing so new quiz respondents are assigned and contacted within minutes, and set alerts for any high-tier lead left untouched past a threshold. Faster first-touch is the single biggest lever for keeping aging low.
What counts as the start of a lead's age?
Most teams start the clock at record creation, meaning the moment a form is submitted or a contact is imported. The more useful variant restarts it on each meaningful engagement, so age reflects time since the prospect last showed interest rather than time since they first appeared. Whichever is chosen, apply it consistently or comparisons across sources become meaningless.
What aging buckets should we use?
Buckets should match the shape of the response curve, not a calendar. For inbound quiz or demo traffic, hours matter, so brackets of under one hour, one to four hours, same day and older are common. For long enterprise cycles, weekly or monthly brackets are more useful. Pick the boundaries where reply rate visibly changes.
Is lead aging the same as lead decay?
No. Aging is the measurement of elapsed time; decay is the decline in a lead's likely value as that time passes. Aging can be read from a timestamp, while decay has to be estimated from historical conversion by age. A lead can be old without having decayed much, for example when the buyer is on a fixed renewal date.
At what age should a lead be removed from the active queue?
Set the boundary where the reply rate for that source drops to roughly the rate of a cold list, because at that point the record carries no advantage over new prospecting. Move it to a lower-touch nurture rather than deleting it. Records that keep opening emails should stay out of that rule regardless of age.
Does contacting a lead faster actually improve conversion?
For high-intent inbound it usually does, because the prospect is comparing options in the same session and the first useful reply frames the comparison. The effect is much weaker for research-stage contacts, where speed can feel intrusive. Test it by holding response time constant for one segment and varying it for another rather than assuming the rule applies everywhere.
Who should own the aging metric, marketing or sales?
Sales owns time to first touch, because that is a capacity and routing question. Marketing owns the inflow rate that determines whether the team can keep up. Problems arise when neither reviews the oldest bucket, so it grows unowned. A short weekly review of untouched records past the threshold, attended by both, fixes most of it.