0 / 24 done on this device
Stage 3 · Lesson 2 of 4 · GUIDE · 6 min

Custom fields that earn their place

And ones to avoid

By the wpdailylive editorial team · Part of CRM for small business, the complete guide

Key takeaways

  1. The test: Add a field only if you will filter, report or automate on it.
  2. Useful fields: Lead source, industry, deal value, close date and lost reason.
  3. Dropdowns beat free text: Fixed options keep reports clean.
  4. Few required fields: Keep fewer than ten required fields on a deal.
  5. Quarterly review: Hide fields nobody has filled in for 90 days.

Every extra field slows data entry. Only add a field if you will filter, report or automate on it.

Worth addingLead source, industry, deal value, close date, lost reason, renewal date.
Usually skipFree-text "notes 2", fax number, fields nobody reports on.
DATA STAYS CLEAN WHEN IT’S SHORT
< 10required fields on a deal
Dropdownsbeat free text for anything you report on
Source: Common CRM adoption guidance

Fields worth adding, by business

BUSINESSUSEFUL CUSTOM FIELDS
AgencyProject type, budget range, decision date
SaaSPlan interest, seats, current tool
TradesProperty type, job type, postcode
AnyLead source, lost reason, industry

Field type guide

DATAFIELD TYPE
Fixed options (source, industry)Dropdown
Several options (interests)Multi-select
MoneyCurrency
Dates (renewal, contract end)Date
NotesFree text, rarely

Custom field examples by business

BUSINESSUSEFUL CUSTOM FIELDS
AgencyService type, budget range, launch date, decision-maker
TradesJob type, property type, site visit date, postcode
SaaSPlan interest, seats, current tool, renewal date
B2B servicesIndustry, company size, contract value, renewal month

Rules for adding a field

  1. 1.Name the report or decision it feeds
  2. 2.Prefer a dropdown to free text so data stays consistent
  3. 3.Decide who fills it in and when
  4. 4.Make it required only at the stage it matters
  5. 5.Remove it if nobody uses it within a quarter

Required fields at each stage

STAGEREQUIRED FIELD
QualifiedLead source, budget range
ProposalDeal value, expected close date
LostLost reason

Common mistakes to avoid

✕ Dozens of optional fieldsKeep only what you report on.
✕ Free-text fields for categoriesUse dropdowns.
✕ Everything required up frontRequire fields by stage.
PEOPLE ALSO ASK
What are CRM custom fields?

Extra fields you add to contacts, companies or deals to capture information specific to your business, such as service type or budget range.

How many custom fields should a CRM have?

As few as possible: usually five to ten that feed reports or decisions.

Should CRM fields be required?

Only at the stage they matter, for example deal value at proposal and lost reason when a deal is lost.

What field types should I use?

Dropdowns for categories, numbers for values, dates for deadlines and checkboxes for yes/no; avoid free text for anything you report on.

What are examples of useful CRM fields?

Lead source, budget range, decision-maker, expected close date, service type and lost reason.

Reviews of tools in this lesson