Skip to content
CRM & Automation

CRM implementation for Indian SMBs: a week-by-week plan, who does what, what each route costs and the 30-day review, drawn from Xale and the CRMs we build.

Published
Updated
Reading time
17 minutes

Drafted with AI tools; researched, edited and approved by Althameem Ali. Our editorial policy

On this page · 10 sections
  1. What does CRM implementation involve?
  2. What does the week-by-week plan look like?
  3. Who does what?
  4. What does it cost in India?
  5. Why do rollouts fail?
  6. What goes on the go-live checklist?
  7. What should the 30-day review check?
  8. Frequently asked questions
  9. Plan the rollout before you buy
  10. Changelog

We build custom CRMs: we set teams up on Xale and build what Xale doesn't cover (reported by our team), and our co-founders are two of Xale's three founders. So we aren't neutral between the routes below. Our own starting prices are in the cost table and on our pricing page; every other price here is another seller's public price, dated, or a planning model we state.

This guide is the project plan. It draws on Xale, the CRM built by the team behind Marketlube, which reports 10,000+ new leads captured every month and 150+ user seats in its largest single workspace (Xale's platform figures (opens in a new tab), September 2026), and on CRMs our team has built. Still choosing one? Our Zoho CRM vs custom CRM comparison comes first.

What does CRM implementation involve?#

Five pieces of work, whichever CRM you choose. Each has a technical side that our post on building a scalable CRM covers in depth, so here is one line on each, linked to the detail:

Four routes get you there: a SaaS CRM you set up yourself, one a partner implements, a CRM configured and extended on a platform such as Xale, or a from-scratch build. The plan below fits all four; the costs and timelines differ.

What does the week-by-week plan look like?#

Here is the implementation process as a week-by-week roadmap. For a team of 5 to 30 people moving onto a SaaS CRM with a partner's help, plan on about eight weeks, then 30 days of review. That sits inside the timelines partners publish: Skynetiks, an authorised Zoho partner in Noida, gives two to four weeks for a focused single-pipeline rollout and six to twelve for a multi-team one with migration and integrations (Skynetiks (opens in a new tab), updated 19 August 2026).

WeekWhat happensDone when
0Name the owner and the admin; write down the goal and the one number that will show it workedA one-page brief the team has read
1Map how a lead becomes a sale today: the sources, stages, hand-offs and lost reasonsStages, statuses and lost reasons signed off
2Configure the pipeline, three or four fields at entry, roles, permissions and follow-up rulesOne real user of each role gets through a day's work in a test
3Connect the lead sources: ad forms, website forms, WhatsApp and callsA test lead from every source arrives once, with its campaign
3 to 4Clean and import: phone numbers in one format, duplicates resolved, a pilot batch firstTotals per branch and stage match the old sheet
5Pilot with one team on real leads, with a ten-minute review every dayThe pilot team works only in the CRM
6Train each role on its own day's work, then switch everyone overNew enquiries go into the CRM only, and the old sheet is read-only
7 to 8Fix what the pilot found; move the manager's weekly review into the CRMThe weekly meeting runs from the CRM's reports
The next 30 daysThe usage review described belowA list of fixes, each with an owner and a date

Messy data and slow decisions stretch this more than anything else. For consultancies leaving Excel, xale.in's migration plan puts a single-branch team with tidy data at two to three weeks and says multi-branch teams with years of history take longer, "almost entirely on cleaning" (xale.in (opens in a new tab), updated 15 September 2026); study abroad and admissions teams should follow that plan. If your leads mostly arrive on WhatsApp, our WhatsApp CRM guide's four-week rollout is a shorter version of the same idea.

A from-scratch build adds design and development before Week 2: 8 to 16 weeks to a first version in the published prices below, three to four months in our own planning model. Ask for a working version every fortnight, and pilot it on real leads before the rest is built.

On Xale most of that phase is already done. Roles by stage and branch, automations that retry and log every run, call and WhatsApp capture and reports that open the leads behind every number exist on Xale's platform (opens in a new tab), as xale.in describes it, so the weeks go into Week 1's map, Week 2's configuration and any modules of your own. Our price list gives 6 to 12 weeks to a first working version, and 10 to 16 with a WhatsApp inbox.

Who does what?#

Give every part of the work a name, because a vendor can finish the set-up but can't own what comes after it:

RoleOwnsWhen
Owner (the founder or sales head)The goal and the one number, decisions on stages and access, the weekly reviewWeek 0 and Week 1, then every week
Admin (someone in-house, not the vendor)Users, roles, fields, imports, fixing assignments after go-liveThrough the project, then a little every week
Sales or branch leadsTesting with real leads, the daily stuck-leads review, championing it in their teamThe pilot, the switch-over and the first month
Vendor or partnerConfiguration, integrations, the data import, training material, support in the first weeksAs the contract says, in writing
Every userLogging calls, outcomes and the next follow-up in the CRM, not on WhatsAppFrom the day of the switch-over

Two outside views say the same. Skynetiks writes that "every implementation that survived had one person inside the business who cared whether reps updated records". xale.in's migration plan gives each step a named owner, from the operations lead to the branch heads, and suggests "one champion per branch for the first two weeks".

What does it cost in India?#

These are published prices from sellers in India, read on 8 October 2026. Licence prices are before GST; ask whether a partner's fee includes it. The first two rows use Zoho, whose partners in India publish their implementation prices; the third is our own route, at our starting prices; the fourth is what other builders publish:

RouteOne-time costEvery monthTime to go live
A SaaS CRM you set up yourselfNo fee: your admin's timeLicences: Zoho CRM ₹800 to ₹2,600 a user, billed yearly3 to 6 months to a CRM the team consistently uses, in one Zoho partner's estimate
A partner implements a SaaS CRMAbout ₹15,000 for a small set-up to ₹5 lakh; ₹10 lakh or more for complex rolloutsLicences, plus a support retainer of ₹10,000 to ₹50,0001 to 4 weeks for a simple or focused set-up; 4 to 14 weeks with migration and integrations
A CRM on Xale, configured and extended by usPaid as one fee: from ₹2 lakh for a focused lead CRM, from ₹5 lakh with a WhatsApp inbox, before GSTOr taken as a subscription instead: one of Xale's own plans, priced per workspace, not per user, as Xale's pricing page (opens in a new tab) lists them, with no figure printed here. Enterprise custom deployment and enterprise pricing are available on request6 to 12 weeks to a first working version; 10 to 16 with a WhatsApp inbox (our price list)
A from-scratch CRM build, from another builder₹3 lakh to ₹8 lakh for a basic CRM; ₹8 lakh to ₹16 lakh with WhatsApp, automation and a mobile appHosting, maintenance and changes: ₹3 lakh to ₹5 lakh a year8 to 16 weeks for a first version

Where the numbers come from, in alphabetical order:

  • Aaxonix, a Zoho partner: do-it-yourself "typically takes 3 to 6 months to reach a functional, consistently-used CRM"; a boutique partner charges ₹75,000 to ₹3.5 lakh over 4 to 10 weeks (Aaxonix (opens in a new tab), updated July 2026).
  • CloudHouse Technologies: ₹3 lakh to ₹8 lakh for a basic custom CRM built in 8 to 12 weeks, then ₹3 lakh to ₹5 lakh a year for hosting, maintenance and enhancements (CloudHouse (opens in a new tab), 4 October 2026).
  • Codingclave: ₹3 lakh to ₹7 lakh for a basic custom CRM in 8 to 10 weeks; ₹8 lakh to ₹16 lakh in 12 to 16 weeks with WhatsApp, automation and a mobile app (Codingclave (opens in a new tab), 9 June 2026).
  • Codroid Labs, a Zoho partner: ₹15,000 to ₹50,000 for a small business, live in one to two weeks; up to ₹10 lakh or more for enterprise rollouts of 8 to 14 weeks (Codroid (opens in a new tab), 15 July 2026).
  • HubSpot: Sales Hub Professional, $90 a seat a month billed yearly, requires a one-time onboarding fee of $1,500, about ₹1.45 lakh at ₹96.62 to the dollar, the FBIL reference rate for 7 October 2026 shown on the Reserve Bank of India's website (opens in a new tab) (HubSpot (opens in a new tab)).
  • Skynetiks, a Zoho partner: "typically between ₹45,000 and ₹5,00,000", depending on users, automation and integrations (updated 19 August 2026).
  • Tech Magify, which implements Zoho: ₹40,000 for a lean five-user rollout to ₹3 lakh or more; support retainers ₹10,000 to ₹50,000 a month (Tech Magify (opens in a new tab), 15 September 2026).
  • Zoho: licences from ₹800 a user a month (Standard) to ₹2,600 (Ultimate), local taxes extra (Zoho (opens in a new tab)).

A worked example: for five users on Zoho's Standard edition with a simple pipeline, Tech Magify's published first-year budget is ₹88,000 to ₹1.18 lakh, made up of ₹48,000 of licences and ₹40,000 to ₹70,000 of implementation. For a from-scratch build, our custom software cost guide models a CRM at 4 to 8 person-months, ₹4 lakh to ₹16 lakh at a lean Kerala team's rate, in line with the published prices.

Three routes. A SaaS CRM such as Zoho or HubSpot, set up by you or by a partner, suits a standard pipeline and a small team, and often costs them less: the five-user example above comes to ₹88,000 to ₹1.18 lakh in its first year. A CRM on Xale suits a process with stages of its own, many users, or heavy WhatsApp and portal work. We configure and extend a platform that already exists, so Week 2 starts with the pipeline, roles and reports in place; you pay one fee, or take it as a subscription on one of Xale's own plans, which are priced per workspace, with every feature included and no per-user licence, and our price list gives 6 to 12 weeks to a first working version. A from-scratch CRM is what other builders sell. We don't, because the pipeline, roles, automations and reports it would write first are already on the platform.

Three costs hide in every route: cleaning the old data, connecting the lead sources and training. Per-user licences also grow with every hire, where a one fee stays put and a per-workspace plan doesn't add a charge for each seat inside the plan. And WhatsApp messages carry Meta's charges whichever CRM sends them; our WhatsApp CRM guide explains the rates.

Why do rollouts fail?#

The biggest CRM implementation challenges are people and data, not software. xale.in's migration plan puts it plainly: "Migrations rarely fail because of the software; they fail because of the data and habits you carry across." The patterns to watch for:

  1. Nobody inside owns it. The vendor finishes, the admin goes back to the day job, and nobody reads the dashboard.
  2. The old sheet stays open. Two places to update means neither is right.
  3. Too many fields on day one. Ask for three or four at entry and collect the rest later.
  4. Leads still live in staff phones. If chats and calls don't reach the CRM, it sees only part of the work.
  5. Managers still ask on WhatsApp. When the weekly review runs from the CRM, the team keeps it current.
  6. Follow-up stays optional. In our experience running ads across industries, most leads that go cold were never properly followed up (our account, not a measured statistic; see lead problem or follow-up problem?). A CRM must put the next follow-up in front of someone.

A rollout can also go well. Our team built a CRM for Skymark Education, a study abroad consultancy (reported by our team). Building it for a large consultancy gave us the research, the product thinking and the automation know-how that later helped us build a bigger product, Xale. Skymark moved onto Xale in March 2026, as xale.in's story of the move (opens in a new tab) tells it.

What goes on the go-live checklist?#

Run through this before the switch-over, with the owner in the room:

CheckWhy it matters
Stages, statuses and lost reasons signed offReports mean the same thing to everyone
A test lead from every source arrives once, with its campaign and sourceThe admissions page we built for DiYES International sends every enquiry to the school's CRM tagged with its grade and the campaign it came from; check yours does the same
Phone numbers stored in one international format, and the duplicate rule testedOne person, one record, even when they enquire twice
Each role tested by a real userNobody sees too much or too little
Open follow-ups imported with owners and due dates; stale ones left behindxale.in warns that stale dates leave counsellors facing "hundreds of overdue tasks"
Totals per branch and stage reconciled with the old sheetProof that nothing was lost
Old sheet read-only, and the switch-over date announcedOne source of truth from day one
Exports restricted, and a consent notice on every formIndia's DPDP Rules require a clear consent notice (the government's backgrounder (opens in a new tab)); our DPDP checklist covers the rest

What should the 30-day review check?#

Usage, not features. Thirty days after go-live, the owner, the admin and the sales leads read these signals together:

SignalHealthyRed flag
New enquiries enteredNearly all, the same dayEntered days late, or in bulk
Overdue follow-upsFalling week on weekCleared in bulk without notes
Leads idle for seven days or moreA short list with reasonsWhole portfolios untouched
Leads with a sourceEvery one"Unknown" growing
Calls and chats on the leadLogged by most of the teamLogged by a few people only
The weekly reviewRun from the CRM's reportsRun from WhatsApp updates

The first three rows are the adoption signals in xale.in's migration plan; the last three are ours. Fix what the review finds in order: the data first, then the follow-up rules, then the reports. Trust in the numbers matters most: in the ERP our team built for ReelsBuddy, our video brand, the leads CRM has a needs-attention queue and tooltips that explain how each figure is counted, and it held 5,408 leads when we read its dashboards on 28 September 2026 (ReelsBuddy case study). Repeat the review at 90 days.

Frequently asked questions#

How long does CRM implementation take?#

For a small team on a SaaS CRM, published timelines from firms that implement Zoho run from one or two weeks for a simple set-up to four to fourteen weeks with migration and integrations; a from-scratch CRM's first version takes 8 to 16 weeks. On Xale, our price list gives 6 to 12 weeks to a first working CRM, and 10 to 16 with a WhatsApp inbox. Add 30 days of usage review after go-live.

What does CRM implementation cost in India?#

Three parts: the licences (Zoho CRM lists ₹800 to ₹2,600 a user a month, billed yearly, before GST), the implementation (published Zoho partner fees run from about ₹15,000 for a small set-up to ₹5 lakh, and more for complex rollouts) and support afterwards (published retainers of ₹10,000 to ₹50,000 a month). A from-scratch build swaps the licences for a one-time cost, ₹3 lakh to ₹16 lakh in published ranges, plus hosting and upkeep. All read on 8 October 2026.

Why do CRM implementations fail?#

Mostly on data and habits rather than software: nobody inside owns the rollout, the old spreadsheet stays in use, too many fields are required, leads stay in staff phones and managers keep asking for updates on WhatsApp. A usage review 30 days after go-live catches most of these early.

Plan the rollout before you buy#

Write down your stages, your lead sources and who will own the CRM before you choose one; that page shapes the timeline and the cost more than the software does. Study abroad and admissions teams should start on xale.in: its migration plan, linked above, is written for them, and Xale is sold to them directly, with an Education template (opens in a new tab) for schools and institutes. For any other business, talk through your CRM or ERP rollout with Althameem Ali, our co-founder, in a one-hour consultation, after which you get a written action plan within 24 hours, or read how the platform works and what we build on it.

Changelog#

  • 2026-10-12: Our own route is now in the cost table: a CRM configured and extended on Xale, paid as one fee (from ₹2 lakh, or from ₹5 lakh with a WhatsApp inbox) or as a subscription on one of Xale's own plans, which are priced per workspace, with enterprise custom deployment and enterprise pricing on request. The route this post called a custom build is named as what it is, a from-scratch build that other builders sell. Skymark's CRM history reads as our team reports it: we built Skymark a CRM, what we learned building it later helped us build Xale, and Skymark moved onto Xale in March 2026, as xale.in's story of the move tells it. Xale's figures now read as xale.in publishes them today (its fact sheet, read 12 October 2026): 10,000+ new leads captured every month and 150+ user seats in its largest single workspace (Platform figures, September 2026). The older user and lead totals are gone, because xale.in no longer publishes them. The description no longer carries a lead total. The disclosure links our CRM page as custom CRMs again, and still says we set teams up on Xale. Our row's time to go live is now the figure on our price list, 6 to 12 weeks to a first working version and 10 to 16 with a WhatsApp inbox, where it said only "Weeks"; the plan section and the timing answer give the same figure, and the three-routes paragraph is in this guide's own words, around its five-user example. On 13 October the per-user subscription figure this update first carried was withdrawn, and the line on hidden costs no longer counts a per-user price of ours: the subscription is now described as Xale's own per-workspace plans, as Xale's pricing page lists them, with no figure printed. Skymark's history took the wording above the same day.

Related services

Written by

Co-founder, Marketlube

Althameem Ali researched, edited and approved this post. Marketlube is a growth partner in Calicut building brands, websites, CRMs and campaigns for businesses across Kerala, India and the Gulf.

Start a project

Want this working for your brand?

Tell us what you're growing and where. A strategist replies within one working day, and after a short call your written plan (the channels, the budget and the first 90 days) follows within 48 hours.

Every rupee you spend with us has to earn its keep.