Your team has a CRM. Maybe you just bought it, maybe you inherited it from the previous sales manager. Either way, it does not quite fit: stages nobody uses, fields nobody fills in, and a pipeline review where everyone opens their own spreadsheet.
The problem is rarely the tool. It is the configuration. A CRM set up around the way your team really sells gets used. One set up by default, or by someone who never sold, gets ignored.
This guide explains what CRM configuration means, then walks you through eight steps to configure your CRM for a sales team, with a fictional example and the mistakes to avoid.
What is CRM configuration?
Configuring a CRM means adjusting its settings so it matches the way your team sells, without writing a single line of code. In practice, you decide:
- The pipeline stages a deal goes through, from first contact to signature.
- The fields your team fills in on contacts, companies and deals.
- Who sees and edits what: users, teams and permissions.
- What connects to the CRM: email inboxes and calendars.
- The views each person opens every morning.
- The simple automations that save clicks, such as a task created when a deal changes stage.
Configuration is often confused with customization. The difference matters, because one is quick to change and the other is not.
- Uses the settings the CRM already offers
- Stages, fields, views, simple automations
- An admin can change it in minutes
- Requires development work
- Custom code, specific connections to other tools
- Slower and costlier to change
For most sales teams, configuration covers almost everything. Start there, and only consider customization when a real need remains after a few months of use.
Before you start: write down how your team sells
Do not open the settings yet. Take an hour with two or three reps and answer three questions on paper:
- What are the steps of a typical deal? Not the ideal process from a training deck: what really happens.
- What does your manager ask in the pipeline review? Those questions tell you which fields matter.
- Who will own the CRM? One person decides on changes. Without an owner, every rep adds their own field and the setup drifts within months.
If your sales process has never been written down, our checklist for a scalable B2B sales process will help you do it before you configure anything.
How to configure your CRM in 8 steps
- Define your pipeline stagesEach stage ends with something the buyer did
- Choose the fields that matterFew required fields, all of them used
- Describe every fieldOne line on what it contains and when to fill it in
- Set up users and permissionsTeams, roles and who can change the settings
- Import and clean your dataRemove duplicates before, not after
- Connect email and calendarSo exchanges and meetings are logged without typing
- Build views for reps and managersOne view for the day, one for the pipeline review
- Add a few simple automationsOnly the ones that save clicks every day
1. Define your pipeline stages
Your stages are the backbone of the CRM. Keep five to seven, and give each one an exit criterion: something the buyer did, not something the rep feels. "Demo done" is a fact. "Interested" is an opinion.
Name stages after the buyer's progress (discovery done, proposal sent, verbal agreement) rather than your internal tasks. That way, when a deal moves, everyone knows what actually happened.
2. Choose the fields that matter
Most CRMs come with dozens of default fields. You need far fewer. Think in three objects:
- ContactsName, job title, email, phone and their part in the decision
- CompaniesIndustry, size, location and who owns the account
- DealsStage, amount, close date, next step and the main contact
Then decide which fields are required. Only make a field required if your forecast or your pipeline review cannot work without it.
Watch out: Every required field you add is one more reason for a rep to type anything just to save the record. Ten required fields often means ten fields filled with "TBD".
3. Describe every field
This is the step most teams skip, and it costs them later. Give each field a one-line description: what it contains, in which unit, and when to fill it in. For example: "The customer's estimated yearly budget, in euros, filled in after the discovery call."
A described field is filled in the same way by everyone. It also helps new reps, your future self, and any tool that reads your CRM, including a sales copilot.
4. Set up users, teams and permissions
Create teams that match your organization (regions, new business and account management, for example), then decide who can do what. Reps edit their own deals. Managers see their team's pipeline. Only the CRM owner changes stages and fields.
5. Import and clean your data
Before importing your old spreadsheets or your previous CRM, clean them: remove duplicates, merge companies written three different ways, delete contacts who left years ago. Importing a mess gives you a messy CRM from day one, and reps lose trust in it immediately.
6. Connect email and calendar
Connect each rep's inbox and calendar so that emails and meetings are logged automatically on the right contact. This is what saves the most typing, and it gives everyone the full history of an account without asking around.
7. Build views for reps and managers
A rep needs one screen for the day: today's tasks, deals with a next step due, deals closing this month. A manager needs one screen for the pipeline review: deals by stage, amounts, close dates, deals with no activity for two weeks. Build those two views first. Everything else can wait.
8. Add a few simple automations
Start with two or three automations that save clicks every day, for example:
- create a follow-up task when a deal moves to "Proposal sent";
- alert the owner when a close date is in the past;
- assign new inbound leads to the right rep.
Resist the temptation to automate everything on day one. Automations nobody understands quickly become automations nobody trusts.
Constellia helps sales managers get a pipeline they can trust: Orion, the sales copilot, reads your CRM to prepare each meeting and suggests the updates after each call. See how it helps sales managers
Example: a CRM configured in one week
Here is a fictional case. A team of six reps sells cleaning equipment to industrial sites. Their sales manager configures the CRM in one week:
- Stages: new lead, discovery done, site visit done, proposal sent, negotiation, won or lost. Each stage has its exit criterion written in the stage description.
- Required deal fields: amount, close date, next step and main contact. Everything else is optional.
- Described fields: "Number of sites", "Current supplier", "Contract end date", each with a one-line description.
- Views: "My week" for reps, "Pipeline review" for the Monday meeting.
- Automations: a reminder task three days after a proposal is sent, and an alert when a close date passes.
Example: In the first pipeline review, the manager no longer asks "where are we on this one?". The stage, the next step and the close date already answer it.
Mistakes to avoid when configuring a CRM
- Copying another company's setup. Their stages describe their sales, not yours.
- Configuring without the reps. They are the ones who fill in the CRM. Ask them before, and listen to them after.
- Too many stages. Beyond seven, nobody agrees on where a deal is.
- Fields without descriptions. Two reps, two meanings, and a report nobody can read.
- Never revisiting the setup. Your sales evolve; your CRM must follow.
Test, adjust, then review every quarter
Once configured, run the CRM for two weeks with the whole team, then hold a short feedback session: which fields are never filled in, which stages confuse people, which view is missing. Fix what comes up, then put a quarterly review in the calendar.
A good configuration is not the one with the most options. It is the one your reps fill in without thinking, because it matches what they do. To keep the data fresh day after day, pair it with a simple habit: updating your CRM after every sales call.
What a sales copilot adds to a well-configured CRM
A clean configuration makes your CRM readable for people. It also makes it readable for a sales copilot.
Orion, the Constellia sales copilot, works from your CRM. Before each meeting, it prepares a brief from the contact, the company and the deal history. After the call, it suggests the updates (stage, amount, close date, next step, new contacts, note) and you approve them: nothing is saved without your approval. You can also ask it about the state of your CRM, for instance which deals have no next step.
For your own custom fields, you choose which ones Orion reads, and it understands each one through its description. Step 3 pays off twice. Our help center explains how to choose and describe your CRM fields for Orion.
FAQ
What is CRM configuration? CRM configuration means adjusting a CRM's settings to match the way your team sells, without writing code: pipeline stages, fields, users and permissions, views, email and calendar connections and simple automations.
What is the difference between CRM configuration and customization? Configuration uses the settings the CRM already offers, and an admin can change them in minutes. Customization means development work, such as custom code or a specific connection to another tool. It is slower and costlier to change.
How long does it take to configure a CRM? For a sales team, the essentials (stages, key fields, users and data import) take a few days to a few weeks, depending mostly on how clean your existing data is. Plan a review after the first month of real use.
How many required fields should a deal have? As few as possible: the ones your forecast and your pipeline review actually use, such as stage, amount, close date and next step. Every extra required field is one more reason to type anything just to save.
Who should configure the CRM? One owner, often a sales manager, a sales operations person or an experienced rep, with input from the reps who use the CRM every day. A setup decided without them rarely survives the first month.
Ready to get more out of your CRM? Constellia is the sales copilot that helps B2B teams prepare their meetings, follow up faster and keep their CRM up to date. Request a demo
