CRM features

Custom fields in CRM: capture what matters without clutter

How custom fields should work in a modern CRM, which field types matter, and how SchemaDesk uses fields on objects you define.

Updated September 22, 2026

We built SchemaDesk. These guides are our honest take on the CRM category, including where we are not the right fit.

What custom fields are

Custom fields store attributes on a record: close date, property type, candidate notice period, retainer hours, ARR, referral source, and similar facts.

Good fields are typed and intentional. Bad fields are an endless pile of optional text boxes nobody trusts.

Why field design matters

Reports, filters, and automation can only use clean values. If everything is a paragraph note, you cannot answer simple operational questions.

Field design is also change management. Every required field is a tax on the person updating the record. Charge that tax only when the data earns its keep.

How SchemaDesk thinks about fields

SchemaDesk attaches fields to the objects in your workspace schema. Because objects are flexible, fields live on the right record instead of overloading a generic contact form.

Prefer typed fields for status, dates, numbers, selects, and relations. Keep long narrative in notes when structure would create false precision.

Field types buyers should expect

At minimum, look for text, number, currency, date, select, multi-select, checkbox, URL, email, phone, and relation fields. File and formula support matter later for many teams.

Select fields for stages and categories you report on
Dates for renewals, viewings, start dates, and follow-ups
Currency and number for commercial metrics
Relations instead of typing linked names as free text

Governance without bureaucracy

Name fields clearly. Document who owns the definition. Archive unused fields instead of leaving ghosts on every form. Revisit required flags quarterly.

FAQ

How many custom fields is too many?

If users skip the form or invent parallel trackers, you have too many. Start with fields needed for this week's decisions, then expand with evidence.

Should every note become a field?

No. Fields are for values you filter, sort, or report on. Narrative context can stay in activity notes.

How do custom fields work with SchemaDesk objects?

SchemaDesk lets you add fields to the objects you define, so attributes sit on properties, jobs, or clients rather than crowding a single default contact layout.