How to configure a new CRM
Configuration is where a generic CRM becomes yours - and where it either stays lean and usable or bloats into a mess.
The discipline is to configure to your actual process and keep it minimal, resisting the urge to build every possible field and workflow up front.
Short answer
Configure a new CRM by setting up the data model to match your sales process, defining pipeline stages with exit criteria, adding only the fields you will act on, wiring lead routing and core automations, connecting email and calendar, and setting permissions. Configure to your real process and start lean, adding customization only as genuine needs prove out.
Step by step
Model your process
Set up objects, relationships, and pipeline stages that mirror how you actually sell, with clear stage exit criteria.
Add only fields you will act on
Configure the lean set of fields that drive routing, scoring, or reporting, and enrich the rest rather than requiring it.
Wire routing and automation
Set up lead routing, activity capture, and the core workflows that remove daily busywork.
Set permissions
Configure roles and access on least-privilege lines, so people see and edit what their role needs.
Configure to your process, not the template
A CRM's defaults reflect a generic process, not yours. Configuring to how you actually sell - your stages, your key data, your handoffs - is what makes the system fit. But fit does not mean maximal: start lean and add only as needs prove out, or you trade a generic mess for a custom one.
How Ardovo helps
Ardovo arrives with sensible defaults and alive with data, so configuration is tailoring to your process rather than building from empty. Rook sets up routing, capture, and cleanup, so you configure the parts unique to your business and inherit the rest working.
Frequently asked questions
What do you configure first in a new CRM?
The data model to match your sales process - objects, relationships, and pipeline stages with clear exit criteria. Everything else builds on this, so getting the model aligned to how you actually sell comes before fields, automation, and permissions.
How many fields should a new CRM have?
As few as drive real action. Configure the lean set of fields used for routing, scoring, and reporting, and enrich the rest automatically rather than requiring reps to fill them. Starting with a minimal field set and adding only as needs prove out prevents the bloat that buries the fields that matter.
Should you configure everything before launch?
No - start lean and launch with the essentials that match your process, then add customization as genuine needs emerge. Building every possible field and workflow up front produces a bloated system reps resist. A simple, working CRM you extend deliberately beats an over-configured one at launch.