The CRM implementation checklist, and why most CRMs go unused
The short answer
CRMs go unused because they are slower than the notebook they replaced. Implement with five fields on the create form, automatic capture of source and activity, stages defined by observable buyer actions, and reports the manager runs from the CRM rather than from Excel.
Key takeaways
- Adoption is a design outcome, not a training problem.
- If two salespeople would stage the same deal differently, the stages are wrong.
- Capture source at submission — it cannot be reconstructed later.
- Send the qualification outcome back to the ad platforms or the loop stays open.
The pattern is consistent: the software is configured to the vendor's default process, the sales team finds it slower than their notebook, and within four months the real pipeline lives in somebody's head again.
The implementation checklist
Before go-live
- Process mapped by watching, not by being briefed in a management meeting.
- Five fields on the create form. Past that, people enter rubbish to get through it.
- Source, campaign and creative captured automatically at the moment of submission.
- Stages defined by buyer actions with written entry criteria.
- Deduplication on a normalised phone number — the reliable identity key in India.
- Assignment rules by territory, product or language, applied in seconds not overnight.
- Stall alerts — an expected duration per stage, and a nudge when it is exceeded.
- Loss reasons as a short required list on closing a deal lost.
- Dashboards inside the CRM, so nobody exports to Excel to answer a normal question.
- An adoption review at thirty days — what is filled in, what is avoided, what must change.
Stages: buyer actions, not seller feelings
| Weak stage | Better stage | Why |
|---|---|---|
| Interested | Discovery call completed | Something happened that can be verified |
| Hot lead | Site visit booked | A commitment was made |
| Negotiating | Proposal sent | A dated artefact exists |
| Almost closed | Verbal agreement, contract sent | Specific and checkable |
Zoho, HubSpot or custom
Configure a product
- Your process is recognisable to a sales team anywhere
- You want it running in weeks
- Someone else should own the maintenance
- Budget matters
Build custom
- Pricing tiers, credit terms or approvals a product cannot model
- Multi-party workflows with unusual permissions
- The CRM is genuinely part of the product you sell
- You have engineering capacity to maintain it
Custom is rarer than people think — strong preferences are not the same as a process that cannot be modelled. Stage design is covered in sales pipeline design, and the full engagement on CRM Builds.