Aged leads vs real-time leads: what the price difference actually buys
The difference between aged and real-time leads, what each costs, how fast contact data decays, and when a cheap aged file is genuinely the better buy.
8 min read · Published September 19, 2026
The short answer
The short version.
- Aged leads are records exported weeks or years ago and resold. Real-time leads are built and checked at the moment you receive them.
- B2B contact data decays roughly 2 to 3 percent a month, so a 12 month old file is typically a quarter wrong before you dial it.
- Aged data is cheaper per record and far more expensive per conversation, because your dials-per-connect number rises with the age of the file.
- Aged files can still be worth buying for market sizing or a re-engagement campaign, never for a rep's daily calling list.
The gap between a 2 cent record and a 15 cent record is almost entirely age. Understanding what age does to a contact file is the single most useful thing a buyer can learn in this market.
What aged and real-time actually mean
Aged leads were collected at some earlier point and stored until sold. Real-time leads are sourced, screened and checked at the point of delivery.
Nobody advertises a file as aged. The tells are in the language: a fixed record count, instant download, a per-record price under 5 cents, and no answer to the question of when the phone number was last confirmed. Real-time delivery cannot quote you a file size up front, because the file does not exist yet.
- Ask one question: on what date was this phone number last confirmed?
- A vendor who answers with a range rather than a date is selling you a warehouse.
How fast B2B contact data goes wrong
Around 2 to 3 percent of B2B contact records break every month through job changes, number changes and company closures.
Job changes are the main driver, and they break the email and the direct dial at the same time. Mobile numbers survive a job change but the company and title on the record are then wrong, so the contact no longer matches your profile even though the phone still rings.
| Age of file | Still correct | Practical use |
|---|---|---|
| Under 30 days | 95 to 98 percent | Daily calling list |
| 3 months | 90 to 94 percent | Usable with light cleaning |
| 6 months | 83 to 89 percent | Re-verify before dialing |
| 12 months | 70 to 80 percent | Market sizing, re-engagement |
| 24 months | 50 to 65 percent | Little calling value |
The real cost comparison
A 2 cent aged record with a 4 percent connect rate costs more per conversation than a 12 cent fresh record with a 12 percent connect rate.
Run it per conversation rather than per record. Two cents divided by a 4 percent connect rate is 50 cents per conversation. Twelve cents divided by a 12 percent connect rate is $1 per conversation, which looks worse until you add the rep's time. At $25 an hour and 20 dials an hour, every dial costs $1.25 in labour. The aged file needs 25 dials per conversation and the fresh one needs about 8. Labour swamps the data price completely, and the cheap file loses by a wide margin.
- Data price is usually under 5 percent of the cost of a conversation.
- Connect rate, not record price, decides what a list costs you.
- Any list where the majority of numbers are switchboards is an aged list in practice, whatever its date.
When aged leads are genuinely the right buy
For market sizing, territory planning, account list building or a low-cost email re-engagement pass, aged data is fine and cheaper.
If you need to know how many plumbing contractors exist in three states, nobody needs the phone number to be live. Same for building a target account list you will enrich later. Problems only appear when an aged file is handed to a rep as a calling list and the rep's day disappears into disconnected numbers.
How to test a vendor's freshness claim
Take a sample of 20 records, dial them yourself in one sitting, and record how many reach the named person.
Twenty calls takes under an hour and tells you more than any specification sheet. Eight or more live conversations with the named person means a genuinely fresh, mobile-weighted file. Two or three means you are holding a warehouse export, regardless of what the invoice says.
Key takeaways
- Age is the main driver of price, and connect rate is the main driver of cost.
- Aged files are for planning and re-engagement, never for a rep's daily list.
- Test freshness by dialing 20 records yourself before you commit to volume.
See the data behind the advice
Five ICP matched prospects with mobile numbers, direct dials and work emails, free. Same pipeline that fills a paid account, no credit card.
Frequently asked questions
What are aged leads?
Contact records that were collected earlier and stored before being sold, often resold many times. They cost the least per record and carry the highest failure rate on the phone.
Are real-time leads worth the extra cost?
Yes when a human will call them, because rep time costs many times more than the record. No when you only need counts or account names for planning.
How old is too old for a B2B contact list?
Past six months you should re-verify before dialing. Past twelve months, expect a quarter of the file to be wrong.
How fresh are LeadNumbers records?
Each batch is sourced and checked at build time and delivered the same business day, so the record is days old, not years. Wrong numbers are replaced free within fair-use limits.
Keep reading
Economics
How much do leads cost? Real 2026 prices by type of lead
What B2B leads cost in 2026 by type: contact data, marketing qualified leads, appointment setting and paid ads, with the maths for working out what a lead is worth to you.
Operations
How to get sales leads: the five routes, and what each one really costs
The five ways B2B teams get sales leads, what each costs per lead and per meeting, and how to pick one based on whether you already have reps.
Benchmarks
Cold call connect rates by industry, and what a good one looks like
Connect rates for B2B cold calling by industry and role, why mobile numbers move the number more than any script change, and how to tell a data problem from a message problem.