Five CRM Fields You Should Delete Tomorrow

Most B2B sales teams collect more CRM data than they ever use. So it’s time to simplify CRM fields before the team gives up on the system entirely.

In fact, every quarter someone in operations decides a new field would be useful. Industry vertical. Lead source. Deal type. Decision criteria. Competitive landscape. However, three months later that field is half-filled, inconsistently labeled, and nobody looks at it.

Now repeat that pattern across five years and three CRM admins, and you end up where most teams are: forty-seven fields per opportunity, sales reps avoiding the CRM, and reports nobody trusts.

Now repeat that pattern across five years and three CRM admins, and you end up where most teams are: forty-seven fields per opportunity, sales reps avoiding the CRM, and reports nobody trusts.

Why bad CRM design happens

CRMs grow the way attics grow. Specifically, they expand slowly and silently, without anyone noticing. Until one day, the system is so cluttered that nobody can find anything useful.

The reasons are predictable. For example, a marketing person asks for a custom field to track campaigns. Meanwhile, finance needs a field for billing codes. And sales managers want a “deal temperature” score on a 1-10 scale. Each request is reasonable in isolation. However, together they create administrative overhead that nobody designed on purpose.

Here’s the part nobody talks about. The more fields you add, the worse the data quality gets. Because reps stop filling things in consistently. As a result, the fields that actually matter get the same half-effort treatment as the ones nobody reads.

That’s not a discipline problem. Instead, that’s a design problem. So the only way out is to simplify CRM fields, not to add more of them.

“A CRM with 47 fields per opportunity isn’t comprehensive. It’s a graveyard.”

The test before you keep a field

Before we get to the five fields you should probably delete, here’s the test that should apply to every CRM field in your system.

A field deserves to exist only if at least one of these is true. First, it triggers an automation. Second, it shows up on a dashboard somebody actually uses. Third, it filters a report that drives a weekly decision. Or finally, it changes how a deal gets handled.

If your field doesn’t do one of those things, it’s decoration. And decoration in a CRM is just admin in a fancy outfit. Therefore, simplify CRM fields by asking this question of every single one.

Field #1 – “Industry Vertical” (when you sell to everyone)

Industry classification feels strategic. However, when you look at how it’s actually used, the picture changes.

For instance, most B2B teams have 30+ industry options in their CRM. And reps pick inconsistently. One marks a fintech startup as “Financial Services.” Another picks “Technology.” A third picks “SaaS.” Therefore, six months later, your industry-based reporting is useless because the same companies are categorized three different ways.

So delete it unless you have a sharply defined ICP (Ideal Customer Profile) across exactly 3 to 5 verticals, with different sales motions for each. Otherwise the field is noise.

What to keep instead: one boolean field. “ICP fit: yes/no.” That’s all the segmentation that matters at the deal level.

Field #2 – “Lead Source” (without a clear taxonomy)

Lead source sounds like the most important field in the CRM. However, it isn’t. Or at least, not the way most teams have it set up.

For example, here’s the classic pattern. A dropdown with 20+ options. Then somebody adds “Other.” After that, everyone picks “Other.”

Without a clear taxonomy enforced at the moment the lead enters the system, this field becomes archaeological evidence of past marketing campaigns. Not a decision-driving data point.

So delete it unless lead source is automatically populated from your marketing automation, with a fixed list of 5 to 7 options maximum. Because manual entry kills this field.

What to keep instead: one simplified dropdown with categories that actually drive different sales motions, like Inbound, Outbound, Referral, and Partner. Done.

Field #3 – “Deal Probability %” (when reps just guess)

Deal probability is a beloved field in sales operations. However, it’s also the most fictional data point in most CRMs.

Here’s how it usually works. A rep is asked: “what’s the probability of closing this deal?” The rep guesses based on gut feeling. Then the number gets typed in. Nobody pushes back. As a result, forecasting software multiplies the deal value by the probability and produces a number that looks like data but is built on vibes.

In contrast, real forecasting probability comes from stage-based weighting. Not from rep gut-feeling. For example, a deal in “proposal sent” stage might be 40% historically, while a deal in “verbal commit” might be 80%. Those numbers are based on actual data from past deals, not on what the rep hoped to be true on a Tuesday afternoon.

So delete the manual probability field. Instead, replace it with stage-based weighted forecasting that doesn’t depend on rep optimism.

What to keep instead: clear stage definitions. Because each stage has its own historical conversion rate. That’s your forecast.

Field #4 – “Next Step” (without a date)

Every CRM has a “Next Step” field. However, most of them are filled with phrases like “follow up,” “check in,” “circle back,” and “send update.”

But none of these are next steps. Instead, they are intentions disguised as actions. In fact, a real next step has three things: first, a specific action; second, a specific person responsible; and third, a specific date. Anything less is a deal sitting still while looking busy.

So the fix isn’t to delete the field. Instead, redesign it so it can’t be filled with vague language.

First, delete the open text “Next Step” field. Then replace it with two required fields: a dropdown for action type, plus a mandatory date picker.

What to keep instead: structured next action with type and date. Because if those two aren’t filled, the deal can’t advance stage. So the CRM stops being optional.

Field #5 – “Notes” (as a single text field used for everything)

The “Notes” field is the place where good intentions go to die.

For example, some reps use it for call summaries. Others paste in email threads. A handful write a single line. The rest don’t use it at all. As a result, six months later, when somebody needs to find what was discussed in the May meeting with the procurement lead, the “Notes” field is an unstructured graveyard of varying detail.

Modern CRMs handle this automatically when integrated with your calendar, email, and call tools. Therefore, the issue is rarely the CRM capability. Instead, it’s the lazy default of using “Notes” as the catch-everything field.

Modern CRMs handle this automatically when integrated with your calendar, email, and call tools. So the issue is rarely the CRM capability. Instead, it’s the lazy default of using “Notes” as the catch-everything field.

So delete the generic Notes field. Then force structured activity logs instead. Or use AI summarization tools that automatically log call recaps to the right place.

What to keep instead: a structured activity timeline. Each interaction has its own type, date, and content, which makes it searchable, sortable, and actually useful when you need it.

The discipline behind simplifying CRM fields

Deleting fields feels destructive. However, it isn’t. Because bad fields aren’t data. Instead, they’re noise. And noise hides the signal.

Most sales leaders are afraid to simplify CRM fields because someone, somewhere, might be using them. But that’s exactly the problem. If you don’t know who uses a field or why, the field is already broken. So deleting it surfaces the people who actually need it. Then they’ll ask. After that, you can rebuild it properly, with a real use case.

In short, better to have 12 CRM fields that reps actually fill in, than 47 fields half-filled by people who hate the system. Because a CRM should drive action, not just store information.

Practical checklist — Is your CRM bloated?

1. Reps openly complain about the CRM taking too much time ☐
2. You have more than 25 custom fields per opportunity ☐
3. At least 30% of your fields have low fill rates (under 60%) ☐
4. Different reps fill the same field differently (no standard taxonomy) ☐
5. You can’t immediately name 3 dashboards that use the data ☐
6. “Other” is the most-used option in at least one dropdown ☐
7. You have fields tracking similar things (“priority”, “score”, “temperature”) ☐
8. Onboarding new reps on the CRM takes more than 1 hour ☐

If three or more sound familiar, your CRM is bloated. So it’s time to simplify CRM fields before the team gives up on the system entirely.

The ODB Way

At ODB Growth, one of the first things we do when we walk into a commercial team is audit their CRM. Not the configuration. Instead, the actual usage patterns.

First, we pull fill-rate reports for every field. Then we look at which fields have automated downstream uses. After that, we check which fields are inconsistently labeled. Finally, we propose deletions, often dozens of them.

The result is consistent. As a result, reps spend less time on admin and more time on selling. Furthermore, data quality on the remaining fields goes up. Reports become trustworthy. And nobody misses the fields we deleted.

Because the goal of a CRM isn’t to capture everything. Instead, it’s to drive the right action at the right moment. So when you simplify CRM fields properly, action stops getting buried under data, because it’s exactly one of the four sales leaks every B2B company has.