How to set up a CRM that actually gets used

Adoption fails on field count, not features.

Every field you add is a small tax on every deal, paid by the person least motivated to pay it. Teams abandon CRMs because someone specified twenty-two required fields in month one. Start with five, get consistent use, and add a field only when a real decision depends on it.

Make it the easiest place to look, not a reporting duty.

A CRM that only serves management gets fed reluctantly and inaccurately. One that tells a rep what happened last time, what was promised and what is due gets opened first thing. Build for the person entering the data and the reporting follows for free.

Define the stages as observable events.

"Qualified" is an opinion; "had a scoping call" is a fact. Stages that describe something that visibly happened get applied consistently. Stages describing confidence drift within a week and make the forecast meaningless.

Clean at the point of entry.

Deduplication after the fact is permanent, expensive work. Matching on entry, required formats, and one owner for creating accounts cost a day to set up and save a quarterly clean-up forever after.

The five fields, set up to be quick to fill

The five that earn their place on a deal are stage, expected close date, value, next step and owner. Contact details sit on the contact record and are matched on entry, so they do not count against the deal. How each field is configured matters as much as which fields you pick, because every extra click is paid on every deal.

Stage: a dropdown of the events listed below, never a typed-in label
Expected close date: a date picker left blank by default, so nobody accepts a made-up date by pressing save
Value: a single rupee figure, not a range and not a text box
Next step: a short line plus a due date, which feeds the rep’s list for the day
Owner: defaults to whoever creates the deal, with every change of owner logged

A stage template built on events

Here is a starting list for a typical business-to-business sale. Rename the stages in your own language, but keep each one tied to something anyone could verify from an email, a calendar entry or a document. Then write, next to each stage, who is allowed to move a deal into it; that single line gives every forecast discussion a rule to point to.

Enquiry received: a form, call, message or referral is logged
Scoping call held: the meeting happened and the notes are attached
Proposal sent: a dated document went to a named contact
Accepted: the buyer has confirmed in writing
Won: purchase order, signed agreement or advance received
Lost: closed with a reason chosen from a short fixed list

Setting it up, step by step

The order matters more than the software. Start by configuring the tool and you design around its defaults; start on paper and you design around your own process. These steps keep the decisions ahead of the configuration, and each one is cheap to change until the next is done.

Write the stage list and field rules on a single page before opening any software
Set the matching rules for phone numbers, emails and company names, and name the one person who creates new accounts
Import only live deals and active customers; archive the rest where it can still be searched
Connect the places leads already arrive, such as the website form, email and WhatsApp, so nobody retypes them
Build the rep’s home screen first: today’s next steps, overdue follow-ups and recent activity
Pilot with a small group of reps, fix what annoys them, then roll out
Retire the old spreadsheet on a named date, announced in advance

Templates to get the team on board

Adoption is a communication job as much as a configuration one. These short templates cover the moments where a rollout can lose people: the announcement, the first meetings and the questions nobody likes to ask in front of colleagues. Keep each one to a page, and put them where the team already looks.

Rollout note: why the change, what the rep gets from it, the date the spreadsheet stops and who to ask
Field rules card: the five fields, the format for each and one example of a correct entry
Stage sheet: the list above, with the evidence each stage needs and who may move a deal
Weekly pipeline agenda: overdue next steps, deals that changed stage, deals with no next step, then the forecast, all run from the CRM screen
Feedback prompt: which field took longest this week, and which one you skipped

Common mistakes, and what to do instead

Each of these looks harmless on the day it is decided. Together they can turn a CRM into a place where data goes to be ignored. Each line below names the mistake first and then what to do in its place, whatever tool you are using.

Importing every row of the old spreadsheet: bring across what is live and archive the rest
Adding a probability field: reps guess and managers adjust, so let the stage carry the forecast instead
Building dashboards before anyone enters data: get consistent entry first, because reports follow it, not the other way round
Running the pipeline meeting from an export: run it from the CRM screen, so the meeting uses the same record the team is asked to keep
Letting managers edit reps’ records quietly: comment instead, so the owner stays the owner
Leaving mobile until later: test the phone view in the pilot, because for reps on the road it is the CRM

Off-the-shelf, custom or built for your sector

If your pipeline lives in spreadsheets and the process is standard, a configured off-the-shelf CRM is enough to start; our Sales CRM Starter begins at ₹18,000. If leads, quotes, invoices and pipelines need to sit in one system shaped around how you work, Custom CRM Setup starts at ₹95,000. Moving platforms without carrying duplicates across is CRM Migration & Cleanup, from ₹9,000.

Some sectors have their own shape: site visits, unit inventory and channel partners in property; appointments, recalls and consent in clinics. Real Estate CRM and Patient CRM & Recalls each start at ₹45,000. The CRM packages page lists what each one includes.