Your Lead Database Needs Seven Fields — Twenty Will Hollow It Out

Post 22 Sep 2026 CRMLead ManagementData QualitySales OperationsProcess Design

Seven fields are enough to make the only two decisions a new lead requires — qualify or not, and who owns it: company name, contact and their role, one confirmed channel of communication, source, stated need, region, and owner. Any eighth field has to pass a single test: does an actual decision change depending on its value? If the answer is no, it's curiosity satisfied at the expense of data accuracy.

Why more fields empty the system out

Long forms don't get filled with lies — they get filled with blanks first, then with noise. A rep facing twenty boxes before they can save a lead will pick the first option in every dropdown just to clear the screen. Three months later, reports are built on those arbitrary values, and someone discovers that "lead source" says 70% of customers came from "Other." At that point the team loses faith not in one field, but in the entire report. That's the second price you pay.

The test for a useful field: decision or curiosity?

Ask three questions about every field before you keep it:

  1. Which decision depends on it? Routing, priority, pricing, or disqualification. If it's none of those, delete it.
  2. Does the rep know it at creation time? "Estimated budget" isn't known on the first call; it belongs to a later stage, not the intake form.
  3. Can it be derived? If the system can calculate it from other fields, don't ask a human for it.

The seven fields: what they are, who fills them, and when

FieldFilled byWhy it's essential
Company nameCreatorThe key to duplicate prevention
Contact and roleCreatorSeparates the speaker from the decision-maker
One confirmed contact channelCreatorPrerequisite for any follow-up
SourceAutomatic or creatorMeasures which acquisition channels pay off
Stated need (one line)CreatorThe basis of the qualification call
RegionCreatorThe basis of territory routing
OwnerAutomatic via routing rulePrevents orphaned leads

The first six take under a minute. The seventh shouldn't be filled manually at all. In Effistar, the owner is assigned by a routing rule based on region or source the moment the lead is created, which removes an entire field from the rep's workload.

Who are you looking for?
Sector: government City: Riyadh Size: 200+ Signal: digital-transformation unit
Results ranked by priority
9.1Government authority, transportRiyadh · 840 staff · existing digital-transformation unit
8.4Major municipal bodyCentral region · 1,200 staff · smart-cities programme
7.6Tourism development authorityRiyadh · 460 staff
5.2Small services firmRiyadh · 18 staff, out of segment
Buying committee, top account
ADecision-makerHead of digital transformation
STechnical influencerIT director
FProcurement leadProcurement · process gatekeeper
## Where everything else goes: derived, stage-gated, or free-text

What you cut isn't lost — it moves to one of three places:

  • Derived: lead age, last activity date, number of attempts. The system calculates these; never ask anyone to type them.
  • Stage-gated: budget, timeline, incumbent vendor. These appear when a lead converts to an opportunity, not before.
  • Free-text notes: every contextual detail that no report is built on. One honest line of notes beats a dropdown someone was forced to guess at.

Local compliance fields: commercial registration, VAT number, region

All three are real and necessary — just not on the lead form. Commercial registration and VAT numbers are needed when you issue a quote or an invoice, and at that point you request them from an official contact at the company, not from a rep making an educated guess. Region stays in the seven because it determines the owner. The rule: ask for a regulatory field at the first document that requires it, not at the first phone call.

How to clean up a twenty-field form without upsetting anyone

Don't cut everything at once. Pull a field-completion report for the last six months. Any field filled less than 30% of the time, or holding the same value in 90% of records, goes on a review list. Take that list to the team with one question: "Who uses this field to make a decision?" Anything without a defender gets hidden from the form for a month — not deleted. If nobody asks for it within that month, archive the data and remove the field.

Three signs the form is getting heavy again

  1. One value swallows the list: "Other" or the first option accounts for more than half of all records.
  2. Duplicate leads with near-identical names: proof that reps are creating new records to avoid searching and editing existing ones.
  3. A gap between created and worked: leads get logged with no activity recorded against them within a week — the form consumed the energy that was meant for the call.

Start tomorrow with one step: open your lead form and write, next to each field, the decision that depends on it. Anything you can't write a decision for goes on the review list.

Want to see this inside your organization? Request an invite