EN
See the demo

Sales pipeline

CRM custom fields setup: add the fields your sales process needs

Krokul CRM is a B2B CRM for contract-based companies: deals, projects and profit per client in one system, implemented by integration partners. This recipe shows how an admin adds a field such as Budget to deals, decides who must fill it in and at which stage, and checks how many records use it.

Short answer

A CRM custom fields setup adds the fields your company needs to deals, contacts, client companies and other records for data the standard form lacks. Choose the record, name the field, pick a type and decide whether it is required. Group related fields into a block so a card stays readable.

  • Records: six models
  • Field types: ten
  • Who adds fields: an admin
On this page
  1. Short answer
  2. When you need them
  3. The six steps
  4. Example fields
  5. Common mistakes
  6. Checklist
  7. In Krokul
  8. FAQ

When your sales process needs custom fields#

Add a custom field when the standard card has no place for something your process depends on. A field is also the way to make a stage demand the data, as described in how to build a sales pipeline that predicts revenue.

  • Every quote depends on a budget, and the budget lives in comments that nobody can filter.
  • A manager asks which deals have a delivery date, and the answer is a spreadsheet.
  • Two reps record the same fact under different names and the reports do not add up.
  • A stage should not accept a deal until a certain fact is known.
  • A client company has a contract number or an account tier that every manager needs to see.
Custom field
A custom field is a field that a company adds to its own records, with its own name and type, to hold data the standard form does not have.
Field block
A field block is a named group of custom fields that appears as one section on a card.

How to do a CRM custom fields setup in six steps#

Adding a custom field means deciding what the field is for before opening the settings. The six steps below go from the question to the filter, and each one prevents a common cleanup later.

  1. Name the question the field answers

    Write the question in one sentence, for example “What budget did the client confirm?”. A field that answers one clear question gets filled in, and a field called “Notes 2” does not.

    Decide which record it belongs to: a deal, a contact, a client company, a product, a task or a project. The record cannot change after the field exists.

  2. Choose the type once

    Pick the type that matches the answer: text, long text, whole number, number, date, date and time, list, multi-select list, yes or no, or link. Use a list when the answers come from a fixed set, so the register can count them without spelling variants.

    The type of an existing field cannot be changed, because saved values would be read as a different type. Choosing a number for a budget now saves a rebuild later.

  3. Create the field in the settings

    Only an admin adds fields. Open the Custom fields tab in the settings, choose the record, press the add button, enter the name and the type, and for a list type add the options.

    Krokul builds a stable key for the field from its name, with the prefix cf_, and keeps it when you later rename the label. Renaming the key is a separate, confirmed action that shows how many records use the field.

  4. Put related fields into one block

    Give the field a block name, such as “Qualification” or “Delivery”. Fields of one block sit together under one heading in the Passport tab of the deal card.

    Leave the block empty for a field that stands alone. Most fields in a company need no block.

  5. Decide who must fill the field and when

    The required switch on the field demands it on every record of that model, which fits a fact like the client company. For a deal fact that matters only from a certain moment, leave the switch off and name the field as a required field of the stage instead. The stage list of required fields offers the deal custom fields next to the standard ones, so a person cannot move a deal into the stage until the budget is filled.

    This keeps new deals easy to create and puts the discipline where the process needs it. The article on stage exit criteria for pipelines explains how to choose the fields.

  6. Check the usage of the field

    Open the field to see how many records already hold a value, and watch that number grow as the team fills the field. The list of fields shows the same count in its own column.

    Mark a field for selection when an integration must find deals by its value, such as the delivery date; the API can then select records by it. Review the list of fields once a quarter. A field with almost no values is a question the team does not use, and removing it keeps the card short.

    Tip. Add a field only when someone will read the answer. Every extra field costs the manager a few seconds on every deal.

Deal card of a demo workspace with the items tab, availability and a feed of tasks and stage changes
A different screen: a deal card in Krokul, the record on which deal custom fields hold their values.

Which fields a B2B sales team usually adds#

Most teams start with a handful of fields that answer questions the standard card cannot. The table below shows four typical fields for deals and what makes each one useful.

Example: four custom fields for deals
FieldTypeRequiredWhy it is there
BudgetNumberAt the Proposal sent stageA quote is built around a budget the client confirmed
Delivery dateDateNoThe team and integrations read the agreed date
Decision makerTextAt the Negotiation stageA deal without the person who decides stalls
Budget statusListNoConfirmed, not disclosed, not approved yet

The rule behind the table: a field is required only at the stage that needs the answer. Four fields, two of them gated, mean the form for a new deal stays short and the later stages stay strict.

Which mistakes make custom fields useless#

  • Using text for everything. Free text cannot be counted, so use a list when the answer comes from a fixed set.
  • Marking a deal field required for the whole company. Every new deal then asks for facts nobody knows yet, so require it at the stage instead.
  • Creating a field per rep or per team. Reports split, so create one field and agree on its meaning.
  • Leaving unused fields on the card. They hide the useful ones, so review the list every quarter.
  • Changing the meaning of a field after launch. Old values then mean something else, so create a new field.

A checklist for adding a custom field#

Copy the list into the admin’s routine. The weekly review of deals that depend on such fields is covered in how to find stalled deals.

  • The field answers one clear question that someone reads.
  • The record and the type are chosen correctly the first time.
  • The name is written the way the team speaks.
  • Related fields sit in one named block.
  • Required is set at the stage that needs the fact, unless the fact is always known.
  • Selection is switched on for fields that integrations use to find deals.
  • The list of fields is reviewed once a quarter.

How custom fields work in Krokul#

Krokul lets an admin add custom fields to deals, contacts, client companies, products, tasks and projects, with ten field types. Every role can read the list of fields, and only an admin changes it. The values of a deal field are filled in on the deal card in the group of additional fields, and the list of fields shows how many records hold a value.

A deal field can be named as a required field of a stage in the pipeline settings, which is how stage gates in a Krokul pipeline ask for the data. The same fields describe client companies, as on the page about client company cards in Krokul.

Frequently asked questions#

Who can add custom fields?

An admin. Other roles read the list of fields and fill in the values on the records they work with, but the composition of fields is changed only by an admin.

Can I change the type of a field later?

No. The type is fixed when the field is created, because saved values would otherwise be read as another type. Create a new field with the right type and move the data.

What happens to a field key when I rename the label?

The key stays the same. It is built from the name once and renaming it is a separate confirmed action that shows how many records are affected.

Should a field be required for every deal?

Only when the fact is known at creation. For a fact that appears later, name the field as required at that stage, so a deal cannot enter the stage without it.

Can I select deals by a custom field?

Through the API. Mark the field for selection in the settings, and an integration can select deals by its value. The deal register on the screen does not offer such a filter.

Krokul Team

The people who build Krokul CRM

We write about getting paid, billing delivered work and project margin, and check every product statement against Krokul itself.

First published

See the demo