What should we configure first in a new CRM?

Pipeline stages, and do not rush them. Every report, every forecast and most automation depends on stages, so changing them later means rebuilding whatever was built on top. Agree them with the people who will use them, define each by an observable event rather than a level of confidence, and keep the count to five to seven. Only once stages are settled should you add fields, then build views, then add automation. Teams that configure in the reverse order, starting with automation because it is the exciting part, generally rebuild everything within a quarter.

How many custom fields is too many?

The number is less useful than the test. For each proposed field, name the report it will appear in or the automation that will use it, and the person who will look at it. Fields that fail that test are decoration, and each one adds a small permanent cost to every record created from then on. There is a second test worth applying: will the person entering data know the answer at the moment of entry. Fields requiring research get skipped, and a field that is usually blank is worse than no field.

Should fields be mandatory?

Only the ones you would genuinely refuse to work without, typically a name, a contact method and an owner. Making fields mandatory at creation feels like enforcing quality and usually produces the opposite, because a seller capturing a fast conversation will enter whatever passes validation. A better pattern is to require information at the point where it is genuinely known, using stage entry criteria: a deal cannot move to quoted without a value, or to won without a close date. That places the requirement where the answer actually exists.

How do we name things so it stays comprehensible?

Pick a convention on day one and write it down. Use the vocabulary your team already speaks rather than the vendor terminology. Be consistent about singular or plural, about whether you abbreviate, and about ordering, so that related items sit together in an alphabetical list. Prefix automation rules with what triggers them, so the list is readable at a glance. None of this is interesting and all of it saves time, particularly when someone new takes over administration and has to work out what an ambiguously named field was for.

Can we change stages later without ruining our history?

Partly, and this is worth understanding before you start. Renaming a stage is usually safe. Merging two stages typically reassigns historical deals, which changes what your past reports show. Deleting a stage can be destructive. Before any stage change, export a snapshot of open and recent deals, make the change on a copy or in a sandbox if one is available, and check a saved report before and after. Then tell the team what changed, because a silently reshaped pipeline is the fastest way to lose trust in reporting.

What should we never customise?

Anything that duplicates a standard object. Creating your own contact-like record because the standard one lacks a field is a decision you will regret, since reporting, deduplication and integrations all understand the standard object and understand nothing about yours. Similarly, avoid encoding a temporary process into a permanent field structure, and avoid building automation around a policy that is still being argued about. Configure the parts that are settled and leave the unsettled parts manual until they stop moving.

How do we know if our configuration has gone wrong?

Three signals. People keep a private spreadsheet alongside the system, which means the system does not answer a question they need. Fields are blank on a large share of records, which means they are not answerable at entry time. And reports need manual adjustment before anyone trusts them. Any one of those is worth an afternoon of cleanup. HelloGrowthCRM keeps configuration deliberately light for small teams, with stages, fields and automation manageable without an administrator, from $10/user/month billed annually with a free plan available.

No-Code CRM Customisation

Customising a CRM without code, and without creating a mess you cannot undo

The order to configure things in, the fields worth adding and the ones that will haunt you, naming conventions that save an afternoon a year, and how to change something later without breaking your history.

Free Forever Book a demo

Free Forever • No Credit Card Required

Illustration of CRM configuration showing stages, fields, views and automation being set up in order

Quick answer

Is HelloGrowthCRM right for No-Code CRM Customisation?

Yes. HelloGrowthCRM gives No-Code CRM Customisation a single system to capture every lead, automate follow-up across phone, WhatsApp, and email, prioritise leads with AI scoring, and forecast revenue — with calling and messaging built in instead of sold as add-ons. It's built for the problems these teams actually hit — like the system was configured enthusiastically in the first week and nobody can now explain why half the fields exist — rather than generic sales busywork.

Configure in this order: pipeline stages, then the small set of required fields, then views, then automation. Building automation on stages you have not settled means rebuilding it twice
Stages are the highest-leverage configuration in any CRM, because every report, forecast and automation depends on them. Spend an hour agreeing them and ten minutes building them
Define each stage by an observable event rather than a feeling. We have sent a quote is a stage. The customer is interested is a mood, and moods produce forecasts nobody can challenge

See pricing Book a demo

Order matters more than choices

Most CRM configuration regret comes from sequence rather than from bad individual decisions. Stages first, because everything depends on them. Then the small set of fields you actually need. Then the views people will work from every day. Then automation, once the things it acts on have stopped moving.

Reversing that order is common because automation is the visible, satisfying part. The cost is that a stage change in month two invalidates a set of rules built in month one, and the rebuild is rarely done thoroughly.

Stages: the hour that pays for itself

Stage	Entry criterion	What it is not
New	Record exists with contact details	Someone we might call one day
Qualified	We have spoken and confirmed a real need	They seem interested
Quoted	A written price has been sent	We discussed pricing
Negotiating	They have responded with terms or objections	We are hopeful
Won or lost	A decision has been given	It has gone quiet

That last row deserves emphasis. Deals that go quiet are the largest single distortion in small business pipelines, because they sit in a stage indefinitely and inflate the forecast. Decide in advance what happens to a deal with no activity for a set period, and apply it consistently.

Fields, and the discipline of saying no

The two tests

Will anyone filter, report or automate on it. And will the person entering data know the answer at the moment they are entering. A field that fails the first is decoration; a field that fails the second will be blank. Applying both tests will cut a proposed field list roughly in half, which is the intended outcome.

Picklists for anything countable

Lead source, loss reason, industry, product interest. If you plan to count it, constrain it, and keep the list short enough that the right option is obvious. Long option lists produce inconsistent selection, which looks like structured data and behaves like free text.

Automation, added slowly

Add one rule, watch it for a week, then add the next. This feels excessively cautious until the first time something behaves oddly and you have fourteen rules to inspect. Name rules by their trigger so the list reads as a description of behaviour. Keep an owner against each. And always test on a record created for the purpose, because the alternative is a live customer receiving a message that begins with the word test.

Changing your mind later

Configuration is not permanent, but changes have different costs. Renaming is cheap. Deactivating a field is cheap and preserves history. Merging stages rewrites what your historical reports say. Deleting anything is the expensive option and often takes data with it. Before any structural change, export a snapshot, note what your key report says today, make the change, and compare. Then tell the team what moved. Most loss of confidence in a CRM traces back to a report that changed without explanation, not to the change itself.

Related setup and configuration reading: what is a CRM, features, CRM versus Excel, free CRM, sales automation, and lead management software.

Challenges we solve

The problems holding this industry back — and the fix

Every team in this space loses revenue to the same recurring gaps. Here is what they cost you and how HelloGrowthCRM closes each one.

The system was configured enthusiastically in the first week and nobody can now explain why half the fields exist.

Keep a short configuration note recording each field, why it exists and who asked for it. Twenty minutes of documentation makes future cleanup a decision rather than an investigation.Configuration notes

Reporting is unreliable because key information sits in free-text fields that nobody filled consistently.

Use picklists for anything you intend to count, keep the option lists short, and reserve free text for context. This is the single most common cause of a CRM that holds data but cannot answer questions.Picklists for countable data

Data entry is slow because everything is mandatory, so sellers enter minimum-viable nonsense to get past the screen.

Require only the fields you would refuse to work without, and enforce the rest through stage entry criteria rather than at creation. Mandatory fields at the wrong moment produce bad data, not complete data.Minimal required fields

An automation misfires and nobody can work out which of the fourteen rules did it.

Add one rule at a time with a gap between them, name rules descriptively, and keep a list with owners. Automation debt accumulates faster than anyone expects in a system that is easy to configure.Incremental automation

What you get

Why teams choose HelloGrowthCRM

AI-powered CRM with the features you need to close more deals.

Configure in this order: pipeline stages, then the small set of required fields, then views, then automation. Building automation on stages you have not settled means rebuilding it twice.

Stages are the highest-leverage configuration in any CRM, because every report, forecast and automation depends on them. Spend an hour agreeing them and ten minutes building them.

Define each stage by an observable event rather than a feeling. We have sent a quote is a stage. The customer is interested is a mood, and moods produce forecasts nobody can challenge.

Five to seven stages is enough for almost every small business. More stages produce more precise-looking reporting and worse data, because people stop caring where a deal sits.

Every required field is a tax paid at the worst possible moment, which is when someone is trying to record a fast-moving conversation. Require the three that matter and make the rest optional.

A field nobody filters or reports on is decoration. Before adding one, name the report it will appear in and the person who will use it.

Use picklists rather than free text wherever you intend to count something. Free text is fine for context and useless for reporting, and the difference only becomes visible a year later.

Adopt a naming convention on day one and write it down. Consistent, boring names make training faster and prevent the situation where three fields describe roughly the same thing.

Do not delete fields, deactivate them. Deletion usually takes the historical values with it, and someone will ask about those values eventually.

Automation should be added one rule at a time with a week between them, so that when something behaves strangely you know what caused it.

Test every automation on a record you have created for the purpose, not on a live customer. This advice is universal, ignored under time pressure, and the reason so many customers receive test messages.

Write a short configuration note listing your stages, required fields, automations and their owner. It takes twenty minutes and it is the difference between onboarding an administrator and archaeology.

Compare HelloGrowthCRM to HubSpot, Salesforce & more

HelloGrowthCRM by the numbers

$12: per user/month list price — $10/user/mo on annual billing, ₹899/user/mo in India
$0: free forever starter plan — no credit card required
14-day: trial included on paid plans
259+: live integrations, from WhatsApp to Tally and QuickBooks
500+: teams worldwide run their pipeline on HelloGrowthCRM

Frequently Asked Questions

Common questions about using HelloGrowthCRM in your industry.

Ready to grow?

Join small businesses that close more deals with HelloGrowthCRM.

Free Forever View all industries

Free Forever • No Credit Card Required

Take the next step

Free Forever • No Credit Card Required

Start FreeSet up in minutes — no card WhatsApp UsReplies within minutes+1 607 318-2126Mon–Fri, 9 AM–6 PM ET (6 AM–3 PM PT)

Prefer email? Write to sales@hellogrowthcrm.com