Blog

Required CRM fields that actually get filled accurately

November 9, 2026

In short

Required fields often get filled with whatever unlocks the save button, which is worse than leaving them empty. Choose a small set of decision-driving fields, map each to something a buyer would say out loud, and let a revenue orchestration platform fill them from the meeting with the source attached.

The problem with required fields

Admins make fields required because they are tired of empty records. Reps respond by entering placeholder values: a close date at quarter end, a generic next step, the first contact in the list as decision maker. The field is full and the information is wrong.

Step 1: Keep only fields that drive decisions

Ask of every field: what decision changes if this value changes? If the answer is none, remove the requirement. Most teams can start with:

  • Next step, with a date.
  • Close date.
  • Decision maker and champion.
  • Identified pain.
  • Key risk.

Step 2: Map each field to something a buyer says

Accurate fields come from buyer language, not rep opinion. Define the evidence for each one.

  • Close date: the buyer named a timeline or event.
  • Decision maker: someone stated who signs.
  • Pain: the buyer described a cost of the status quo.
  • Risk: a blocker, competitor, or budget concern was mentioned.

Step 3: Align fields to your methodology

If your team uses MEDDPICC, BANT, or a custom framework, the fields should mirror it exactly. That makes deals comparable and coaching easier. Berri lets you define the note format once and apply it to every update.

Step 4: Let the meeting fill them

Once fields map to conversation evidence, a revenue orchestration platform can fill them automatically. Berri listens to the meeting, drafts each field, and keeps the quote or moment it came from so anyone can check.

Step 5: Audit with sources, not spot checks

  • Sample filled fields weekly and check them against the source.
  • Track how often reps edit drafted values.
  • Retire fields that are rarely used in decisions.

The takeaway

Fewer fields, defined by buyer evidence, filled from the conversation. That is how required fields become reliable fields.

Frequently asked questions

How many required fields should an opportunity have?

Only as many as drive decisions. Many teams do well with five to eight.

Why are required CRM fields inaccurate?

Reps fill them to save the record, not to describe the deal, especially when entry happens long after the meeting.

Can AI fill CRM fields from meetings?

Yes. Berri drafts fields from meetings and keeps the source attached for review.

Get Started