A Prospect List Is Not a Spreadsheet Full of People

Open a typical prospect list and it looks impressive. There are 10,000 rows. Every row has a company name, employee count, industry, first name, last name, job title, email address, phone number, and LinkedIn URL. The emails are verified. The data is neatly formatted. The cells are complete.

And almost none of it explains why anyone on the list belongs there.

This is the beautiful dead spreadsheet: accurate enough to send to, empty of reasons to contact.

Verified does not mean valid

A verified email means the address is likely to receive mail. It does not mean the person is relevant. A correct job title does not mean the person owns the problem. An accurate employee count does not mean the company is in a buying situation. A fresh phone number does not mean a call makes sense.

Data quality and targeting quality are different things. A list can be technically clean and commercially poor. This distinction matters because prospecting tools often highlight what they can measure: coverage, verification, freshness, and match rates. Those are useful. But they answer, “Can we reach this person?” They do not answer, “Why are we reaching this person?”

Think of the list as evidence

Imagine a court case where the lawyer says:

We have 10,000 names and addresses.

The judge would ask what those names prove. A prospect list works the same way. Each row is making a small claim:

This company is likely to have a relevant problem, this person is plausibly connected to it, and now is a reasonable time to ask about it.

The fields in the row are evidence for that claim. Industry and company size may support structural fit. A hiring announcement may support timing. A job description may reveal an operating problem. A public comment may reveal pain. A role change may identify a likely owner. Without evidence, the row is only contact data.

Build the list backwards from the problem

Suppose the problem is:

Sales teams hiring quickly often struggle to keep account research and prioritisation consistent.

A list built backwards from that problem might look for companies with recent sales hiring, a meaningful increase in team size, expansion into new territories, signs that reps are expected to self-source pipeline, sales operations or enablement roles, public discussion of inconsistent process or ramp time, and a current tool stack that suggests manual work.

Now each filter has a reason. This is different from starting with “VP Sales at software companies with 50 to 500 employees.” The second list is larger. The first list contains more of the argument.

Five layers of list quality

1. Account fit

Does the company structurally fit the product? Industry, size, business model, geography, and technical environment live here.

2. Problem fit

Is there evidence that the relevant problem exists or is becoming more likely? This layer turns a market into a target.

3. Person fit

Is the contact close enough to the problem and senior enough to do something with the conversation?

4. Timing fit

Why might the topic matter now? A recent change often matters more than a static characteristic.

5. Data reliability

Can the person actually be reached, and is the information current?

Most list-building workflows begin and end with layers one and five. The middle three are where relevance lives.

How false precision enters a list

A spreadsheet creates a feeling of certainty. A row says:

John Smith | VP Sales | 238 employees | SaaS | Verified email

Everything looks exact. But the exact fields can hide uncertain assumptions: does John still work there, does he own the relevant process, is the sales team actually growing, is the problem present, is the account already locked into another solution, is the company cutting costs, did a recent reorganisation move ownership elsewhere?

The row is precise about identity and vague about relevance. That is false precision.

The anti-list matters

A strong list-building process creates not only a target list, but also an anti-list. The anti-list contains companies that look attractive but are poor targets. For example: companies with the right size but no active outbound motion, teams that recently cut the relevant function, accounts with a long contract remaining on a competing tool, companies where the problem occurs too rarely, businesses using an operating model the product does not support, contacts who have the title but not the ownership, and accounts already approached recently by another team.

The anti-list prevents the same bad accounts from repeatedly entering new campaigns. It also forces the team to explain what “not a fit” means.

What a useful row looks like

A useful row is not simply a row with more columns. It contains a compact reason for contact. For example:

Company: Northstar Labs
Change: Added 14 account executives across the US and UK in 90 days
Likely issue: Account research and prioritisation may be inconsistent across the new team
Contact: Head of Revenue Operations
Why this person: Owns sales process and tooling
Evidence: Hiring posts mention self-sourced pipeline and manual territory research
Question: Has account selection become centralised, or are new reps still choosing targets independently?

That row can produce a message. A row containing only a name and email cannot.

Smaller lists can create more learning

A 10,000-contact campaign often produces enough noise to hide the reason for success or failure. A reply may come from one industry, one role, one company stage, or one signal. But the campaign mixed everything together.

A smaller list built around one clear hypothesis creates cleaner learning. For example:

100 companies that added at least five sales reps in the last quarter, where self-sourced pipeline appears in current job descriptions.

If the response is weak, the hypothesis can be examined. Maybe the role is wrong. Maybe the hiring threshold is too low. Maybe the problem appears later. Maybe the signal is weak. Maybe the question is poor. The list becomes an experiment rather than a warehouse.

The row-level challenge

Pick any row from a prospect list and cover the email address. Now ask: why this company, what evidence suggests a problem, why this person, why now, and what question would test the idea?

If the row cannot answer those questions, the verified email is doing too much work. A prospect list is not a spreadsheet full of people. It is a collection of reasoned bets about who may benefit from a conversation.