The CRM Fields Small B2B Teams Actually Need (and the Ones to Drop)
By the Tracklibute team · October 29, 2026
Most CRMs come with dozens of fields, and most small teams add a few more each quarter. Eventually creating a deal takes three minutes, half the fields are empty, and the other half are filled with "N/A". More fields don't give you better data. The right handful of fields, kept accurate, does.
This guide lists the fields a small B2B sales team actually needs, why each one earns its place, and which fields you can usually drop.
Key takeaways
- Keep about 8 to 12 fields on a deal, and make sure each one is used in a decision or a report.
- The most important fields describe what happens next, not what happened before.
- Use picklists for anything you want to count or filter on.
- Review your fields every quarter and remove any nobody has used.
The test every field has to pass
Before keeping a field, ask: what decision or report uses this? If nobody can answer, the field is costing time without giving anything back. A good field is used in at least one of these:
- Deciding what to do next on a deal
- The weekly pipeline review
- The forecast
- Understanding why you win and lose
The essential deal fields
| Field | Type | Why it matters |
|---|---|---|
| Deal name | Text | Company plus product, for example "Acme – Growth plan" |
| Owner | User | Someone has to be responsible |
| Stage | Picklist | Where the deal is, using written definitions |
| Amount | Number | Needed for any forecast |
| Expected close date | Date | Shows timing and slippage |
| Next step | Text | The single most useful field for follow-up |
| Next step date | Date | Turns a vague plan into a commitment |
| Lead source | Picklist | Shows which channels bring real deals |
| Primary contact | Contact | Who you're actually talking to |
| Decision maker | Contact | Often a different person from the primary contact |
| Loss reason | Picklist | Filled in when a deal closes as lost |
That's 11 fields. Some teams add one or two of their own, such as plan type or region, but every addition should pass the test above.
Why "next step" and "next step date" matter most
Most fields describe the past. These two describe the future. They tell you what has to happen and when, which makes them the base for follow-ups, stall detection and a useful pipeline review. If you only improve one thing in your CRM this month, make it this. We explain how to use them to catch slowing deals in how to spot a stalled deal.
Why picklists beat free text
You can't easily count free text. If loss reasons are typed by hand, "price", "too expensive" and "budget" end up as three different answers. A short picklist, with an "Other" option and a notes field, gives you numbers you can actually use.
The essential contact fields
Keep contacts lean too: name, email, company, role, phone (optional), owner and last activity date. Role is worth keeping because it tells you whether you're speaking with a user, a manager or a budget holder.
Fields you can usually drop
- Probability % when it's typed by hand. Reps guess, and the guesses rarely match reality. Tie probability to stage instead, or leave it out.
- Long lists of "nice to know" facts such as company founding year or office count, unless you actually segment on them.
- Duplicate date fields such as "first contacted", "first meeting" and "first demo" when the activity history already shows them.
- Fields created for a one-off project that ended months ago.
Hide them first rather than deleting them, in case someone depends on them. If nobody notices after a month, remove them.
Required or optional?
Make only a few fields required: owner, stage, amount, expected close date and next step. Everything else should be easy to fill in but not compulsory. When too many fields are required, people enter placeholder values just to save the record, and the data gets worse.
Example: trimming a cluttered deal form
*This is an illustrative example, not a real customer.* A small IT services team had 27 fields on its deal form, 9 of them required. In a quarterly review, it found 14 fields that hadn't appeared in any report or pipeline review. It hid those 14 and cut required fields down to 5. Creating a deal now takes under a minute, and next step was filled in on almost every open deal the following month, because it was no longer buried among fields nobody used.
Where Tracklibute fits
Tracklibute's CRM hygiene job watches the fields that matter most, such as missing next steps, past-due close dates and empty loss reasons, and prepares updates from your emails and meeting notes. Important changes wait for your approval. For the weekly routine that keeps these fields accurate, see CRM hygiene without a RevOps team.
Frequently asked questions
How many fields should a deal record have?
For most small B2B teams, around 8 to 12. The exact number matters less than whether each field is used in a decision or report.
Should we track deal probability?
Only if it's tied to stage or calculated from real history. Hand-typed probabilities are usually too optimistic to help a forecast.
How often should we review our fields?
Once a quarter. Remove or hide anything nobody has used, and check that picklist values still match how you sell.
