The custom fields trap
Custom fields in CRM software are the difference between a generic database and a tool that fits your business. A tutoring center needs "grade level" and "subject." A real estate agent needs "price range" and "neighborhoods." A salon needs "color formula" and "preferred stylist."
Without these fields, you cram industry-specific information into the notes field, where it becomes unsearchable and unusable. With these fields, every lead is structured data you can filter, segment, and act on.
The catch: custom fields scale badly. A CRM with 8 well-chosen custom fields runs smoothly. A CRM with 47 custom fields — added one at a time over two years — becomes unusable. Most small business CRMs are quietly in the second category.
The four categories of custom fields and how many you need
| Category | Examples | Recommended Count |
|---|---|---|
| Identity | Industry, company size | 1-2 |
| Intent | Budget, timeline, decision authority | 2-3 |
| Engagement | Source, lead magnet, last activity | 2-3 |
| Industry-specific | Whatever is unique to your business | 2-4 |
Total: 7-12 custom fields covers almost every small business case. More than 12 and you have crossed into field sprawl.
The questions every custom field should pass
Before adding a custom field, ask three questions:
- Will I filter or segment by this field? If you cannot imagine running a search like "show all leads where this field equals X," the field has no operational purpose.
- Will I update this field after the lead is created? Static fields (industry, source) are fine. Dynamic fields (engagement score, last activity) need to be auto-updated or they decay.
- Will my future self thank me for this field? Fields that match a fad ("ChatGPT interest level") become noise in 18 months.
A field that fails any of these three questions should not exist.
The "notes vs custom field" decision
A common dilemma: should this information be a custom field or just a note?
- Custom field: structured, filterable, analytics-friendly, future-proof
- Note: flexible, narrative, fast to write, hard to search
The rule: if you would ever want to count how many leads have this attribute, it should be a custom field. If it is purely contextual ("they mentioned they have a dog"), it belongs in notes.
A tutoring center should have "grade level" as a custom field (you will count students per grade for capacity planning). A note like "student seems shy" should stay a note (no operational use case).
The maintenance discipline
Custom fields decay if not actively maintained. Three habits keep them healthy:
- Quarterly audit. Review every custom field. Delete the ones nobody updates. Most CRMs let you see "% of leads with this field populated." Anything under 20% is dead weight.
- One owner per field. A field with no clear owner gets updated by nobody. Assign each custom field to a specific role.
- Mandatory at intake, optional later. Force the field at lead creation (when context is fresh), allow editing later.
The honest custom field test: scroll through your CRM's custom fields list. How many can you describe the purpose of without looking at the data? Anything you cannot explain should probably be deleted.
How field sprawl happens (and how to prevent it)
Field sprawl follows a predictable pattern:
- Month 1: 3 fields, all used
- Month 6: 8 fields, mostly used
- Year 1: 15 fields, half used
- Year 2: 25 fields, a third used
- Year 3: 40 fields, most ignored
The cause is benign — every "let's track this!" idea adds a field, and fields rarely get removed. The cure is process: every new field requires deleting an unused one. This forced trade-off keeps the count sane.
The all-in-one platform advantage
Some all-in-one platforms (website builder + CRM + lead capture in one product) ship with smart defaults — the right custom fields are already there for common business types. You start from a curated 5-7 fields rather than building from scratch.
This pre-curation matters more than it sounds. Most small business owners do not know which custom fields to start with, so they either start with none (and lose data forever) or start with too many (and field sprawl begins immediately).
The bottom line
Custom fields in CRM are the most powerful underused feature for small businesses. Start with 7-12 well-chosen fields. Pass every new field through three questions before adding it. Audit quarterly and delete the dead ones. The CRM that respects field discipline stays useful at year five — the CRM that does not becomes a museum of abandoned tracking ideas.
