Guide

What fields should my CRM have?

The right fields are the ones someone will fill in and someone else will use. Here's how to find them.

Start from decisions, not data

Every field should answer a question someone asks while working: who do I call next, what does this customer owe, when is the job due. If nobody would miss a field, leave it out.

List the five decisions your team makes most often, then the information each one needs. That list is most of your fields.

The fields almost every business needs

Whatever you do, people and the work you do for them need a few basics:

  • People: name, email, phone, and who in your team owns the relationship.
  • Companies, if you sell to businesses: name, and the people who work there.
  • The work itself (jobs, deals, projects, orders): what it is, its stage, its value, and the date that matters.
  • Dates that drive follow-up: when it's due, when you last spoke, when it renews.

Link records instead of repeating them

If you type a customer's name on every job, you have two copies that will disagree. Link the job to the customer instead, and the CRM can show every job for that customer and add up what they're worth.

Fields to be careful with

Some fields cause more trouble than they solve:

  • Free-text status fields: use stages or a fixed list of choices instead, so you can count them.
  • Fields only one person understands: name them in plain words, and describe them.
  • Totals typed by hand: let the CRM work them out from the records.

Make the important ones required, and check the rest

Mark a field required only if a record is useless without it. For fields needed only sometimes (a close date once a deal is won), use a rule instead, so people aren't forced to invent values.

Or let the interview work it out

Chaudie asks how your business runs and designs the modules and fields from your answers, with the reason for each one, before anything is built.

Questions

How many fields should a CRM have?+

As few as do the job. Most modules need 5 to 15; more than that usually means two modules sharing one.

Should every field be required?+

No. Require only what makes a record useless when missing, and use rules for the rest.

More to read

Start with the interview.

You'll see exactly what we'd build before anything is built.

Build my CRM