Notes for owners · CRM, automation and RevOps
CRM implementation checklist for SMEs
A CRM fails when it is installed before the sales process is written down. This checklist covers process, data, stages, training and the ninety-day review.
The GullySales team · Updated 15 Sept 2026 · 7 min read
On this page
A CRM does not fail because the software was wrong. It fails because it was installed before anybody wrote down how the company actually sells. The stages then mean different things to different people, and the reports cannot be trusted by month three. Do the work in order. Write the process, clean the data, define the stages and fields, and set the routing rules. Then train on real enquiries and review adoption at thirty, sixty and ninety days. The configuration is the easy part.
Before you buy anything
- Write your sales process on one page: the stages an enquiry passes through, from first contact to order
- Define each stage by something the buyer does, not by how the salesperson feels
- List every place an enquiry currently arrives: website form, phone, WhatsApp, IndiaMART, walk-in, referral, exhibition
- Decide the three reports the owner will actually look at every week
- Count your team and decide who needs a licence, including the person who answers the phone
- Check whether your team works on a laptop or a phone, because that decides which CRM is usable
- Agree what a qualified enquiry means, in writing, with the sales and marketing sides both present
- Name one internal owner for the system
The second point is where most implementations go wrong. A stage called Follow-up tells you nothing. A stage called Quotation sent, requirement confirmed tells you exactly where the deal is and what has to happen next.
Getting the data in without poisoning the system
Data decides whether the team believes the CRM. Four steps.
Pull everything into one spreadsheet first: the old Excel file, the exported contacts, the IndiaMART enquiries, the visiting cards in the drawer. Look at it before you import anything.
Deduplicate on phone number, then on email, then on company name. In Indian SME data the phone number is the only reliable key.
Standardise the fields you will report on. City spelled one way. Industry from a fixed list of ten or twelve. Lead source from a fixed list. Free-text fields cannot be reported on, and a dropdown with forty options is a free-text field.
Import only what is alive: current customers, open opportunities, and enquiries from the last twelve months. Everything older goes into an archive sheet. You can always bring a record in later.
Configuring for a small team
| Decision | What works for an SME | What to avoid |
|---|---|---|
| Stages | Five to seven, each defined by a buyer action | Twelve stages copied from a template |
| Mandatory fields | Four or five at creation: name, phone, source, city | Fifteen mandatory fields, so executives enter rubbish |
| Lead sources | A fixed list matching where enquiries actually arrive | A field typed by hand, so nothing can be counted |
| Assignment | An automatic rule by territory, product or round robin | The manager forwarding enquiries on WhatsApp |
| Alerts | A notification on a phone within a minute of a new enquiry | An email digest nobody opens |
| Next step | A mandatory next action with a date on every open deal | Deals sitting with no task, which is how they die quietly |
| Connected so conversations are recorded against the contact | Enquiries living on personal phones | |
| Calls | Logged automatically through your IVR or cloud number | Call notes typed from memory hours later |
| Reports | Three: enquiries by source, pipeline by stage, reply time | A dashboard of eighteen charts |
The theme is subtraction. A CRM with five fields that are always filled is worth more than one with thirty that are half filled.
Training, go-live and the first ninety days
Train on real enquiries, not on demonstration data. Sit the team down with yesterday's actual enquiries and have each person enter and progress their own. An hour of that beats a two-hour presentation.
Go live with a hard rule: from Monday, an enquiry that is not in the CRM does not exist. No quotation is approved for a deal that is not in the system. That single rule does more for adoption than any amount of encouragement.
Then run the weekly sales review from the CRM screen, never from a separately prepared spreadsheet. The moment a manager accepts a parallel spreadsheet, the CRM becomes optional.
Review at three points. At thirty days, check what percentage of enquiries have a next action with a date, and which fields are being skipped. At sixty days, check whether reply time has moved and whether stage definitions are being applied consistently. At ninety days, remove the fields nobody uses and fix the two things the team complains about most.
A worked example
For example, imagine a building materials trading firm in Bengaluru with nine sales people. Enquiries arrive through IndiaMART, a website form, WhatsApp and walk-ins to the Peenya office, with a Tally file for billing. The details and figures below are illustrative.
The process page came first. Five stages: enquiry received, requirement confirmed, quotation sent, negotiation, order. Each defined by an action. Requirement confirmed means quantity, grade and delivery location known.
Data cleaning took nine days and removed roughly a third of the contact list as duplicates or dead. That step felt like waste and turned out to be the reason the team trusted the reports later.
Configuration was deliberately small. Four mandatory fields, a fixed list of six lead sources, and automatic assignment by product category. A phone alert on every new enquiry, and a mandatory next action on every open deal.
Three reports for the owner: enquiries by source each week, pipeline by stage with age, and average first reply time per executive.
For example, the firm handles 250 enquiries a month. If first reply time falls from six hours to thirty minutes, even a small lift in conversion pays for the licences many times over. The figures are illustrative. What is reliable is that reply time moves the moment it becomes visible.
What to do next
Do not shortlist software yet. Write your five stages on one page, with each stage defined by something the buyer does, and show it to your two best sales people. If they disagree about what a stage means, you have found the real work, and it is worth two weeks.
If you want help with the process and the rollout, tell us what you need.
