Why are my reps wasting time on stale target lists?
Because the list was true on the day it was built and nothing about it has been true since. A target list captures two kinds of fact. Slow facts, like industry, headcount band, and business model, stay roughly correct for a year. Fast facts, like who runs the function you sell to, what the company just funded, and whether a decision is currently being made, are wrong within weeks. Reps work the list as though every column were a slow fact, so they spend their week on companies that fit and on people who have moved.
The second reason is ordering. Even a perfectly accurate list gives no instruction about what to do first, so the default orderings take over: alphabetical, import date, or logo familiarity. Every one of those spreads rep attention evenly across wildly unequal opportunities. The list is not the problem. The absence of a re-sort is.
Two decays, running at different speeds
It helps to separate the two things people mean by a stale list. Contact decay is the obvious one: people change jobs, titles change, mailboxes get deactivated. It degrades your ability to reach anybody. Timing decay is the expensive one: the account's reason to buy either has not happened yet or happened and passed. It degrades the value of reaching them at all.
Teams buy tools for the first and ignore the second, which is backwards. A verified email address for a person with no reason to talk to you is a more efficient way to be ignored. The fix for contact decay is refresh. The fix for timing decay is a re-sort on fresh events, which is a different operation entirely and cannot be bought as a data cleanse.
The arithmetic, worked
Do not take numbers from a vendor slide. Run this on your own list, because the inputs are things you can actually measure and the conclusion is usually more dramatic than any statistic you would have quoted. The example below uses a 500-account list and three assumptions, each of which you should replace with your own observed rate. The assumptions are labeled as assumptions on purpose: nothing here is a measured industry constant.
| Row | Input | Symbol | Illustrative value | How you measure your own |
|---|---|---|---|---|
| 01 | Accounts on the list | N | 500 | Count the rows a rep is actually expected to work. |
| 02 | Share with a dated event in the last 90 days | p | 12% | Sample 50 accounts by hand, spend five minutes each, count the ones with a dated event you can source. |
| 03 | Share of named contacts still in role | c | 80% | Take 50 contacts, check each against the company site or a professional profile, count the survivors. |
| 04 | Accounts worth a first touch this quarter | N x p | 60 | The only rows on the list that have a reason attached. |
| 05 | Reachable and worth touching | N x p x c | 48 | The real working universe. Everything else is a watch list. |
| 06 | Rows a rep will actually touch this quarter | capacity | about 200 | Your own touched-account count from the CRM, per rep, per quarter. |
| 07 | Touches landing on a reason-free account | capacity minus (N x p x c) | about 152 | The gap. This is the number to put on a slide, and it is arithmetic on your own inputs, not an estimate from anyone else. |
The shape of the result is what matters, not the specific figures. With any plausible values of p and c, rep capacity is much larger than the population of accounts that currently have a reason to talk. The team is not lazy and the list is not fake. There is simply more capacity than there are live windows, so the surplus effort lands on accounts with nothing happening, and those touches produce the polite deferrals that everyone then blames on messaging.
The four columns that fix it
You do not need a new list. You need four columns added to the one you have, and a weekly job that recomputes them. Any spreadsheet can hold this, which is the point: build it by hand first so you understand what you are later asking software to do.
- Last event date: the date of the most recent dated public event at this account, blank if none. This is the column the whole sheet sorts on.
- Event source URL: the link where you read it. A blank here means the row is a rumor and should be treated as blank.
- Consequence sentence: one plain sentence naming what the event makes harder in the next thirty to ninety days. If it cannot be written, the event does not count for you.
- Owning role: the job title that absorbs the consequence. Role, not person. The person is a lookup you do after the row survives.
Then add the discipline that makes the columns real: a weekly re-sort. Every Monday the sheet is re-ranked with another week of decay applied to every event. Skip the re-sort for three weeks and you are back to working a photograph, no matter how good the columns are. The re-sort, not the enrichment, is what stops a list going stale.
What this changes for the rep
The visible change is that the top of the list stops being the same twenty companies every week. Accounts arrive at the top because something happened to them, work through, and drop back to the watch list. Reps stop asking which accounts are mine and start asking which of my accounts moved, which is a question with an answer.
The less visible change is in what a first touch sounds like. When the row carries an event, a date, a consequence and a role, the opening line writes itself out of the evidence, and the rep is not inventing a reason to be in the inbox. When the row is blank, the rep has to manufacture relevance, and that is the exact material that makes buyers stop reading.
This is what the category calls data decay and account prioritization.
Vendors call the first half of this problem data decay or database hygiene, and they sell refresh and verification against it. That is a real product category and it fixes contact decay: bad emails, moved people, dead phone numbers.
The second half has a different name. Ranking a list by fit and timing rather than by import order is account prioritization, and when the ranking input is dated public events it is usually filed under buying signals or trigger events. Knowing both names is useful, because a data-hygiene purchase will not solve a prioritization problem and teams buy the wrong one all the time.
Questions people ask next
Should I just buy a bigger list?
A bigger list raises the count of accounts with no reason attached faster than it raises the count with one. If p is small, doubling N doubles the surplus capacity problem. Fix the sort before you buy volume.
How often does the re-sort need to run?
Weekly is the minimum useful cadence, because event freshness is the dominant term and a week of decay changes the order. Daily is better if the events arrive daily. Monthly is not a re-sort, it is a quarterly review with extra steps.
My CRM already has a lead score. Is that the same thing?
Usually not. Most lead scores are fit models plus engagement with your own marketing. Neither term moves when something changes inside the prospect's business, so the ranking is stable in exactly the situation where it should be volatile.
Where to check this yourself
Primary records and published research, not vendor blog posts. Every link was checked on September 1, 2026.
- Census Business Dynamics Statisticscensus.gov
Official U.S. data on firm openings, closings, and expansions, the underlying churn that makes any company list decay.
- Census Business Formation Statisticscensus.gov
Weekly and monthly business application data, useful for sizing how fast the top of a market changes.
- SEC EDGAR full-text searchsec.gov
Free way to re-date an account: search the company name and read what has actually been filed this year.
- The Bridge Group, SDR Models and Metrics researchblog.bridgegroupinc.com
Biennial survey research on sales development structure, ramp, and metrics. Use it to sanity check your capacity assumptions.
Intakra keeps those four columns current for you: it watches public sources for dated events on your accounts, keeps only the ones where it can name the consequence and the role, and re-ranks the list as evidence ages.
Free scan, no signup, no card