The two ways a contact record fails
Every contact record fails in one of two opposite directions. The first is the sticky note: a name, an email, maybe a phone number, and nothing else — so when you reopen it before a call, it tells you who they are and nothing about why you're talking. The second, less obvious failure is the bloated form: forty fields, half of them mandatory, most of them empty or filled with garbage because a rep had to type something to save the record. Both fail for the same underlying reason — the record isn't designed around what you'll actually do with the information. The art of a good contact record is figuring out the small set of things that change a decision, capturing those reliably, and refusing to capture the rest.
This matters more than it sounds, because the contact record is the atom of your whole CRM. Your segments, your lead scores, your lifecycle stages, and your reports are all built on top of these fields. Design the record well and everything downstream gets easier; design it badly and you'll be fighting empty fields and meaningless data forever. Getting this right is the foundation of CRM data hygiene — clean data starts with capturing the right things.
Start from the decision, not the field
The trap most teams fall into is starting with "what could we track?" — which has an infinite answer — instead of "what would change what we do?" Flip it. For every field you're tempted to add, ask: when this is filled in, what decision does it change, or what action does it trigger? If the honest answer is "none, but it might be nice to have," leave it out. A field that drives nothing is pure cost: it clutters the form, it dilutes the fields that matter, and it trains your team that most of the record is optional noise.
The fields that survive that test cluster into a few groups. Identity and reach: name, email, phone, company, role — the basics you genuinely act on. Fit: the one or two attributes that tell you whether this is your ideal customer — company size, industry, the thing that defines a good account for you. Context: where they came from (the source field that, as any outreach compliance or attribution question proves, is worth its weight), and what stage of the relationship they're in. Everything else should earn its place or stay out.
Custom properties beat a wall of mandatory fields
Here's the tension: different contacts need different information. The data that matters for a trade-show lead isn't what matters for an inbound trial user or a referral. If you try to serve all of them with one giant mandatory form, you get the bloat problem — fields that are essential for one kind of contact and meaningless for another, all demanded of everyone.
The cleaner solution is a small core of fields everyone has, plus custom properties you attach only where they're relevant. A property is just a named piece of data on the contact — "trial plan," "renewal date," "NAICS code," whatever your business actually acts on — that doesn't need to exist on every record. This keeps the common record lean while letting you capture depth where it counts. The principle is the same one behind logging activity well: capture what you'll use, in a structured place, and don't drown the signal in mandatory noise.
Tags are for the questions you'll ask later
Properties hold values; tags answer questions. A tag is a lightweight label you stick on a contact — "webinar-march," "enterprise," "champion," "asked-about-pricing" — and its whole purpose is to let you pull a list later. The test for a good tag is simple: will you ever want to find everyone with this label? If yes, it's a tag. If it's a one-off detail about a single contact, it's a note, not a tag.
Tags earn their keep when they feed segmentation. "Everyone who came from the March webinar and hasn't been contacted in two weeks" is a campaign waiting to happen — but only if you tagged the webinar source when the contacts came in. The discipline is to tag at the moment of capture, not in a cleanup pass that never happens, because a tag applied consistently is a segment you can act on and a tag applied haphazardly is just clutter. Used well, tags turn your database from a pile of records into a set of audiences you can message with precision.
The unwritten rule: if nobody fills it in, delete it
A field's real value isn't its potential — it's its fill rate. A "budget" field that's blank on 80% of records isn't giving you data; it's giving you a false sense of having data, and it's wasting the half-second of attention reps spend skipping past it every time. The healthiest thing you can do for a contact record is periodically audit which fields actually get filled in and ruthlessly cut the ones that don't. This is the maintenance side of data hygiene: a lean record people keep current beats a comprehensive record people abandon.
The same logic explains why you shouldn't make every useful-sounding field mandatory. A required field that a rep can't honestly fill in just teaches them to type "n/a" or "asdf" to get past it — and now your data is worse than if the field were empty, because empty at least reads as "unknown" instead of masquerading as a real answer. Require only what you genuinely have at the moment of creation; let the rest fill in naturally as the relationship develops.
Design the record around what your CRM will do with it
The reason to think hard about all this is that the contact record is where your CRM's intelligence comes from. Every smart thing the system does — scoring, segmenting, routing, automating — reads these fields, and it can only be as good as what you put there.
In Hitt CRM, the core contact fields plus flexible properties and tags give you exactly this lean-core-plus-depth model: the common fields stay clean while custom properties and tags capture what your business specifically acts on. Those tags and properties power segments you can message, feed the lead score and lifecycle stage that tell you who to focus on, and surface on the contact timeline alongside every interaction so the record reads as a relationship instead of a row in a database. Design the record around the decisions you'll make and the actions you'll automate, and the rest of the CRM gets sharper for free.
The one-sentence version
A contact record fails by being too thin to inform a call or too bloated with empty mandatory fields to trust, so the fix is to start from the decision rather than the field — keeping a lean core everyone has, attaching custom properties only where they're acted on, tagging at the moment of capture for the segments you'll build later, and deleting any field nobody actually fills in — because everything your CRM does downstream is only as good as the handful of things you chose to track well.