Custom fields that earn their place

Why field discipline matters

A custom field is a promise. It promises that reps will fill it, that someone will read it, and that a report or automation will use it. Break any of those and the field is clutter. Break all three across forty fields and the deal detail view becomes a wall of grey that reps scroll past, including past the three fields that actually matter.

Fields also decay reports. Insights can only group and filter on what is filled in consistently. A field with a 30 percent fill rate produces a report about 30 percent of your business, presented as if it were all of it. Field discipline is not tidiness. It is the price of trustworthy numbers.

The design decisions that matter

Decision one: the admission test. A field earns its place when you can name the filter, report or automation that will consume it. We ask one question in every workshop: what will you do differently when this field is filled? No answer, no field.

Decision two: the right object. Data about the company goes on the organization, like industry or employee count. Data about the human goes on the person, like role. Data about this specific opportunity goes on the deal, like use case or contract length. The most common misplacement is company data on deals, which then needs re-entering on every new deal with that customer.

Decision three: the right type. Single option for anything you will group by. Numeric or monetary for anything you will sum. Date for anything time-based. Free text only for notes a human reads. Pipedrive also offers formula fields on higher plans for derived values, which beats asking reps to calculate margins by hand.

Decision four: when it must be filled. Marking fields as important puts them at the top of the detail view. Requiring them at a specific stage is stronger, and it turns your stage exit criteria into enforced data. Require the use case before Discovery held, and the discovery notes write themselves into structure.

A worked example

The field set we deploy for a typical B2B services team. Twelve custom fields in total across three objects, and not one more.

Note the option lists are short and mutually exclusive. Employee band has five options, not a free number nobody can group. Every field names its consumer in the last column, and that column is the audit trail for the next cleanup.

Common mistakes

The department dump is the big one. Finance wants four fields, delivery wants six, marketing wants five, and every request is granted because saying yes is easy. The deal form becomes a group filing cabinet. Route those needs to the tools that own them, and keep the CRM about selling.

Second, free text for reportables. A text field called Industry produces fintech, FinTech, financial services and banking for the same segment. The report groups them as four industries. Convert it to options and migrate the values once, as part of a hygiene pass.

Third, fields nobody may refuse. When any admin can add fields on a whim, the list grows back after every cleanup. Give field creation to one owner and make everyone else ask. The friction is the feature.

Maintenance

Run a field audit twice a year. For each custom field, check the fill rate with a simple filter on the field being empty, and check whether its named consumer still exists. Fields under 60 percent fill either get enforced at a stage or get retired. Fields whose report died get retired with them.

Retire in two steps. Prefix the name with x, drag it out of the important fields, and wait a quarter. If nobody asks, export the values and delete. This slow route has saved us more than once, and it costs nothing. Field discipline set up this way holds through the checkpoints of the six step method and long after the project ends.

Questions