Chapter 4: Required fields, properties, and data discipline

Part of the Small B2B CRM Setup Handbook.
This chapter explains how to design CRM fields that support decision making instead of slowing your team down.

← Back to the handbook overview

Why data discipline matters

Data discipline is the difference between a useful CRM and an expensive address book.

Every field you add to your CRM is a tax on the seller’s time. If a piece of data is not used to make a decision, automate a process, or generate a report, it is clutter and should not exist.

Required fields should be reserved for the handful of data points that genuinely matter for forecasting, prioritization, and process enforcement.

The most common mistake

The most common mistake is creating dozens or hundreds of properties “just in case” they might be useful later.

This creates visual noise, slows down data entry, and makes it impossible for sellers to understand which fields actually matter. Over time, they stop trusting the CRM and start working around it.

The need to know principle

Every property in your CRM should earn its place.

Apply the Need to Know principle ruthlessly.

1. Audit every property

For each field, ask a simple question: Who uses this data, and what decision do they make with it?

If the answer is “no one” or “I don’t know,” the field should be deleted or archived.

2. Field type matters

Always use the most restrictive field type possible.

  • Use dropdowns instead of free text whenever possible
  • Use date pickers for dates
  • Use numeric fields for amounts and counts

Dropdown fields enforce consistency, which is essential for reliable reporting. Free text fields create chaos and destroy data quality over time.

3. Be selective with required fields

Only make a field required if its absence genuinely breaks your sales process or forecasting.

Whenever possible, make fields conditionally required at specific pipeline stages instead of globally required. This reduces friction while still enforcing discipline.

HubSpot guidance

HubSpot offers a wide range of property types, but the most important concept to master is property grouping.

  • Property groups: Organize fields into logical sections such as Sales Information, Company Firmographics, or Marketing Data. This helps sellers find what they need quickly.
  • Sidebar customization: Use the “Customize left sidebar” feature to surface only the most critical properties by default.
  • Calculated properties: Use calculated fields to derive values like Time Since Last Activity instead of asking sellers to track them manually.

Calculated properties are one of the most effective ways to improve CRM usefulness without increasing manual effort.

Actionable setup

Create a property group called Required for Forecasting.

Place only the three to five fields absolutely necessary for revenue prediction in this group, such as:

  • Deal amount
  • Close date
  • Forecast category

Everything else is secondary and should never block progress in the sales process.

Continue reading the handbook:

← Previous: Chapter 3 – Designing a sales pipeline that reflects reality
Next: Chapter 5 – User roles, permissions, and ownership rules →