Which CRM fields a small sales team actually needs

A small sales team needs about ten fields to carry a deal from first contact to order. They are the name and phone, where the lead came from, what they want, the stage, who owns the deal, the next step with its date, a rough value, the reason if lost, the company, and an expected close date. Everything else waits until someone can name the decision it would change. The easiest way to see why is to follow one enquiry and add a field only when the enquiry forces you to.

What does one enquiry force you to record?

Take an invented stone and granite slab dealer in Jaipur that gets a call on a Monday at eleven. A builder wants kitchen counter slabs for twelve flats. Here is what the team must write down, in order, and what each item gives them.

1. Name and phone. Without them nobody can ring back.
2. Source. The builder was referred by an architect. Months later, this one field tells the dealer that architects send orders and a directory listing sends only enquiries.
3. What the builder wants, in the builder's words. "Black slabs, polished, twelve kitchens." This goes into the first reply.
4. Stage. The dealer has quoted nothing yet, so the deal sits at "enquiry".
5. Owner. One salesperson, so the deal is not everyone's and no one's.
6. Next step and its date. "Visit the site and measure, Thursday." The date is the reason anyone opens the record again.
7. Rough value. An estimate marked as one, so the day's work can be ranked.
8. Lost reason. Not needed today. It is chosen from a short list if the deal dies, and it is the field that later shows why.

That is eight. Add company or household, so you know what kind of buyer it is, and an expected close date if somebody reads a forecast. Those make ten. The list is what the enquiry needed and nothing it did not.

How do the extra fields creep in?

Adding a field costs nothing on the day, and the price arrives later. Someone asks "can we also track the customer's anniversary?", the person doing the setup says yes, and six months on the record has forty boxes, thirty-one empty. The salesperson skips the form altogether. A small team has no data-entry clerk, so each field is a request for a seller's time, made while a customer waits.

The usual passengers:

• Birthday and anniversary. Useful in a jeweller's shop where the owner knows the family, of little use to a parts supplier.
• Industry, sub-industry, company size, revenue. Keep them only if you report or target by them.
• Three phone numbers and four emails. One of each at entry. Add more when a real call needs them.
• Lead score. It needs history to mean anything. With a few deals a month it is a number a formula invented.
• Competitor on every record. Ask it when a deal is lost, not on every new lead.

What is the test for a new field?

Three questions.

What decision does this field change?
Who fills it in, and at which moment?
How will we know if it is empty?

If the answers come slowly, do not add it. Let questions asked aloud in your meeting choose the fields. If every Monday someone asks which deals came from the dealer meet, you need a source value for it. If every quote needs the site pincode to price freight, add pincode.

A form cut from forty fields to eleven

Suppose the Jaipur dealer had bought a setup with forty fields on the enquiry form. The salespeople typed a name and a number and put the rest in notes. The reports came out empty, and the owner concluded the CRM was useless.

The owner began by counting. Of fifty records, only nine fields held anything. The owner hid the rest and did not delete them, because deleting is hard to undo, and added two items the team had always kept on paper, next step and its date, in bold at the top. The stage list also went from nine to five, to match how orders really moved: enquiry, quote sent, sample or site check, negotiation, order.

Then the Monday meeting ran from one view: every deal whose next step date was today or earlier. The owner saw for the first time which deals had no next step at all. That list ran to three pages, which was uncomfortable. Two salespeople said the date field felt like being watched, and the owner agreed to read it only in the Monday meeting, not during the week. The old form had been built from what could be tracked, and this one was built from what would be decided.

What do you make required?

Only what the next person cannot act without: contact, source, stage, owner, next step and date. Everything else stays optional. Use drop-down lists for source, stage and lost reason, because you will want to count them. Leave "what they want" as free text, where the customer's own words matter.

Give required fields defaults where possible. The owner is whoever created the record, and the stage starts at the first stage. Fewer clicks mean fewer skipped boxes. Lead source is worth keeping honest, and tracking lead source in your CRM shows how.

When should the list grow?

When a repeated question appears in your meetings, and not in a busy season or the week after set-up, when the team is still forming the habit. Keep requests in a list and add them together once a quarter, through one person. A factory quoting parts needs drawing numbers and quantities. A clinic needs consent to contact. Where data is about health, finance or other regulated matters, store only what you need and check with your own adviser or the regulator.

Strike out the empty ones

Print one current record and strike out every field nobody filled in over the last month. What survives is your real form. If you want help setting the form up around your decisions, CRM implementation and customisation is the work, part of how you sell. When you have the list, tell us what you need.