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
- The test: Add a field only if you will filter, report or automate on it.
- Useful fields: Lead source, industry, deal value, close date and lost reason.
- Dropdowns beat free text: Fixed options keep reports clean.
- Few required fields: Keep fewer than ten required fields on a deal.
- 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.
< 10required fields on a deal
Dropdownsbeat free text for anything you report on
Fields worth adding, by business
| BUSINESS | USEFUL CUSTOM FIELDS |
|---|---|
| Agency | Project type, budget range, decision date |
| SaaS | Plan interest, seats, current tool |
| Trades | Property type, job type, postcode |
| Any | Lead source, lost reason, industry |
Field type guide
| DATA | FIELD TYPE |
|---|---|
| Fixed options (source, industry) | Dropdown |
| Several options (interests) | Multi-select |
| Money | Currency |
| Dates (renewal, contract end) | Date |
| Notes | Free text, rarely |
Custom field examples by business
| BUSINESS | USEFUL CUSTOM FIELDS |
|---|---|
| Agency | Service type, budget range, launch date, decision-maker |
| Trades | Job type, property type, site visit date, postcode |
| SaaS | Plan interest, seats, current tool, renewal date |
| B2B services | Industry, company size, contract value, renewal month |
Rules for adding a field
- 1.Name the report or decision it feeds
- 2.Prefer a dropdown to free text so data stays consistent
- 3.Decide who fills it in and when
- 4.Make it required only at the stage it matters
- 5.Remove it if nobody uses it within a quarter
Required fields at each stage
| STAGE | REQUIRED FIELD |
|---|---|
| Qualified | Lead source, budget range |
| Proposal | Deal value, expected close date |
| Lost | Lost 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.















