What we decline to collect

A natural instinct in any data business is to collect as much as you reasonably can, because more fields make a record look richer, and a richer-looking record is easier to sell. ExecLeads resists that instinct more often than it indulges it, and I think the resistance is one of the least visible and most important decisions we make as a company, precisely because nobody outside the company notices it happening.

Every field we hold about a person is a field we are responsible for — responsible for keeping accurate, responsible for securing, responsible for using fairly, and responsible for eventually explaining if anyone ever asks why we have it. A field with no clear purpose is not an asset sitting quietly in reserve for a future use case. It is a liability sitting quietly, accumulating risk, waiting for the day something goes wrong with it or someone reasonably asks why it was collected in the first place and we do not have a good answer.

The question we ask before adding a field

Before we add a new category of information to what we hold, the question is not whether it is available or whether clients might find it interesting. The question is whether we can articulate, specifically, a legitimate business use for it that justifies the responsibility of holding it. If the honest answer is that the field would simply make the dataset look more thorough, that is not a sufficient reason, because thoroughness for its own sake is a marketing benefit wearing the costume of a product improvement.

Every field we hold is a field we are responsible for. Collecting without a purpose is not richness. It is exposure.

Why the clients who matter understand this

We have lost prospective clients over this. Some buyers come to us wanting a dataset with every imaginable field populated, comparing our offering unfavorably to a competitor who collected more broadly and asks fewer questions about why. We have learned to explain our restraint directly rather than apologize for it, and the clients who understand the explanation tend to be the ones building something durable themselves, because they recognize that a vendor who thinks carefully about what they collect is a vendor who will still be trustworthy when it matters most.

The clients who leave over this are, in most cases, not a loss I lose sleep over. A buyer who wants maximum data regardless of purpose is usually optimizing for something other than long-term reliability, and that is simply a different business than the one Dale and his team have built. Restraint does not show up on a feature comparison chart. It shows up a few years later, when a dataset that collected broadly and carelessly becomes the subject of a headline nobody wanted to be in, and a dataset that held less, on purpose, is not.